Review Prompt Content #39

src/content/prompts/architecture-design.mdx

@@ -1,19 +1,100 @@
 ---
-title: 'Architecture Design'
+title: '아키텍처 설계'
 version: 'v1'
-description: 'Prompt starter for defining the technical structure from a product specification.'
+description: 'ARCHITECTURE.md 작성을 위한 기술 구조 설계 프롬프트'
 publishedAt: '2026-06-12T00:00:00Z'
 ---
 
-```prompt
-Design the architecture for this product.
+# 목적
 
-Focus on:
-- repository structure
-- content model
-- routing
-- constraints
-- implementation boundaries
+제품 요구사항을 구현 가능한 기술 구조로 변환한다.
 
-Return architecture that supports static, content-first delivery.
+이 단계의 목적은 기능을 정의하는 것이 아니다.
+
+기능을 구현할 수 있는 구조를 정의하는 것이다.
+
+---
+
+# 산출물
+
+```text
+ARCHITECTURE.md
+```
+
+---
+
+# 사용 방법
+
+PRODUCT_SPEC.md가 완료된 이후 사용한다.
+
+AI는 제품 요구사항을 만족할 수 있는 기술 구조를 설계해야 한다.
+
+기술 선택은 제품 요구사항을 지원하기 위한 수단이어야 한다.
+
+---
+
+# 프롬프트
+
+``````prompt
+Generate ARCHITECTURE.md.
+
+Assume PRODUCT_SPEC.md already exists and is correct.
+
+The purpose of ARCHITECTURE.md is to define:
+
+```text
+How the product works internally.
+How responsibilities are separated.
+How information flows through the system.
+Which invariants must always remain true.
 ```
+
+Do not describe implementation technologies.
+
+Do not describe frameworks.
+
+Do not describe programming languages.
+
+Do not describe libraries.
+
+Do not describe deployment.
+
+Do not describe coding conventions.
+
+Architecture must remain technology-agnostic.
+
+The document must include:
+
+- Purpose
+- Core Concepts
+- System Flow
+- Components
+- Component Responsibilities
+- Responsibility Boundaries
+- Data Flow
+- Architectural Rules
+- Failure Boundaries
+- Non-Goals
+- Architectural Invariants
+
+Every component must have:
+
+- Responsibilities
+- Inputs
+- Outputs
+- Explicit ownership boundaries
+
+Identify:
+
+- missing responsibilities
+- conflicting responsibilities
+- ambiguous flows
+
+Resolve them before generating the document.
+
+Prefer clear ownership over abstraction.
+
+Optimize for implementation certainty.
+
+The document is intended for AI implementation, not human documentation.
+``````

src/content/prompts/execution-validation.mdx

@@ -1,19 +1,100 @@
 ---
-title: 'Execution Validation'
+title: '실행 검증'
 version: 'v1'
-description: 'Prompt starter for validating implementation against the approved plan.'
+description: '구현 결과가 승인된 계획과 일치하는지 검증하기 위한 프롬프트'
 publishedAt: '2026-06-12T00:00:00Z'
 ---
 
-```prompt
-Validate the implementation against TASKS.md, ARCHITECTURE.md, and PRODUCT_SPEC.md.
+# 목적
 
-Check:
-- required files
-- content accuracy
-- navigation
-- build correctness
-- architecture alignment
+구현 결과가 프로젝트 문서와 일치하는지 검증한다.
 
-Report only mismatches, risks, and missing coverage.
+이 단계의 목적은 새로운 기능을 제안하는 것이 아니다.
+
+승인된 범위 내에서 정확하게 구현되었는지 확인하는 것이다.
+
+---
+
+# 산출물
+
+```text
+Validation Report
+```
+
+---
+
+# 사용 방법
+
+구현이 완료된 이후 사용한다.
+
+AI는 구현 결과를 PRODUCT_SPEC.md, ARCHITECTURE.md, TASKS.md와 비교하여 검토해야 한다.
+
+새로운 요구사항을 추가하지 않는다.
+
+범위를 확장하지 않는다.
+
+이미 승인된 계획과의 일치 여부만 평가한다.
+
+---
+
+# 프롬프트
+
+``````prompt
+Review the following documents together:
+
+- PRODUCT_SPEC.md
+- ARCHITECTURE.md
+- FRAMEWORK.md
+
+Assume you are responsible for implementing the entire product.
+
+Assume no additional information will be provided.
+
+Your goal is to determine whether implementation can begin with confidence.
+
+Generate only questions.
+
+Do not answer questions.
+
+Do not suggest improvements.
+
+Do not suggest new features.
+
+Do not redesign the product.
+
+Do not modify requirements.
+
+Focus on identifying:
+
+- missing requirements
+- missing architectural responsibilities
+- missing implementation constraints
+- ambiguous behavior
+- conflicting definitions
+- undefined ownership
+- undefined flows
+- undefined inputs
+- undefined outputs
+- contradictions between documents
+
+Treat the three documents as a single implementation contract.
+
+A question is valid only if it blocks implementation certainty.
+
+Ignore:
+
+- personal preferences
+- alternative technologies
+- feature ideas
+- product strategy
+
+Output only a numbered list of questions.
+
+If no blocking questions exist, output:
+
+```text
+Implementation can begin with high confidence.
 ```
+
+Optimize for implementation certainty.
+``````

src/content/prompts/idea-refinement.mdx

@@ -1,21 +1,70 @@
 ---
-title: 'Idea Refinement'
+title: '아이디어 정제'
 version: 'v1'
-description: 'Prompt starter for refining raw ideas into actionable project direction.'
+description: 'IDEAS.md 작성을 위한 아이디어 검증 및 정제 프롬프트'
 publishedAt: '2026-06-12T00:00:00Z'
 ---
 
+## 목적
+
+아이디어를 실행 가능한 제품 방향으로 정제한다.
+
+이 단계의 목적은 솔루션을 설계하는 것이 아니다.
+
+이 아이디어가 실제로 추진할 가치가 있는지 검증하는 것이다.
+
+---
+
+## 산출물
+
+```text
+IDEAS.md
+```
+
+---
+
+## 사용 방법
+
+초기 아이디어를 설명한다.
+
+AI는 아이디어를 비판적으로 검토하고, 가정과 위험 요소를 찾아내며, 사업적 가능성을 검증해야 한다.
+
+AI는 결론을 내리기 전에 질문부터 해야 한다.
+
+---
+
+## 프롬프트
+
 ```prompt
-You are a critical co-founder helping refine a raw project idea.
-
-Focus on:
-- problem clarity
-- target user
-- existing alternatives
-- differentiation
-- constraints
-- long-term viability
-
-Do not write a specification yet.
-Ask the most important questions first.
+# Ideas Prompt
+
+Generate IDEAS.md from this conversation.
+
+This document is intended for human consumption.
+
+Record only information explicitly discussed during the conversation.
+
+Do not expand the idea.
+
+Do not invent features.
+
+Do not invent business models.
+
+Do not invent technical solutions.
+
+Do not invent implementation details.
+
+Do not add assumptions.
+
+Do not add recommendations.
+
+Do not add future possibilities unless explicitly discussed.
+
+Preserve the original intent.
+
+Focus on capturing the idea exactly as discussed.
+
+If information was not mentioned in the conversation, omit it.
+
+Optimize for accurate idea preservation rather than idea improvement.
 ```