mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-05 01:50:27 +08:00
重构 ccw cli 模板系统: - 新增 template-discovery.ts 模块,支持扁平化模板自动发现 - 添加 --rule <template> 选项,自动加载 protocol 和 template - 模板目录从嵌套结构 (prompts/category/file.txt) 迁移到扁平结构 (prompts/category-function.txt) - 更新所有 agent/command 文件,使用 $PROTO $TMPL 环境变量替代 $(cat ...) 模式 - 支持模糊匹配:--rule 02-review-architecture 可匹配 analysis-review-architecture.txt 其他更新: - Dashboard: 添加 Claude Manager 和 Issue Manager 页面 - Codex-lens: 增强 chain_search 和 clustering 模块 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
56 lines
2.1 KiB
Plaintext
56 lines
2.1 KiB
Plaintext
Create a reusable component following project conventions and best practices.
|
|
|
|
## CORE CHECKLIST ⚡
|
|
□ Analyze existing component patterns BEFORE implementing
|
|
□ Follow established naming conventions and prop patterns
|
|
□ Include comprehensive tests (unit + visual + accessibility)
|
|
□ Provide complete TypeScript types and documentation
|
|
|
|
## IMPLEMENTATION PHASES
|
|
|
|
### Design Phase
|
|
1. Analyze existing component patterns and structures
|
|
2. Identify reusable design principles and styling approaches
|
|
3. Review component hierarchy and prop patterns
|
|
4. Study existing component documentation and usage
|
|
|
|
### Development Phase
|
|
1. Create component with proper TypeScript interfaces
|
|
2. Implement following established naming conventions
|
|
3. Add appropriate default props and validation
|
|
4. Include comprehensive prop documentation
|
|
|
|
### Styling Phase
|
|
1. Follow existing styling methodology (CSS modules, styled-components, etc.)
|
|
2. Ensure responsive design principles
|
|
3. Add proper theming support if applicable
|
|
4. Include accessibility considerations (ARIA, keyboard navigation)
|
|
|
|
### Testing Phase
|
|
1. Write component tests covering all props and states
|
|
2. Test accessibility compliance
|
|
3. Add visual regression tests if applicable
|
|
4. Test component in different contexts and layouts
|
|
|
|
### Documentation Phase
|
|
1. Create usage examples and code snippets
|
|
2. Document all props and their purposes
|
|
3. Include accessibility guidelines
|
|
4. Add integration examples with other components
|
|
|
|
## OUTPUT REQUIREMENTS
|
|
- Complete component implementation with TypeScript types
|
|
- Usage examples and integration patterns
|
|
- Component API documentation and best practices
|
|
- Test suite with accessibility validation
|
|
- File:line references for pattern sources
|
|
|
|
## VERIFICATION CHECKLIST ✓
|
|
□ Implementation follows existing component patterns
|
|
□ Complete TypeScript types and prop documentation
|
|
□ Comprehensive tests (unit + visual + accessibility)
|
|
□ Accessibility compliance (ARIA, keyboard navigation)
|
|
□ Usage examples and integration documented
|
|
|
|
Focus: Production-ready reusable component with comprehensive documentation and testing.
|