Menu
Self-review a change before declaring it finished. Use after implementing any feature or fix, before committing or reporting completion.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Clean code and structure standards for this repo. Use when writing or refactoring any TypeScript/React code — covers naming, file layout, typing, and testing discipline.
Understand the true intent behind a request before writing any code. Use at the start of every non-trivial task, especially vague ones ("make it better", "add a page", "fix the layout").
Next.js 16 App Router best practices for this repo. Use when creating routes, layouts, data fetching, metadata, or anything touching the Next.js framework surface.
Security rules for all code in this repo. Use when handling any external input, env vars, auth, API routes, server actions, or dependencies.
UI/UX design standards for this stack (Tailwind v4 + shadcn/ui). Use whenever creating or modifying any page, component, layout, or style — the goal is professional, consistent UI with zero AI slop.
| name | evaluate |
| description | Self-review a change before declaring it finished. Use after implementing any feature or fix, before committing or reporting completion. |
Never declare work finished on the strength of "it compiles." Evaluate every change against this checklist and report honestly what was and wasn't verified.
npm run lint
npm run type-check
npm run test
npm run format:check
All four must pass. These are the same checks the pre-commit hook enforces — running them yourself avoids a blocked commit.
Read the full diff as if reviewing a stranger's PR:
console.log, commented-out code, TODO, unused import, or dead file?src/components/ or src/lib/?Tests passing is not the same as the feature working:
npm run dev and load the route.src/__tests__/ (or co-located *.test.tsx) that
fails without your change.State what you verified and how. If something is untested or uncertain, say so explicitly — never imply verification that didn't happen.