agentleFS
Sign inStart free
Skryx-L-ASkryx-L-A/project-kit/CLAUDE.md

project-kit

CLAUDE.md2 starsChanged 3 months agoMITView on GitHub

Public Claude Code plugin (github.com/Skryx-L-A/project-kit): the new-project bootstrapper + 26 type sub-skills + build-business. On this Mac the LIVE install path is the plugin (marketplace, auto-installed via settings.json) — never run install.sh here (Linux-era symlink installer; plugin supersedes it).

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Distinctive:

    After changes: bump VERSION + CHANGELOG.md, commit as Skryx-L-A (English, no co-author trailer).

    line 11
  2. Very specific:

    Keep committed skills GENERIC — personal project examples belong ONLY in local/GROUNDING.md (gitignored).

    line 13
  3. Very specific:

    Test changes by triggering the skill (e.g.

    line 18

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

project-kit — Claude instructions

Public Claude Code plugin (github.com/Skryx-L-A/project-kit): the new-project bootstrapper + 26 type sub-skills + build-business. On this Mac the LIVE install path is the plugin (marketplace, auto-installed via settings.json) — never run install.sh here (Linux-era symlink installer; plugin supersedes it).

Working in this repo

  • This repo is the source of truth for skill content; the plugin cache (~/.claude/plugins/cache/project-kit/...) is a copy — edit HERE, never the cache.
  • After changes: bump VERSION + CHANGELOG.md, commit as Skryx-L-A (English, no co-author trailer). A push updates what the marketplace serves.
  • Keep committed skills GENERIC — personal project examples belong ONLY in local/GROUNDING.md (gitignored). Never leak project names, hosts, or paths from there into committed files.
  • Skills must stay self-contained (templates/policies/scaffold inside the skill folder) and cross-platform (no Linux-isms: no readlink -f, no /home paths).
  • Test changes by triggering the skill (e.g. new-project on a throwaway) before committing — done-bar is "triggers + scaffolds correctly", not "reads well".

Knowledge base

Vault branch: ~/Knowledge/20-projects/project-kit/. Search before bigger changes; distill session results there after.

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.

Check your setup, free