design

Define UI directions and generate ASCII wireframes with Change Specs for /arc:implement workflows.

26|2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/howells/arc --skill design-howells
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/howells/arc/tree/main/skills/design
Command: npx skills add https://github.com/howells/arc --skill design-howells

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams define distinctive UI directions and translate them into actionable design documentation.

Core Features & Use Cases

  • Phase-guided design: Guides from ideation to a concrete change spec including typography, color, spacing, layout, and motion decisions.
  • ASCII wireframes: Produces lightweight, version-controllable wireframes to communicate structure before coding.
  • Change-spec generation: Outputs a structured Change Spec that can be consumed by /arc:implement.

Quick Start

Use the design skill to begin a new UI direction, load references, and generate a Change Spec for the target component.

Frequently Asked Questions about design

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

FAQPage Schema
How do I translate a UI direction into actionable design documentation?

To translate a UI direction into actionable design documentation, define distinctive aesthetic choices for typography, color, spacing, layout, and motion, then output a structured Change Spec. This spec captures phase-aligned decisions and ASCII wireframes ready for implementation workflows.

What is the best way to create version-controllable wireframes for UI redesigns?

The best way to create version-controllable wireframes for UI redesigns is generating lightweight ASCII wireframes. These text-based structural layouts communicate component arrangement clearly without binary image files, ensuring seamless version tracking and team collaboration.

How do I define typography and color specifications when extending an existing UI?

To define typography and color specifications when extending an existing UI, apply phase-aligned design decisions across Phases 4-6. This process delivers explicit aesthetic directions, ensuring new interface elements match the established branding and visual language.

Can I generate a design change spec for a phase-guided UI workflow?

Yes, you can generate a design change spec for a phase-guided UI workflow. The process guides ideation through Phase 4-6, delivering concrete layout, spacing, and motion decisions that produce a consumable design document for implementation.

Does the generated design document work with the arc:implement workflow?

Yes, the generated design document works directly with the /arc:implement workflow. The output is a concrete Change Spec containing UI patterns, ASCII wireframes, and layout decisions structured specifically for consumption by the implementation phase.

When do I need ASCII wireframes for UI specification?

You need ASCII wireframes for UI specification when communicating structural layouts before coding begins. They provide a lightweight, version-controllable format to define component arrangement and page structure, ensuring design alignment prior to technical implementation.