nikitakurpas/standards
Engineering principles as skills. /with-standards applies them to the current task.
Finds what a change could break beyond its diff, and proves the one fact that makes it safe by running real code.
Restates the user's goals and the problem they're solving, so you can check the agent understood.
Minimize project documentation without losing truth. Use when writing or reviewing repository docs, or when asked to prevent documentation sprawl. Not for general prose.
Concentrates validation and error handling at system boundaries, trusts internal types, and keeps business logic pure.
Builds the script, codemod, or generator that does or proves the work, so a reviewer can rerun it.
Turns a repeated instruction or correction into a lint, metadata flag, runtime check, or script.
Builds 2-3 competing prototypes for a decision with no precedent and compares them before committing.
Chooses user delight over implementation convenience, and fewer polished features over more rough ones.
Traces each symptom to the first place the system went wrong and fixes it there.
Settles core types, data structures, and shared state before writing logic.
Keeps the main context lean by routing bulk reading to subagents and keeping only their summaries.
Prefers deletion and the smallest change that solves the problem over new abstractions or layers.
Designs commands, lifecycle steps, and loops to reach the same end state after crashes, restarts, and retries.
Moves every caller to a new internal API and deletes the old one in the same wave.
Cuts the layers and hidden state a reader must trace, collapsing one-caller wrappers and shrinking mutable scope.
Encodes domain rules in one structure, such as a state machine, typed model, or table, instead of scattered conditionals.
Proceeds on reversible work instead of asking permission, then presents the result for correction.
Drives rewrites and migrations straight to the target architecture, without throwaway compatibility code.
Verifies finished work against the real artifact, not a proxy, a self-report, or a passing build.
Integrates a new requirement by redesigning as if it had been there from the start.
Splits multi-step work into small units that each end in a check, and orders commits and PRs so the sequence proves itself.
Removes dead code and redundant pieces before adding, refactoring, or rewriting.
Writes tests that assert observable behavior, so they fail when behavior breaks and survive internal changes.
Designs types that make illegal states unrepresentable, brand primitives, and parse external data at boundaries.
Writing standard for docs, readmes, RFCs, PR descriptions, and commit messages, built on Diátaxis, Google developer style, STE, and Global English.
TypeScript rules for modeling types, narrowing safely, validating at boundaries, and testing real code.
Removes AI writing patterns such as filler, hedging, stock vocabulary, and jargon.
Applies the Standards principles to the current task and names the ones that shaped each decision. Use when writing, refactoring, or reviewing code or docs, or designing a change.