بنقرة واحدة
do-work
// End-to-end implementation workflow. Use when user wants to implement a feature, fix a bug, or make changes and have everything validated and committed.
// End-to-end implementation workflow. Use when user wants to implement a feature, fix a bug, or make changes and have everything validated and committed.
Optimize slow React Router loaders by eliminating redundant DB queries, creating slim query variants, and parallelizing independent fetches. Use proactively when writing or reviewing loader code that calls DBFunctionsService, or when triaging a slow page load.
Survey the codebase, pick ONE high-leverage deepening opportunity (filtering out anything already proposed), and publish it as a PRD-shaped GitHub issue via /to-prd-project. Designed to run unattended in the daily architecture-review workflow.
Break a PRD into native GitHub sub-issues attached to the parent PRD. Project-local variant of /to-issues, adapted for this repo's PRD-as-parent + native sub-issues + agent:implement multi-session workflow. Argument is the parent PRD issue number.
Turn the current conversation context into a PRD and publish it as a GitHub issue that is ready to receive sub-issues from /to-issues-project. Project-local variant of /to-prd, adapted for this repo's PRD-as-parent-issue + sub-issues + agent:implement workflow.
Generate or update documentation for the AI Hero API by reading the source code at ~/repos/ai/course-builder. Use when user wants to document, update docs for, or understand the AI Hero API endpoints.
Install @effect/* packages safely. Use whenever adding a new Effect ecosystem dependency.
| name | do-work |
| description | End-to-end implementation workflow. Use when user wants to implement a feature, fix a bug, or make changes and have everything validated and committed. |
Complete implementation workflow from exploration to commit.
If you're touching code that interacts with the database, follow the DB TDD workflow.
If you're touching frontend code with complex state (creating/modifying reducers, complex state transitions, non-trivial state management), follow the Frontend TDD workflow.
Run each check, fix issues, and re-run until clean. Do these sequentially:
npm run typechecknpm testIf a check fails, fix the issue and re-run that check before moving to the next one. Do not move on with failing checks.