[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS878WMWBCNYDXZEZ4T4AX":3,"skill-same:01M7CS878WMWBCNYDXZEZ4T4AX":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CS878WMWBCNYDXZEZ4T4AX","mobile-design-system-foundation",null,"Use when the mobile repository has no theme tokens or component library yet (a new app, an \"Apply design system\" task, or a task that asks for one), before building any screen - writes the approved design system's generated files from get_design_system (files true) and builds the theme from them when there is one.","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fmobile-design-system-foundation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mobile-design-system-foundation\ncategory: mobile\ndescription: Use when the mobile repository has no theme tokens or component library yet (a new app, an \"Apply design system\" task, or a task that asks for one), before building any screen - writes the approved design system's generated files from get_design_system (files true) and builds the theme from them when there is one.\nsource: ehmo\u002Fplatform-design-skills (MIT), android\u002Fskills (Apache-2.0), adapted\n---\n# Mobile Design System Foundation\n\n## Overview\n\nA screen built before tokens and an atomic component library exist turns into `Color(0x…)`, one-off paddings, and a library that never forms. This skill lays the foundation once, in order, so every screen after it is composition, not invention.\n\n**Core principle:** Lay the foundation before the first screen — tokens, folders, and the first atoms come before any feature work.\n\n## Detect first\n\n`get_design_system` with `files: true` for this repository before anything else. When it returns a design system, the direction is already decided and approved: skip the design direction below and materialize it instead. Write every file in `files` verbatim at its `path` — `DESIGN.md`, `design\u002Ftokens.json`, `design\u002Ftokens.css`, `design\u002FINVENTORY.md`; each carries a generated-file header and is never edited by hand, never transcribed. Then build the stack's theme from `design\u002Ftokens.json` by role (Flutter: `ColorScheme` light and dark plus `ThemeExtension`s for spacing, radius and sizes; SwiftUI: asset-catalog colour sets with Any\u002FDark appearances plus `Theme.swift` for type, spacing and radius; Compose: `Color.kt` \u002F `Theme.kt` \u002F `Type.kt` \u002F `Shape.kt` with a light and a dark `ColorScheme`), each value exactly as its token holds it and named after it (`color.light.primary` → `primary`). Use the colours as given — no `ColorScheme.fromSeed` that would recompute them. The repository's own `INVENTORY.md` lists its components under the names `design\u002FINVENTORY.md` gives them. A theme that already exists but differs from it gets its VALUES updated to the design system's, its structure kept. Only an empty answer leaves the direction to you.\n\nA `ThemeData`\u002F`ThemeExtension`, an asset-catalog colour set, a `MaterialTheme` wrapper, or an `INVENTORY.md` already present (and, when `get_design_system` returned a design system, the generated `design\u002F` files present and matching it) means this skill doesn't apply — stop, map and follow the existing structure (`flutter-atomic-components` \u002F `mobile-ui-ux`) instead.\n\n## Design direction (5 minutes, written into the plan, not a separate doc)\n\nOnly when `get_design_system` returned nothing. One line each, from the task brief (the brief's own words win over any default below): **audience + tone**; **4–6 named brand colours** mapped onto semantic roles (primary\u002Fsecondary\u002Ferror at minimum); **type pairing**; **radius** choice; **ASCII wireframe** of the key screen at phone (360) and tablet (768) width.\n\n## Per-stack tokens\n\n**Flutter (verified: `flutter analyze` clean):**\n\n```dart\n@immutable\nclass AppSpacing extends ThemeExtension\u003CAppSpacing> {\n  const AppSpacing({this.xs = 4, this.sm = 8, this.md = 16, this.lg = 24, this.xl = 32});\n  final double xs, sm, md, lg, xl;\n  @override AppSpacing copyWith({double? xs, double? sm, double? md, double? lg, double? xl}) =>\n      AppSpacing(xs: xs ?? this.xs, sm: sm ?? this.sm, md: md ?? this.md, lg: lg ?? this.lg, xl: xl ?? this.xl);\n  @override AppSpacing lerp(AppSpacing? other, double t) => this;\n}\n\nThemeData buildTheme(Brightness b) => ThemeData(\n  colorScheme: ColorScheme.fromSeed(seedColor: const Color(0xFF2F5BEA), brightness: b),  \u002F\u002F brand colour lives ONLY here\n  extensions: const [AppSpacing()],\n);\n\nextension AppThemeX on BuildContext {\n  AppSpacing get space => Theme.of(this).extension\u003CAppSpacing>()!;\n  ColorScheme get colors => Theme.of(this).colorScheme;\n}\n```\n\nFolders: `lib\u002Fui\u002Fcore\u002F{theme,atoms,molecules,organisms}` + `lib\u002Fui\u002Ffeatures\u002F\u003Cf>\u002F` — this is the official Flutter architecture layout; follow the repo's existing layout if it already has one (e.g. `lib\u002Fui\u002Fatoms`).\n\n**SwiftUI:** asset-catalog colour sets with Any\u002FDark appearances, `enum Space { static let xs: CGFloat = 4; static let sm: CGFloat = 8; static let md: CGFloat = 16; static let lg: CGFloat = 24 }`, semantic `Font` text styles (never `.system(size:)` outside the theme), `@ScaledMetric` for any custom sizing so it still follows Dynamic Type.\n\n**Compose:** `data class AppSpacing(val xs: Dp = 4.dp, val sm: Dp = 8.dp, val md: Dp = 16.dp, val lg: Dp = 24.dp)`, `val LocalSpacing = staticCompositionLocalOf { AppSpacing() }`, `val MaterialTheme.spacing @Composable get() = LocalSpacing.current`; wrap the app in `MaterialTheme(colorScheme = …)` with dynamic colour on API 12+ and a static fallback below it.\n\n## Folders and inventory\n\nCreate the atomic folders (`atoms\u002Fmolecules\u002Forganisms`, or the repo's existing naming) plus `INVENTORY.md` — header line `One line per component: level · name · purpose · variants`, one bullet per component added in the same commit that creates it.\n\nBase atoms to start from: `AppButton`, `AppTextField`, `AppIcon`, `StatusChip`, `Skeleton`, `EmptyState`, `ErrorView`.\n\n## ui-guard as a test inside the normal suite\n\nWire a guard that runs inside the ordinary test command, so the build gate enforces it — not a separate CI step that can be skipped.\n\n**Flutter (verified: flags 4 violations in a raw-styled atom, passes on the token version):**\n\n```dart\n\u002F\u002F test\u002Fui_guard_test.dart — runs inside `flutter test`, so the build gate enforces it\nfinal banned = \u003CString, RegExp>{\n  'raw colour (use context.colors \u002F ColorScheme)': RegExp(r'Color\\(0x|Colors\\.(?!transparent)'),\n  'raw font size (use textTheme)': RegExp(r'fontSize:\\s*\\d'),\n  'raw spacing (use context.space)': RegExp(r'EdgeInsets\\.(all|symmetric|only|fromLTRB)\\([^)]*\\d'),\n};\n\u002F\u002F walks lib\u002Fui\u002F**.dart except lib\u002Fui\u002F**\u002Ftheme\u002F**, collects \"path:line reason\", expect(offenders, isEmpty)\n```\n\n**Compose:** a JVM unit test scanning `src\u002Fmain\u002F**\u002Fui\u002F**` (except `ui\u002Ftheme`) for `Color(0x` and a numeric literal inside `.padding(`.\n\n**iOS:** SwiftLint `custom_rules` (`Color\\(red:`, `\\.font\\(\\.system\\(size:`, `\\.padding\\(\\d`) when the repo already uses SwiftLint; skip if it doesn't rather than introducing a new lint dependency for this alone.\n\n## Worked Example\n\n```\n❌ Start writing a screen straight away: Color(0xFF2196F3) inline, EdgeInsets.all(16)\n   scattered across three widgets, no INVENTORY.md.\n\n✅ 1. Detect: no ThemeData\u002FThemeExtension found → this skill applies.\n   2. Design direction (one paragraph) → 3. buildTheme() + AppSpacing extension\n   → 4. lib\u002Fui\u002Fcore\u002F{theme,atoms,...} folders + INVENTORY.md → 5. AppButton,\n   StatusChip, Skeleton atoms + widget tests → 6. ui_guard_test.dart green\n   → 7. first screen, built entirely from atoms already in INVENTORY.md.\n```\n\n## Common Mistakes\n\n- Writing a screen before any tokens exist — every colour becomes a one-off hex.\n- Skipping `INVENTORY.md` — the next task re-invents a Button.\n- Wiring the ui-guard as a separate script instead of a test inside the normal suite, so a hand-off can skip it.\n- Introducing SwiftLint to a repo that doesn't already use it, just for the guard.\n\n## Red Flags\n\n- A component file with `Color(0x…)`, `Colors.*`, or a numeric `EdgeInsets`\u002F`.padding(` literal anywhere in the diff outside the theme files.\n- `lib\u002Fui\u002F` (or the repo's component folder) with no `INVENTORY.md`.\n- A primitive hand-rolled inline in a screen file instead of placed in the component library.\n","# Mobile Design System Foundation\n\n## Overview\n\nA screen built before tokens and an atomic component library exist turns into `Color(0x…)`, one-off paddings, and a library that never forms. This skill lays the foundation once, in order, so every screen after it is composition, not invention.\n\n**Core principle:** Lay the foundation before the first screen — tokens, folders, and the first atoms come before any feature work.\n\n## Detect first\n\n`get_design_system` with `files: true` for this repository before anything else. When it returns a design system, the direction is already decided and approved: skip the design direction below and materialize it instead. Write every file in `files` verbatim at its `path` — `DESIGN.md`, `design\u002Ftokens.json`, `design\u002Ftokens.css`, `design\u002FINVENTORY.md`; each carries a generated-file header and is never edited by hand, never transcribed. Then build the stack's theme from `design\u002Ftokens.json` by role (Flutter: `ColorScheme` light and dark plus `ThemeExtension`s for spacing, radius and sizes; SwiftUI: asset-catalog colour sets with Any\u002FDark appearances plus `Theme.swift` for type, spacing and radius; Compose: `Color.kt` \u002F `Theme.kt` \u002F `Type.kt` \u002F `Shape.kt` with a light and a dark `ColorScheme`), each value exactly as its token holds it and named after it (`color.light.primary` → `primary`). Use the colours as given — no `ColorScheme.fromSeed` that would recompute them. The repository's own `INVENTORY.md` lists its components under the names `design\u002FINVENTORY.md` gives them. A theme that already exists but differs from it gets its VALUES updated to the design system's, its structure kept. Only an empty answer leaves the direction to you.\n\nA `ThemeData`\u002F`ThemeExtension`, an asset-catalog colour set, a `MaterialTheme` wrapper, or an `INVENTORY.md` already present (and, when `get_design_system` returned a design system, the generated `design\u002F` files present and matching it) means this skill doesn't apply — stop, map and follow the existing structure (`flutter-atomic-components` \u002F `mobile-ui-ux`) instead.\n\n## Design direction (5 minutes, written into the plan, not a separate doc)\n\nOnly when `get_design_system` returned nothing. One line each, from the task brief (the brief's own words win over any default below): **audience + tone**; **4–6 named brand colours** mapped onto semantic roles (primary\u002Fsecondary\u002Ferror at minimum); **type pairing**; **radius** choice; **ASCII wireframe** of the key screen at phone (360) and tablet (768) width.\n\n## Per-stack tokens\n\n**Flutter (verified: `flutter analyze` clean):**\n\n```dart\n@immutable\nclass AppSpacing extends ThemeExtension\u003CAppSpacing> {\n  const AppSpacing({this.xs = 4, this.sm = 8, this.md = 16, this.lg = 24, this.xl = 32});\n  final double xs, sm, md, lg, xl;\n  @override AppSpacing copyWith({double? xs, double? sm, double? md, double? lg, double? xl}) =>\n      AppSpacing(xs: xs ?? this.xs, sm: sm ?? this.sm, md: md ?? this.md, lg: lg ?? this.lg, xl: xl ?? this.xl);\n  @override AppSpacing lerp(AppSpacing? other, double t) => this;\n}\n\nThemeData buildTheme(Brightness b) => ThemeData(\n  colorScheme: ColorScheme.fromSeed(seedColor: const Color(0xFF2F5BEA), brightness: b),  \u002F\u002F brand colour lives ONLY here\n  extensions: const [AppSpacing()],\n);\n\nextension AppThemeX on BuildContext {\n  AppSpacing get space => Theme.of(this).extension\u003CAppSpacing>()!;\n  ColorScheme get colors => Theme.of(this).colorScheme;\n}\n```\n\nFolders: `lib\u002Fui\u002Fcore\u002F{theme,atoms,molecules,organisms}` + `lib\u002Fui\u002Ffeatures\u002F\u003Cf>\u002F` — this is the official Flutter architecture layout; follow the repo's existing layout if it already has one (e.g. `lib\u002Fui\u002Fatoms`).\n\n**SwiftUI:** asset-catalog colour sets with Any\u002FDark appearances, `enum Space { static let xs: CGFloat = 4; static let sm: CGFloat = 8; static let md: CGFloat = 16; static let lg: CGFloat = 24 }`, semantic `Font` text styles (never `.system(size:)` outside the theme), `@ScaledMetric` for any custom sizing so it still follows Dynamic Type.\n\n**Compose:** `data class AppSpacing(val xs: Dp = 4.dp, val sm: Dp = 8.dp, val md: Dp = 16.dp, val lg: Dp = 24.dp)`, `val LocalSpacing = staticCompositionLocalOf { AppSpacing() }`, `val MaterialTheme.spacing @Composable get() = LocalSpacing.current`; wrap the app in `MaterialTheme(colorScheme = …)` with dynamic colour on API 12+ and a static fallback below it.\n\n## Folders and inventory\n\nCreate the atomic folders (`atoms\u002Fmolecules\u002Forganisms`, or the repo's existing naming) plus `INVENTORY.md` — header line `One line per component: level · name · purpose · variants`, one bullet per component added in the same commit that creates it.\n\nBase atoms to start from: `AppButton`, `AppTextField`, `AppIcon`, `StatusChip`, `Skeleton`, `EmptyState`, `ErrorView`.\n\n## ui-guard as a test inside the normal suite\n\nWire a guard that runs inside the ordinary test command, so the build gate enforces it — not a separate CI step that can be skipped.\n\n**Flutter (verified: flags 4 violations in a raw-styled atom, passes on the token version):**\n\n```dart\n\u002F\u002F test\u002Fui_guard_test.dart — runs inside `flutter test`, so the build gate enforces it\nfinal banned = \u003CString, RegExp>{\n  'raw colour (use context.colors \u002F ColorScheme)': RegExp(r'Color\\(0x|Colors\\.(?!transparent)'),\n  'raw font size (use textTheme)': RegExp(r'fontSize:\\s*\\d'),\n  'raw spacing (use context.space)': RegExp(r'EdgeInsets\\.(all|symmetric|only|fromLTRB)\\([^)]*\\d'),\n};\n\u002F\u002F walks lib\u002Fui\u002F**.dart except lib\u002Fui\u002F**\u002Ftheme\u002F**, collects \"path:line reason\", expect(offenders, isEmpty)\n```\n\n**Compose:** a JVM unit test scanning `src\u002Fmain\u002F**\u002Fui\u002F**` (except `ui\u002Ftheme`) for `Color(0x` and a numeric literal inside `.padding(`.\n\n**iOS:** SwiftLint `custom_rules` (`Color\\(red:`, `\\.font\\(\\.system\\(size:`, `\\.padding\\(\\d`) when the repo already uses SwiftLint; skip if it doesn't rather than introducing a new lint dependency for this alone.\n\n## Worked Example\n\n```\n❌ Start writing a screen straight away: Color(0xFF2196F3) inline, EdgeInsets.all(16)\n   scattered across three widgets, no INVENTORY.md.\n\n✅ 1. Detect: no ThemeData\u002FThemeExtension found → this skill applies.\n   2. Design direction (one paragraph) → 3. buildTheme() + AppSpacing extension\n   → 4. lib\u002Fui\u002Fcore\u002F{theme,atoms,...} folders + INVENTORY.md → 5. AppButton,\n   StatusChip, Skeleton atoms + widget tests → 6. ui_guard_test.dart green\n   → 7. first screen, built entirely from atoms already in INVENTORY.md.\n```\n\n## Common Mistakes\n\n- Writing a screen before any tokens exist — every colour becomes a one-off hex.\n- Skipping `INVENTORY.md` — the next task re-invents a Button.\n- Wiring the ui-guard as a separate script instead of a test inside the normal suite, so a hand-off can skip it.\n- Introducing SwiftLint to a repo that doesn't already use it, just for the guard.\n\n## Red Flags\n\n- A component file with `Color(0x…)`, `Colors.*`, or a numeric `EdgeInsets`\u002F`.padding(` literal anywhere in the diff outside the theme files.\n- `lib\u002Fui\u002F` (or the repo's component folder) with no `INVENTORY.md`.\n- A primitive hand-rolled inline in a screen file instead of placed in the component library.\n",{"name":5,"source":24,"category":25,"description":7},"ehmo\u002Fplatform-design-skills (MIT), android\u002Fskills (Apache-2.0), adapted","mobile","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fmobile-design-system-foundation",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill mobile-design-system-foundation",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill mobile-design-system-foundation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill mobile-design-system-foundation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fmobile-developer\u002Fskills\u002Fmobile-design-system-foundation\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]