all publishers

nmnmcc

@nmnmcc source repo

28 published skills

  1. ▌
    UX 2 · nmnmcc bundle
    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 that do not help. Use when making, changing, reviewing, or fixing any user-facing product, feature, flow, screen, API, message, animation, loading state, notification, help, payment, support path, or way to leave, and when checking ease, access, emotion, safety, privacy, speed, or reliability.
    3 repo stars
  2. ▌
    Line 2 · nmnmcc bundle
    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 local fixes may become different. Use it with point for small cause-and-effect work. Use it with plane when the rule is part of a result that crosses technical domains.
    3 repo stars
  3. ▌
    Plane 2 · nmnmcc bundle
    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. Set the rules at each boundary, the safe order for old and new versions, integration, migration, and end-to-end proof. Use it with point for local causes and line for shared rules inside each domain.
    3 repo stars
  4. ▌
    Point 2 · nmnmcc bundle
    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 refactor, or failing test. Use it with line when one shared rule must hold across a technical domain. Use it with plane when the change is part of a result that crosses technical domains.
    3 repo stars
  5. ▌
    Study 2 · nmnmcc bundle
    Study deeply before anything. Use at the start of every task and again whenever the work reaches an important unknown, before answering, planning, judging, designing, coding, changing, deciding, or acting. Learn the real object, purpose, context, constraints, history, evidence, alternatives, and failure modes deeply enough for the stakes. Inspect primary material and actual behavior instead of relying on memory, first impressions, or fluent guesses. Keep study brief for clear, low-risk, reversible work; broaden and deepen it for unfamiliar, complex, contested, costly, or irreversible work. Continue learning from action and feedback.
    3 repo stars
  6. ▌
    Testing 2 · nmnmcc bundle
    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 suite that is weak, flaky, slow, hard to change, or gives a false picture. Put rules first in the design, types, exhaustive checks, schemas, constraints, static analysis, or direct proof. Then test the important risk left where proof ends.
    3 repo stars
  7. ▌
    Typesafe 2 · nmnmcc bundle
    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 implementation, refactoring, API and data-flow design, integration, migration, review, debugging, compiler settings, declarations, and generated types.
    3 repo stars
  8. ▌
    Just Do It 2 · nmnmcc bundle
    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.
    3 repo stars
  9. ▌
    Simplicity 2 · nmnmcc bundle
    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 change; or when you must decide how much structure and protection from failure the work needs.
    3 repo stars
  10. ▌
    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.
    3 repo stars
  11. ▌
    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.
    3 repo stars
  12. ▌
    Dx · nmnmcc bundle
    Use when developers need a clearer path to understand, change, verify, or operate software.
    3 repo stars
  13. ▌
    UX · nmnmcc bundle
    Use when product behavior, interface, or content must improve for the people using it.
    3 repo stars
  14. ▌
    Docs · nmnmcc bundle
    Use when documentation or comments must explain current behavior to a specific reader.
    3 repo stars
  15. ▌
    Line · nmnmcc bundle
    Use when one technical rule must stay coherent across related modules.
    3 repo stars
  16. ▌
    Self · nmnmcc bundle
    Use when responsibility, authority, or handoff is unclear between people, agents, or systems.
    3 repo stars
  17. ▌
    Plane · nmnmcc bundle
    Use when one result crosses technical domains and needs integrated scope and proof.
    3 repo stars
  18. ▌
    Point · nmnmcc bundle
    Use for one local cause-and-effect change with a focused proof.
    3 repo stars
  19. ▌
    Study · nmnmcc bundle
    Use when an unfamiliar, costly, or high-risk task needs evidence before a decision or change.
    3 repo stars
  20. ▌
    Effect · nmnmcc bundle
    Use when effects, dependencies, failures, resources, concurrency, or execution boundaries need explicit modeling.
    3 repo stars
  21. ▌
    Cluster · nmnmcc bundle
    Use for work with two or more independently owned workstreams that need coordinated integration.
    3 repo stars
  22. ▌
    Pattern · nmnmcc bundle
    Use when a project-specific coding pattern must be found, taught, applied, or maintained.
    3 repo stars
  23. ▌
    Testing · nmnmcc bundle
    Use when deciding what evidence can expose a credible software fault.
    3 repo stars
  24. ▌
    Typesafe · nmnmcc bundle
    Use when data, runtime values, types, contracts, and allowed operations must stay aligned.
    3 repo stars
  25. ▌
    Just Do It · nmnmcc bundle
    Use to keep an accepted task moving through implementation, verification, and handoff.
    3 repo stars
  26. ▌
    Simplicity · nmnmcc bundle
    Use when choosing the smallest complete design that meets the real need.
    3 repo stars
  27. ▌
    Nobody Cares How · nmnmcc bundle
    Use when user-facing behavior exposes implementation detail, jargon, or technical showmanship.
    3 repo stars
  28. ▌
    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.
    3 repo stars