What problem does it solve? Teams repeatedly re-type the same working directives each session, and agents lose consistent standards for reasoning traces, verification gates, commits, and GUI quality. This Skill encodes a standing house style so every session on the think-and-ship + ministr + serpapi MCP triad follows the same doctrine automatically. ## Core Features & Use Cases - Tri-MCP interleave doctrine: Cycles think (frame reasoning), ministr (ground in real code), serpapi (validate against 2026 norms), and ship (track execution) at every decision point, with cross-referenced traces. - Always-on engineering rules: Enforces staged tool loading, atomic one-chunk-per-pass changes, commit-on-main discipline, real-gate verification without masking exit codes, and honest reporting of failures. - GUI tier (self-gating): For projects with a UI, applies object-first OOUX/ORCA modeling, Storybook-by-object organization, design-token composition, and empirical Playwright scrutiny with UX-expert critique. - Use Case: At the start of a working session on a triad project, invoke /craft to load the doctrine so the agent frames decisions with think steps, grounds changes in the actual code, verifies with the project's real test gate, and commits atomically on main. ## Quick Start Invoke /craft at the start of a working session to load the house operating doctrine for the project.
