agentleFS
tahabozdemirtahabozdemir/promptify/CLAUDE.md

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.

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
  1. Very specific:

    Keep SKILL.md short; it is the only file that stays in context when the skill runs.

    line 5
  2. Very specific:

    Before finishing any change: bash scripts/validate.sh.

    line 9

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

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.md short; it is the only file that stays in context when the skill runs. Detail goes in references/, prompt shapes in templates/.
  • 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.sh is 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.md frontmatter metadata.version, .claude-plugin/plugin.json, .claude-plugin/marketplace.json.
  • Before finishing any change: bash scripts/validate.sh.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.