From 4aec163441ec700587e3ef925dd1e40d10bacc03 Mon Sep 17 00:00:00 2001 From: catlog22 Date: Thu, 16 Oct 2025 10:41:38 +0800 Subject: [PATCH] refactor: reorganize memory commands and update brainstorm workflows MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Changes: - Move memory commands to .claude/commands/memory/ directory - Relocate update-memory-full.md and update-memory-related.md - Add new docs.md command for documentation workflows - Update brainstorm commands (api-designer, data-architect, system-architect, ui-designer, ux-expert) - Remove deprecated workflow/tools/docs.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../{workflow/tools => memory}/docs.md | 4 +-- .../{ => memory}/update-memory-full.md | 10 +++---- .../{ => memory}/update-memory-related.md | 10 +++---- .../workflow/brainstorm/api-designer.md | 19 ++++++++++++ .../workflow/brainstorm/data-architect.md | 20 +++++++++++++ .../workflow/brainstorm/system-architect.md | 19 ++++++++++++ .../workflow/brainstorm/ui-designer.md | 29 ++++++++++++++++--- .../commands/workflow/brainstorm/ux-expert.md | 29 ++++++++++++++++--- 8 files changed, 120 insertions(+), 20 deletions(-) rename .claude/commands/{workflow/tools => memory}/docs.md (99%) rename .claude/commands/{ => memory}/update-memory-full.md (97%) rename .claude/commands/{ => memory}/update-memory-related.md (98%) diff --git a/.claude/commands/workflow/tools/docs.md b/.claude/commands/memory/docs.md similarity index 99% rename from .claude/commands/workflow/tools/docs.md rename to .claude/commands/memory/docs.md index b1c1202b..098e1f71 100644 --- a/.claude/commands/workflow/tools/docs.md +++ b/.claude/commands/memory/docs.md @@ -4,7 +4,7 @@ description: Documentation planning and orchestration - creates structured docum argument-hint: "[path] [--tool ] [--mode ] [--cli-generate]" --- -# Documentation Workflow (/workflow:docs) +# Documentation Workflow (/memory:docs) ## Overview Lightweight planner that analyzes project structure, decomposes documentation work into tasks, and generates execution plans. Does NOT generate documentation content itself - delegates to doc-generator agent. @@ -37,7 +37,7 @@ Lightweight planner that analyzes project structure, decomposes documentation wo ## Parameters ```bash -/workflow:docs [path] [--tool ] [--mode ] [--cli-generate] +/memory:docs [path] [--tool ] [--mode ] [--cli-generate] ``` - **path**: Target directory (default: current directory) diff --git a/.claude/commands/update-memory-full.md b/.claude/commands/memory/update-memory-full.md similarity index 97% rename from .claude/commands/update-memory-full.md rename to .claude/commands/memory/update-memory-full.md index 1bc8647b..292f29b9 100644 --- a/.claude/commands/update-memory-full.md +++ b/.claude/commands/memory/update-memory-full.md @@ -1,10 +1,10 @@ --- -name: update-memory-full +name: update-full description: Complete project-wide CLAUDE.md documentation update argument-hint: "[--tool gemini|qwen|codex] [--path ]" --- -# Full Documentation Update (/update-memory-full) +# Full Documentation Update (/memory:update-full) ## Coordinator Role @@ -301,7 +301,7 @@ REQUIREMENTS: **Update configuration directory only:** ```bash -/update-memory-full --path .claude +/memory:update-full --path .claude ``` - Updates only .claude directory and subdirectories - Useful after workflow or command modifications @@ -309,7 +309,7 @@ REQUIREMENTS: **Update specific feature module:** ```bash -/update-memory-full --path src/features/auth +/memory:update-full --path src/features/auth ``` - Updates authentication feature and sub-modules - Ideal for feature-specific documentation @@ -317,7 +317,7 @@ REQUIREMENTS: **Update nested structure:** ```bash -/update-memory-full --path .claude/workflows/cli-templates +/memory:update-full --path .claude/workflows/cli-templates ``` - Updates deeply nested directory tree - Maintains relative path structure in output diff --git a/.claude/commands/update-memory-related.md b/.claude/commands/memory/update-memory-related.md similarity index 98% rename from .claude/commands/update-memory-related.md rename to .claude/commands/memory/update-memory-related.md index 31ee036c..d4c6fe25 100644 --- a/.claude/commands/update-memory-related.md +++ b/.claude/commands/memory/update-memory-related.md @@ -1,10 +1,10 @@ --- -name: update-memory-related +name: update-related description: Context-aware CLAUDE.md documentation updates based on recent changes argument-hint: "[--tool gemini|qwen|codex]" --- -# Related Documentation Update (/update-memory-related) +# Related Documentation Update (/memory:update-related) ## Coordinator Role @@ -268,13 +268,13 @@ REQUIREMENTS: ```bash # Daily development update (default: gemini) -/update-memory-related +/memory:update-related # After feature work with specific tool -/update-memory-related --tool qwen +/memory:update-related --tool qwen # Code quality review after implementation -/update-memory-related --tool codex +/memory:update-related --tool codex ``` ## Tool Parameter Reference diff --git a/.claude/commands/workflow/brainstorm/api-designer.md b/.claude/commands/workflow/brainstorm/api-designer.md index dd32d046..e9041e81 100644 --- a/.claude/commands/workflow/brainstorm/api-designer.md +++ b/.claude/commands/workflow/brainstorm/api-designer.md @@ -22,6 +22,25 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*) - **Data Contracts**: Request/response schemas, validation rules, and data transformation - **API Documentation**: OpenAPI/Swagger specifications and developer experience +### Role Boundaries & Responsibilities + +#### **What This Role OWNS (API Contract Within Architectural Framework)** +- **API Contract Definition**: Specific endpoint paths, HTTP methods, and status codes +- **Resource Modeling**: Mapping domain entities to RESTful resources or GraphQL types +- **Request/Response Schemas**: Detailed data contracts, validation rules, and error formats +- **API Versioning Strategy**: Version management, deprecation policies, and migration paths +- **Developer Experience**: API documentation (OpenAPI/Swagger), code examples, and SDKs + +#### **What This Role DOES NOT Own (Defers to Other Roles)** +- **System Architecture Decisions**: Microservices vs monolithic, overall communication patterns → Defers to **System Architect** +- **Canonical Data Model**: Underlying data schemas and entity relationships → Defers to **Data Architect** +- **UI/Frontend Integration**: How clients consume the API → Defers to **UI Designer** + +#### **Handoff Points** +- **FROM System Architect**: Receives architectural constraints (REST vs GraphQL, sync vs async) that define the design space +- **FROM Data Architect**: Receives canonical data model and translates it into public API data contracts (as projection/view) +- **TO Frontend Teams**: Provides complete API specifications, documentation, and integration guides + ## ⚙️ **Execution Protocol** ### Phase 1: Session & Framework Detection diff --git a/.claude/commands/workflow/brainstorm/data-architect.md b/.claude/commands/workflow/brainstorm/data-architect.md index 6da1884c..d049c4aa 100644 --- a/.claude/commands/workflow/brainstorm/data-architect.md +++ b/.claude/commands/workflow/brainstorm/data-architect.md @@ -22,6 +22,26 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*) - **Data Quality Management**: Data accuracy, completeness, and consistency - **Analytics and Insights**: Data analysis and business intelligence solutions +### Role Boundaries & Responsibilities + +#### **What This Role OWNS (Canonical Data Model - Source of Truth)** +- **Canonical Data Model**: The authoritative, system-wide data schema representing domain entities and relationships +- **Entity-Relationship Design**: Defining entities, attributes, relationships, and constraints +- **Data Normalization & Optimization**: Ensuring data integrity, reducing redundancy, and optimizing storage +- **Database Schema Design**: Physical database structures, indexes, partitioning strategies +- **Data Pipeline Architecture**: ETL/ELT processes, data warehousing, and analytics pipelines +- **Data Governance**: Data quality standards, retention policies, and compliance requirements + +#### **What This Role DOES NOT Own (Defers to Other Roles)** +- **API Data Contracts**: Public-facing request/response schemas exposed by APIs → Defers to **API Designer** +- **System Integration Patterns**: How services communicate at the macro level → Defers to **System Architect** +- **UI Data Presentation**: How data is displayed to users → Defers to **UI Designer** + +#### **Handoff Points** +- **TO API Designer**: Provides canonical data model that API Designer translates into public API data contracts (as projection/view) +- **TO System Architect**: Provides data flow requirements and storage constraints to inform system design +- **FROM System Architect**: Receives system-level integration requirements and scalability constraints + ## ⚙️ **Execution Protocol** ### Phase 1: Session & Framework Detection diff --git a/.claude/commands/workflow/brainstorm/system-architect.md b/.claude/commands/workflow/brainstorm/system-architect.md index fce42c32..bade34f9 100644 --- a/.claude/commands/workflow/brainstorm/system-architect.md +++ b/.claude/commands/workflow/brainstorm/system-architect.md @@ -22,6 +22,25 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*) - **Performance & Scalability**: Capacity planning and optimization strategies - **Integration Patterns**: System communication and data flow design +### Role Boundaries & Responsibilities + +#### **What This Role OWNS (Macro-Architecture)** +- **System-Level Architecture**: Service boundaries, deployment topology, and system composition +- **Cross-Service Communication Patterns**: Choosing between microservices/monolithic, event-driven/request-response, sync/async patterns +- **Technology Stack Decisions**: Language, framework, database, and infrastructure choices +- **Non-Functional Requirements**: Scalability, performance, availability, disaster recovery, and monitoring strategies +- **Integration Planning**: How systems and services connect at the macro level (not specific API contracts) + +#### **What This Role DOES NOT Own (Defers to Other Roles)** +- **API Contract Details**: Specific endpoint definitions, URL structures, HTTP methods → Defers to **API Designer** +- **Data Schemas**: Detailed data model design and entity relationships → Defers to **Data Architect** +- **UI/UX Design**: Interface design and user experience → Defers to **UX Expert** and **UI Designer** + +#### **Handoff Points** +- **TO API Designer**: Provides architectural constraints (REST vs GraphQL, sync vs async) that define the API design space +- **TO Data Architect**: Provides system-level data flow requirements and integration patterns +- **FROM Data Architect**: Receives canonical data model to inform system integration design + ## ⚙️ **Execution Protocol** ### Phase 1: Session & Framework Detection diff --git a/.claude/commands/workflow/brainstorm/ui-designer.md b/.claude/commands/workflow/brainstorm/ui-designer.md index a84c593a..699172f9 100644 --- a/.claude/commands/workflow/brainstorm/ui-designer.md +++ b/.claude/commands/workflow/brainstorm/ui-designer.md @@ -17,10 +17,31 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*) - **Agent Delegation**: Use conceptual-planning-agent for analysis generation ### Analysis Scope -- **User Experience Design**: Intuitive and efficient user experiences -- **Interface Design**: Beautiful and functional user interfaces -- **Interaction Design**: Smooth user interaction flows and micro-interactions -- **Accessibility Design**: Inclusive design meeting WCAG compliance +- **Visual Design**: Color palettes, typography, spacing, and visual hierarchy implementation +- **High-Fidelity Mockups**: Polished, pixel-perfect interface designs +- **Design System Implementation**: Component libraries, design tokens, and style guides +- **Micro-Interactions & Animations**: Transition effects, loading states, and interactive feedback +- **Responsive Design**: Layout adaptations for different screen sizes and devices + +### Role Boundaries & Responsibilities + +#### **What This Role OWNS (Concrete Visual Interface Implementation)** +- **Visual Design Language**: Colors, typography, iconography, spacing, and overall aesthetic +- **High-Fidelity Mockups**: Polished designs showing exactly how the interface will look +- **Design System Components**: Building and documenting reusable UI components (buttons, inputs, cards, etc.) +- **Design Tokens**: Defining variables for colors, spacing, typography that can be used in code +- **Micro-Interactions**: Hover states, transitions, animations, and interactive feedback details +- **Responsive Layouts**: Adapting designs for mobile, tablet, and desktop breakpoints + +#### **What This Role DOES NOT Own (Defers to Other Roles)** +- **User Research & Personas**: User behavior analysis and needs assessment → Defers to **UX Expert** +- **Information Architecture**: Content structure and navigation strategy → Defers to **UX Expert** +- **Low-Fidelity Wireframes**: Structural layouts without visual design → Defers to **UX Expert** + +#### **Handoff Points** +- **FROM UX Expert**: Receives wireframes, user flows, and information architecture as the foundation for visual design +- **TO Frontend Developers**: Provides design specifications, component libraries, and design tokens for implementation +- **WITH API Designer**: Coordinates on data presentation and form validation feedback (visual aspects only) ## ⚙️ **Execution Protocol** diff --git a/.claude/commands/workflow/brainstorm/ux-expert.md b/.claude/commands/workflow/brainstorm/ux-expert.md index 43a851c4..1af5d88e 100644 --- a/.claude/commands/workflow/brainstorm/ux-expert.md +++ b/.claude/commands/workflow/brainstorm/ux-expert.md @@ -17,10 +17,31 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*) - **Agent Delegation**: Use conceptual-planning-agent for analysis generation ### Analysis Scope -- **User Interface Design**: Visual hierarchy, layout patterns, and component design -- **Interaction Patterns**: User flows, navigation, and microinteractions -- **Usability Optimization**: Accessibility, cognitive load, and user testing strategies -- **Design Systems**: Component libraries, design tokens, and consistency frameworks +- **User Research**: User personas, behavioral analysis, and needs assessment +- **Information Architecture**: Content structure, navigation hierarchy, and mental models +- **User Journey Mapping**: User flows, task analysis, and interaction models +- **Usability Strategy**: Accessibility planning, cognitive load reduction, and user testing frameworks +- **Wireframing**: Low-fidelity layouts and structural prototypes (not visual design) + +### Role Boundaries & Responsibilities + +#### **What This Role OWNS (Abstract User Experience & Research)** +- **User Research & Personas**: Understanding target users, their goals, pain points, and behaviors +- **Information Architecture**: Organizing content and defining navigation structures at a conceptual level +- **User Journey Mapping**: Defining user flows, task sequences, and interaction models +- **Wireframes & Low-Fidelity Prototypes**: Structural layouts showing information hierarchy (boxes and arrows, not colors/fonts) +- **Usability Testing Strategy**: Planning user testing, A/B tests, and validation methods +- **Accessibility Planning**: WCAG compliance strategy and inclusive design principles + +#### **What This Role DOES NOT Own (Defers to Other Roles)** +- **Visual Design**: Colors, typography, spacing, visual style → Defers to **UI Designer** +- **High-Fidelity Mockups**: Polished, pixel-perfect designs → Defers to **UI Designer** +- **Component Implementation**: Design system components, CSS, animations → Defers to **UI Designer** + +#### **Handoff Points** +- **TO UI Designer**: Provides wireframes, user flows, and information architecture that UI Designer will transform into high-fidelity visual designs +- **FROM User Research**: May receive external research data to inform UX decisions +- **TO Product Owner**: Provides user insights and validation results to inform feature prioritization ## ⚙️ **Execution Protocol**