promptify
CLAUDE.md0 starsChanged 36 days agoMITView on GitHub
This repo is a Claude Code skill: SKILL.md at the root is the product; everything else supports it. (When installed as a plugin this file is not loaded — it is only for contributors.)
In this repositoryOne other file it gives its agents.
- promptifySkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Keep SKILL.md short; it is the only file that stays in context when the skill runs.
- Very specific: line 9
Before finishing any change: bash scripts/validate.sh.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
promptify — notes for agents working in this repo
This repo is a Claude Code skill: SKILL.md at the root is the product; everything else supports it. (When installed as a plugin this file is not loaded — it is only for contributors.)
- Keep
SKILL.mdshort; it is the only file that stays in context when the skill runs. Detail goes inreferences/, prompt shapes intemplates/. - The skill's own rules apply to edits here: positive instructions with reasons, no all-caps emphasis, no "be thorough / double-check / show your reasoning".
scripts/snapshot.shis injected into the prompt before the skill runs and must exit 0 everywhere (a failing injected command aborts the skill).- Bump the version in three places together:
SKILL.mdfrontmattermetadata.version,.claude-plugin/plugin.json,.claude-plugin/marketplace.json. - Before finishing any change:
bash scripts/validate.sh.
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.

