<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 2d ago

by arla6ka

skills

Agent skills for building a design system from your app and moving every screen onto it.

  • New — Created in the last 30 days
  • Active — Updated in the last 14 days
View on GitHub (opens in a new tab)

112 GitHub stars (112)

+112 in 18 days

Stars gained per day · daily snapshots since Sep 30
Stars gained per day, Sep 30 to Oct 16: +89 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 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
  • 6 skills (6 skills found in its SKILL.md files)
  • 9 forks (9 forks)
  • 2d ago last update (Last updated 2d ago)

Install

Skills CLI

npx skills add arla6ka/skills

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

Claude Code

git clone https://github.com/arla6ka/skillscp -r "skills/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/skills

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 an ask names one phase of design system work, such as "extract tokens from the app" or "add states and specs to our Button", or for an empty repo, such as "start a design system from scratch". A whole-app ask on a shipped app ("we need a design system") goes to design-system-boss when it is installed. Moving an app onto an existing system is migrate-design-system.

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

  • component-docs

    Writes one component's documentation entry from its code, stories and real call sites, in a Geist-style page order. Use for "document the button", "write docs for Select", "what states does Toast have", usage rules for a component, or a new or changed component. Skip foundations, overview pages and multi-component patterns. Docs for a whole design system go to design-system-boss.

    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, like "our UI is a mess, fix it", "we need a design system", "we hardcode colors everywhere", "make the buttons consistent for an upstream PR", "document our whole design system" or "check the app before I ship". Triages the app, then runs the design.how skills in order. One named screen goes to ui-review, one component to…

    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. When design-system-boss is installed and nobody has checked the system's specs, the boss triages first, since a migration copies a weak system's gaps everywhere. Not for making the system.

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

  • token-mapping

    Reports how hardcoded style values on a page, file or diff map onto a project's existing design tokens, purpose first, then value. Use for "are we using our tokens here", "which hardcoded colors map to which tokens", a token audit or planning a token migration. It never edits and never creates or renames tokens. Fixes and whole-app consistency go to design-system-boss.

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

  • ui-review

    Critiques a screen, flow, prototype or running build against agreed criteria, accessibility included, and ranks findings by severity. Use for "check this page before I ship", "is this flow ready", "is it accessible", keyboard or screen-reader checks, "it feels off on my phone", "it feels janky", or a second read on UI. A whole-app ship check goes to design-system-boss, token compliance to token-m…

    skills/ui-review/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.