Principle Redesign From First Principles Skill for Claude
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.
208 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
255
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/michael-denyer/pstack-claude --skill principle-redesign-from-first-principlesThe instruction itself
1 sections, as written by the authorRedesign From First Principles
When integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there 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.
How to use it
Copy the folder
Take michael-denyer/principle-redesign-from-first-principles from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.