agentleFS
Sign inStart free
PyModelPyModel/designer-skill/.claude/skills/designer-skill-mcp-consistency/SKILL.md

designer-skill-mcp-consistency

Skill52 starsChanged 3 days agoMITView on GitHub

Use when changing designer-skill-mcp versions or names.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Before calling a designer-skill-mcp change consistent, check every name, version pin and ownership line across package.json, server.json, …

    line 9

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

designer-skill-mcp: name, pin and ownership consistency

Before calling a designer-skill-mcp change consistent, check every name, version pin and ownership line across package.json, server.json, plugin manifests, mcp.json, README, docs/ and docs/blog/. Pins outside PIN_TARGETS (scripts/versions.mjs) are checked by no script; add a file there when it gains a pin.

  • Core names are consistent (npm @pymodel/designer-skill-mcp, mcpName io.github.PyModel/designer-skill-mcp, bin designer-skill-mcp). Keep them.
  • Three names, each with one job: designer-skill-mcp is the server and package identifier (SERVER_NAME), designer-skill is the config key and plugin name, and Designer Skill is the human title (SERVER_TITLE and every manifest's display name). Never change one side silently.
  • Copyright and credit lines say © <year> PyModel LLC (LICENSE, README, Info.plist, footers).
  • Blog and docs use the live domain (niblet.pymodel.com) and current version pins.
  • Moving or renaming a test file, or rewording a reference doc, breaks names pinned elsewhere. Grep README.md and docs/ for the old test path (test/rendered.test.ts went stale when rendered tests moved into test/audit-fixes.test.ts). When test/reference-reachability.test.ts pins a phrase from a reference doc, update that assertion in the same change (remote-only became this server's pass-through in the niblet catalogue doc), then rerun the suite.
  • Open drift at v0.24.0: references/known-drift-2026-11-12.md. Re-verify with a fresh grep before acting on it.
  • A tool rename (e.g. get_design_system to get_skill_contract) needs a grep of the old name across README, docs/ and the skill folders before the change is called consistent.

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