/prompt-enhancer

name: prompt-enhancer
description: Enhance user prompts by analyzing project context (code structure, dependencies, conventions, existing patterns). Use when users provide brief development requests that would benefit from project-specific context to generate more accurate, contextually-aware prompts.

Prompt Enhancer

Transform brief development requests into clear, detailed requirements by analyzing project context. Present the enhanced requirements to the user for confirmation before implementation.

When to Use This Skill

Use this skill when:

• User provides a brief development request like "로그인 기능 만들어줘", "API 추가해줘"
• Request lacks specific implementation details
• User uploads project files or mentions "the project"
• Task requires understanding project architecture

Core Workflow

Step 1: Analyze Project Context

**Check for uploaded files:**

view /mnt/user-data/uploads

**Gather key information:**

• Project structure and organization
• Technology stack (package.json, pubspec.yaml, requirements.txt, etc.)
• Existing patterns (state management, API calls, routing)
• Code conventions (naming, file structure)
• Similar existing features

Step 2: Extract Request Intent

From the user's brief request, identify:

• **Feature type**: New feature, bug fix, refactoring, API integration
• **Scope**: Single screen, full flow, backend + frontend
• **Dependencies**: Related features or systems

Step 3: Build Enhanced Requirements

Create a structured requirement document with:

# [기능명] 구현 요구사항

## 📋 프로젝트 컨텍스트
- Framework: [detected framework and version]
- Architecture: [detected pattern]
- State Management: [detected library]
- Key Libraries: [list relevant dependencies]

## 🎯 구현 범위

### 주요 기능
1. [Main feature 1]
2. [Main feature 2]
3. [Main feature 3]

### 파일 구조

[Expected file structure based on project]

## 📝 상세 요구사항

### 1. [Layer/Component Name]
- **위치**: [File path]
- **목적**: [What it does]
- **구현 내용**:
  - [Specific requirement 1]
  - [Specific requirement 2]
- **기존 패턴 따르기**: [Reference to existing pattern]

### 2. [Next Layer/Component]
...

## ✅ 성공 기준
- [ ] [Acceptance criteria 1]
- [ ] [Acceptance criteria 2]
- [ ] [Acceptance criteria 3]
- [ ] 기존 코드 스타일 및 아키텍처 일관성 유지
- [ ] 모든 주요 기능에 대한 테스트 작성

## 🔍 확인 사항
- [Any questions or clarifications needed]
- [Assumptions made]

---
이 요구사항으로 진행할까요? 수정이 필요한 부분이 있다면 말씀해주세요.

Step 4: Present to User

**Important**: After creating the enhanced requirements, present them to the user and ask for confirmation:

위 요구사항을 분석해서 정리했습니다. 

이대로 진행해도 될까요? 
수정하거나 추가할 내용이 있으면 말씀해주세요!

**Do NOT implement** until the user confirms. The goal is to clarify requirements first.

Analysis Patterns by Stack

Flutter Projects

**Detect**: pubspec.yaml, lib/ directory

**Key context to gather:**

• State management (Riverpod, Bloc, Provider, GetX)
• Architecture (Clean Architecture, MVVM, MVC)
• Navigation (go_router, auto_route, Navigator)
• Network (Dio, http)
• Local storage (Hive, SharedPreferences, SQLite)

**Enhanced requirements should include:**

## 구현 범위

### Presentation Layer
- 화면: lib/presentation/[feature]/[screen]_screen.dart
- 상태: [StateNotifier/Bloc/Controller] with [state pattern]
- 위젯: 재사용 가능한 컴포넌트

### Domain Layer
- Entity: lib/domain/entities/[name].dart
- UseCase: lib/domain/usecases/[action]_usecase.dart
- Repository Interface: lib/domain/repositories/

### Data Layer
- Model: lib/data/models/[name]_model.dart (fromJson/toJson)
- Repository Implementation: lib/data/repositories/
- DataSource: lib/data/datasources/

### Navigation
- Route: [route path]
- Navigation method: [context.go/push based on router]

## 성공 기준
✅ [State management]로 상태 관리
✅ [Existing widget] 스타일 일관성 유지
✅ API 응답 에러 처리
✅ 로딩 상태 표시
✅ Widget test 작성

Next.js/React Projects

**Detect**: package.json with "next" or "react"

**Key context to gather:**

• Next.js version (App Router vs Pages Router)
• State management (Zustand, Redux, Context)
• Styling (Tailwind, CSS Modules, styled-components)
• API approach (Next.js API routes, external API)
• TypeScript usage

**Enhanced requirements should include:**

## 구현 범위

### UI Components
- 컴포넌트: [path]/[ComponentName].tsx
- Props interface: [existing pattern]
- Styling: [Tailwind classes/CSS modules]

### State Management
- Store: [existing state structure]
- Actions: [action naming convention]

### API Layer
- Endpoint: [app/api or external]
- Method: [GET/POST/PUT/DELETE]
- Response type: [TypeScript interface]

### Routing
- Route: [app/[route] or pages/[route]]
- Dynamic segments: [if needed]

## 성공 기준
✅ TypeScript 타입 안정성
✅ [Existing components] 재사용
✅ 반응형 디자인 (모바일/데스크톱)
✅ SEO 최적화 (메타데이터)
✅ Unit test + Integration test

Python (Django/FastAPI) Projects

**Detect**: requirements.txt, manage.py, main.py

**Key context to gather:**

• Framework (Django, FastAPI, Flask)
• ORM (SQLAlchemy, Django ORM, Tortoise)
• Authentication approach
• API documentation (OpenAPI/Swagger)

**Enhanced requirements should include:**

## 구현 범위

### Models/Schema
- Model: [app]/models.py or schemas/[name].py
- Fields: [field definitions with types]
- Relationships: [ForeignKey/relationships]

### Views/Endpoints
- Route: [path]
- Method: [HTTP method]
- Request/Response schema: [Pydantic models]

### Business Logic
- Service: [if applicable]
- Validation: [input validation]

### Database
- Migration: [migration command]

## 성공 기준
✅ API documentation 자동 생성
✅ Request validation
✅ Error handling with proper status codes
✅ Unit test + Integration test
✅ [Authentication] 적용

Example Enhancement

**User input:**

로그인 기능 구현해줘

**Skill output:**

# 로그인 기능 구현 요구사항

## 📋 프로젝트 컨텍스트
- Framework: Flutter 3.16.0 with null safety
- Architecture: Clean Architecture
- State Management: Riverpod (StateNotifier pattern)
- Network: Dio 5.3.0
- Storage: flutter_secure_storage
- Navigation: go_router

## 🎯 구현 범위

### 주요 기능
1.