DesignAgent Guardrails (Contract Compliance)
These are hard constraints. Do NOT violate:
- Do not skip any step in contract.json entry.steps
- Do not merge or reorder output sections
- Do not invent data or hallucinate facts
- Do not execute outside the defined step order
- If input is incomplete, ask only for missing required fields
name: 01-intake
description: "Use when starting a new design project — gather context, constraints, stakeholders, and goals before entering the design process. First step of the DesignAgent linear workflow."
01-Intake: Project Intake
Overview
Every design project begins with intake — not research, not sketching, but understanding. Before you can discover anything, you need to know: what are we doing, who is it for, and what does success look like? This skill captures the brief, constraints, and stakeholder landscape. Output feeds directly into 02-discover.
Non-Negotiable Rule
HARD GATE: Complete intake before entering any design phase. If you cannot answer who the client is, what the deliverable is, and when it is due, you are not ready to design. No research, no solutions, no sketches — just understanding.
When To Use
- Starting any new design project
- A new request arrives with unclear scope, audience, or deliverables
- Before any research, sketching, or concept work
When NOT To Use
- "Open my Figma file" → just do it
- "What color is the logo?" → answer directly, this is a lookup
- "Resize this image" → this is production, not design
- Revisions to an existing project already in-flight → resume where you left off
Process
1. Capture the Brief
- What is the project? (type, scope, category)
- What are the deliverables? (list specific outputs)
- What is the timeline? (key milestones, drop-dead dates)
- What is the budget or resourcing? (if known)
2. Identify Stakeholders
- Who is the client / decision-maker?
- Who are the end users?
- Who else needs to approve?
- Who will implement / build / produce?
3. Surface Constraints
- Brand constraints (existing guidelines, equity)
- Platform / medium constraints (digital, print, physical)
- Technical / production constraints
- Regulatory or legal constraints
- Cultural or market constraints
4. Define Success Criteria
- What outcomes matter? (business, user, creative)
- How will success be measured?
- What does "done" look like?
- What are the non-negotiables from the client?
5. Assess Project Type
- Choose the DesignAgent workflow path:
- Brand / identity → include brand-strategy
- Interior / architecture → include interior-design or architecture-design
- UI/UX / product → include ui-ux-design
- Industrial / product design → include industrial-design
- General design → use core A-layer only
Rationalization Prevention
| Excuse |
Reality |
| "I already know the project, let me start" |
Write it down. Intake makes implicit assumptions explicit. |
| "We can figure out success criteria later" |
Define success now, or you won't know when you're done. |
| "The brief is simple, this is overkill" |
Simple briefs are where assumptions hide. Surface them. |
Red Flags
- You skipped intake and started sketching
- You cannot name the decision-maker
- Success criteria are vague ("make it look good")
- The timeline has no milestones
Verification
→ Continue to: use 02-discover to research users, context, and competition.
1---2name: 01-intake3description: DesignAgent Guardrails (Contract Compliance)4---5## DesignAgent Guardrails (Contract Compliance)67These are hard constraints. Do NOT violate:89- Do not skip any step in contract.json entry.steps10- Do not merge or reorder output sections11- Do not invent data or hallucinate facts12- Do not execute outside the defined step order13- If input is incomplete, ask only for missing required fields1415---16name: 01-intake17description: "Use when starting a new design project — gather context, constraints, stakeholders, and goals before entering the design process. First step of the DesignAgent linear workflow."18---1920# 01-Intake: Project Intake2122## Overview23Every design project begins with intake — not research, not sketching, but understanding. Before you can discover anything, you need to know: what are we doing, who is it for, and what does success look like? This skill captures the brief, constraints, and stakeholder landscape. Output feeds directly into 02-discover.2425## Non-Negotiable Rule26**HARD GATE: Complete intake before entering any design phase.** If you cannot answer who the client is, what the deliverable is, and when it is due, you are not ready to design. No research, no solutions, no sketches — just understanding.2728## When To Use29- Starting any new design project30- A new request arrives with unclear scope, audience, or deliverables31- Before any research, sketching, or concept work3233## When NOT To Use34- "Open my Figma file" → just do it35- "What color is the logo?" → answer directly, this is a lookup36- "Resize this image" → this is production, not design37- Revisions to an existing project already in-flight → resume where you left off3839## Process4041### 1. Capture the Brief42- What is the project? (type, scope, category)43- What are the deliverables? (list specific outputs)44- What is the timeline? (key milestones, drop-dead dates)45- What is the budget or resourcing? (if known)4647### 2. Identify Stakeholders48- Who is the client / decision-maker?49- Who are the end users?50- Who else needs to approve?51- Who will implement / build / produce?5253### 3. Surface Constraints54- Brand constraints (existing guidelines, equity)55- Platform / medium constraints (digital, print, physical)56- Technical / production constraints57- Regulatory or legal constraints58- Cultural or market constraints5960### 4. Define Success Criteria61- What outcomes matter? (business, user, creative)62- How will success be measured?63- What does "done" look like?64- What are the non-negotiables from the client?6566### 5. Assess Project Type67- Choose the DesignAgent workflow path:68 - Brand / identity → include brand-strategy69 - Interior / architecture → include interior-design or architecture-design70 - UI/UX / product → include ui-ux-design71 - Industrial / product design → include industrial-design72 - General design → use core A-layer only7374## Rationalization Prevention7576| Excuse | Reality |77|--------|---------|78| "I already know the project, let me start" | Write it down. Intake makes implicit assumptions explicit. |79| "We can figure out success criteria later" | Define success now, or you won't know when you're done. |80| "The brief is simple, this is overkill" | Simple briefs are where assumptions hide. Surface them. |8182## Red Flags83- You skipped intake and started sketching84- You cannot name the decision-maker85- Success criteria are vague ("make it look good")86- The timeline has no milestones8788## Verification89- [ ] Project brief captured in one paragraph90- [ ] Key stakeholder identified with role91- [ ] At least 3 constraints documented92- [ ] Success criteria defined (not just "looks good")93- [ ] DesignAgent workflow path selected94- [ ] Next phase confirmed before proceeding9596→ Continue to: use **02-discover** to research users, context, and competition.