name: final-shape-review description: Re-examine a nearly merge-ready implementation after review comments are addressed to ask whether the final data shapes, contracts, types, transitions, interfaces, ownership boundaries, and abstractions can be materially simplified before merge. Use when the code works and feedback is resolved, but the implementation may still carry discovery scars from trial and error and you want a bounded late-stage zoom-out pass that pushes the merged shape toward obvious, boring, future-maintainable code.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "name": "field_notes_validated_array", | |
| "schema": { | |
| "type": "object", | |
| "properties": { | |
| "items": { | |
| "type": "array", | |
| "items": { | |
| "type": "object", | |
| "properties": { |
| filepath | AGENTS.md |
|---|
- Before making changes, read
.instructions/general.instructions.mdand any relevant instructions inside.instructions/appsor.instructions/packagesfor the files you plan to modify. - Keep TypeScript strictly typed. Do not use
@ts-ignoreor ESLint disable comments. - Always run
pnpm typecheckto ensure your code is working. This also builds any needed deps. So do this anytime you cross a package boundary. - Use
pnpm lintto check for linting errors and code style. - Use
pnpm format -wto format all packages before committing.