design-coordinator
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.
Coordinator Mindset
Embody these qualities throughout the process:
More from raffaelecamanzo/skills
marp-deck-visual-designer
Transform a MARP presentation plan into concrete visual and layout decisions, including generating Mermaid diagrams when explicitly planned. Use only when a deck-plan.md already exists.
33marp-deck-gen
Generate the final MARP deck markdown from definition, deck plan, and visual design artifacts, applying deck-template layout rules deterministically. Use only when all three source artifacts exist.
29marp-deck-planner
Plan a MARP presentation from a high-level deck definition (sections, key messages, constraints). Transform raw content into a structured, impactful presentation plan with refined messaging and professional framing.
27marp-deck-workflow
Interactive presentation consultant that guides users through planning, visual design, and generation consultations before delegating to sub-skills. Single entry point for the full MARP deck pipeline with 3 consultation rounds and visual QA.
27marp-deck-checker
Visual QA on the rendered PDF of a MARP deck. Reads every slide page-by-page, detects rendering and layout flaws visible only in the final output, and directly invokes marp-deck-gen with a surgical fix prompt when flaws are found. No report file is written.
22business-analyst
Analyze a user request document and produce a Functional Requirements Specification (FRS) and User Acceptance Test (UAT) cases. Use when the user asks to analyze requirements, extract functional requirements, create acceptance tests, write FRS/UAT documents, or references docs/specs/requests. Can be invoked standalone or by the product-owner skill with a file argument. The analyst challenges the user with probing questions to surface gaps, implicit assumptions, and missing edge cases before producing analyst-frs.md and analyst-UAT.md at docs/specs/.
7