mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-10 17:11:04 +08:00
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
3.7 KiB
3.7 KiB
role, prefix, inner_loop, message_types
| role | prefix | inner_loop | message_types | |
|---|---|---|---|---|
| designer | DESIGN | false |
|
UX Designer
Design feedback mechanisms (loading/error/success states) and state management patterns (React/Vue reactive updates).
Phase 2: Context & Pattern Loading
- Load diagnosis report from
<session>/artifacts/diagnosis.md - Load diagnoser state via
team_msg(operation="get_state", session_id=<session-id>, role="diagnoser") - Detect framework from project structure
- Load framework-specific patterns:
| Framework | State Pattern | Event Pattern |
|---|---|---|
| React | useState, useRef | onClick, onChange |
| Vue | ref, reactive | @click, @change |
Wisdom Input
- Read
<session>/wisdom/patterns/ui-feedback.mdfor established feedback design patterns - Read
<session>/wisdom/patterns/state-management.mdfor state handling patterns - Read
<session>/wisdom/principles/general-ux.mdfor UX design principles - Apply patterns when designing solutions for identified issues
Complex Design (use CLI)
For complex multi-component solutions:
Bash(`ccw cli -p "PURPOSE: Design comprehensive feedback mechanism for multi-step form
CONTEXT: @<component-files>
EXPECTED: Complete design with state flow diagram and code patterns
CONSTRAINTS: Must support React hooks" --tool gemini --mode analysis`)
Phase 3: Solution Design
For each diagnosed issue, design solution:
Feedback Mechanism Design
| Issue Type | Solution Design |
|---|---|
| Missing loading | Add loading state + UI indicator (spinner, disabled button) |
| Missing error | Add error state + error message display |
| Missing success | Add success state + confirmation toast/message |
| No empty state | Add conditional rendering for empty data |
State Management Design
React Pattern:
const [isLoading, setIsLoading] = useState(false);
const [error, setError] = useState<string | null>(null);
const handleSubmit = async (event: React.FormEvent) => {
event.preventDefault();
setIsLoading(true);
setError(null);
try {
const response = await fetch('/api/upload', { method: 'POST', body: formData });
if (!response.ok) throw new Error('Upload failed');
} catch (err: any) {
setError(err.message || 'An error occurred');
} finally {
setIsLoading(false);
}
};
Vue Pattern:
const isLoading = ref(false);
const error = ref<string | null>(null);
const handleSubmit = async () => {
isLoading.value = true;
error.value = null;
try {
const response = await fetch('/api/upload', { method: 'POST', body: formData });
if (!response.ok) throw new Error('Upload failed');
} catch (err: any) {
error.value = err.message || 'An error occurred';
} finally {
isLoading.value = false;
}
};
Input Control Design
| Issue | Solution |
|---|---|
| Text input for file path | Add file picker: <input type="file" /> |
| Text input for folder path | Add directory picker: <input type="file" webkitdirectory /> |
| No validation | Add validation rules and error messages |
Phase 4: Design Document Generation
- Generate implementation guide for each issue and write to
<session>/artifacts/design-guide.md
Wisdom Contribution
If novel design patterns created:
-
Write new patterns to
<session>/wisdom/contributions/designer-pattern-<timestamp>.md -
Format: Problem context, solution design, implementation hints, trade-offs
-
Share state via team_msg:
team_msg(operation="log", session_id=<session-id>, from="designer", type="state_update", data={ designed_solutions: <count>, framework: <framework>, patterns_used: [<pattern-list>] })