Design Systems Skills

Build a design system with the method already written.

Nine skills for the work every system needs.

  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

One-time purchase. Works with Claude Code, Codex, Cursor and Gemini CLI.

Lost count of the number of button variations ? Or more banner variations than anyone can count ? Having a Figma file nobody trusts is a problem. It's time to build a system that accelerates your workflow .

Without an inventory, structure and governance, every team builds its own version. Developers guess at the specs. The system slows everyone down and then gets ignored.

These nine skills give your agent the method to inventory what exists, decide how it is organised, document it so developers can build from it, and keep it healthy once it ships.

The system is a pile of components

An inventory shows every pattern in use

Each team builds its own variant

Clear rules say how components are built and named

Documentation is out of date

Governance keeps the system current

See it work

An example conversation. Your output depends on your project.

design-systems
You9:41

We have six products and no shared components. Where do we start?

AgentAgent9:41

Using Interface inventory and Architecture logic. Starting with the screenshots you shared.

Agent is working

System starting point, draft 1

  • An inventory of patterns grouped by type, with duplicates marked
  • A proposed structure for tokens, components and patterns
  • A short list of what to standardise first

Caveats

Frequency counts come from sampled screens. Check them against the codebase.

You9:48

Write the governance model.

Quick start, 30 seconds

  1. 01

    Download the files.

    From your Methodloop library, in the format for your tool.

  2. 02

    Drop them into your project.

    Add them to your repo or your tool's skills folder.

  3. 03

    Name the skill.

    Tell your agent which one to use. Claude Code, Codex, Cursor and Gemini CLI all work.

What you will be able to do

First hour

In your first hour you have an inventory of every pattern in the screens you share.

First week

By the end of the week you have a proposed structure and a standardise-first list.

Next quarter

By next quarter teams build from documented components and a governance model they agreed.

What is inside

Each one is a skill file you drop into your agent, so it works in Claude Code, Codex, Cursor and Gemini CLI.

  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI
SKILL 01

Interface inventory

Catalogue every pattern in use and where it appears.

Skill file for
SKILL 02

Architecture logic

Decide how components, tokens and patterns are organised.

Skill file for
SKILL 03

Component frameworks

Define how components are built, named and varied.

Skill file for
SKILL 04

Accessibility

Set accessibility requirements at the component level.

Skill file for
SKILL 05

Governance and maintenance

Agree who changes the system and how it stays healthy.

Skill file for
SKILL 06

Technical documentation

Document components so developers can build from them.

Skill file for
SKILL 07

Design tokens

Define colour, type and spacing tokens that carry across platforms.

Skill file for
SKILL 08

Handoff specs

Produce specs developers can build from without questions.

Skill file for
SKILL 09

Adoption metrics

Measure whether teams are using the system.

Skill file for

Choose your skills

0 of 9 paid skills selected

Total: $0

Buy selected skillsBuy the bundle, $249

Why this works

Each skill is a plain markdown file that tells your agent the steps, the questions to ask and the format to produce. The method is written down, so the output follows it.

Who wrote them

Anton has spent sixteen years doing this work inside Myer, Telstra Health and Flybuys. The methods in these files are the ones used on real projects. Two skills are free, so you can judge the quality before you spend anything.

Everything in the bundle

$249one time

Bought one at a time, $441.

The bundle is $249. You keep $192.

  • All 9 skills
  • Every skill in four formats: Claude Code, Codex, Cursor and Gemini CLI
  • Example prompts for each skill
  • A Methodloop library with every file in one place
  • Updates while the skills are on sale

The One Real Project guarantee

Use the skills on one real component library. If they do not save you time, ask within 14 days and I refund every dollar.

This is for you if:

  • You inherited a system or a mess of components
  • You are starting a system and want the method first
  • You need developers to build from your specs

This is probably not for you if:

  • You run a mature system with full governance and adoption tracking
  • You want a finished component library delivered

Fair questions.

The skills set the method, the structure and the documentation. Your team or your agent builds the components to that standard.

The method applies to both. Your agent works with whatever you share, such as screenshots, tokens and code.

No. A small team gets the most from a clear structure early.

Claude Code, Codex, Cursor and Gemini CLI. Every purchase includes all four formats.

In your Methodloop library. Your account is created at checkout, or sign in if you already have one.

Yes, while the skills are on sale.

Give the system a method.

9 skills for $249, one time. Or start with the two that are free.

P.S. 9 skills for $249. Bought one at a time they come to $441.

P.S. Two skills are free. Start there and judge the work yourself.

P.S. At checkout you can add related material and save.