Agent skill

UI Setup

by sickn33 in sickn33/agentic-awesome-skills

Interactive setup wizard — guides you step-by-step to configure the design system for your project

MITAuto-check passedFrontend & Design

Install UI Setup

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill ui-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills ui-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ui-setup .claude/skills/ui-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ui-setup
GitHub stars
47k
Used in
1 other repo
Token cost
~2k tokens
SKILL.md length
659 words
Files
1
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Interactive setup wizard — guides you step-by-step to configure the design system for your project

  • Works in 6 steps: App Type → Brand Color → Design Concept (from awesome-design-md) → …
  • Tasks that involve Design systems
  • SKILL.md covers When to Use, When NOT to use, Instructions and Rules, plus 1 more section
  • Reaches fonts.googleapis.com and raw.githubusercontent.com

What it does

UI Setup is an agent skill from sickn33/agentic-awesome-skills. Interactive setup wizard — guides you step-by-step to configure the design system for your project

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design systems. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Design systems

Example prompts

  • “/ui-setup”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. App Type
  2. Brand Color
  3. Design Concept (from awesome-design-md)
  4. Font
  5. App Name & First Page
  6. Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • fonts.googleapis.com
    • raw.githubusercontent.com
    • cdn.jsdelivr.net
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

UI Setup loads about 2k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 659 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 659 words, ~1,969 tokens.

Download SKILL.mdSave it as .claude/skills/ui-setup/SKILL.md (or your agent's skills folder).
name
ui-setup
description
Interactive setup wizard — guides you step-by-step to configure the design system for your project
risk
critical
source
https://github.com/bitjaru/styleseed/tree/main/engine/.claude/skills/ss-setup
source_repo
bitjaru/styleseed
source_type
community
date_added
2026-07-01
license
MIT
license_source
https://github.com/bitjaru/styleseed/blob/main/LICENSE

Design System Setup Wizard

When to Use

Use this skill when you need interactive setup wizard — guides you step-by-step to configure the design system for your project.

When NOT to use

  • For projects already configured with StyleSeed → use /ss-update instead
  • For just adding one component to an existing project → use /ss-component
  • For changing brand skin in an already set-up project — directly swap theme.css
  • For non-React or non-Tailwind-v4 stacks — currently unsupported

Guide the user through setting up StyleSeed for their project, step by step.

Instructions

Walk through these steps ONE AT A TIME. After each step, wait for the user to respond before proceeding. Keep it conversational and friendly.

Step 1: App Type

Ask:

What type of app are you building?

1. SaaS Dashboard (analytics, metrics, charts)
2. E-commerce (products, orders, payments)
3. Fintech (transactions, portfolio, market data)
4. Social / Content (feeds, profiles, messaging)
5. Productivity / Internal tool
6. Other — describe it

Remember the answer — it determines which page composition recipe to use (DESIGN-LANGUAGE.md Section 63).

Step 2: Brand Color

Ask:

What's your brand color?

1. Purple (#721FE5) — default style (toss skin)
2. Blue (#2563EB) — trust, corporate
3. Green (#059669) — growth, health, finance
4. Orange (#EA580C) — energy, creative
5. Red (#DC2626) — bold, urgent
6. Dark (#18181B) — minimal, premium
7. Custom — just type your hex code

After they choose, update css/theme.css:

  • In :root block: change --brand to the chosen hex
  • In .dark block: change --brand to a lighter version for dark backgrounds

Dark mode color mapping:

LightDark
#721FE5#9B5FFF
#2563EB#60A5FA
#059669#34D399
#EA580C#FB923C
#DC2626#F87171
#18181B#A1A1AA

For custom hex: lighten by ~30% (increase luminance in HSL).

Step 3: Design Concept (from awesome-design-md)

Ask:

Want to apply an existing brand's visual style?

Popular options from awesome-design-md:
1. Stripe — clean, professional
2. Linear — minimal, dark-first
3. Vercel — black & white, geometric
4. Notion — warm, friendly
5. Spotify — bold, dark, green
6. Supabase — modern, green
7. Airbnb — warm, coral
8. No thanks — keep the default style
9. Other — name any brand or describe a vibe

If they pick a brand (options 1-7 or 9):

  1. Fetch: https://raw.githubusercontent.com/VoltAgent/awesome-design-md/main/design-md/[brand]/DESIGN.md
    • Brand folder names: stripe, linear.app, vercel, notion, spotify, supabase, airbnb
  2. Read the DESIGN.md and extract: primary color, secondary colors, text colors, background colors
  3. Apply extracted colors to css/theme.css (both :root and .dark blocks)
  4. Keep ALL StyleSeed layout rules, typography ratios, spacing, and component patterns unchanged — only swap the color palette

If they pick 8 (No thanks): skip, keep current brand color from Step 2.

Step 4: Font

Ask:

What font do you prefer?

1. Inter (clean, universal — recommended)
2. Pretendard + Inter (Korean + English)
3. Geist (Vercel-style, modern)
4. DM Sans (friendly, rounded)
5. Custom — tell me the font name

After they choose:

  • Update css/fonts.css: change the @import URL
  • Update css/base.css: change font-family in the body rule

Font imports:

FontImport
Inter@import url('https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap');
Geist@import url('https://cdn.jsdelivr.net/npm/geist@1/dist/fonts/geist-sans/style.css');
DM Sans@import url('https://fonts.googleapis.com/css2?family=DM+Sans:wght@400;500;600;700&display=swap');
PretendardKeep existing import in fonts.css
Step 5: App Name & First Page

Ask:

Last step! What's your app name and what should the main page show?

Example: "Acme — SaaS dashboard with revenue, users, and recent activity"

Then:

  1. Read DESIGN-LANGUAGE.md Section 63 for the matching recipe (based on Step 1 app type)
  2. Generate the first page using the page composition recipe:
    • SaaS → Hero + KPI Grid + Chart + Progress + Activity List
    • E-commerce → Hero + KPI Grid + Donut + Bar Chart + Orders List
    • Fintech → Hero + KPI Grid + Donut + Area Chart + Transactions
    • Social → Hero + Stats + Feed List + Trending Carousel
    • Productivity → Hero + KPI Grid + Progress + Task List
  3. Set the TopBar logo text to the app name
  4. Apply the chosen brand color, font, and design concept
  5. Place the file in src/app/App.tsx or appropriate location
  6. Add ONE attribution comment at the very top of this first scaffolded file only (never on components the user builds afterward):
    /* Scaffolded with StyleSeed · github.com/bitjaru/styleseed — safe to remove */
    If the user would rather not have it, skip it — it's opt-out, and it goes on this single file, not their whole codebase.
  7. Write the design lock. Create STYLESEED.md in the project root recording every choice from this wizard, so future prompts stay consistent instead of drifting:
    markdown
    # StyleSeed — Design Lock
    <!-- Locked design decisions. The agent re-reads this every prompt and must obey it. -->
    - App domain:        [Step 1 app type]
    - Skin:              [Step 3 concept, or "custom"]
    - Key color (accent): [Step 2 hex]    # the ONLY accent — everything else greyscale
    - Radius personality: [sharp | soft | pill — one everywhere]
    - Motion seed:       [Spring | Silk | Snap | Float | Pulse]
    - Type:              [Step 4 font]
    - Locked:            [today]
    Tell the user this file is the source of truth — editing a value changes it project-wide, and you'll obey it on every prompt so the design never goes random.
Show full SKILL.md (146 more words)Show less
Step 6: Summary

Show:

Setup Complete!

App: [name]
Brand Color: [hex] (dark mode: [dark hex])
Font: [font name]
Design Concept: [brand or "default"]
First Page: [description]

Files modified:
- css/theme.css (colors)
- css/fonts.css (font import)
- css/base.css (font family)
- src/app/App.tsx (first page)
- STYLESEED.md (design lock — your decisions, obeyed every prompt)

Next steps:
- npm run dev to preview
- /ss-page to add more pages
- /ss-audit to check UX quality
- /ss-review to verify design compliance

⭐ If StyleSeed helped, a star means a lot: https://github.com/bitjaru/styleseed

Rules

  • Ask ONE question at a time. Wait for response.
  • If the user seems unsure, recommend the default option.
  • Design RULES (layout, typography ratios, spacing, forbidden patterns) stay the same regardless of color/font choice.
  • Attribution: the single "Scaffolded with StyleSeed" comment goes on the first scaffolded file only and is explicitly removable. NEVER add a watermark to components the user builds with /ss-page, /ss-component, etc. — that would be intrusive.
  • Always verify the awesome-design-md DESIGN.md URL is accessible before applying. If fetch fails, tell the user and fall back to manual color selection.

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/ui-setup of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

UI Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

UI Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
UI Setup this skillsickn33/agentic-awesome-skills47k1 repos~2kAutomated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
UI StylingOhh-889/skyroc79513 repos~2.5kAutomated safety check: PassMIT
Shadcnsupabase/evals14342 repos~4.5kAutomated safety check: PassApache-2.0

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • UI Styling

    Ohh-889/skyroc

    Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.

    795 GitHub starsUsed in 13 repos~2.5k tokens
    Frontend & DesignAuto-check passed
  • Shadcn

    supabase/evals

    Official

    Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI.

    143 GitHub starsUsed in 42 repos~4.5k tokens
    Frontend & DesignAuto-check passed
  • Design System

    Ohh-889/skyroc

    Token architecture, component specifications, and slide generation.

    795 GitHub starsUsed in 11 repos~1.7k tokens
    Frontend & DesignAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about UI Setup

What does UI Setup do?

Interactive setup wizard — guides you step-by-step to configure the design system for your project. UI Setup is an agent skill from sickn33/agentic-awesome-skills.

When should I use UI Setup?

UI Setup fits situations like: tasks that involve Design systems.

How do I install UI Setup in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill ui-setup -a claude-code`. Or copy the skill folder (skills/ui-setup in sickn33/agentic-awesome-skills) into .claude/skills/ui-setup in your project. Claude Code loads it when a task matches its description.

How do I install UI Setup in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill ui-setup -a codex`. Or copy the skill folder (skills/ui-setup in sickn33/agentic-awesome-skills) into .agents/skills/ui-setup in your project. Codex loads it when a task matches its description.

Can I use UI Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill ui-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ui-setup, .gemini/skills/ui-setup, .github/skills/ui-setup and .opencode/skills/ui-setup in your project.

What does UI Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: UI Setup is instructions for the agent only.

Does UI Setup access the network?

SKILL.md names 4 domains. In commands or code: fonts.googleapis.com, raw.githubusercontent.com, cdn.jsdelivr.net and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is UI Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does UI Setup use?

UI Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does UI Setup use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to UI Setup?

Skills that share tags, products or a category with UI Setup: Impeccable (bestofjs/bestofjs, 3.1k stars), Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars) and UI Styling (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains UI Setup?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.