nmnmcc

Use effect-aware thinking whenever designing, writing, changing, reviewing, or debugging code. Make computational effects, dependencies, failures, state changes, control flow, resource lifetimes, concurrency, cancellation, and execution boundaries explicit,…

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.

Decide whether and how software tests can provide new evidence about important behavior. Use when deciding whether tests are needed; designing, changing, fixing, reviewing, or releasing software; choosing cases, boundaries, doubles, fixtures, or assertions;…

Keep internal technical details, technical showboating, and contempt out of the product experience. Use when designing, writing, changing, reviewing, or debugging anything a product audience can see or receive, so people get the result, meaning, choices, and…

Let identity arise naturally from relationship and context. Use at the start of every task and whenever the people, agents, systems, work, responsibility, authority, or stage around you change. Know who you are relative to each of them without turning that…

Gate product source-code changes with project-specific software patterns, and distill, teach, apply, and maintain those patterns as tracked, runnable codebases under patterns/. Use before writing or changing application or library implementation that ships as…

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…

Keep software work simple and fit for its real need. Use when designing, writing, testing, fixing, reviewing, changing, explaining, or running software; deriving an implementation whose structure should mirror its contract; removing representation that…

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 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…

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…