Menu

Individual skill

rico-design-md

0upvotes

Create design system documents from any website URL. Use this skill for: DESIGN.md, preview.html, design tokens, CSS variables, style references, brand analysis, or format conversion between DESIGN.md/tokens.json/variables.css/theme.css. Trigger on: "create a DESIGN.md", "extract design tokens", "analyze [brand]'s design system", "reverse-engineer [url]'s visual style", "rico DESIGN.md", "rico tokens", "rico 全部输出". Covers: DESIGN.md, preview.html, tokens.json (DTCG), variables.css, theme.css (Tailwind v4).

skills/rico-design-md/SKILL.md

Read pinned source

Source commit bb423881d379bc82fbc762dddbe6be48db97c584

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
274
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Get Design MD

Convert any website into design system documents, or convert between formats.

## Do's

- **Read the reference example first.** Before generating any format, read the matching file
  in `references/themes-github/` to match structure exactly. This prevents format drift.
- **Use semantic token names.** Name tokens by role (ink, surface-1, accent-blue) not by
  appearance (vapor-white, charcoal-canvas) — unless the descriptive name is the brand's own.
- **Capture full CSS syntax for shadows.** Write `rgba(255,255,255,0.1) 0 0.5px 0 0.5px`,
  not "subtle shadow". Downstream consumers need parseable values.
- **Document every observed component state.** Hover, focus, active, selected — each state
  changes CSS properties. Missing states mean incomplete implementation.
Back to top