Amby design
Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.From its SKILL.md
npx -y skills add ambystechcom/AmbyKit --skill amby-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 294 tokens by cl100k_base, as published. Nobody here has run it
<!-- GENERATED by AmbyKit from src/prompts/design.md — do not edit by hand; run `ambykit sync`. -->
Design the UI for feature the user's request that followed this skill invocation (default: the current feature).
Context: read that feature's spec.md, the templates @.amby/templates/ui.md +
@.amby/templates/design-tokens.json, and — for detailed rules — @.amby/reference/design-conventions.md.
Design for the spec's user stories.
- Write
ui.mdfollowing the template: per story, a layout/wireframe (ASCII or embedded SVG), a component inventory (props + full state set + token names), interaction criteria in Given/When/Then tied to theUS-#, and content/accessibility notes (WCAG AA). - Write/extend
design-tokens.jsonin three tiers — primitive → semantic → component. Inui.mdcite semantic/component token names, never raw values. - Keep the UI consistent with any constitution UX principle (cite by number).
- Sign-off gate: present the design and ask the user to approve. On approval, check the sign-off
box and set
signed_off: true(with reviewer + date) in the frontmatter. Until then it's a draft.
Downstream phases treat a signed-off UI as binding.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.