test: 통합 테스트 오류 및 경고 수정
Some checks failed
Flutter Test & Quality Check / Test on macos-latest (push) Has been cancelled
Flutter Test & Quality Check / Test on ubuntu-latest (push) Has been cancelled
Flutter Test & Quality Check / Build APK (push) Has been cancelled

- 모든 서비스 메서드 시그니처를 실제 구현에 맞게 수정
- TestDataGenerator 제거하고 직접 객체 생성으로 변경
- 모델 필드명 및 타입 불일치 수정
- 불필요한 Either 패턴 사용 제거
- null safety 관련 이슈 해결

수정된 파일:
- test/integration/screens/company_integration_test.dart
- test/integration/screens/equipment_integration_test.dart
- test/integration/screens/user_integration_test.dart
- test/integration/screens/login_integration_test.dart
This commit is contained in:
JiWoong Sul
2025-08-05 20:24:05 +09:00
parent d6f34c0a52
commit 198aac6525
145 changed files with 41527 additions and 5220 deletions

139
CLAUDE.md
View File

@@ -7,6 +7,8 @@
## 🤖 Agent Selection Rules
- **Always select and use a specialized agent appropriate for the task**
- **Utilize parallel processing when multiple agents can work simultaneously**
- **Design custom agents when existing ones don't meet specific needs**
## 🎯 Mandatory Response Format
@@ -24,17 +26,86 @@ Before starting any task, you MUST respond in the following format:
- **flutter-offline-developer**: Flutter offline functionality development
- **flutter-network-engineer**: Flutter network implementation
- **flutter-qa-engineer**: Flutter QA/testing
- **flutter-web-expansion-specialist**: Flutter web platform expansion
- **app-launch-validator**: App launch validation
- **aso-optimization-expert**: ASO optimization
- **mobile-growth-hacker**: Mobile growth strategy
- **Idea Analysis**: Idea analysis
- **mobile-app-startup-mentor**: Mobile app startup mentoring
- **mobile app mvp planner**: MVP planning
- **app-store-optimizer**: App store optimization
- **tiktok-strategist**: TikTok marketing strategy
- **rapid-prototyper**: Rapid prototype development
- **test-writer-fixer**: Test writing and fixing
- **backend-architect**: Backend architecture design
- **mobile-app-builder**: Mobile app development
- **frontend-developer**: Frontend development
- **devops-automator**: DevOps automation
- **ai-engineer**: AI/ML implementation
- **workflow-optimizer**: Workflow optimization
- **test-results-analyzer**: Test results analysis
- **performance-benchmarker**: Performance testing
- **api-tester**: API testing
- **tool-evaluator**: Tool evaluation
- **sprint-prioritizer**: Sprint planning and prioritization
- **feedback-synthesizer**: User feedback analysis
- **trend-researcher**: Market trend research
- **studio-producer**: Studio production coordination
- **project-shipper**: Project launch management
- **experiment-tracker**: Experiment tracking
- **studio-coach**: Elite performance coaching
- **whimsy-injector**: UI/UX delight injection
- **ui-designer**: UI design
- **brand-guardian**: Brand management
- **ux-researcher**: UX research
- **visual-storyteller**: Visual narrative creation
- **legal-compliance-checker**: Legal compliance
- **analytics-reporter**: Analytics reporting
- **support-responder**: Customer support
- **finance-tracker**: Financial management
- **infrastructure-maintainer**: Infrastructure maintenance
- **joker**: Humor and morale boost
**Examples:**
- `Claude Opus 4 - Direct Implementation. I have reviewed all the following rules: development guidelines, class structure, testing rules. Proceeding with the task. Master!`
- `Claude Opus 4 - flutter-network-engineer. I have reviewed all the following rules: API integration, error handling, network optimization. Proceeding with the task. Master!`
- For extensive rules: `coding style, class design, exception handling, testing rules` (categorized summary)
## 🚀 Agent Utilization Strategy
### Optimal Solution Derivation
- **Analyze task requirements** to identify the most suitable agent(s)
- **Consider agent specializations** and select based on expertise match
- **Evaluate complexity** to determine if multiple agents are needed
- **Prioritize solutions** that minimize side effects and maximize efficiency
### Parallel Processing Guidelines
- **Identify independent tasks** that can be executed simultaneously
- **Launch multiple agents** concurrently when tasks don't have dependencies
- **Coordinate results** from parallel agents to ensure consistency
- **Monitor resource usage** to prevent system overload
- **Example scenarios**:
- UI design + Architecture planning
- Testing + Documentation
- Performance optimization + Security audit
### Side Effect Prevention
- **Analyze impact** before implementing any solution
- **Isolate changes** to minimize unintended consequences
- **Implement rollback strategies** for critical operations
- **Test thoroughly** in isolated environments first
- **Document all changes** and their potential impacts
- **Use feature flags** for gradual rollouts
- **Monitor system behavior** after implementations
### Custom Agent Design
When existing agents don't meet requirements:
1. **Identify gap** in current agent capabilities
2. **Define agent purpose** and specialization
3. **Design agent interface** and expected behaviors
4. **Implement agent logic** following existing patterns
5. **Test agent thoroughly** before deployment
6. **Document agent usage** and best practices
## 🚀 Mandatory 3-Phase Task Process
@@ -195,6 +266,11 @@ Detailed explanation if needed
BREAKING CHANGE: description (if applicable)
```
### Git Signature Rules
- **DO NOT include Claude signature** in git commits
- **Use standard commit format** without AI attribution
- **Maintain clean commit history** without automated signatures
### Commit Types
- `feat`: New feature
- `fix`: Bug fix
@@ -328,4 +404,65 @@ Before completing any task, confirm:
---
## 📊 Advanced Prompt Engineering
### Context Engineering Techniques
- **Structured prompts** with clear sections and hierarchy
- **Few-shot examples** to demonstrate expected patterns
- **Chain-of-thought** reasoning for complex problems
- **Role-based prompting** to activate specific expertise
- **Constraint specification** to guide solution boundaries
- **Output formatting** instructions for consistent results
### Prompt Optimization Strategies
- **Be specific** about requirements and constraints
- **Include context** relevant to the task
- **Define success criteria** explicitly
- **Use delimiters** to separate different sections
- **Provide examples** of desired outputs
- **Iterate and refine** based on results
## 📑 Session Continuity Management
### Long Conversation Handling
When conversations are expected to be lengthy:
1. **Create session documentation** in markdown format
2. **Document key decisions** and implementation details
3. **Track progress** with checkpoints and milestones
4. **Summarize complex discussions** for easy reference
5. **Save state information** for resuming work
### Continuity Document Structure
```markdown
# Session: [Task Name] - [Date]
## Objective
[Clear description of the goal]
## Progress Summary
- [ ] Task 1: Description
- [x] Task 2: Completed - Details
- [ ] Task 3: In Progress
## Key Decisions
1. Decision: Rationale
2. Decision: Rationale
## Implementation Details
[Technical details, code snippets, configurations]
## Next Steps
[What needs to be done in the next session]
## Important Context
[Any critical information for continuing work]
```
### State Preservation
- **Save work incrementally** to prevent loss
- **Document assumptions** and constraints
- **Track dependencies** and blockers
- **Note unresolved issues** for future sessions
- **Create handoff notes** for seamless continuation
**Remember**: These are guidelines, not rigid rules. Use professional judgment and adapt to project needs while maintaining high quality standards.