nmnmcc

Coordinate a complete subagent work cluster when the user explicitly invokes $cluster, or when complex work has at least two independently reviewable workstreams or separate technical-domain owners. The root agent uses plane, domain agents use line, and local…

Write, review, and maintain software documentation and code comments that stay in step with the code and contracts they explain and help a specific reader understand, use, change, or operate the real system. Use when implementation changes behavior readers…

Improve developer experience when understanding, designing, writing, changing, reviewing, testing, debugging, building, documenting, releasing, or maintaining software. Use when Codex must read or explain a project from overall purpose and structure to local…

Just do it — and enjoy it! Use in every scenario and at every stage; recommended as the default for every task. Spot what matters, take the next useful step with a light heart, care for real risks, and leave a clean result that feels good to receive.

Resolve one branch passed from Plane by making all needed parts of one technical domain follow one clear rule. Use line when a domain branch, shared design, interface, migration, or review spans several related parts and separate local fixes may become…

Shape one visible result across two or more technical domains, from an intentionally incomplete sketch through implementation and release. Use plane when meaning, control, or guarantees must cross UI, API, services, data, infrastructure, observability, or…

Make one small software change by finding its cause and getting clear proof. Use point when the wanted change, the part that causes it, the limits, and the best useful check are local. Examples include one bug fix, small feature, configuration change, focused…

Improve any product or service from the user's point of view. Follow every touch before, during, and after use; check the result, words, visual form, sound, touch, motion, waiting, response, physical setting, people, trust, and later effects; and remove parts…

Just do it — and enjoy it! Use in every scenario and at every stage; recommended as the default for every task. Spot what matters, take the next useful step with a light heart, care for real risks, and leave a clean result that feels good to receive.

Use effect-aware thinking whenever designing, writing, changing, reviewing, or debugging code. Make observable work, dependencies, failures, state changes, resource lifetimes, concurrency, cancellation, and execution boundaries explicit. Follow the project's…

Write, review, and maintain software documentation and code comments that stay in step with the code and contracts they explain and help a specific reader understand, use, change, or operate the real system. Use when implementation changes behavior readers…

Improve developer experience when understanding, designing, writing, changing, reviewing, testing, debugging, building, documenting, releasing, or maintaining software. Use when Codex must read or explain a project from overall purpose and structure to local…

Make all needed parts of one technical domain follow one clear rule. Use when one rule, shared design, interface, migration, or review covers several parts of frontend, backend, data, infrastructure, testing, security, or another single domain, and separate…

Make one visible result work from end to end across two or more technical domains. Use when meaning and guarantees must pass through boundaries such as UI, API, services, data, infrastructure, or observability, so no single domain can prove the full result.…

Make one small software change by finding its cause and getting clear proof. Use when the wanted change, the part that causes it, the limits, and the best useful check are local. Examples include one bug fix, small feature, configuration change, focused…

Improve any product or service from the user's point of view. Follow every touch before, during, and after use; check the result, words, visual form, sound, touch, motion, waiting, response, physical setting, people, trust, and later effects; and remove parts…

Define, run, inspect, and repair repeatable UI previews with @nmnmcc/preview and the target project's real Vite setup. Use when an agent works on plain Vite, React, Vue, Svelte, React Router, SvelteKit, or vinext and needs to understand or verify a component…

Write good software tests after proving every rule that can be proved. Use when you design, change, fix, review, or release software; choose test cases, boundaries, levels, doubles, fixtures, assertions, or checks; decide which tests to run; or fix a test…

Just do it — and enjoy it! Use in every scenario and at every stage; recommended as the default for every task. Spot what matters, take the next useful step with a light heart, care for real risks, and celebrate a job well done.

Keep software work simple and fit for its real need. Use when designing, writing, testing, fixing, reviewing, changing, explaining, or running software. Use it most when code has too many parts, layers, rules, or steps; when it is hard to understand or…

Use TypeSafe thinking whenever writing or changing TypeScript. Show all needed values, states, rules, and failures; give every stronger type a proof; allow only safe operations; and keep the type guarantee safe from its source to its final use. Use for…

Write, insert, or update Effect public API JSDoc so it satisfies the jsdocs oxlint rule. Use when adding or fixing JSDoc comments, resolving jsdocs diagnostics, preparing docs for JSON extraction, or reviewing public API documentation.

Use Progress Protocol 1 and the installed progress CLI to guide an Agent or human in moving source-adjacent software outcomes steadily from discovery and planning through design, implementation, verification, review, release, operation, and feedback. Use when…