julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
126 lines
4.4 KiB
Markdown
126 lines
4.4 KiB
Markdown
---
|
|
name: 'step-02-define-component'
|
|
description: 'Create a new design system component or update an existing one'
|
|
|
|
# File References
|
|
nextStepFile: './step-03-validate-usage.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow-design-system.md'
|
|
---
|
|
|
|
# Step 2: Define or Update Component
|
|
|
|
## STEP GOAL:
|
|
|
|
Create a new design system component or update an existing one — defining its properties, states, variants, content, interactions, and responsive behavior.
|
|
|
|
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
|
|
### Universal Rules:
|
|
|
|
- 🛑 NEVER generate content without user input
|
|
- 📖 CRITICAL: Read the complete step file before taking any action
|
|
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
|
- 📋 YOU ARE A FACILITATOR, not a content generator
|
|
- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
|
|
|
### Role Reinforcement:
|
|
|
|
- ✅ You are Freya, a creative and thoughtful UX designer collaborating with the user
|
|
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
|
|
- ✅ We engage in collaborative dialogue, not command-response
|
|
- ✅ You bring design expertise and systematic thinking, user brings product vision and domain knowledge
|
|
- ✅ Maintain creative and thoughtful tone throughout
|
|
|
|
### Step-Specific Rules:
|
|
|
|
- 🎯 Focus on complete component definition using object-type templates
|
|
- 🚫 FORBIDDEN to skip complexity assessment
|
|
- 💬 Approach: Structured definition through properties, states, variants
|
|
- 📋 Reference object-types templates for consistent documentation
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
|
|
- 🎯 Define component through structured questions about properties, states, variants
|
|
- 💾 Save component definition to design system folder
|
|
- 📖 Reference object-types templates in `../data/object-types/templates/`
|
|
- 🚫 FORBIDDEN to save incomplete component definitions
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
|
|
- Available context: Design system inventory from step 01, object-type templates
|
|
- Focus: Single component definition
|
|
- Limits: Define one component at a time
|
|
- Dependencies: Design system review should be complete
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 1. Component Context
|
|
|
|
- What is this component? (name, purpose)
|
|
- Where is it used? (which pages/sections)
|
|
- Is it a variant of an existing component?
|
|
|
|
### 2. Define Component
|
|
|
|
Using the object-types templates in `../data/object-types/templates/`:
|
|
|
|
- **Properties:** configurable attributes
|
|
- **States:** default, hover, active, disabled, error, loading
|
|
- **Variants:** size, color, layout variations
|
|
- **Content:** text, images, labels
|
|
- **Interactions:** click, hover, focus behaviors
|
|
- **Responsive:** mobile, tablet, desktop adaptations
|
|
|
|
### 3. Complexity Assessment
|
|
|
|
Reference `../data/object-types/COMPLEXITY-ROUTER.md`:
|
|
|
|
- Simple (single element, few states)
|
|
- Moderate (multiple elements, several states)
|
|
- Complex (nested components, many interactions)
|
|
|
|
### 4. Save
|
|
|
|
Write component definition to `{output_folder}/D-Design-System/`
|
|
|
|
### 5. Present MENU OPTIONS
|
|
|
|
Display: "**Select an Option:** [C] Continue to Validate Usage | [R] Return to Review Current | [M] Return to Activity Menu"
|
|
|
|
#### Menu Handling Logic:
|
|
|
|
- IF C: Load, read entire file, then execute {nextStepFile}
|
|
- IF R: Load, read entire file, then execute ./step-01-review-current.md
|
|
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
|
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
|
|
|
|
#### EXECUTION RULES:
|
|
|
|
- ALWAYS halt and wait for user input after presenting menu
|
|
- User can chat or ask questions — always respond and then redisplay menu options
|
|
|
|
## CRITICAL STEP COMPLETION NOTE
|
|
|
|
ONLY WHEN the user selects an option from the menu and the component has been defined and saved will you proceed to the next step or return as directed.
|
|
|
|
---
|
|
|
|
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### ✅ SUCCESS:
|
|
|
|
- Component fully defined (properties, states, variants, content, interactions)
|
|
- Complexity assessment completed
|
|
- Component saved to design system folder
|
|
- User confirmed definition
|
|
|
|
### ❌ SYSTEM FAILURE:
|
|
|
|
- Saving incomplete component definition
|
|
- Skipping complexity assessment
|
|
- Not using object-type templates
|
|
- Generating component definition without user input
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|