agentleFS
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/design-system-persist/SKILL.md

design-system-persist

Skill10 starsChanged 27 days agoMITView on GitHub

Save a generated design system to disk as a hierarchical Master + per-page-overrides structure so future sessions can retrieve it for the project. Trigger when the user says "save the design system", "persist this", "make this the master for the project", "remember these design choices", or wants the design system to survive across sessions.

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:

    Get the design system: Use a design-system-gen result (JSON or ASCII) or the spec the user pasted.

    line 38
  2. Very specific:

    Read design-system/MASTER.md.

    line 52

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

design-system-persist

Family: design Status: Stable

Purpose

Save a design system into a project's design-system/ folder so it survives across sessions and is shared across skills. Uses a Master + Overrides pattern:

  • design-system/MASTER.md — the global system (every page inherits it by default)
  • design-system/pages/<page-name>.md — per-page overrides (clean deviations)

Future sessions check pages/<current-page>.md first; if present, its rules override Master, else Master applies. A 12-page site gets one Master + small page files instead of one bloated spec enumerating every exception inline.

Triggers

  • "save the design system" / "persist this"
  • "make this the master"
  • "remember these design choices"
  • "design system to disk"

Inputs

  • A design system spec (from design-system-gen, or pasted by the user)
  • Project root path
  • Page name (optional — for a per-page override)

Steps

  1. Get the design system. Use a design-system-gen result (JSON or ASCII) or the spec the user pasted.
  2. Locate/create design-system/ at the project root (and pages/ if saving an override).
  3. Fill the starter template templates/design-system-starter.md: map the palette hex + contrast, typography + weights, pattern, style, effects, anti-patterns, and the pre-delivery checklist into its slots.
  4. Write the file:
    • Master → design-system/MASTER.md
    • Page override → design-system/pages/<name>.md with explicit deviation + reason notes (keep deviations minimal).
  5. Write/refresh design-system/README.md explaining the structure to future agents.
  6. Emit a retrieval prompt for the next session, e.g.: "I'm building [page]. Read design-system/MASTER.md; also check design-system/pages/[name].md — page rules override Master."

Outputs

  • design-system/MASTER.md (and/or pages/<name>.md)
  • design-system/README.md
  • A paste-ready context-retrieval prompt for the next session

Dependencies

  • templates/design-system-starter.md (required)
  • design-system-gen (typical upstream)

Notes

The Master + Overrides shape scales cleanly and keeps the global system as the single source of truth. Files are written to the user's project workspace, never into the plugin (see references/ENGINE-CONTRACTS.md §10).

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.