arla6ka
12 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
arla6kadesign-system-boss
Use for vague whole-app design system asks on an app that already ships UI, such as "our UI is a mess, fix it", "we need a design system", "we hardcode colors everywhere", "make the buttons consistent" or "check the app before I ship". One named screen goes to ui-review, one component to component-docs, a token report to token-mapping. A repo with no UI yet is out of scope.
- instalacje
- 2
- GitHub Stars
- 141
- Aktualizacja
- 19 paź
arla6kamigrate-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. Not for making the system or for swapping raw values for tokens, which are build-design-system.
- instalacje
- 2
- GitHub Stars
- 141
- Aktualizacja
- 19 paź
arla6katoken-mapping
Use to report how hardcoded style values on a page, file or diff map onto a project's existing design tokens, such as "are we using our tokens here", "which hardcoded colors map to which tokens", a token audit or planning a token migration. It never edits. Replacing the values is build-design-system.
- instalacje
- 2
- GitHub Stars
- 141
- Aktualizacja
- 19 paź
arla6kaui-review
Use to critique a screen, flow, prototype or running build, accessibility included, and rank what is broken, such as "check this page before I ship", "is this flow ready", "is it accessible", keyboard or screen-reader checks, "it feels off on my phone" or "it feels janky". Not for token compliance, which is token-mapping.
- instalacje
- 2
- GitHub Stars
- 141
- Aktualizacja
- 19 paź
arla6katoken-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.
- instalacje
- 2
- GitHub Stars
- 51
- Aktualizacja
- 5 paź
arla6kabuild-design-system
Use when someone wants a design system built from the UI an app already ships, or one phase of it, such as "extract tokens from the app", "add states to our Button", "replace the hardcoded colors with tokens" or "start a design system". Moving screens onto an existing system's components is migrate-design-system. A vague whole-app ask goes to design-system-boss.
- instalacje
- 1
- GitHub Stars
- 146
- Aktualizacja
- 20 paź
arla6kacomponent-docs
Use to write one component's documentation entry from its code, stories and real call sites, such as "document the button", "write docs for Select", "what states does Toast have", or usage rules for a new or changed component. Not for foundations or pages that span components, which no skill here writes, nor for changing the component, which is build-design-system.
- instalacje
- 1
- GitHub Stars
- 146
- Aktualizacja
- 20 paź
arla6kabuild-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.
- instalacje
- 1
- GitHub Stars
- 32
- Aktualizacja
- 5 paź
arla6kacomponent-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.
- instalacje
- 1
- GitHub Stars
- 32
- Aktualizacja
- 5 paź
arla6kadesign-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 component-docs, an empty repo to build-design-system.
- instalacje
- 1
- GitHub Stars
- 32
- Aktualizacja
- 5 paź
arla6kamigrate-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.
- instalacje
- 1
- GitHub Stars
- 32
- Aktualizacja
- 5 paź
arla6kaui-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-mapping.
- instalacje
- 1
- GitHub Stars
- 32
- Aktualizacja
- 5 paź