ateam-design

Generates design tokens, screen flows, and greyscale lofi prototypes from product context documents.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/subvisual/the-a-team --skill ateam-design-subvisual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ateam-design
Source: https://github.com/subvisual/the-a-team/tree/main/.claude/skills/ateam-design
Command: npx skills add https://github.com/subvisual/the-a-team --skill ateam-design-subvisual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a product discovery brief into a coherent, reviewable design set normally requires manual coordination of token systems, screen flows, and prototypes. This Skill conducts the design phase of the A-Team harness, producing durable design tokens, a design.md with screens and flows, and a navigable lofi prototype in one pass. ## Core Features & Use Cases - Design token generation: Creates or consumes durable tokens (scale.ts, palette.ts, shadcn-theme.css) under docs/product/design-system/ with WCAG checks and a create-once guarantee. - Screens & flows drafting: Derives screen graphs from wireflow briefs or JTBD documents, emitting an executable flow-contract JSON handoff. - Lofi prototype conduction: Builds a greyscale navigable prototype with runtime-swappable variants under docs/features/<slug>/lofi/, calibrated by fidelity settings. - Use Case: After discovery has captured jobs-to-be-done in docs/product/jtbd/, run the design phase to produce tokens, a design.md with derived calls and flags, and a lofi prototype ready for human gate review. ## Quick Start Run the design phase for the current feature using the existing docs/product context and report any blocking flags for the gate review.

Frequently Asked Questions about ateam-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the design phase in the A-Team harness?▼

Invoke the ateam-design skill after discovery has produced active jobs in docs/product/jtbd/ and a context.md with a Design context section. The orchestrator calls feature-cli.mjs start first, then the skill writes tokens, design.md, and the lofi before calling the completion command.

What artifacts does the design phase produce?▼

It produces durable design tokens (scale.ts, palette.ts, shadcn-theme.css) under docs/product/design-system/, a design.md with Screens & flows and derived calls, and a navigable greyscale lofi prototype under docs/features/<slug>/lofi/ with variant URLs.

Can the design skill run without wireflow briefs?▼

Yes. When briefs/ are absent it drafts screens and flows directly from the JTBD documents and prd.md if present, marking the section as derived without briefs so the gate reviews it as a proposal rather than settled fact.

What happens if there is no brand seed for the palette?▼

The skill runs a TBD-draft with neutral colors, semantics, and typography while leaving the brand as TBD, and raises a blocking flag for the gate. It never invents a brand seed to appear finished.

When does the design phase stop instead of drafting?▼

The one hard stop is a missing North Star: if docs/product/jtbd/ contains no active jobs, the skill leaves the phase in progress and reports that discovery must run first, since a design without jobs is decoration.

Does revising a design regenerate the design tokens?▼

No. Re-invocation overwrites design.md cleanly and regenerates lofi screens mapped from revision notes, but durable tokens only change through explicit delta edits or an explicit regeneration instruction in the revision notes.