matheuspoleza

Implement a milestone autonomously inside a Conductor worktree without stop-and-ask checkpoints, strictly enforcing scope-first and logging anything out of scope. Use when running parallel Conductor lanes, asked to "build autonomously", "run this in the…

Implement a milestone's tasks one at a time using BDD then TDD, with live progress tracked in three places and a Review Contract filled per task. Use when ready to implement, given a milestone path, or asked to "build the next milestone" or "start…

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism,…

Build a product field guide for an unfamiliar app — one markdown file per feature with pages, flows, screenshots, and the gotchas only a human knows. Use when starting on a new project, joining an existing codebase, or asked to "map the product", "understand…

Build a single progressive PRD doc that captures problem, product requirements, tech design, and milestones — grilling the user via /grill-me at each section to reach shared understanding. Use when starting a feature, scoping a non-trivial change, or asked to…

Validate a completed milestone in two phases — agentic QA (run tests, hit endpoints, screenshot visuals) then human-eyes pass (manual test guide, feedback collection) — and end with a PR-ready description. Use after a milestone is built, or asked to "review",…

Build and refine a personal writing-style profile that /humanizer auto-loads, by sampling real writing (Slack, Linear), interviewing the user, and calibrating with example rewrites. Use when setting up voice matching, when /humanizer output still needs the…

Interview the user one question at a time about a plan, decision, or design until a shared understanding emerges. Use when planning, designing, scoping, picking among options, or asked to "grill me", "interview me", "drill into this", or "pressure-test the…

After implementing or changing anything that affects the rendered UI, use the chrome-devtools MCP to navigate to the affected routes, take screenshots, and verify the result yourself — do not ask the user to "open the browser and check". Use whenever a code…

Write BDD-style acceptance criteria using Given/When/Then scenarios for features, tests, and design docs. Use when writing tests, defining requirements for a new feature, planning a non-trivial change, or asked to "add acceptance criteria".

Run a product + UX discovery process for a new product, feature, or major change. Produces four linked artifacts — PRD, Design & UX Plan, Technical Discovery, Tech Plan — through a strict sequence of product thinking → UX thinking → tech thinking. Use when…

React code standards and architectural patterns for writing clean, maintainable React components. Use when creating new React components, pages, modals, or hooks, or when refactoring existing React code.

Strict Test-Driven Development workflow (Red → Green → Refactor) for writing reliable code one behavior at a time. Use when adding new features, fixing bugs with a reproducible failure, or asked to "write tests first" / "do TDD" / "test-drive this".

The conventions apps/docs holds itself to — what is generated and never edited, the house voice, the shape of each page type, frontmatter, links and the diagnosis vocabulary. Use when writing or reviewing anything under apps/docs.

The conventions apps/web holds itself to — feature colocation, the file suffixes, arrow components with named props, hooks over inline queries, and no explanatory comments. Use when writing or reviewing anything under apps/web/src.

Add or extend a bounded context in apps/api — layering, tagged-union modelling, closure-based dependencies, module wiring and the architecture test. Use when adding an endpoint, use case, port or adapter to the API.

The conventions apps/api holds itself to — no explanatory comments, no classes, errors as values, the closed verb set, one unit per file and the suffix that names a file's role. Use when writing or reviewing anything under apps/api/src.