noahdgrant
@noahdgrant
Public Skills
ns-principle-sequence-verifiable-units
by noahdgrant
"Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer."
ns-review
by noahdgrant
REVIEW phase. Runs a local, multi-provider review of a unit's diff before push, writes review.md with Critical/Important/Suggestion findings, and loops fixes until no Critical stays open. Use after verify, before shipping, or when asked to review a branch or diff.
ns-principle-fix-root-causes
by noahdgrant
"Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes."
ns-principle-make-operations-idempotent
by noahdgrant
"Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs."
ns-principle-redesign-from-first-principles
by noahdgrant
"Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on."
ns-principle-encode-lessons-in-structure
by noahdgrant
"Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text."
ns-principle-attack-the-premise
by noahdgrant
"Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it."
ns-principle-foundational-thinking
by noahdgrant
"Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious."
ns-principle-experience-first
by noahdgrant
"Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones."
ns-principles
by noahdgrant
Index of the ns-principle-* skills, with one line per principle saying when it applies. Read it when choosing which engineering principles bear on a task.
ns-tdd
by noahdgrant
Test-driven development with red-green-refactor. Use when building a feature or fixing a bug test-first, or when writing integration tests.
ns-principle-build-the-lever
by noahdgrant
"Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a brief your delegates follow) instead of working by hand. The tool is the artifact a reviewer can rerun."
ns-principle-separate-before-serializing-shared-state
by noahdgrant
"Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant."
ns-principle-migrate-callers-then-delete-legacy-apis
by noahdgrant
"Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers."
ns-principle-outcome-oriented-execution
by noahdgrant
"Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code."
ns-setup-verify
by noahdgrant
Generate a project's verification skill (verify-<project>) and the control CLI it drives, then prove both end to end. Use when a repo has no scripted way to drive its real surface (CLI, service, board, emulator), when docs/agents/verify.md is missing or points nowhere, or when ns-verify asks for it.
ns-swarm
by noahdgrant
Fan out parallel fresh-context workers, drain them, and return one PASS/ISSUES/BLOCKED report. Use when work splits into independent slices, when racing several attempts at one brief, or when another skill asks for a fan-out.
ns-principle-exhaust-the-design-space
by noahdgrant
"Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing."
ns-principle-model-the-domain
by noahdgrant
"Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals."