docs: 초기 파일 추가 및 기본 설정 구성

- .git-commit-template.txt: 커밋 메시지 템플릿 추가
- .gitignore: OS 및 데이터베이스 관련 파일 무시 설정 추가
- .mcp.json: MCP 서버 설정 추가
- CLAUDE.md: SuperClaude 엔트리 포인트 문서 추가
- README.md: 프로젝트 템플릿 설명 추가
- .claude/COMMANDS.md: 명령어 실행 프레임워크 문서 추가
- .claude/FLAGS.md: 플래그 시스템 문서 추가
- .claude/MCP.md: MCP 서버 통합 문서 추가
- .claude/MODES.md: 운영 모드 문서 추가
- .claude/ORCHESTRATOR.md: 지능형 라우팅 시스템 문서 추가
- .claude/PERSONAS.md: 페르소나 시스템 문서 추가
- .claude/PRINCIPLES.md: 핵심 원칙 문서 추가
- .claude/RULES.md: 실행 가능한 규칙 문서 추가
- .claude/settings.json: 권한 설정 추가
- .claude/commands 디렉토리: 다양한 명령어 문서 추가
- .taskmaster/config.json: 기본 설정 파일 추가
- .taskmaster/docs 디렉토리: 문서 파일 추가
- .taskmaster/tasks/tasks.json: 기본 작업 파일 추가

.claude/RULES.md

@@ -0,0 +1,66 @@
+# RULES.md - SuperClaude Framework Actionable Rules
+
+Simple actionable rules for Claude Code SuperClaude framework operation.
+
+## Core Operational Rules
+
+### Task Management Rules
+- TodoRead() → TodoWrite(3+ tasks) → Execute → Track progress
+- Use batch tool calls when possible, sequential only when dependencies exist
+- Always validate before execution, verify after completion
+- Run lint/typecheck before marking tasks complete
+- Use /spawn and /task for complex multi-session workflows
+- Maintain ≥90% context retention across operations
+
+### File Operation Security
+- Always use Read tool before Write or Edit operations
+- Use absolute paths only, prevent path traversal attacks
+- Prefer batch operations and transaction-like behavior
+- Never commit automatically unless explicitly requested
+
+### Framework Compliance
+- Check package.json/pyproject.toml before using libraries
+- Follow existing project patterns and conventions
+- Use project's existing import styles and organization
+- Respect framework lifecycles and best practices
+
+### Systematic Codebase Changes
+- **MANDATORY**: Complete project-wide discovery before any changes
+- Search ALL file types for ALL variations of target terms
+- Document all references with context and impact assessment
+- Plan update sequence based on dependencies and relationships
+- Execute changes in coordinated manner following plan
+- Verify completion with comprehensive post-change search
+- Validate related functionality remains working
+- Use Task tool for comprehensive searches when scope uncertain
+
+## Quick Reference
+
+### Do
+✅ Read before Write/Edit/Update
+✅ Use absolute paths
+✅ Batch tool calls
+✅ Validate before execution
+✅ Check framework compatibility
+✅ Auto-activate personas
+✅ Preserve context across operations
+✅ Use quality gates (see ORCHESTRATOR.md)
+✅ Complete discovery before codebase changes
+✅ Verify completion with evidence
+
+### Don't
+❌ Skip Read operations
+❌ Use relative paths
+❌ Auto-commit without permission
+❌ Ignore framework patterns
+❌ Skip validation steps
+❌ Mix user-facing content in config
+❌ Override safety protocols
+❌ Make reactive codebase changes
+❌ Mark complete without verification
+
+### Auto-Triggers
+- Wave mode: complexity ≥0.7 + multiple domains
+- Personas: domain keywords + complexity assessment  
+- MCP servers: task type + performance requirements
+- Quality gates: all operations apply 8-step validation