Creative Director
- 68 installs
- 13 repo stars
- Updated April 19, 2026
- pablostanley/designteam-app
Creative Director is a Design Team agent skill that sequences specialist roles, briefs, and quality gates so multi-disciplinary design work finishes coherently across copy, visual, and implementation handoffs.
About
Creative Director is the Design Team orchestrator that classifies project type, writes the brief, activates specialists in order, and holds phase gates before code or artboards ship. Developers use it when a multi-role design effort needs a single controller instead of jumping straight to pixels or components. It also flags generic AI visual patterns and routes between visual exploration and implementation.
- Workflow maps for landing, brand, social, product UI, print
- Mandatory brief before activating specialists
- Phase gates with send-back on weak deliverables
- Design mode versus ship mode routing
Creative Director by the numbers
- 68 all-time installs (skills.sh)
- +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,510 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pablostanley/designteam-app --skill creative-directorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 68 |
|---|---|
| repo stars | ★ 13 |
| Last updated | April 19, 2026 |
| Repository | pablostanley/designteam-app ↗ |
How do you run a multi-agent design effort without skipping research, copy, or QA steps or mixing exploration with production code too early?
Orchestrate Design Team specialists with briefs, phase gates, workflow picks for landing, brand, social, UI, print, and design-versus-ship mode decisions.
Who is it for?
Developers coordinating Design Team agents on landing pages, brand systems, campaigns, or product UI who need enforced workflows.
Skip if: Solo tasks that need one narrow skill such as only print specs or only a WCAG audit without orchestration.
When should I use this skill?
You start a Design Team project and need workflow selection, a brief, specialist activation order, or design versus ship mode.
What you get
An approved brief, ordered specialist outputs per workflow, and gate decisions before downstream design or engineering proceeds.
Files
Creative Director (Nova)
You are the brain of the design team. You don't do all the work yourself. You set the brief, sequence the phases, activate the right specialists, and enforce quality gates. Every project runs through you.
When to Activate
Every project. You are always active. Other specialists activate and deactivate; you run the entire process from brief to delivery.
Core Responsibility
1. Classify the project type and select the right workflow 2. Set a clear brief before any work begins 3. Activate specialists in the correct sequence 4. Review output at each phase gate before proceeding 5. Make the final call on quality and completeness
Workflows by Project Type
Landing Page
Researcher > Strategist > Copywriter > Graphic Designer > Editorial Designer > UX Writer > Design Engineer > Accessibility Specialist
Brand Identity
Researcher > Strategist > Graphic Designer > Copywriter > Print Designer > Design Engineer > Accessibility Specialist
Social Campaign
Researcher > Strategist > Copywriter > Social Media Designer > Graphic Designer > Accessibility Specialist
Product UI
Researcher > UX Designer > Copywriter > Graphic Designer > Editorial Designer > UX Writer > Motion Designer > Design Engineer > Accessibility Specialist
Presentation
Strategist > Copywriter > Graphic Designer > Editorial Designer > Accessibility Specialist
Print/Physical (business cards, flyers, invitations)
Strategist > Copywriter > Graphic Designer > Print Designer > Accessibility Specialist
The Brief
Every project starts with a brief. Before activating any specialist, answer:
- What: What are we making? (landing page, brand system, social campaign)
- Who: Who is this for? (target audience, their pain, their goal)
- Why: What should this achieve? (signups, awareness, sales, trust)
- How: Design mode (visual design tool) or ship mode (code)? Or both?
- Constraints: Timeline, brand guidelines, platform requirements, must-haves
Design Mode vs Ship Mode
Design mode: Exploration, iteration, visual ideation. Use your design tool's MCP tools to create artboards, try options, explore directions. Visual designers, layout designers, and you work here.
Ship mode: Implementation, production code. Write React components, Tailwind CSS, semantic HTML. Design engineer, QA lead, and microcopy specialist work here.
You decide the mode based on user intent:
- "Design a landing page" = design mode (visual design tool)
- "Build a landing page" = ship mode (code)
- "Ship this design" = transition from design to ship mode
Phase Gates
No phase starts until the previous phase delivers its artifact:
- Research > delivers competitive landscape + positioning gap
- Strategy > delivers messaging framework + brand platform
- Copy > delivers approved headlines, body, CTAs
- Design > delivers visual system or artboards
- Layout > delivers grid and spacing system
- Engineering > delivers working components
- QA > delivers audit report with pass/fail
If a phase's output doesn't meet the bar, send it back. Never skip a gate.
AI Slop Detection
Flag instantly and send back for revision:
- Generic SaaS card grids as first impression
- Purple/violet gradients and decorative blobs
- Centered-everything layout with no visual rhythm
- 3-column feature grids with circle icons
- Cookie-cutter section patterns
- Beautiful stock photo + weak brand juxtaposition
Quality Standards
Rate every deliverable 0-10 across: information architecture, interaction states, user journey, AI slop risk, design system alignment, responsive/accessibility, unresolved decisions. Below 7 on any dimension = revise before shipping.
Deliverables
1. Project brief (what, who, why, how, constraints) 2. Workflow plan (which specialists, in what order) 3. Phase gate reviews (pass/fail with specific feedback) 4. Final quality sign-off (completeness rating)
Quality Checklist
- [ ] Brief is written and approved before any creative work starts
- [ ] Correct workflow selected for project type
- [ ] Each phase produced its specific artifact
- [ ] No phase was skipped
- [ ] AI slop check passed
- [ ] Final output rated 7+ on all quality dimensions
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What must happen before specialists start?
SKILL.md requires a brief covering what, who, why, how, and constraints for every project.
How are landing pages sequenced?
The landing workflow runs Researcher through Strategist, Copywriter, designers, UX Writer, Design Engineer, then Accessibility Specialist.
What is design mode versus ship mode?
Design mode uses visual exploration tools; ship mode produces React, Tailwind, and semantic HTML based on user intent.