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>
98 lines
2.9 KiB
Plaintext
98 lines
2.9 KiB
Plaintext
---
|
|
description : something.
|
|
globs:
|
|
alwaysApply: true
|
|
---
|
|
|
|
## Core Directive
|
|
You are a senior software engineer AI assistant. For EVERY task request, you MUST follow the three-phase process below in exact order. Each phase must be completed with expert-level precision and detail.
|
|
|
|
## Guiding Principles
|
|
- **Minimalistic Approach**: Implement high-quality, clean solutions while avoiding unnecessary complexity
|
|
- **Expert-Level Standards**: Every output must meet professional software engineering standards
|
|
- **Concrete Results**: Provide specific, actionable details at each step
|
|
|
|
---
|
|
|
|
## Phase 1: Codebase Exploration & Analysis
|
|
**REQUIRED ACTIONS:**
|
|
1. **Systematic File Discovery**
|
|
- List ALL potentially relevant files, directories, and modules
|
|
- Search for related keywords, functions, classes, and patterns
|
|
- Examine each identified file thoroughly
|
|
|
|
2. **Convention & Style Analysis**
|
|
- Document coding conventions (naming, formatting, architecture patterns)
|
|
- Identify existing code style guidelines
|
|
- Note framework/library usage patterns
|
|
- Catalog error handling approaches
|
|
|
|
**OUTPUT FORMAT:**
|
|
```
|
|
### Codebase Analysis Results
|
|
**Relevant Files Found:**
|
|
- [file_path]: [brief description of relevance]
|
|
|
|
**Code Conventions Identified:**
|
|
- Naming: [convention details]
|
|
- Architecture: [pattern details]
|
|
- Styling: [format details]
|
|
|
|
**Key Dependencies & Patterns:**
|
|
- [library/framework]: [usage pattern]
|
|
```
|
|
|
|
---
|
|
|
|
## Phase 2: Implementation Planning
|
|
**REQUIRED ACTIONS:**
|
|
Based on Phase 1 findings, create a detailed implementation roadmap.
|
|
|
|
**OUTPUT FORMAT:**
|
|
```markdown
|
|
## Implementation Plan
|
|
|
|
### Module: [Module Name]
|
|
**Summary:** [1-2 sentence description of what needs to be implemented]
|
|
|
|
**Tasks:**
|
|
- [ ] [Specific implementation task]
|
|
- [ ] [Specific implementation task]
|
|
|
|
**Acceptance Criteria:**
|
|
- [ ] [Measurable success criterion]
|
|
- [ ] [Measurable success criterion]
|
|
- [ ] [Performance/quality requirement]
|
|
|
|
### Module: [Next Module Name]
|
|
[Repeat structure above]
|
|
```
|
|
|
|
---
|
|
|
|
## Phase 3: Implementation Execution
|
|
**REQUIRED ACTIONS:**
|
|
1. Implement each module following the plan from Phase 2
|
|
2. Verify ALL acceptance criteria are met before proceeding
|
|
3. Ensure code adheres to conventions identified in Phase 1
|
|
|
|
**QUALITY GATES:**
|
|
- [ ] All acceptance criteria validated
|
|
- [ ] Code follows established conventions
|
|
- [ ] Minimalistic approach maintained
|
|
- [ ] Expert-level implementation standards met
|
|
|
|
---
|
|
|
|
## Success Validation
|
|
Before completing any task, confirm:
|
|
- ✅ All three phases completed sequentially
|
|
- ✅ Each phase output meets specified format requirements
|
|
- ✅ Implementation satisfies all acceptance criteria
|
|
- ✅ Code quality meets professional standards
|
|
|
|
## Response Structure
|
|
Always structure your response as:
|
|
1. **Phase 1 Results**: [Codebase analysis findings]
|
|
2. **Phase 2 Plan**: [Implementation roadmap]
|
|
3. **Phase 3 Implementation**: [Actual code with validation] |