← all publishers

nmnmcc

@nmnmcc source repo

Report this profile Claim this profile

• 19 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Jsdocs · nmnmcc

   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.
   0
   installs
2. ▌
   Preview · nmnmcc bundle

   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 or real route, add *.preview.* coverage, capture responsive or state variants, generate or inspect visual artifacts locally or in CI, or fix discovery, capture lifecycle, browser, build-removal, and artifact problems. Use for UI work that can run on Node 24 or later, Vite 8, and Playwright 1.61.
   0
   installs
3. ▌
   Dx · nmnmcc bundle

   Use when developers need a clearer path to understand, change, verify, or operate software.
   0
   installs
4. ▌
   UX · nmnmcc bundle

   Use when product behavior, interface, or content must improve for the people using it.
   0
   installs
5. ▌
   Docs · nmnmcc bundle

   Use when documentation or comments must explain current behavior to a specific reader.
   0
   installs
6. ▌
   Line · nmnmcc bundle

   Use when one technical rule must stay coherent across related modules.
   0
   installs
7. ▌
   Self · nmnmcc bundle

   Use when responsibility, authority, or handoff is unclear between people, agents, or systems.
   0
   installs
8. ▌
   Plane · nmnmcc bundle

   Use when one result crosses technical domains and needs integrated scope and proof.
   0
   installs
9. ▌
   Point · nmnmcc bundle

   Use for one local cause-and-effect change with a focused proof.
   0
   installs
10. ▌
    Study · nmnmcc bundle

    Use when an unfamiliar, costly, or high-risk task needs evidence before a decision or change.
    0
    installs
11. ▌
    Effect · nmnmcc bundle

    Use when effects, dependencies, failures, resources, concurrency, or execution boundaries need explicit modeling.
    0
    installs
12. ▌
    Cluster · nmnmcc bundle

    Use for work with two or more independently owned workstreams that need coordinated integration.
    0
    installs
13. ▌
    Pattern · nmnmcc bundle

    Use when a project-specific coding pattern must be found, taught, applied, or maintained.
    0
    installs
14. ▌
    Testing · nmnmcc bundle

    Use when deciding what evidence can expose a credible software fault.
    0
    installs
15. ▌
    Typesafe · nmnmcc bundle

    Use when data, runtime values, types, contracts, and allowed operations must stay aligned.
    0
    installs
16. ▌
    Just Do It · nmnmcc bundle

    Use to keep an accepted task moving through implementation, verification, and handoff.
    0
    installs
17. ▌
    Simplicity · nmnmcc bundle

    Use when choosing the smallest complete design that meets the real need.
    0
    installs
18. ▌
    Nobody Cares How · nmnmcc bundle

    Use when user-facing behavior exposes implementation detail, jargon, or technical showmanship.
    0
    installs
19. ▌
    Progress · nmnmcc bundle

    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 Codex needs to adopt Progress; shape, validate, query, or visualize a complete outcome graph; author or change fenced Progress Items; choose, implement, or coordinate ready work, including explicitly requested one-Item-per-subagent parallel work; complete or reopen Items truthfully; consume CLI exports; or diagnose protocol and graph failures. Do not use for generic status reports, progress indicators, or task tracking that is not backed by Progress Protocol 1.
    0
    installs