<Devsly/>
NotebookLM Watermark Remover
Remove the NotebookLM watermark from PDF slide exports — free, unlimited, and 100% in your browser.
View
NotebookLM Video Watermark Remover
Remove the NotebookLM watermark from every frame of your MP4 and auto-trim the end card — free and unlimited.
View
Gemini Watermark Remover
Remove the Gemini (Veo) sparkle watermark from every frame of your AI-generated MP4 — free and unlimited.
View
MCP https://devsly.io/mcp MCP Tools Best Skills API Docs
Devsly

Keyboard Shortcuts

Navigation

Quick Search
⌘ / Ctrl + K
Toggle Dark Mode
⌘ / Ctrl + D
Close Dialogs
Esc

Tool Actions

Execute / Process
⌘ / Ctrl + Enter
Clear Input
⌘ / Ctrl + Shift + C
Copy Output
⌘ / Ctrl + Shift + X

Editor

Select All
⌘ / Ctrl + A
Undo
⌘ / Ctrl + Z
Redo
⌘ / Ctrl + Shift + Z

Updated 1d ago

by arla6ka

design.how

Design systems, skills and visuals for coding agents

  • Active — Updated in the last 14 days
  • Multi-agent — Targets three or more agents
Works with
  • Claude
  • Codex
  • Cursor
View on GitHub (opens in a new tab)

243 GitHub stars (243)

+215 in 30 days

Stars gained per day · daily snapshots since Sep 30
Stars gained per day, Sep 30 to Nov 5: +220 in total; the busiest day was Oct 9 with +31 stars.Oct 1: +1 starsOct 2: 0 starsOct 3: +1 starsOct 4: 0 starsOct 5: 0 starsOct 6: +3 starsOct 7: +1 starsOct 8: +3 starsOct 9: +31 starsOct 10: +6 starsOct 11: +6 starsOct 12: +2 starsOct 13: 0 starsOct 14: +3 starsOct 15: +13 starsOct 16: +19 starsOct 17: +14 starsOct 18: +1 starsOct 19: +10 starsOct 20: +4 starsOct 21: +4 starsOct 22: +1 starsOct 23: +1 starsOct 24: +14 starsOct 25: +14 starsOct 26: +17 starsOct 27: +6 starsOct 28: +4 starsOct 29: +11 starsOct 30: +5 starsOct 31: +4 starsNov 1: +3 starsNov 2: +9 starsNov 3: +2 starsNov 4: +5 starsNov 5: +2 stars
Stars gained between daily snapshots
PeriodNew stars
Oct 1+1
Oct 20
Oct 3+1
Oct 40
Oct 50
Oct 6+3
Oct 7+1
Oct 8+3
Oct 9+31
Oct 10+6
Oct 11+6
Oct 12+2
Oct 130
Oct 14+3
Oct 15+13
Oct 16+19
Oct 17+14
Oct 18+1
Oct 19+10
Oct 20+4
Oct 21+4
Oct 22+1
Oct 23+1
Oct 24+14
Oct 25+14
Oct 26+17
Oct 27+6
Oct 28+4
Oct 29+11
Oct 30+5
Oct 31+4
Nov 1+3
Nov 2+9
Nov 3+2
Nov 4+5
Nov 5+2
  • 10 skills (10 skills found in its SKILL.md files)
  • 16 forks (16 forks)
  • 1d ago last update (Last updated 1d ago)

Install

Skills CLI

npx skills add arla6ka/design.how

Asks which skills and agents to install. Just one: npx skills add arla6ka/design.how --skill build-design-system — add -g for every project.

Claude Code

git clone https://github.com/arla6ka/design.howcp -r "design.how/skills/build-design-system" ~/.claude/skills/

Copies the build-design-system skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add arla6ka/design.how

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

In the author's own words, from each skill's SKILL.md.

  • build-design-system

    Use when someone wants a design system built from the UI an app already ships, or one phase of it, such as "extract tokens from the app", "add states to our Button", "replace the hardcoded colors with tokens" or "start a design system". Moving screens onto an existing system's components is migrate-design-system. A vague whole-app ask goes to design-system-boss.

    skills/build-design-system/SKILL.md on GitHub (opens in a new tab)

  • component-docs

    Use to write one component's documentation entry from its code, stories and real call sites, such as "document the button", "write docs for Select", "what states does Toast have", or usage rules for a new or changed component. Not for foundations or pages that span components, which no skill here writes, nor for changing the component, which is build-design-system.

    skills/component-docs/SKILL.md on GitHub (opens in a new tab)

  • design-system-boss

    Use for vague whole-app design system asks on an app that already ships UI, such as "our UI is a mess, fix it", "we need a design system", "we hardcode colors everywhere", "make the buttons consistent" or "check the app before I ship". One named screen goes to ui-review, one component to component-docs, a token report to token-mapping. A repo with no UI yet is out of scope.

    skills/design-system-boss/SKILL.md on GitHub (opens in a new tab)

  • migrate-design-system

    Use when an app has to move onto a design system that already exists, such as "migrate the app to our design system", "move every screen onto the new components", a rollout, or an adoption audit. Not for making the system or for swapping raw values for tokens, which are build-design-system.

    skills/migrate-design-system/SKILL.md on GitHub (opens in a new tab)

  • token-mapping

    Use to report how hardcoded style values on a page, file or diff map onto a project's existing design tokens, such as "are we using our tokens here", "which hardcoded colors map to which tokens", a token audit or planning a token migration. It never edits. Replacing the values is build-design-system.

    skills/token-mapping/SKILL.md on GitHub (opens in a new tab)

  • ui-review

    Use to critique a screen, flow, prototype or running build, accessibility included, and rank what is broken, such as "check this page before I ship", "is this flow ready", "is it accessible", keyboard or screen-reader checks, "it feels off on my phone" or "it feels janky". Not for token compliance, which is token-mapping.

    skills/ui-review/SKILL.md on GitHub (opens in a new tab)

  • glaze

    Glaze design system rules for this project's UI. Use when building or changing any screen, component, form or style, when porting an existing screen onto Glaze, or when checking UI against Glaze.

    systems/glaze/SKILL.md on GitHub (opens in a new tab)

  • lime

    Lime design system rules for this project's UI. Use when building or changing any screen, component, form or style, when porting an existing screen onto Lime, or when checking UI against Lime.

    systems/lime/SKILL.md on GitHub (opens in a new tab)

  • quartz

    Quartz design system rules for this project's UI. Use when building or changing any screen, component, form or style, when porting an existing screen onto Quartz, or when checking UI against Quartz.

    systems/quartz/SKILL.md on GitHub (opens in a new tab)

  • sodium

    Sodium design system rules for this project's UI. Use when building or changing any screen, component, form or style, when porting an existing screen onto Sodium, or when checking UI against Sodium.

    systems/sodium/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.