{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "arla6ka-design-how--build-design-system-from-app",
 "repo": "arla6ka/design.how",
 "repo_url": "https://github.com/arla6ka/design.how",
 "repo_slug": "arla6ka-design-how",
 "title": "Build a design system from your existing app UI",
 "page_title": "How to build a design system from your existing app UI with Design How",
 "summary": "Turn the screens your app already ships into tokens, components, docs and checks.",
 "who": "A frontend developer whose app has three buttons, dozens of grays and a token file that half the code ignores, and who wants one system an agent can follow.",
 "problem": "Agents copy whatever is in the repo, so every new screen picks a different button, gray or spacing value.",
 "outcome": "A tokenized system with one canonical component per family, docs, checks, and one real flow moved onto it, on a new run branch.",
 "steps": [
  "Run `npx skills@latest add arla6ka/design.how` in your app repository to install the six skills.",
  "Open your coding agent in the repo and describe what is wrong in plain words, then ask it to run design-system-boss.",
  "Let the agent build tokens, components and docs with build-design-system, and review the flow it proves the system on.",
  "Check the CI check it adds, and read the migration size it offers before deciding on a full migration."
 ],
 "agent_prompt": "In the arla6ka/design.how skills installed in this repo, run design-system-boss on <target app path>. Report the tokens, canonical components, docs and CI check it creates, plus the run branch name. Verify that no commit landed on the default branch.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "1 hour",
 "basis": "readme",
 "caveat": "The README says merging is your call and the skills never commit to your default branch, so you still review and merge the run branch yourself.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A coding agent that reads skills, such as Claude Code",
  "Node.js, since the install and scripts run through npx and node",
  "Your app in a git repository, since the skills commit to a run branch",
  "Playwright and a Chromium browser for the scripts that drive a browser"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": true,
 "score": 1.0,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/arla6ka-design-how/build-design-system-from-app/",
 "md": "https://dedupedai.com/use-cases/arla6ka-design-how/build-design-system-from-app/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/arla6ka-design-how--build-design-system-from-app.json",
 "api_version": "v1"
}