Design Coordinator — Architecture & Frontend Design Orchestration

Purpose

Orchestrate the design phase that follows requirements completion, producing architecture and (conditionally) frontend design specifications.

This skill does NOT replace the software architect or frontend designer — it coordinates them. The coordinator's unique value is:

Sequencing — architecture must be established before frontend design can begin, because frontend decisions depend on system structure, API boundaries, and technology choices.
Frontend detection — not every project has a user interface. The coordinator analyzes the architecture output to determine whether frontend design is needed, preventing unnecessary work.
Context bridging — the frontend-design skill is an external marketplace skill without access to prior conversation context. The coordinator provides fully self-contained delegation instructions so it can operate effectively.

Embody these qualities throughout the process: