coji831

Use when gathering files, running searches, and producing a structured context manifest for other agents. Read-only — never writes code or makes design decisions.

Use when solution design, architecture-fit analysis, task decomposition, or high-ambiguity tradeoff analysis needs stronger reasoning before coding starts.

Use when executing a feature end to end through plan, implement, test, docs, review, ledger updates, and bounded recursive repair.

Use when implementing code changes in a repository where domain-specific specialists are not installed. Generic — no stack assumptions. Stack context loaded from the project's .instructions.md at runtime.

Use when reviewing changes for regressions, correctness, security, and missing coverage. Generic — no stack assumptions. Stack context loaded from the project's .instructions.md at runtime.

Use when adding or repairing tests — unit, integration, or component. Generic — no stack assumptions. Stack context loaded from the project's .instructions.md at runtime.

Use when implementing backend Express, Prisma, service, repository, route, controller, middleware, or backend contract changes in the repository's backend area.

Use when syncing rollout docs, BR docs, implementation docs, review checklists, and knowledge base notes after code or process changes.

Use when: designing a new page or feature UI, deciding where to place a component, or choosing between creating new vs reusing existing components.

Run this skill when auditing frontend code. Covers CSS tokens, shared component reuse, API client rules, barrel files, store placement, accessibility, responsiveness, memoization, timer edge cases, console leftovers, and wireframe alignment.

Extract a lesson from recent agent struggles and create a .instructions.md file to prevent recurrence. Use when: agent made a mistake, discovered a new convention, found a recurring issue pattern.

Run this skill when auditing backend code. Covers error message format, architecture boundaries, input validation, DI compliance, Prisma safety, test coverage, API contracts, and security.

Run Prisma schema changes safely after editing schema.prisma. Use when: editing schema.prisma, adding new models, changing columns, database migration.