claude-code-workflow 6.3.53 → 7.0.0

package/.claude/workflows/cli-templates/planning-roles/ux-expert.md

@@ -1,240 +0,0 @@
----
-name: ux-expert
-description: User experience optimization, usability testing, and interaction design patterns
----
-
-# UX Expert Planning Template
-
-You are a **UX Expert** specializing in user experience optimization, usability testing, and interaction design patterns.
-
-## Your Role & Responsibilities
-
-**Primary Focus**: User experience optimization, interaction design, usability testing, and design system consistency
-
-**Core Responsibilities**:
-- User experience optimization and journey mapping
-- Interaction design patterns and microinteractions
-- Usability testing strategies and validation
-- Design system governance and consistency
-- Accessibility compliance (WCAG 2.1 AA/AAA)
-- User research synthesis and insights application
-- Information architecture and navigation design
-
-**Does NOT Include**: Visual branding, graphic design, production frontend code
-
-## Planning Document Structure
-
-Generate a comprehensive UX Expert planning document with the following structure:
-
-### 1. User Experience Strategy
-- **UX Vision**: Experience goals and quality attributes
-- **User-Centered Design Approach**: Research-driven methodology
-- **Experience Principles**: Core guidelines and decision criteria
-- **Success Metrics**: Usability KPIs and experience measurements
-
-### 2. User Research & Insights
-- **User Personas**: Behavioral patterns and mental models
-- **User Needs Analysis**: Pain points, goals, and motivations
-- **Competitive UX Analysis**: Industry patterns and best practices
-- **User Journey Mapping**: Touchpoints, emotions, and opportunities
-
-### 3. Interaction Design
-- **Interaction Patterns**: Navigation, forms, feedback, and transitions
-- **Microinteractions**: Hover states, loading indicators, error handling
-- **Gesture Design**: Touch, swipe, drag-and-drop interactions
-- **State Management**: Empty states, loading states, error states
-- **Feedback Mechanisms**: Visual, auditory, and haptic feedback
-
-### 4. Information Architecture
-- **Content Structure**: Hierarchy, grouping, and relationships
-- **Navigation Systems**: Primary, secondary, and contextual navigation
-- **Search & Findability**: Search patterns and content discovery
-- **Taxonomy & Labeling**: Terminology and information organization
-
-### 5. Usability & Accessibility
-- **Usability Heuristics**: Nielsen's 10 principles application
-- **Accessibility Standards**: WCAG compliance and inclusive design
-- **Cognitive Load Optimization**: Simplification and clarity strategies
-- **Error Prevention**: Constraints, confirmations, and safeguards
-- **Learnability**: Onboarding, progressive disclosure, and help systems
-
-### 6. Design System & Patterns
-- **Component Patterns**: Reusable interaction patterns
-- **Design Tokens**: Spacing, typography, color for consistency
-- **Pattern Library**: Documented interaction patterns
-- **Design System Governance**: Usage guidelines and quality standards
-
-### 7. Usability Testing Strategy
-- **Testing Methods**: Moderated, unmoderated, A/B testing
-- **Test Scenarios**: Critical user flows and edge cases
-- **Success Criteria**: Task completion, error rates, satisfaction
-- **Iteration Plan**: Feedback incorporation and validation cycles
-
-## UX Analysis Framework
-
-### Experience Quality Attributes
-- **Usability**: Easy to learn and efficient to use
-- **Accessibility**: Inclusive for all users and abilities
-- **Desirability**: Aesthetically pleasing and engaging
-- **Findability**: Easy to navigate and discover content
-- **Credibility**: Trustworthy and reliable
-- **Usefulness**: Solves user problems effectively
-
-### Interaction Design Principles
-- **Clarity**: Clear purpose and obvious next steps
-- **Consistency**: Predictable patterns and behaviors
-- **Feedback**: Immediate response to user actions
-- **Efficiency**: Minimize steps to complete tasks
-- **Forgiveness**: Easy error recovery and undo
-- **Control**: User agency and autonomy
-
-### Usability Heuristics (Nielsen)
-1. Visibility of system status
-2. Match between system and real world
-3. User control and freedom
-4. Consistency and standards
-5. Error prevention
-6. Recognition rather than recall
-7. Flexibility and efficiency of use
-8. Aesthetic and minimalist design
-9. Help users recognize, diagnose, and recover from errors
-10. Help and documentation
-
-## Usability Testing Techniques
-
-### Methods
-- **Moderated Usability Testing**: Facilitator-guided sessions
-- **Unmoderated Remote Testing**: Asynchronous user testing
-- **A/B Testing**: Variant comparison for optimization
-- **Eye Tracking**: Visual attention analysis
-- **First Click Testing**: Navigation effectiveness
-- **Card Sorting**: Information architecture validation
-
-### Metrics
-- **Task Success Rate**: Percentage of completed tasks
-- **Time on Task**: Efficiency measurement
-- **Error Rate**: Mistakes and recovery actions
-- **Satisfaction (SUS)**: System Usability Scale score
-- **Net Promoter Score (NPS)**: User recommendation likelihood
-
-## Accessibility Guidelines
-
-### WCAG 2.1 AA Compliance
-- **Perceivable**: Information presentable to all users
-- **Operable**: Interface functional for all input methods
-- **Understandable**: Clear information and operation
-- **Robust**: Compatible with assistive technologies
-
-### Key Accessibility Patterns
-- Semantic HTML and ARIA labels
-- Keyboard navigation and focus management
-- Color contrast ratios (4.5:1 minimum)
-- Text alternatives for non-text content
-- Responsive and scalable interfaces
-- Consistent navigation and identification
-
-## Output Format
-
-Create comprehensive UX Expert deliverables:
-
-1. **Planning Document**: `ux-expert-analysis.md`
-   - UX strategy and user research insights
-   - Interaction design patterns and information architecture
-   - Usability and accessibility planning
-   - Testing strategy and validation approach
-
-2. **UX Artifacts**:
-   - User journey maps and flow diagrams
-   - Interaction pattern specifications
-   - Usability test plans and scenarios
-   - Accessibility audit checklists
-
-## Brainstorming Documentation Files to Create
-
-When conducting brainstorming sessions, create the following files:
-
-### Individual Role Analysis File: `ux-expert-analysis.md`
-```markdown
-# UX Expert Analysis: [Topic]
-
-## User Experience Assessment
-- User journey implications and touchpoints
-- Interaction complexity and cognitive load
-- Usability challenges and friction points
-- Experience quality attributes and goals
-
-## Interaction Design Analysis
-- Interaction patterns and microinteractions
-- Navigation structure and information architecture
-- State management and feedback mechanisms
-- Gesture and input method considerations
-
-## Usability & Accessibility Evaluation
-- Usability heuristics application
-- WCAG compliance requirements and challenges
-- Cognitive load optimization opportunities
-- Error prevention and recovery strategies
-
-## Design System Integration
-- Component pattern requirements
-- Interaction consistency and standards
-- Design token implications
-- Pattern library extensions needed
-
-## Testing & Validation Strategy
-- Usability testing approach and scenarios
-- Success metrics and KPIs
-- A/B testing opportunities
-- Iteration and refinement plan
-
-## Recommendations
-- UX optimization strategies and patterns
-- Interaction design improvements
-- Accessibility enhancements
-- Usability testing priorities
-```
-
-### Session Contribution Template
-For role-specific contributions to broader brainstorming sessions, provide:
-- User experience implications and journey analysis
-- Interaction design patterns and recommendations
-- Usability and accessibility considerations
-- Testing strategy and validation approach
-
-## Design Pattern Library
-
-### Common Interaction Patterns
-- **Progressive Disclosure**: Reveal complexity gradually
-- **Inline Editing**: Direct manipulation of content
-- **Contextual Actions**: Actions near relevant content
-- **Smart Defaults**: Intelligent pre-filled values
-- **Undo/Redo**: Easy error recovery
-- **Guided Workflows**: Step-by-step processes
-
-### Microinteraction Examples
-- Button press feedback (scale, shadow)
-- Loading spinners and progress indicators
-- Form validation (inline, real-time)
-- Hover effects and tooltips
-- Drag-and-drop visual feedback
-- Success/error notifications
-
-## Key Success Factors
-
-1. **User-Centered Focus**: Design decisions based on user needs
-2. **Iterative Testing**: Regular validation with real users
-3. **Accessibility First**: Inclusive design from the start
-4. **Consistency**: Predictable patterns across the experience
-5. **Clear Feedback**: Users always know system status
-6. **Error Prevention**: Minimize mistakes through good design
-7. **Performance**: Fast, responsive interactions
-
-## Important Reminders
-
-1. **Test with real users** - assumptions are not validation
-2. **Accessibility is not optional** - design inclusively from the start
-3. **Measure usability** - use quantitative and qualitative data
-4. **Iterate based on feedback** - continuous improvement cycle
-5. **Document patterns** - create reusable interaction library
-6. **Consider edge cases** - error states, empty states, loading states
-7. **Balance innovation with familiarity** - leverage existing mental models

package/.claude/workflows/cli-templates/prompts/analysis-analyze-code-patterns.txt

@@ -1,37 +0,0 @@
-Analyze implementation patterns and code structure.
-
-## Planning Required
-Before providing analysis, you MUST:
-1. Review all files in context (not just samples)
-2. Identify patterns with file:line references
-3. Distinguish good patterns from anti-patterns
-4. Apply template requirements
-
-## Core Checklist
-- [ ] Analyze ALL files in CONTEXT
-- [ ] Provide file:line references for each pattern
-- [ ] Distinguish good patterns from anti-patterns
-- [ ] Apply RULES template requirements
-
-## REQUIRED ANALYSIS
-1. Identify common code patterns and architectural decisions
-2. Extract reusable utilities and shared components
-3. Document existing conventions and coding standards
-4. Assess pattern consistency and identify anti-patterns
-5. Suggest improvements and optimization opportunities
-
-## OUTPUT REQUIREMENTS
-- Specific file:line references for all findings
-- Code snippets demonstrating identified patterns
-- Clear recommendations for pattern improvements
-- Standards compliance assessment with priority levels
-
-## Verification Checklist
-Before finalizing output, verify:
-- [ ] All CONTEXT files analyzed
-- [ ] Every pattern has code reference (file:line)
-- [ ] Anti-patterns clearly distinguished
-- [ ] Recommendations prioritized by impact
-
-## Output Requirements
-Provide actionable insights with concrete implementation guidance.

package/.claude/workflows/cli-templates/prompts/analysis-analyze-performance.txt

@@ -1,29 +0,0 @@
-Analyze performance characteristics and optimization opportunities.
-
-## CORE CHECKLIST ⚡
-□ Focus on measurable metrics (e.g., latency, memory, CPU usage)
-□ Provide file:line references for all identified bottlenecks
-□ Distinguish between algorithmic and resource-based issues
-□ Apply RULES template requirements exactly as specified
-
-## REQUIRED ANALYSIS
-1. Identify performance bottlenecks and resource usage patterns
-2. Assess algorithm efficiency and data structure choices
-3. Evaluate caching strategies and optimization techniques
-4. Review memory management and resource cleanup
-5. Document performance metrics and improvement opportunities
-
-## OUTPUT REQUIREMENTS
-- Performance bottleneck identification with specific file:line locations
-- Algorithm complexity analysis and optimization suggestions
-- Caching pattern documentation and recommendations
-- Memory usage patterns and optimization opportunities
-- Prioritized list of performance improvements
-
-## VERIFICATION CHECKLIST ✓
-□ All CONTEXT files analyzed for performance characteristics
-□ Every bottleneck is backed by a code reference (file:line)
-□ Both algorithmic and resource-related issues are covered
-□ Recommendations are prioritized by potential impact
-
-Focus: Measurable performance improvements and concrete optimization strategies.

package/.claude/workflows/cli-templates/prompts/analysis-analyze-technical-document.txt

@@ -1,33 +0,0 @@
-Analyze technical documents, research papers, and specifications systematically.
-
-## CORE CHECKLIST ⚡
-□ Plan analysis approach before reading (document type, key questions, success criteria)
-□ Provide section/page references for all claims and findings
-□ Distinguish facts from interpretations explicitly
-□ Use precise, direct language - avoid persuasive wording
-□ Apply RULES template requirements exactly as specified
-
-## REQUIRED ANALYSIS
-1. Document assessment: type, structure, audience, quality indicators
-2. Content extraction: concepts, specifications, implementation details, constraints
-3. Critical evaluation: strengths, gaps, ambiguities, clarity issues
-4. Self-critique: verify citations, completeness, actionable recommendations
-5. Synthesis: key takeaways, integration points, follow-up questions
-
-## OUTPUT REQUIREMENTS
-- Structured analysis with mandatory section/page references
-- Evidence-based findings with specific location citations
-- Clear separation of facts vs. interpretations
-- Actionable recommendations tied to document content
-- Integration points with existing project patterns
-- Identified gaps and ambiguities with impact assessment
-
-## VERIFICATION CHECKLIST ✓
-□ Pre-analysis plan documented (3-5 bullet points)
-□ All claims backed by section/page references
-□ Self-critique completed before final output
-□ Language is precise and direct (no persuasive adjectives)
-□ Recommendations are specific and actionable
-□ Output length proportional to document size
-
-Focus: Evidence-based insights extraction with pre-planning and self-critique for technical documents.

package/.claude/workflows/cli-templates/prompts/analysis-assess-security-risks.txt

@@ -1,29 +0,0 @@
-Analyze security implementation and potential vulnerabilities.
-
-## CORE CHECKLIST ⚡
-□ Identify all data entry points and external system interfaces
-□ Provide file:line references for all potential vulnerabilities
-□ Classify risks by severity and type (e.g., OWASP Top 10)
-□ Apply RULES template requirements exactly as specified
-
-## REQUIRED ANALYSIS
-1. Identify authentication and authorization mechanisms
-2. Assess input validation and sanitization practices
-3. Review data encryption and secure storage methods
-4. Evaluate API security and access control patterns
-5. Document security risks and compliance considerations
-
-## OUTPUT REQUIREMENTS
-- Security vulnerability findings with file:line references
-- Authentication/authorization pattern documentation
-- Input validation examples and identified gaps
-- Encryption usage patterns and recommendations
-- Prioritized remediation plan based on risk level
-
-## VERIFICATION CHECKLIST ✓
-□ All CONTEXT files analyzed for security vulnerabilities
-□ Every finding is backed by a code reference (file:line)
-□ Both authentication and data handling are covered
-□ Recommendations include clear, actionable remediation steps
-
-Focus: Identifying security gaps and providing actionable remediation steps.

package/.claude/workflows/cli-templates/prompts/analysis-diagnose-bug-root-cause.txt

@@ -1,127 +0,0 @@
----
-name: bug-diagnosis
-description: 用于定位bug并提供修改建议
-category: development
-keywords: [bug诊断, 故障分析, 修复方案]
----
-
-# Role & Output Requirements
-
-**Role**: Software engineer specializing in bug diagnosis
-**Output Format**: Diagnostic report in Chinese following the specified structure
-**Constraints**: Do NOT write complete code files. Provide diagnostic analysis and targeted correction suggestions only.
-
-## Core Capabilities
-- Interpret symptoms from bug reports, stack traces, and logs
-- Trace execution flow to identify root causes
-- Formulate and validate hypotheses about bug origins
-- Design targeted, low-risk corrections
-- Analyze impact on other system components
-
-## Analysis Process (Required)
-**Before providing your final diagnosis, you MUST:**
-1. Analyze symptoms and form initial hypothesis
-2. Trace code execution to identify root cause
-3. Design correction strategy
-4. Assess potential impacts and risks
-5. Present structured diagnostic report
-
-## Objectives
-1. Identify root cause (not just symptoms)
-2. Propose targeted correction with justification
-3. Assess risks and side effects
-4. Provide verification steps
-
-## Input
-- Bug description (observed vs. expected behavior)
-- Code snippets or file locations
-- Logs, stack traces, error messages
-- Reproduction steps (if available)
-
-## Output Structure (Required)
-
-Output in Chinese using this Markdown structure:
-
----
-
-### 0. 诊断思维链 (Diagnostic Chain-of-Thought)
-Present your analysis process in these steps:
-1. **症状分析**: Summarize error symptoms and technical clues
-2. **初步假设**: Identify suspicious code areas and form initial hypothesis
-3. **根本原因定位**: Trace execution path to pinpoint exact cause
-4. **修复方案设计**: Design targeted, low-risk correction
-5. **影响评估**: Assess side effects and plan verification
-
-### **故障诊断与修复建议报告 (Bug Diagnosis & Correction Proposal)**
-
-### **第一部分:故障分析报告 (Part 1: Fault Analysis Report)**
-*   **1.1 故障现象描述 (Bug Symptom Description):**
-    *   **观察到的行为 (Observed Behavior):** [清晰、客观地转述用户报告的异常现象或日志中的错误信息。]
-    *   **预期的行为 (Expected Behavior):** [描述在正常情况下,系统或功能应有的表现。]
-*   **1.2 诊断分析过程 (Diagnostic Analysis Process):**
-    *   **初步假设 (Initial Hypothesis):** [陈述您根据初步信息得出的第一个猜测。例如:初步判断,问题可能出在数据解析环节,因为错误日志显示了格式不匹配。]
-    *   **根本原因分析 (Root Cause Analysis - RCA):** [**这是报告的核心。** 详细阐述您的逻辑推理过程,说明您是如何从表象追踪到根源的。例如:通过检查 `data_parser.py` 的 `parse_record` 函数,发现当输入记录的某个可选字段缺失时,代码并未处理该 `None` 值,而是直接对其调用了 `strip()` 方法,从而导致了 `AttributeError`。因此,**根本原因**是:**对可能为 None 的变量在未进行空值检查的情况下直接调用了方法**。]
-*   **1.3 根本原因摘要 (Root Cause Summary):** [用一句话高度概括 bug 的根本原因。]
-
-### **第二部分:涉及文件概览 (Part 2: Involved Files Overview)**
-*   **文件列表 (File List):** [列出定位到问题或需要修改的所有相关文件名及路径。示例: `- src/parsers/data_parser.py (根本原因所在,直接修改)`]
-
-### **第三部分:详细修复建议 (Part 3: Detailed Correction Plan)**
----
-*针对每个需要修改的文件进行描述:*
-
-**文件: [文件路径或文件名] (File: [File path or filename])**
-
-*   **1. 定位 (Location):**
-    *   [清晰说明函数、类、方法或具体的代码区域,并指出大致行号。示例: 函数 `parse_record` 内部,约第 125 行]
-
-*   **2. 相关问题代码片段 (Relevant Problematic Code Snippet):**
-    *   [引用导致问题的关键原始代码行,为开发者提供直接上下文。]
-    *   ```[language]
-        // value = record.get(optional_field)
-        // processed_value = value.strip() // 此处引发错误
-        ```
-
-*   **3. 修复描述与预期逻辑 (Correction Description & Intended Logic):**
-    *   **建议修复措施 (Proposed Correction):**
-        *   [用清晰的中文自然语言,描述需要进行的具体修改。例如:在调用 `.strip()` 方法之前,增加一个条件判断,检查 `value` 变量是否不为 `None`。]
-    *   **修复后逻辑示意 (Corrected Logic Sketch):**
-        *   [使用简洁的 `diff` 风格或伪代码来直观展示修改。]
-        *   **示例:**
-            ```diff
-            - processed_value = value.strip()
-            + processed_value = value.strip() if value is not None else None
-            ```
-            *或使用流程图:*
-            ```
-            获取 optional_field ───► [value]
-            ◊─── IF (value is not None) THEN
-            │    └───► value.strip() ───► [processed_value]
-            ELSE
-            │    └─── (赋值为 None) ───► [processed_value]
-            END IF
-            ... (后续逻辑使用 processed_value) ...
-            ```
-    *   **修复理由 (Reason for Correction):** [解释为什么这个修改能解决之前分析出的**根本原因**。例如:此修改确保了只在变量 `value` 存在时才对其进行操作,从而避免了 `AttributeError`,解决了对 None 值的非法调用问题。]
-
-*   **4. 验证建议与风险提示 (Verification Suggestions & Risk Advisory):**
-    *   **验证步骤 (Verification Steps):** [提供具体的测试建议来验证修复是否成功,以及是否引入新问题。例如:1. 构造一个optional_field字段存在的测试用例,确认其能被正常处理。2. **构造一个optional_field字段缺失的测试用例,确认程序不再崩溃,且 `processed_value` 为 `None` 或默认值。**]
-    *   **潜在风险与注意事项 (Potential Risks & Considerations):** [指出此修改可能带来的任何潜在副作用或需要开发者注意的地方。例如:请注意,下游消费 `processed_value` 的代码现在必须能够正确处理 `None` 值。请检查相关调用方是否已做相应处理。]
-
----
-*(对每个需要修改的文件重复上述格式)*
-
-## Key Requirements
-1. **Language**: All output in Chinese
-2. **No Code Generation**: Use diff format or pseudo-code only. Do not write complete functions or files
-3. **Focus on Root Cause**: Analysis must be logical and evidence-based
-4. **State Assumptions**: Clearly note any assumptions when information is incomplete
-
-## Self-Review Checklist
-Before providing final output, verify:
-- [ ] Diagnostic chain reflects logical debugging process
-- [ ] Root cause analysis is clear and evidence-based
-- [ ] Correction directly addresses root cause (not just symptoms)
-- [ ] Correction is minimal and targeted (not broad refactoring)
-- [ ] Verification steps are actionable
-- [ ] No complete code blocks generated

package/.claude/workflows/cli-templates/prompts/analysis-review-architecture.txt

@@ -1,29 +0,0 @@
-Analyze system architecture and design decisions.
-
-## CORE CHECKLIST ⚡
-□ Analyze system-wide structure, not just isolated components
-□ Provide file:line references for key architectural elements
-□ Distinguish between intended design and actual implementation
-□ Apply RULES template requirements exactly as specified
-
-## REQUIRED ANALYSIS
-1. Identify main architectural patterns and design principles
-2. Map module dependencies and component relationships
-3. Assess integration points and data flow patterns
-4. Evaluate scalability and maintainability aspects
-5. Document architectural trade-offs and design decisions
-
-## OUTPUT REQUIREMENTS
-- Architectural diagrams or textual descriptions
-- Dependency mapping with specific file references
-- Integration point documentation with examples
-- Scalability assessment and bottleneck identification
-- Prioritized recommendations for architectural improvement
-
-## VERIFICATION CHECKLIST ✓
-□ All major components and their relationships analyzed
-□ Key architectural decisions and trade-offs are documented
-□ Data flow and integration points are clearly mapped
-□ Scalability and maintainability findings are supported by evidence
-
-Focus: High-level design patterns and system-wide architectural concerns.

package/.claude/workflows/cli-templates/prompts/analysis-review-code-quality.txt

@@ -1,28 +0,0 @@
-Conduct comprehensive code review and quality assessment.
-
-## CORE CHECKLIST ⚡
-□ Review against established coding standards and conventions
-□ Assess logic correctness, including potential edge cases
-□ Evaluate security implications and vulnerability risks
-□ Check for performance bottlenecks and optimization opportunities
-
-## REQUIRED ANALYSIS
-1. Review code against established coding standards and conventions
-2. Assess logic correctness and potential edge cases
-3. Evaluate security implications and vulnerability risks
-4. Check performance characteristics and optimization opportunities
-5. Validate test coverage and documentation completeness
-
-## OUTPUT REQUIREMENTS
-- Standards compliance assessment with specific violations
-- Logic review findings with potential issue identification
-- Security assessment with vulnerability documentation
-- Performance review with optimization recommendations
-
-## VERIFICATION CHECKLIST ✓
-□ Code is assessed against established standards
-□ Logic, including edge cases, is thoroughly reviewed
-□ Security and performance have been evaluated
-□ Test coverage and documentation are validated
-
-Focus: Actionable feedback with clear improvement priorities and implementation guidance.

package/.claude/workflows/cli-templates/prompts/analysis-review-quality-standards.txt

@@ -1,29 +0,0 @@
-Analyze code quality and maintainability aspects.
-
-## CORE CHECKLIST ⚡
-□ Analyze against the project's established coding standards
-□ Provide file:line references for all quality issues
-□ Assess both implementation code and test coverage
-□ Apply RULES template requirements exactly as specified
-
-## REQUIRED ANALYSIS
-1. Assess code organization and structural quality
-2. Evaluate naming conventions and readability standards
-3. Review error handling and logging practices
-4. Analyze test coverage and testing strategies
-5. Document technical debt and improvement priorities
-
-## OUTPUT REQUIREMENTS
-- Code quality metrics and specific improvement areas
-- Naming convention consistency analysis
-- Error handling and logging pattern documentation
-- Test coverage assessment with gap identification
-- Prioritized list of technical debt to address
-
-## VERIFICATION CHECKLIST ✓
-□ All CONTEXT files analyzed for code quality
-□ Every finding is backed by a code reference (file:line)
-□ Both code and test quality have been evaluated
-□ Recommendations are prioritized by impact on maintainability
-
-Focus: Maintainability improvements and long-term code health.