matheuspoleza/pr-diagram

visual-check

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…

Quellsprache: Englisch

bdd-acceptance-criteria

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".

Quellsprache: Englisch

discovery

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…

Quellsprache: Englisch

react-standards

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.

Quellsprache: Englisch

tdd-discipline

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".

Quellsprache: Englisch