promote-to-core
Skill1 starsChanged 3 days agoMITView on GitHub
Move a reusable component, hook or style from a deck in presentation/ or showcase/ into the reusable foundation in core/. Use when the user asks to promote or generalize deck work.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- abhayla/claude-best-practicestheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- abhayla/claude-best-practices★ 9same 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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- core/AGENTS.mdAGENTS.md
- presentation/AGENTS.mdAGENTS.md
- showcase/AGENTS.mdAGENTS.md
- build-slideSkill
- build-templateSkill
- openprezSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- opp-applySkill
- opp-archiveSkill
- opp-exploreSkill
- opp-proposeSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 4 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If it only makes sense for the source deck's story, leave it in that deck and tell the user why.
- Distinctive: line 19
Remove all topic text, deck-specific data and deck assets.
- Distinctive: line 21
Use the theme tokens, not hard-coded colors.
- Very specific: line 22
If the piece is interactive and assumes unscaled screen pixels, apply the counter-zoom pattern: read the display scale from …
- Very specific: line 26
Put it in core/components/, or a fitting core/ folder.
- Very specific: line 28
Update the donating deck to import it from @core, and delete its implementation copy.
- Very specific: line 32
Add any new public export to both the "Public @core API" table in the root AGENTS.md and docs/core-api.md.
- Very specific: line 33
Add focused behavior tests under tests/core/.
- Very specific: line 38
Follow the foundation release-versioning rules in core/AGENTS.md: determine and apply the required semantic version increment, then propose …
- Very specific: line 39
Follow the core dependency and validation routine in core/AGENTS.md, including pnpm update --latest for this actual foundation development, …
- Very specific: line 40
Check in pnpm dev that the donating deck still looks and behaves the same.
- Distinctive: line 41
Keep foundation and deck changes separable so the user can carry back or commit them independently.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Promote deck work to the foundation
Turn something built for one deck into a generic foundation feature. The result must contain no deck content, and both decks must keep working.
1. Confirm it's reusable
- Name the piece and the general problem it solves, independent of this deck's topic.
- If it only makes sense for the source deck's story, leave it in that deck and tell the user why.
2. Make it generic
- Remove all topic text, deck-specific data and deck assets. Pass them in as props instead.
- Make the variations configurable through props with sensible defaults: content, colors, steps, sizes.
- Use the theme tokens, not hard-coded colors.
- If the piece is interactive and assumes unscaled screen pixels, apply the counter-zoom pattern: read the display scale from
StageScaleContext(or measure it against the stage dimensions, as the showcase'sInteractiveSlidedoes) and divide screen pixels back into stage pixels.
3. Move it into core/
- Put it in
core/components/, or a fittingcore/folder. - Export it, with its props type, from
core/index.ts. - Update the donating deck to import it from
@core, and delete its implementation copy. Keep this deck integration separate from the foundation extraction so the user can carry and commit the two workstreams independently.
4. Document it
- Add any new public export to both the "Public
@coreAPI" table in the rootAGENTS.mdanddocs/core-api.md. - Add focused behavior tests under
tests/core/; keep tests for the donor deck with that deck. - If the source is the user deck in
presentation/and the promotion also changes its content or design intent, handle that content change through a separate/opp-*workflow. Do not editopenprez/specs/presentation.mddirectly as part of a foundation extraction; a purely implementation-level extraction needs no canonical content change. For ashowcase/source, followshowcase/AGENTS.md.
5. Version, verify and report
- Follow the foundation release-versioning rules in
core/AGENTS.md: determine and apply the required semantic version increment, then propose the matching tag for the user. Never create the tag or commit. - Follow the core dependency and validation routine in
core/AGENTS.md, includingpnpm update --latestfor this actual foundation development, then run scoped tests; ensure the showcase and starter deck still exercise the public API. - Check in
pnpm devthat the donating deck still looks and behaves the same. - Keep foundation and deck changes separable so the user can carry back or commit them independently. Never commit unless explicitly asked.
- Tell the user that the foundation changed, so it can be carried back to the bare foundation.
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.

