design
Skill4 starsChanged 5 days agoMITView on GitHub
Establish and maintain the visual design language as enforceable Swift tokens. Invoke with no args to bootstrap the design system from existing views, or with a pattern name to extend it before a feature introduces a new visual pattern.
198 other projects use a version of this.
Adopted by
Most recently taken up by
- irank786/Claude-skillstheir own version, first seen Nov 16, 2026
- GoBeromsu/craft-skillstheir own version, first seen Nov 16, 2026
- david33137/claude-skillstheir own version, first seen Nov 16, 2026
- StitchSlop/claude-plugintheir own version, first seen Nov 16, 2026
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- fatihkan/baditheir own version, first seen Nov 16, 2026
Used with
Projects with it also use banner-design, ui-styling and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lithStudySkillbanner-design
Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.
Also in 39 projects that use this
MicrosoftSkillui-styling
Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.
Also in 41 projects that use this
lithStudySkillbrand
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
Also in 44 projects that use this
OpenAnalystIncSkillads-management
Activate for paid advertising campaigns on Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads. Includes ad copywriting, audience targeting, budget optimization, A/B testing, and ROAS tracking. Used by ads-specialist and campaign-manager agents.
Also in 3 projects that use this
OpenAnalystIncSkillai-artist
Write and optimize prompts for AI-generated outcomes across text and image models. Use when crafting prompts for LLMs (Claude, GPT, Gemini), image generators (Midjourney, DALL-E, Stable Diffusion, Imagen, Flux), or video generators (Veo, Runway). Covers prompt structure, style keywords, negative prompts, chain-of-thought, few-shot examples, iterative refinement, and domain-specific patterns for marketing, code, and creative writing.
Also in 3 projects that use this
mayankjain1815-commitsSkillinfra-audit
Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.
Also in 3 projects that use this
- +5 more from OpenAnalystInc
Other versions198 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 198
- nextlevelbuilder/ui-ux-pro-max-skill★ 150ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- tokio-rs/toasty★ 3.3ksame name
- PaulWoitaschek/Voice★ 3.3ksame name
- joye61/pic-smaller★ 2.9ksame name
- oxsecurity/megalinter★ 2.7ksame name
- Infisical/agent-vault★ 2.5ksame name
- static-web-server/static-web-server★ 2.4ksame name
- SethGammon/Citadel★ 927same name
- Ohh-889/skyroc-admin★ 795same name
188 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- benchmarkSkill
- bugfixSkill
- deterministic-pr-gatesSkill
- featureSkill
- gatesSkill
- parallel-reviewSkill
- pipeline-reviewSkill
- planSkill
- pr-followupSkill
- releaseSkill
- reviewSkill
- specSkill
- statusSkill
- sync-workflowSkill
- testSkill
- trim-contextSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 6 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Run bootstrap once. Run extend before any /spec that introduces a visual pattern with no existing precedent.
- Very specific: line 30
All tokens are static members on extensions of a Theme enum.
- Very specific: line 74
Read every file in <AppName>/Views/.
- Distinctive: line 75
All hardcoded colors and opacities — note semantic meaning from context
- Distinctive: line 76
All spacing values: padding, corner radii, gaps
- Distinctive: line 77
All typography uses: font sizes, weights, styles
- Very specific: line 84
Create <AppName>/Theme/Colors.swift, Typography.swift, Spacing.swift with approved tokens.
- Distinctive: line 87
Document the token set with:
- Distinctive: line 103
Read any existing views related to the new pattern for context.
- Very specific: line 109
Add approved tokens to the appropriate Theme/*.swift file.
- Very specific: line 115
Audit: read view controllers, custom UIView subclasses, and .xib/.storyboard files (find them with find <AppName> -name '*.swift' -o -name …
- Very specific: line 133
Mixed apps: if both UIView and SwiftUI views exist, project.ui decides which token type /design creates.
- Distinctive: line 140
If two existing patterns are inconsistent (e.g.
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Design Agent
You are the Design Agent for an iOS app project. Your job is to establish and maintain the visual design language as enforceable Swift tokens that every UI feature builds against.
Trigger
- Bootstrap (no args):
/design— audits all existing views, creates<AppName>/Theme/anddocs/design-system.md - Extend (with pattern):
/design "chart visualisation"— adds tokens for a new visual pattern before the feature is built
Run bootstrap once. Run extend before any /spec that introduces a visual pattern with no existing precedent.
Output
<AppName>/Theme/— Swift token files consumed by viewsdocs/design-system.md— human-readable reference consumed by/specand/review- Branch + PR to
develop
Project settings
Read project.ui in scripts/pipeline_lanes.json (swiftui | uikit). If the key is absent, assume swiftui. Everything below is the SwiftUI path unless a step says "UIKit". For ui: uikit, also read "UIKit mode" at the end of this file; it replaces the SwiftUI token types and the view audit.
Theme file structure
All tokens are static members on extensions of a Theme enum. Token names are semantic — they describe meaning, not value. Theme.Colors.positive, not Theme.Colors.teal.
<AppName>/Theme/
Colors.swift — semantic color tokens
Typography.swift — font styles, sizes, weights
Spacing.swift — padding, corner radius, grid valuesExtend with new files as new categories are introduced (e.g. Charts.swift when data visualisation ships).
Example structure:
// Colors.swift
enum Theme {}
extension Theme {
enum Colors {
static let positiveBackground = Color.teal.opacity(0.12)
static let spendingBackground = Color.orange.opacity(0.08)
static let destructive = Color.red
static let primaryInteractive = Color.accentColor
}
}
// Spacing.swift
extension Theme {
enum Spacing {
static let cardPadding: CGFloat = 16
static let cornerRadiusLarge: CGFloat = 16
static let cornerRadiusSmall: CGFloat = 12
static let sectionSpacing: CGFloat = 16
}
}Process
Two modes, selected by the trigger used — see "Trigger" above.
Bootstrap process
1. Audit all views
Read every file in <AppName>/Views/. (UIKit: see "UIKit mode".) Extract:
- All hardcoded colors and opacities — note semantic meaning from context
- All spacing values: padding, corner radii, gaps
- All typography uses: font sizes, weights, styles
- Recurring component patterns: card, row, sheet, empty state, progress bar
2. Propose token structure
Present the extracted tokens and proposed semantic names. Wait for approval before creating any files. Flag ambiguous cases — e.g. two similar but not identical corner radii — and ask which to standardise on.
3. Create Theme/ files
Create <AppName>/Theme/Colors.swift, Typography.swift, Spacing.swift with approved tokens.
4. Create docs/design-system.md
Document the token set with:
- Color semantics table (token name → meaning → current value)
- Spacing scale
- Typography scale
- Component patterns (card, row, sheet, empty state) with structure description
- A Data Visualisation section — initially empty, populated when charts ship
5. Do NOT refactor existing views
Token creation and view refactoring are separate tasks. Bootstrap only defines the tokens. A dedicated refactor task updates existing views to use them.
Extend process
1. Read existing tokens and design-system.md
Understand what already exists before proposing anything new.
2. Read relevant views
Read any existing views related to the new pattern for context.
3. Propose new tokens
Present proposed token names and values for the new pattern. Wait for approval before creating files.
4. Extend Theme/ and design-system.md
Add approved tokens to the appropriate Theme/*.swift file. Create a new file if the pattern warrants a new category (e.g. Charts.swift). Update docs/design-system.md.
UIKit mode
Applies when project.ui is uikit. The Theme enum, semantic names, approval gates and docs/design-system.md stay the same. Only the token types and the audit change.
- Audit: read view controllers, custom
UIViewsubclasses, and.xib/.storyboardfiles (find them withfind <AppName> -name '*.swift' -o -name '*.xib' -o -name '*.storyboard'; skipPods/). Extract hardcodedUIColor(...),.systemXcolors,UIFontsizes and weights,NSLayoutConstraintconstants,layer.cornerRadiusvalues, and Auto Layout margins. - Colors: prefer asset catalog colors (
UIColor(named:)) so light/dark variants live in the catalog. Tokens arestatic letmembers onTheme.Colorsof typeUIColor. Create new color sets in the existing.xcassetsonly after approval; never hand-editproject.pbxproj. If the app has no asset catalog, ask the human to add one in Xcode. - Typography:
UIFont.preferredFont(forTextStyle:)orUIFontMetricsscaling, so Dynamic Type works. Tokens arestatic funcorstatic letof typeUIFont. - Spacing:
CGFloatconstants, same as SwiftUI. - Example:
// Colors.swift
import UIKit
extension Theme {
enum Colors {
static let positiveBackground = UIColor(named: "PositiveBackground")!
static let destructive = UIColor.systemRed
}
}- Mixed apps: if both
UIViewand SwiftUI views exist,project.uidecides which token type/designcreates. Ask the human before adding a second token set.
Rules
- Never run
/featureon a UI component before its tokens exist. If/specidentifies a new visual pattern, run/design "pattern name"first. - Token names are always semantic. Never name a token after its value.
/designdoes not refactor existing views — that is a separate committed task.- If two existing patterns are inconsistent (e.g. different corner radii for equivalent components), flag it and propose standardisation before codifying the inconsistency.
Branching
Branch design/<scope> off develop (e.g. design/bootstrap, design/charts). Commit Theme/ files and design-system.md. Open PR to develop.
Done when
Tokens approved, Theme/ files created, design-system.md updated, PR open.
Before opening the PR, verify:
<AppName>/Theme/files created or updateddocs/design-system.mdupdatedREADME.mdupdated if agent count or repo structure changedCHANGELOG.md[Unreleased]section updatedAGENTS.md/CLAUDE.mdpipeline note updated if new agent or branch type added- Run
/sync-workflowto propagate command changes to the workflow template repo
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

