agentsclimarketplace

Amby design

Skill ambystechcom/AmbyKit/.agents/skills/amby-design

Spec-Driven Development framework that helps AI coding assistants build better software — author your specs, user stories, UI design, plans and tasks once, and emit native config for Claude Code, OpenCode, GitHub Copilot, Cursor, Antigravity and more.

Install
npx -y skills add ambystechcom/AmbyKit --skill amby-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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.

What its author says it does

Copied from the file, not written here

Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.

SKILL.md

1.3 KB, 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.

  1. Write ui.md following 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 the US-#, and content/accessibility notes (WCAG AA).
  2. Write/extend design-tokens.json in three tiers — primitive → semantic → component. In ui.md cite semantic/component token names, never raw values.
  3. Keep the UI consistent with any constitution UX principle (cite by number).
  4. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.