Template

Files

Paul.Kim c9020eb796 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: 기본 작업 파일 추가

2025-07-20 22:25:33 +09:00

2.0 KiB

Raw Blame History

# Overview

Project Context

Project Status: Pre-MVP

Read this file: .taskmaster/docs/app-design-document.md - App design document
Read this file: .taskmaster/docs/tech-stack.md - Tech stack, architecture
DO NOT care about breaking changes. We didn't deploy yet.
DO NOT care about unit testing, accessibility, visual testing (Storybook), and performance optimization unless asked.
Care about security, zod validation, authorization, rate limiting, and other production-level concerns. In general, you can see how it's done in the other features.

Overview

[Provide a high-level overview of your product here. Explain what problem it solves, who it's for, and why it's valuable.]

Core Features

[List and describe the main features of your product. For each feature, include:

What it does
Why it's important
How it works at a high level]

User Experience

[Describe the user journey and experience. Include:

User personas
Key user flows
UI/UX considerations]

Technical Architecture

[Outline the technical implementation details:

System components
Data models
APIs and integrations
Infrastructure requirements]

Development Roadmap

[Break down the development process into phases:

MVP requirements
Future enhancements
Do not think about timelines whatsoever -- all that matters is scope and detailing exactly what needs to be build in each phase so it can later be cut up into tasks]

Logical Dependency Chain

[Define the logical order of development:

Which features need to be built first (foundation)
Getting as quickly as possible to something usable/visible front end that works
Properly pacing and scoping each feature so it is atomic but can also be built upon and improved as development approaches]

Risks and Mitigations

[Identify potential risks and how they'll be addressed:

Technical challenges
Figuring out the MVP that we can build upon
Resource constraints]

Appendix

[Include any additional information:

Research findings
Technical specifications]

2.0 KiB Raw Blame History