e0bc5894b2
## 주요 변경사항: ### UI/UX 개선 - shadcn/ui 스타일 기반의 새로운 디자인 시스템 도입 - 모든 주요 화면에 대한 리디자인 구현 완료 - 로그인 화면: 모던한 카드 스타일 적용 - 대시보드: 통계 카드와 차트를 활용한 개요 화면 - 리스트 화면들: 일관된 테이블 디자인과 검색/필터 기능 - 다크모드 지원을 위한 테마 시스템 구축 ### 기능 개선 - Equipment List: 고급 필터링 (상태, 담당자별) - Company List: 검색 및 정렬 기능 강화 - User List: 역할별 필터링 추가 - License List: 만료일 기반 상태 표시 - Warehouse Location: 재고 수준 시각화 ### 기술적 개선 - 재사용 가능한 컴포넌트 라이브러리 구축 - 일관된 코드 패턴 가이드라인 작성 - 프로젝트 구조 분석 및 문서화 ### 문서화 - 프로젝트 분석 문서 추가 - UI 리디자인 진행 상황 문서 - 코드 패턴 가이드 작성 - Equipment 기능 격차 분석 및 구현 계획 ### 삭제/리팩토링 - goods_list.dart 제거 (equipment_list로 통합) - 불필요한 import 및 코드 정리 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
80 lines
2.6 KiB
Plaintext
80 lines
2.6 KiB
Plaintext
---
|
|
description: "Rule for continuous self-improvement and updating coding standards"
|
|
globs: "**/*"
|
|
alwaysApply: true
|
|
---
|
|
|
|
```markdown
|
|
- **Rule Improvement Triggers:**
|
|
- New code patterns not covered by existing rules
|
|
- Repeated similar implementations across files
|
|
- Common error patterns that could be prevented
|
|
- New libraries or tools being used consistently
|
|
- Emerging best practices in the codebase
|
|
|
|
- **Analysis Process:**
|
|
- Compare new code with existing rules
|
|
- Identify patterns that should be standardized
|
|
- Look for references to external documentation
|
|
- Check for consistent error handling patterns
|
|
- Monitor test patterns and coverage
|
|
|
|
- **Rule Updates:**
|
|
- **Add New Rules When:**
|
|
- A new technology/pattern is used in 3+ files
|
|
- Common bugs could be prevented by a rule
|
|
- Code reviews repeatedly mention the same feedback
|
|
- New security or performance patterns emerge
|
|
|
|
- **Modify Existing Rules When:**
|
|
- Better examples exist in the codebase
|
|
- Additional edge cases are discovered
|
|
- Related rules have been updated
|
|
- Implementation details have changed
|
|
|
|
- **Example Pattern Recognition:**
|
|
```typescript
|
|
// If you see repeated patterns like:
|
|
const data = await prisma.user.findMany({
|
|
select: { id: true, email: true },
|
|
where: { status: 'ACTIVE' }
|
|
});
|
|
|
|
// Consider adding to [prisma.mdc](mdc:.cursor/rules/prisma.mdc):
|
|
// - Standard select fields
|
|
// - Common where conditions
|
|
// - Performance optimization patterns
|
|
```
|
|
|
|
- **Rule Quality Checks:**
|
|
- Rules should be actionable and specific
|
|
- Examples should come from actual code
|
|
- References should be up to date
|
|
- Patterns should be consistently enforced
|
|
|
|
- **Continuous Improvement:**
|
|
- Monitor code review comments
|
|
- Track common development questions
|
|
- Update rules after major refactors
|
|
- Add links to relevant documentation
|
|
- Cross-reference related rules
|
|
|
|
- **Rule Deprecation:**
|
|
- Mark outdated patterns as deprecated
|
|
- Remove rules that no longer apply
|
|
- Update references to deprecated rules
|
|
- Document migration paths for old patterns
|
|
|
|
- **Documentation Updates:**
|
|
- Keep examples synchronized with code
|
|
- Update references to external docs
|
|
- Maintain links between related rules
|
|
- Document breaking changes
|
|
|
|
Follow [cursor_rules.mdc](mdc:.cursor/rules/cursor_rules.mdc) for proper rule formatting and structure.
|
|
- Update references to external docs
|
|
- Maintain links between related rules
|
|
- Document breaking changes
|
|
|
|
Follow [cursor_rules.mdc](mdc:.cursor/rules/cursor_rules.mdc) for proper rule formatting and structure.
|