agentsclimarketplace

Design system starter

Skill thanhaq/interface-compass-skills/skills/design-system-starter

Frontend design skill pack for AI coding agents: briefs, design systems, audits, motion, copy, and ship checks.

Install
npx -y skills add thanhaq/interface-compass-skills --skill design-system-starter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create or extend practical frontend design systems with tokens, component contracts, state rules, and migration steps. Use when Codex needs to establish color roles, typography, spacing, radius, elevation, interaction states, or reusable UI primitives for a product interface.

SKILL.md

1.7 KB, 273 tokens by cl100k_base, as published. Nobody here has run it

Design System Starter

Goal

Create a design foundation that is small enough to ship and strong enough to keep future screens coherent.

Workflow

  1. Inspect the app stack, existing styling approach, and component library before proposing files.
  2. Define role-based tokens for color, typography, spacing, radius, elevation, borders, and motion.
  3. Establish component contracts for the primitives the product actually needs.
  4. Include state rules for hover, focus, active, disabled, loading, selected, error, and success.
  5. Migrate one representative screen or component so the system is proven in code.
  6. Document only the decisions future contributors must follow.

Token Principles

  • Name tokens by role, not appearance.
  • Keep primitives private when possible and expose semantic aliases.
  • Use a restrained scale before adding exceptions.
  • Make text, surfaces, borders, and actions distinct roles.
  • Keep responsive values explicit instead of scaling type directly with viewport width.

Component Contract

For each component, specify:

  • Purpose and allowed variants.
  • Required and optional props.
  • Supported sizes and density.
  • Accessibility requirements.
  • Content limits and overflow behavior.
  • Interaction states.
  • Example usage.

Resources

  • Read references/tokens.md before creating token files.
  • Read references/component-contracts.md before designing reusable components.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.