agentleFS
Sign inStart free
lagowskilagowski/ClaudeAutoPM/.claude/skills/add-framework-asset/SKILL.md

add-framework-asset

Skill39 starsChanged 9 days agoMITView on GitHub

Add or change a ClaudeAutoPM command, agent or script in the right source-of-truth location (packages/), sync it into the autopm/ payload, update registries, and run the guards. Use whenever touching packages/*/commands, packages/plugin-core/scripts, autopm/.claude or agent registries.

The file

We split this skill 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:

    Use .claude/ paths, never autopm/ (framework path rule).

    line 15
  2. Very specific:

    Write the failing test first (tdd.enforcement.xml), then implement.

    line 16

≈ “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 or change a framework asset

Asset: $ARGUMENTS

  1. Edit the SOURCE: packages/<plugin>/commands/** (commands) or packages/plugin-core/scripts (scripts). Never edit the synced copy in autopm/.claude or .claude/scripts.
  2. For agents: update .claude/agents/agent-registry.xml and AGENT-REGISTRY.md (and the autopm/.claude equivalents).
  3. Use .claude/ paths, never autopm/ (framework path rule).
  4. Write the failing test first (tdd.enforcement.xml), then implement.
  5. Sync: npm run sync:commands && npm run sync:scripts

  6. Verify:

    npm run sync:commands:check && npm run sync:scripts:check \
  && npm run validate:paths \
  && npx jest test/templates/agent-registry-consistency.test.js \
  && npm test

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