shode666/shode-house

Protect compatibility when changing a shared or public interface, such as a REST, GraphQL, gRPC, event or SDK contract with consumers outside the deploy unit, through breaking-change classification, versioning, deprecation and contract tests. Not for private function signatures or internal database schema.

Entry point for engaging the Shode House software team on consultation, design, implementation, review or resuming an engagement. Asking to explain or review does not authorize edits.

Set up a project's test automation strategy and infrastructure, meaning the mix of unit, integration and end-to-end tests, CI gates and thresholds. Not for the tests of a single change, one changed screen, or spikes and one-off scripts.

Switch to an ultra-compressed reply style that drops filler but keeps technical terms, code, numbers and security warnings verbatim, only when the user explicitly asks for terse output. It is never the default and ends when the user asks for normal prose.

Plan and carry out a schema or data migration, such as DDL, backfill, dual write or expand-contract rollout, with rehearsed rollback and extra care for money and regulated data. Not for ordinary SQL queries, disposable local databases or a manual one-row production fix.

Split an agreed, signed-off scope into small, independently verifiable outcome slices with owners, acceptance criteria and explicit dependencies. Not for work whose finished shape is still unclear, tasks already small, or a backlog already verified and ready.

Apply test-first development and quality gates during implementation or refactor of production code, ending with validation evidence before handoff. Not for spikes, generated code, pure configuration changes, or investigating a problem whose cause is still unknown.

Debug an error, crash, failing test, wrong output, regression or slowdown (พัง, ไม่ทำงาน, ช้า, ทำไมถึง, bug) by reproducing and isolating the root cause before fixing. For live production impact, use incident.

Shared contract for domain expert personas, requiring an AI persona disclaimer and primary-source citations for any claim about a regulation, standard or protocol, and explicit marking when a source cannot be verified. It governs domain claims, not general project evidence or which expert is needed.

Batch-drain ready tickets with isolated workers, independent review, serial merge and evidenced closure (จัดงานที่พร้อม, ปิดงานค้าง). For work not split into concrete, independent tickets, use decompose.

Respond to active production impact such as an outage, degradation, data loss or breach by assigning severity and mitigating first, then a blameless postmortem. Not for bugs not currently hurting production users, nor planned maintenance.

Coordinate independent review of an implemented change by code, runtime, spec, security and domain with severity and merge gates, not self-approval.

Threat model and review a design or change that crosses a meaningful security boundary, such as authentication, authorization, secrets, cryptography, personal or payment data, untrusted input or public exposure. Not for a live incident or unrelated local refactors.

Output and completion contract for anyone producing a deliverable - durable artifact, re-checkable evidence for every claim, no placeholders, no completion claim without real tool output. Not how work is routed or reviewed.

Decide who owns a request, covering type of work, responsible role, conflict resolution, parallel versus sequential execution, and whether a domain specialist is needed because the work requires a domain rule decision rather than merely using domain vocabulary. Phase order and approvals are not decided here.

Coordinate multi-phase delivery with phase gates, recorded approvals, run recovery and drift detection, governing how work proceeds, not who owns it.

Define reliability targets for a production service, covering service level indicators and objectives, error budget policy and burn-rate alerting. Not for responding to a live outage, nor for internal tools or one-off batch jobs.

Automated browser-level end-to-end, visual regression and accessibility testing of a changed, rendered user interface, plus the UI quality rules every frontend change follows. Not for backend-only changes, unrendered designs, or site performance audits.

Audit and improve a public-facing website across Core Web Vitals, performance budgets, SEO, structured data and security headers against agreed measured thresholds. Not for internal or API-only services, nor for functional or accessibility testing of one changed screen.