mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +08:00
25ac862f46
- Convert 40 JS files to TypeScript (CLI, tools, core, MCP server) - Add Zod for runtime parameter validation - Add type definitions in src/types/ - Keep src/templates/ as JavaScript (dashboard frontend) - Update bin entries to use dist/ - Add tsconfig.json with strict mode - Add backward-compatible exports for tests - All 39 tests passing Breaking changes: None (backward compatible) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
123 lines
2.1 KiB
Plaintext
123 lines
2.1 KiB
Plaintext
# Rule Template: Component Rules (Frontend/Fullstack Only)
|
|
|
|
## Variables
|
|
- {TECH_STACK_NAME}: Tech stack display name
|
|
- {FILE_EXT}: File extension pattern
|
|
- {UI_FRAMEWORK}: UI framework (React, Vue, etc)
|
|
|
|
## Output Format
|
|
|
|
```markdown
|
|
---
|
|
paths:
|
|
- "**/components/**/*.{FILE_EXT}"
|
|
- "**/ui/**/*.{FILE_EXT}"
|
|
- "**/views/**/*.{FILE_EXT}"
|
|
- "**/pages/**/*.{FILE_EXT}"
|
|
---
|
|
|
|
# {TECH_STACK_NAME} Component Rules
|
|
|
|
## Component Structure
|
|
|
|
[Organization patterns from Exa research]
|
|
|
|
### File Organization
|
|
```
|
|
components/
|
|
├── common/ # Shared components
|
|
├── features/ # Feature-specific
|
|
├── layout/ # Layout components
|
|
└── ui/ # Base UI elements
|
|
```
|
|
|
|
### Component Template
|
|
```{lang}
|
|
// Standard component structure
|
|
```
|
|
|
|
### Naming Conventions
|
|
- PascalCase for components
|
|
- Descriptive names
|
|
- Prefix conventions (if any)
|
|
|
|
## Props & State
|
|
|
|
[State management guidelines]
|
|
|
|
### Props Definition
|
|
```{lang}
|
|
// Props type/interface example
|
|
```
|
|
|
|
### Props Best Practices
|
|
- Required vs optional
|
|
- Default values
|
|
- Prop validation
|
|
- Prop naming
|
|
|
|
### Local State
|
|
- When to use local state
|
|
- State initialization
|
|
- State updates
|
|
|
|
### Shared State
|
|
- State management approach
|
|
- Context usage
|
|
- Store patterns
|
|
|
|
## Styling
|
|
|
|
[CSS/styling conventions]
|
|
|
|
### Approach
|
|
- [CSS Modules/Styled Components/Tailwind/etc]
|
|
|
|
### Style Organization
|
|
```{lang}
|
|
// Style example
|
|
```
|
|
|
|
### Naming Conventions
|
|
- Class naming (BEM, etc)
|
|
- CSS variable usage
|
|
- Theme integration
|
|
|
|
## Accessibility
|
|
|
|
[A11y requirements]
|
|
|
|
### Essential Requirements
|
|
- Semantic HTML
|
|
- ARIA labels
|
|
- Keyboard navigation
|
|
- Focus management
|
|
|
|
### Testing A11y
|
|
- Automated checks
|
|
- Manual testing
|
|
- Screen reader testing
|
|
|
|
## Performance
|
|
|
|
[Performance guidelines]
|
|
|
|
### Optimization Patterns
|
|
- Memoization
|
|
- Lazy loading
|
|
- Code splitting
|
|
- Virtual lists
|
|
|
|
### Avoiding Re-renders
|
|
- When to memoize
|
|
- Callback optimization
|
|
- State structure
|
|
```
|
|
|
|
## Content Guidelines
|
|
|
|
- Focus on component-specific patterns
|
|
- Include framework-specific examples
|
|
- Cover accessibility requirements
|
|
- Address performance considerations
|