principle-redesign-from-first-principles
Skill1 starsChanged 11 days agoMITView on GitHub
Apply when integrating a new requirement into an existing design.
46 other projects use a version of this, 44 of them edited.
Adopted by
Most recently taken up by
- paramcodes/skillsedited, first seen Nov 8, 2026
- tristanphvn/keeledited, first seen Nov 8, 2026
- requie/endostacktheir own version, first seen Nov 8, 2026
- creedants/pstack-t3edited, first seen Nov 3, 2026
- painhardcore/pstackedited, first seen Nov 2, 2026
- silacode/agent-skillsedited, first seen Nov 1, 2026
Used with
Projects with it also use principle-explain-the-number, setup-pstack and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ianclearySkillprinciple-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
Also in 29 projects that use this
bnemaSkillsetup-pstack
Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.
Also in 25 projects that use this
ianclearySkillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 14 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 19 projects that use this
tristanphvnSkillketchup-video
Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.
Also in 11 projects that use this
drafaelSkillin-your-own-words
Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.
Also in 20 projects that use this
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 44
- backnotprop/pstack★ 3.8k100% same
- jtaroreh/agystack★ 12864% same
- uzairansaruzi/p3-stack★ 12685% same
- dsebban/skills★ 71100% same
- creedants/pstack-t3★ 1896% same
- painhardcore/pstack★ 1896% same
- Scino/fstack★ 1862% same
- mariusflorescu/pstack-t3★ 13100% same
- adjohn/pstack★ 9100% same
- kkgogogo17/pi-pstack★ 964% same
34 more not listed
Wrote their own version · 2
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- requie/endostack★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- codebase-designSkill
- code-reviewSkill
- senior-software-developerSkill
- explainerSkill
- PR-code-reviewSkill
- Product ManagerSkill
- retroSkill
- sherlock-holmesSkill
- testerSkill
- unit-test-unslopSkill
- unslopSkill
The file
We split this skill into the rules it gives an agent
3 rules. 3 are common, 0 are distinctive, and 0 are very specific to this project.
3
Common
Most of the 46 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 9
When integrating a change, don't bolt it onto the existing design.
- Common: line 11
Read all affected files and understand the current design
- Common: line 12
Ask: "if we were writing this from scratch with this new requirement, what would we build?"
“Common” is measured: kept by at least 6 in 10 of the 46 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Redesign From First Principles
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

