Add parallel execution command templates and analysis prompts

- Introduced a comprehensive set of parallel execution command templates for various architectural and functional scenarios.
- Added prompts for analyzing system architecture, implementation patterns, performance, code quality, security, and project structure.
- Created templates for planning tasks, component implementation, migration strategies, and code reviews.
- Established a unified guideline for Gemini CLI usage, including command syntax, file patterns, and template best practices.
- Initialized VSCode settings file for project configuration.1
This commit is contained in:
catlog22
2025-09-09 21:48:40 +08:00
parent b906ce8715
commit 48843cc256
33 changed files with 1620 additions and 1685 deletions

View File

@@ -0,0 +1,16 @@
Analyze system architecture and design decisions:
## 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
Focus on high-level design patterns and system-wide architectural concerns.

View File

@@ -0,0 +1,16 @@
Analyze implementation patterns and code structure:
## 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
Focus on actionable insights and concrete implementation guidance.

View File

@@ -0,0 +1,16 @@
Analyze performance characteristics and optimization opportunities:
## 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 locations
- Algorithm complexity analysis and optimization suggestions
- Caching pattern documentation and recommendations
- Memory usage patterns and optimization opportunities
Focus on measurable performance improvements and concrete optimization strategies.

View File

@@ -0,0 +1,16 @@
Analyze code quality and maintainability aspects:
## 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 pattern documentation
- Test coverage assessment with gap identification
Focus on maintainability improvements and long-term code health.

View File

@@ -0,0 +1,16 @@
Analyze security implementation and potential vulnerabilities:
## 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 gaps
- Encryption usage patterns and recommendations
Focus on identifying security gaps and providing actionable remediation steps.

View File

@@ -0,0 +1,16 @@
Analyze project structure for DMS hierarchy optimization:
## Required Analysis:
1. Assess project complexity and file organization patterns
2. Identify logical module boundaries and responsibility separation
3. Evaluate cross-module dependencies and integration complexity
4. Determine optimal documentation depth and hierarchy levels
5. Recommend content differentiation strategies across hierarchy levels
## Output Requirements:
- Project complexity classification with supporting metrics
- Module boundary recommendations with responsibility mapping
- Hierarchy depth recommendations with level-specific focus areas
- Content strategy with redundancy elimination guidelines
Focus on intelligent documentation hierarchy that scales with project complexity.

View File

@@ -0,0 +1,16 @@
Guide component implementation and development patterns:
## Required Analysis:
1. Define component interface and API requirements
2. Identify reusable patterns and composition strategies
3. Plan state management and data flow implementation
4. Design component testing and validation approach
5. Document integration points and usage examples
## Output Requirements:
- Component specification with clear interface definition
- Implementation patterns and best practices
- State management strategy and data flow design
- Testing approach and validation criteria
Focus on reusable, maintainable component design with clear usage patterns.

View File

@@ -0,0 +1,16 @@
Plan system migration and modernization strategies:
## Required Analysis:
1. Assess current system architecture and migration requirements
2. Identify migration paths and transformation strategies
3. Plan data migration and system cutover procedures
4. Evaluate compatibility and integration challenges
5. Document rollback plans and risk mitigation strategies
## Output Requirements:
- Migration strategy with step-by-step execution plan
- Data migration procedures and validation checkpoints
- Compatibility assessment and integration requirements
- Risk analysis and rollback procedures
Focus on low-risk migration strategies with comprehensive fallback options.

View File

@@ -0,0 +1,16 @@
Create detailed task breakdown and implementation planning:
## Required Analysis:
1. Break down complex tasks into manageable subtasks
2. Identify dependencies and execution sequence requirements
3. Estimate effort and resource requirements for each task
4. Map task relationships and critical path analysis
5. Document risks and mitigation strategies
## Output Requirements:
- Hierarchical task breakdown with specific deliverables
- Dependency mapping and execution sequence
- Effort estimation and resource allocation
- Risk assessment and mitigation plans
Focus on actionable task planning with clear deliverables and timelines.

View File

@@ -0,0 +1,16 @@
Conduct comprehensive code review and quality assessment:
## 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
Focus on actionable feedback with clear improvement priorities and implementation guidance.