principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design.

Get it through your agent npx skills add backnotprop/pstack@principle-redesign-from-first-principles

Skill instructions

Rendered from the published SKILL.md, 11 lines.

When integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been a foundational assumption from the start.

Read all affected files and understand the current design
Ask: "if we were writing this from scratch with this new requirement, what would we build?"
Propagate the change through every reference: types, docs, examples, rationale sections
Think about the whole redesign, then deliver it incrementally

This is the method for preserving option value when integrating changes into an existing design.

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "principle-redesign-from-first-principles"
  }
}

From backnotprop/pstack via skills.sh

principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
4,175 installs
principle-subtract-before-you-add
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
4,148 installs
design-principles
Define actionable principles that resolve trade-offs when the team disagrees. Use when the same decisions keep getting relitigated. For a single project's framing, use `design-brief`.
2,129 installs
principle-subtract-before-you-add
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
4,752 installs
principle-build-the-lever
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 skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
4,733 installs

unslop
Cut AI tells from any writing.
6,197 installs
how
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
5,333 installs
principle-fix-root-causes
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
5,270 installs
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
5,249 installs
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
5,168 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.