Skill Tracer
Skills › BMAD Method › bmad-ux › design-directions.md

design-directions.md

9 lines · skills/bmad-ux/assets/design-directions.md at bd70c64

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Design Directions Renderer
2
3Subagent prompt. Produce 3-6 distinct visual directions for the product's hero screen, each a separate self-contained HTML file at `.working/direction-{name}.html` (or one combined `directions-{n}.html` if the parent's intent says side-by-side).
4
5Each direction is a *complete visual personality* applied to the same key screen — not a palette swap. Differ on density, type weight, motion implication, brand register. Each file: 2-3 sentence rationale, near-1:1 hero screen mockup in a phone or browser frame, ideally a secondary screen, at least one state variant visible (aging row, empty state, etc).
6
7Use real product content from the conversation. Voice/tone from `.memlog.md` applied to every visible string — no lorem. Inline CSS, system fonts, no JS or network. Document hex values in `<style>` comments per direction.
8
9Return to the parent: file paths, one-line personality summary per direction, what hero screen was depicted. Do not dump HTML into parent context. If interactive, open each file in the browser.

Design Directions Renderer

Subagent prompt. Produce 3-6 distinct visual directions for the product's hero screen, each a separate self-contained HTML file at .working/direction-{name}.html (or one combined directions-{n}.html if the parent's intent says side-by-side).

Each direction is a complete visual personality applied to the same key screen — not a palette swap. Differ on density, type weight, motion implication, brand register. Each file: 2-3 sentence rationale, near-1:1 hero screen mockup in a phone or browser frame, ideally a secondary screen, at least one state variant visible (aging row, empty state, etc).

Use real product content from the conversation. Voice/tone from .memlog.md applied to every visible string — no lorem. Inline CSS, system fonts, no JS or network. Document hex values in <style> comments per direction.

Return to the parent: file paths, one-line personality summary per direction, what hero screen was depicted. Do not dump HTML into parent context. If interactive, open each file in the browser.

Raw lines 1 to 9
Starts an agent Subagent :3