# Tui Web Design Orchestrator

> Generate structured design prompt packets for terminal UIs and web UIs from natural-language briefs. Use when the user requests a design prompt/packet for a TUI or web UI, or explicitly invokes this skill. A UI implementation request does not by itself select prompt-packet generation.

- Skill: `rahulrajaram/tui-web-design-orchestrator` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add rahulrajaram/tui-web-design-orchestrator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rahulrajaram/tui-web-design-orchestrator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: rahulrajaram (https://skillmd.com/u/rahulrajaram)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rahulrajaram/tui-web-design-orchestrator

---


# TUI/Web Design Orchestrator

Generate production-minded design prompt packets for `web-page`, `web-app`, `tui-dashboard`, and `tui-wizard` workflows.

## Usage

`/tui-web-design-orchestrator --mode <mode> --brief "<brief>" [options]`

## Arguments

- `--mode <web-page|web-app|tui-dashboard|tui-wizard>`: Required mode preset.
- `--brief "<text>"`: Required design brief.
- `--audience "<text>"`: Optional audience/persona.
- `--constraints "<text>"`: Optional constraint (repeatable).
- `--style "<text>"`: Optional style direction.
- `--tech "<text>"`: Optional implementation stack override.
- `--output <markdown|json>`: Optional output format (default: markdown).
- `--outfile <path>`: Optional path to write output file.
- `--component TEXT`: Repeat for components derived from the actual brief.
- `--name TEXT`: Optional explicit project name; otherwise a provisional label.

## Workflow

1. Bind `SKILL_DIR` to this loaded skill directory, validate mode/brief and
   derive components from the supplied jobs, data and constraints. Pass each as
   `--component TEXT`; do not copy a fixed preset layout into an unrelated brief.
2. Run the packet generator script:

```bash
python3 "$SKILL_DIR/scripts/design_prompt_packet.py" <selected-arguments>
```

3. If `--outfile` is provided, confirm the file path written.
4. If no `--outfile` is provided, return the generated packet inline.
5. If the user asks for stronger rationale or benchmarking, pull patterns from:
- [source-crawl-synthesis.md](references/source-crawl-synthesis.md)
- [design-prompt-blueprints.md](references/design-prompt-blueprints.md)

## Output Contract

A complete packet should include:

1. North star
2. Audience + assumptions
3. IA and component map
4. State matrix (`default`, `hover/focus`, `active`, `disabled`, `error`, `empty`, `loading`, `success`)
5. Accessibility checks
6. Implementation prompt
7. Review prompt

## Mode Guidance

- `web-page`: conversion narrative and responsive section flow.
- `web-app`: recurring workflow efficiency and data-heavy UI patterns.
- `tui-dashboard`: keyboard-first, split-pane, terminal-width-aware operations.
- `tui-wizard`: low-error multi-step guidance with confirmation checkpoints.

## Examples

```bash
# Web app packet
/tui-web-design-orchestrator --mode web-app --brief "Design a release-readiness dashboard" --audience "engineering managers"

# TUI packet with constraints
/tui-web-design-orchestrator --mode tui-dashboard --brief "Design an incident triage terminal UI" --audience "SRE on-call" --constraints "must run over SSH" --constraints "keyboard only"

# JSON output to file
/tui-web-design-orchestrator --mode web-page --brief "Design a landing page for devtool analytics" --output json --outfile /tmp/devtool-ui.json
```

## Guardrails

- Do not invent constraints that the user did not specify; state assumptions explicitly.
- Preserve all provided constraints in the final packet.
- Keep terminal modes keyboard-first and width-aware.
- Always include accessibility checks and explicit state coverage.

## Boundaries and completion

Non-goals: building the UI, selecting new dependencies or inventing a product
architecture. Must not: present preset panels, pricing, testimonials or invented
user requirements as brief facts. Use actual project terminology and distinguish
inferred component choices from constraints. Ask only when a missing material
product decision prevents a useful packet; routine layout options may be proposed
as assumptions. Return a packet faithful to the selected brief, with component
and state coverage tied to it. The packet is a proposal, not an implemented UI.