nmnmcc
- 28 skills
- 0 followers
- 3 repo stars
- last month last updated
- ▌ UX 2 · nmnmcc bundleImprove 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.
- ▌ Line 2 · nmnmcc bundleMake 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.
- ▌ Plane 2 · nmnmcc bundleMake 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.
- ▌ Point 2 · nmnmcc bundleMake 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.
- ▌ Study 2 · nmnmcc bundleStudy 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.
- ▌ Testing 2 · nmnmcc bundleWrite 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.
- ▌ Typesafe 2 · nmnmcc bundleUse 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.
- ▌ Just Do It 2 · nmnmcc bundleJust 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.
- ▌ Simplicity 2 · nmnmcc bundleKeep 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.
- ▌ Jsdocs · nmnmccWrite, 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.
- ▌ Preview · nmnmcc bundleDefine, 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.
- ▌ Dx · nmnmcc bundleUse when developers need a clearer path to understand, change, verify, or operate software.
- ▌ UX · nmnmcc bundleUse when product behavior, interface, or content must improve for the people using it.
- ▌ Docs · nmnmcc bundleUse when documentation or comments must explain current behavior to a specific reader.
- ▌
- ▌ Self · nmnmcc bundleUse when responsibility, authority, or handoff is unclear between people, agents, or systems.
- ▌ Plane · nmnmcc bundleUse when one result crosses technical domains and needs integrated scope and proof.
- ▌
- ▌ Study · nmnmcc bundleUse when an unfamiliar, costly, or high-risk task needs evidence before a decision or change.
- ▌ Effect · nmnmcc bundleUse when effects, dependencies, failures, resources, concurrency, or execution boundaries need explicit modeling.
- ▌ Cluster · nmnmcc bundleUse for work with two or more independently owned workstreams that need coordinated integration.
- ▌ Pattern · nmnmcc bundleUse when a project-specific coding pattern must be found, taught, applied, or maintained.
- ▌
- ▌ Typesafe · nmnmcc bundleUse when data, runtime values, types, contracts, and allowed operations must stay aligned.
- ▌ Just Do It · nmnmcc bundleUse to keep an accepted task moving through implementation, verification, and handoff.
- ▌
- ▌ Nobody Cares How · nmnmcc bundleUse when user-facing behavior exposes implementation detail, jargon, or technical showmanship.
- ▌ Progress · nmnmcc bundleUse 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.