principle-migrate-callers-then-delete-legacy-apis
Skill2 starsChanged 8 months agoMITView on GitHub
Apply when replacing an internal API without leaving ambiguous dual paths.
We split this skill into the rules it gives an agent
5 rules. 5 are common, 0 are distinctive, and 0 are very specific to this project.
5
Common
Most of the 43 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 18
When we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving …
- Common: line 21
Do not keep legacy API paths only because internal callers still exist
- Common: line 23
Treat temporary adapters as exceptional and time-boxed, not default architecture
- Common: line 24
Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details
- Common: line 27
No external users depend on backward compatibility
“Common” is measured: kept by at least 6 in 10 of the 43 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
Migrate Callers Then Delete Legacy APIs
When we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving compatibility layers.
Rule:
- Do not keep legacy API paths only because internal callers still exist
- Inventory callers, migrate them, and delete the old API immediately
- Treat temporary adapters as exceptional and time-boxed, not default architecture
- Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details
When this applies:
- No external users depend on backward compatibility
- The project can absorb coordinated breaking changes
- The new API is part of a simplification or refactor initiative
Keeping both old and new APIs creates dual-path complexity, slows cleanup, and makes the codebase feel append-only.
Other versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 42
- backnotprop/pstack★ 3.3k62% same
- jtaroreh/agystack★ 12879% same
- uzairansaruzi/p3-stack★ 12682% same
- dsebban/skills★ 7162% same
- Scino/fstack★ 1878% same
- creedants/pstack-t3★ 1765% same
- mariusflorescu/pstack-t3★ 1362% same
- adjohn/pstack★ 962% same
- kkgogogo17/pi-pstack★ 979% same
- 0xrsydn/pstack-pi★ 679% same
32 more not listed
Wrote their own version · 1
- TheOnlyFusionCube/potetos-for-everyone★ 18same 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.
Used alongsideProjects with it also use principle-explain-the-number, poteto-mode 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.
juancamiloqhzSkillprinciple-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 18 projects that use this
jtarorehSkillpoteto-mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
Also in 5 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 22 projects that use this
Xia-AtaraxiaSkillmake-bot-ui
Builds a small web page whose buttons wake an agent over a webhook: a local server keeps the sender key server-side and POSTs JSON to a webhook-triggered routine, and the page is exposed on the existing Tailscale node. Use for \"make a bot UI\", \"a dashboard with buttons that trigger the agent\", \"wake the bot from a page\", handing a webhook sender key to the server without pasting it in chat, or putting that UI on the tailnet. Not for general frontend work - use principle-frontend; not for tailnet health or reachability - use tailscale.
Also in 15 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 8 projects that use this
Xia-AtaraxiaSkillbenchmark-checklist
Vets performance measurements for the limiter, tuning, physical limits, errors, repeatability, relevance, and proof that timed work happened. It applies to 'check this benchmark', 'report this speedup', measured regressions, and choosing a library or configuration from numbers. It reports spread and gaps before drawing a conclusion. Not for general testing policy or choosing test oracles - use principle-testing.
Also in 16 projects that use this
In this repository93 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/code-simplifier.mdcCursor rule
- .cursor/rules/tdd-verification.mdcCursor rule
- ckm:banner-designSkill
- ckm:brandSkill
- ckm:designSkill
- ckm:design-systemSkill
- ckm:slidesSkill
- ckm:ui-stylingSkill
- ui-ux-pro-maxSkill
- mission-control-agent-integrationSkill
- agent-watchdogSkill
- architectSkill
- arenaSkill
- automate-meSkill
- babysitSkill
- before-and-afterSkill
- blast-radiusSkill
- broSkill
- code-structureSkill
- create-verification-skillSkill
- deslopSkill
- evidence-driven-testingSkill
- factory-babysit-prSkill
- factory-collectSkill
- factory-human-digestSkill
- factory-lookbackSkill
- factory-recoverSkill
- factory-review-prsSkill
- factory-shipSkill
- factorySkill
- factory-watchdogSkill
- figure-it-outSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- get-pr-commentsSkill
- greploop-appsSkill
- greploopSkill
- howSkill
- interrogateSkill
- maintain-verification-skillSkill
- make-pr-easy-to-reviewSkill
- mission-control-budget-controlSkill
- mission-control-deliverySkill
- mission-control-heartbeatSkill
- mission-control-record-memorySkill
- mission-control-register-agentSkill
- mission-control-request-approvalSkill
- mission-control-run-loggingSkill
- mission-control-submit-deliverableSkill
- mission-control-task-lifecycleSkill
- new-featureSkill
- no-commentsSkill
- plan-arbiterSkill
- poteto-modeSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-encode-lessons-in-structureSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

