agentleFS
Sign inStart free
Mingo07-devMingo07-dev/claude_skills/project-startup/SKILL.md

project-startup

Skill2 starsChanged 7 months agoApache-2.0View on GitHub

Analyze a project and generate .agent files for onboarding. Use to map the codebase, summarize docs, and bootstrap .agent/main.md, .agent/planning.md, and plans.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 9 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use template: assets/main-template.md

    line 21
  2. Distinctive:

    Read README, docs, and key config files

    line 26
  3. Distinctive:

    Add one-line descriptions for key items

    line 31
  4. Distinctive:

    Create the .agent folder

    line 33
  5. Very specific:

    Create .agent/ and .agent/plans/

    line 34
  6. Very specific:

    Create empty .agent/planning.md

    line 35
  7. Very specific:

    Write .agent/main.md (minimal but complete) Include:

    line 37
  8. Distinctive:

    Add these rules (concise):

    line 45
  9. Distinctive:

    Do not create a plan for small, simple fixes.

    line 46
  10. Distinctive:

    Ask questions when critical details are missing.

    line 48
  11. Very specific:

    Update .agent/main.md if you change its knowledge base and notify the user.

    line 49
  12. Distinctive:

    If a git repo exists, record current commit hash and date and keep it updated.

    line 50
  13. Very specific:

    If asked to verify freshness, compare current state to the commit recorded in .agent/main.md.

    line 51
  14. Distinctive:

    Create a plan file only when needed for multi-step work.

    line 58
  15. Very specific:

    Update .agent/main.md as knowledge changes

    line 66

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

Project analysis and .agent bootstrap

When to use

  • Quick onboarding for a new project
  • Mapping the codebase and key docs
  • Setting up .agent rules and plans

Expected output

  • .agent/main.md with concise, useful context
  • .agent/planning.md (empty)
  • .agent/plans/ for multi-step plans only
  • .agent/claude.md, .agent/codex.md, .agent/copilot.md with a minimal rule
  • Use template: assets/main-template.md

Procedure

  1. Gather context
    • Read README, docs, and key config files
    • Identify entrypoints, core modules, scripts, and critical flows
  2. Map the codebase
    • List relevant folders and files
    • Add one-line descriptions for key items
  3. Create the .agent folder
    • Create .agent/ and .agent/plans/
    • Create empty .agent/planning.md

  4. Write .agent/main.md (minimal but complete) Include:

    • Project purpose and goals
    • High-level flow
    • Rules, formats, and conventions
    • Full codebase structure
    • Key docs and locations

    Add these rules (concise):

    • Do not create a plan for small, simple fixes.
    • For multi-step tasks, read .agent/planning.md and write a plan to .agent/plans/.
    • Ask questions when critical details are missing.
    • Update .agent/main.md if you change its knowledge base and notify the user.
    • If a git repo exists, record current commit hash and date and keep it updated.
    • If asked to verify freshness, compare current state to the commit recorded in .agent/main.md.
  5. Create agent files
    • .agent/claude.md, .agent/codex.md, .agent/copilot.md
    • Minimal content like: "Read .agent/main.md on every prompt."
  6. Plans
    • Create a plan file only when needed for multi-step work.
    • Suggested name: YYYYMMDD-HHMM-<slug>.md

Quality criteria

  • Concise, no duplicates
  • Complete but readable structure
  • Consistent with project docs
  • Update .agent/main.md as knowledge changes

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.

Reviews can't be read right now.

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