agentleFS
Sign inStart free
faizkhairifaizkhairi/claude-code-blueprint/skills/register-project/SKILL.md

register-project

Skill73 starsChanged 4 months agoMITView on GitHub

Register an existing project in memory. Use when starting work on a new repo or when a project needs its own context file. Triggers on: 'register project', 'add project to memory', 'track this project', 'create project file'.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test command (check scripts in package manager config)

    line 14
  2. Very specific:

    Read ./memory/templates/coding-template.md for the standard format.

    line 20
  3. Very specific:

    Write to ./memory/projects/active/{project-name}.md using the template, filled with detected info.

    line 28
  4. Distinctive:

    Never overwrite an existing project file.

    line 35
  5. Distinctive:

    Use the template format exactly

    line 36
  6. Distinctive:

    Leave Session Context section with placeholder (populated during actual work)

    line 38

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

Register Project in memory

Step 1: Detect Project Info

Gather from the current working directory or user input:

  • Project name and path
  • Framework/language (check package.json, pyproject.toml, composer.json, etc.)
  • Test command (check scripts in package manager config)
  • Git remote URL
  • Current test count (run tests and count)

Step 2: Read Template

Read ./memory/templates/coding-template.md for the standard format.

Step 3: Check Capacity

Scan ./memory/projects/active/. If 10+ projects exist, identify the oldest by Last Accessed date and suggest archiving it.

Step 4: Create Project File

Write to ./memory/projects/active/{project-name}.md using the template, filled with detected info.

Step 5: Confirm

Show the created file path and key fields to the user.

Rules

  • Never overwrite an existing project file; read it first and update if it exists
  • Use the template format exactly
  • Set Last Accessed to today's date
  • Leave Session Context section with placeholder (populated during actual work)

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