agentleFS
paulo-yamagishipaulo-yamagishi/claude-code-setup/.claude/skills/add-project-guide/SKILL.md

add-project-guide

Skill2 starsChanged 9 months agoMITView on GitHub

Create a new projects/ language-stack guide with templates

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create a new projects/{stack}/ directory with guide and templates for the language/stack specified in $ARGUMENTS.

    line 14
  2. Very specific:

    Study existing project guide: Read the contents of one existing project directory (prefer projects/python/ or projects/typescript/) to …

    line 20
  3. Distinctive:

    Follow the same structure as the reference guide

    line 26
  4. Distinctive:

    Add cross-references to relevant core guides

    line 29
  5. Very specific:

    Use <!-- CUSTOMIZE --> markers for project-specific values

    line 33
  6. Distinctive:

    Follow the structure from the reference template

    line 35
  7. Distinctive:

    All JSON must be valid — no comments, no trailing commas

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

Add Project Guide

Create a new projects/{stack}/ directory with guide and templates for the language/stack specified in $ARGUMENTS.

Steps

  1. Validate: Confirm projects/$ARGUMENTS/ does not already exist. If it does, report and stop.
  2. Study existing project guide: Read the contents of one existing project directory (prefer projects/python/ or projects/typescript/) to extract the pattern:
    • guide.md — stack-specific tooling, conventions, common commands, tips
    • CLAUDE.md.template — project instructions template with <!-- CUSTOMIZE --> markers
    • settings.json.template — settings with stack-appropriate permissions and hooks
  3. Generate projects/$ARGUMENTS/guide.md:
    • Follow the same structure as the reference guide
    • Include stack-specific: package manager, test runner, linter, formatter, build tool
    • Include common commands and conventions for the stack
    • Add cross-references to relevant core guides
    • Keep under 300 lines
  4. Generate projects/$ARGUMENTS/CLAUDE.md.template:
    • Use <!-- CUSTOMIZE --> markers for project-specific values
    • Include stack-appropriate sections: commands, code style, testing conventions
    • Follow the structure from the reference template
  5. Generate projects/$ARGUMENTS/settings.json.template:
    • Include stack-appropriate permission patterns (test, lint, format, build commands)
    • Include appropriate hooks (format-on-save using the stack's formatter)
    • All JSON must be valid — no comments, no trailing commas
  6. Verify: Re-read all generated files and confirm valid JSON, correct structure, under 300 lines each.

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.