moai-project-documentation

name	moai-project-documentation
version	4.0.0
created	"2025-11-12T00:00:00.000Z"
updated	"2025-11-12T00:00:00.000Z"
status	stable
tier	specialization
description	Enhanced project documentation with AI-powered features. Enhanced with Context7 MCP for up-to-date documentation.
allowed-tools	Read, Glob, Grep, WebSearch, WebFetch, mcp__context7__resolve-library-id, mcp__context7__get-library-docs
primary-agent	alfred
secondary-agents	[]
keywords	["project","documentation","git","frontend","kubernetes"]
tags	[]
orchestration	null
can_resume	true
typical_chain_position	middle
depends_on	[]

moai-project-documentation

Project Documentation

Primary Agent: alfred
Secondary Agents: none
Version: 4.0.0
Keywords: project, documentation, git, frontend, kubernetes

---

📖 Progressive Disclosure

Level 1: Quick Reference (Core Concepts)

Core Content

Part 1: Project Type Selection

Ask user to identify their project type:

1. Web Application

   • Examples: SaaS, web dashboard, REST API backend
   • Focus: User personas, adoption metrics, real-time features
   • Template style: Business-focused with UX emphasis

2. Mobile Application

   • Examples: iOS/Android app, cross-platform app (Flutter, React Native)
   • Focus: User retention, app store metrics, offline capability
   • Template style: UX-driven with platform-specific performance
   • Frameworks: Flutter, React Native, Swift, Kotlin

3. CLI Tool / Utility

   • Examples: Data validator, deployment tool, package manager
   • Focus: Performance, integration, ecosystem adoption
   • Template style: Technical with use case emphasis

4. Shared Library / SDK

   • Examples: Type validator, data parser, API client
   • Focus: Developer experience, ecosystem adoption, performance
   • Template style: API-first with integration focus

5. Data Science / ML Project

   • Examples: Recommendation system, ML pipeline, analytics
   • Focus: Data quality, model metrics, scalability
   • Template style: Metrics-driven with data emphasis

---

Part 2: Product.md Writing Guide

Document Structure

# Mission & Strategy
- What problem do we solve?
- Who are the users?
- What's our value proposition?

# Success Metrics
- How do we measure impact?
- What are KPIs?
- How often do we measure?

# Next Features (SPEC Backlog)
- What features are coming?
- How are they prioritized?

Writing by Project Type

Web Application Product.md Focus:

• User personas (team lead, individual contributor, customer)
• Adoption targets (80% within 2 weeks)
• Integration capabilities (Slack, GitHub, Jira)
• Real-time collaboration features

Mobile Application Product.md Focus:

• User personas (iOS users, Android users, power users)
• Retention metrics (DAU, MAU, churn rate)
• App store presence (rating target, download goal)
• Offline capability requirements
• Push notification strategy
• Platform-specific features (GPS, camera, contacts)

CLI Tool Product.md Focus:

• Target workflow (validate → deploy → monitor)
• Performance benchmarks (1M records in <5s)
• Multi-format support (JSON, CSV, Avro)
• Ecosystem adoption (GitHub stars, npm downloads)

Library Product.md Focus:

• API design philosophy (composable, type-safe)
• Developer experience (time-to-first-validation <5 min)
• Performance characteristics (zero-cost abstractions)
• Community engagement (issue response time, contributions)

Data Science Product.md Focus:

• Model metrics (accuracy, precision, recall)
• Data quality requirements
• Scalability targets (1B+ records)
• Integration with ML platforms (MLflow, W&B)

---

Part 3: Structure.md Writing Guide

Document Structure

# System Architecture
- What's the overall design pattern?
- What layers/tiers exist?
- How do components interact?

# Core Modules
- What are the main building blocks?
- What's each module responsible for?
- How do they communicate?

# External Integrations
- What external systems do we depend on?
- How do we authenticate?
- What's our fallback strategy?

# Traceability
- How do SPECs map to code?
- How do we trace changes?

Architecture Patterns by Project Type

Web Application Architecture:

Frontend (React/Vue) ↔ API Layer (FastAPI/Node) ↔ Database (PostgreSQL)
    ↓
WebSocket Server (Real-time features)
    ↓
Message Queue (Async jobs)
    ↓
Background Workers

Mobile Application Architecture:

UI Layer (Screens, Widgets)
    ↓
State Management (Bloc, Redux, Riverpod)
    ↓
Data Layer (Local DB: SQLite/Realm, Remote: REST/GraphQL)
    ↓
Authentication (OAuth, JWT)
    ↓
Native Modules (Camera, GPS, Contacts)
    ↓
Offline Sync Engine

CLI Tool Architecture:

Input Parsing → Command Router → Core Logic → Output Formatter
                                    ↓
                           Validation Layer
                                    ↓
                            Caching Layer

Library Architecture:

Public API Surface
    ↓
Type Guards / Validation
    ↓
Core Logic
    ↓
Platform Adapters (Node.js, Browser, Deno)

Data Science Architecture:

Data Ingestion → Feature Engineering → Model Training → Inference
    ↓
Feature Store
    ↓
Model Registry
    ↓
Monitoring & Alerting

---

Part 4: Tech.md Writing Guide

Document Structure

# Technology Stack
- What language(s)?
- What version ranges?
- Why these choices?

# Quality Gates
- What's required to merge?
- How do we measure quality?
- What tools enforce standards?

# Security Policy
- How do we manage secrets?
- How do we handle vulnerabilities?
- What's our incident response?

# Deployment Strategy
- Where do we deploy?
- How do we release?
- How do we rollback?

Tech Stack Examples by Type

Web Application:

Frontend: TypeScript, React 18, Vitest, TailwindCSS
Backend: Python 3.13, FastAPI, pytest (85% coverage)
Database: PostgreSQL 15, Alembic migrations
DevOps: Docker, Kubernetes, GitHub Actions
Quality: TypeScript strict mode, mypy, ruff, GitHub code scanning

Mobile Application:

Framework: Flutter 3.13 or React Native 0.72
Language: Dart or TypeScript
Testing: flutter test or Jest, 80%+ coverage
State Management: Riverpod, Bloc, or Redux
Local Database: SQLite, Hive, or Realm
HTTP Client: Dio or Axios wrapper
UI: Material Design or Cupertino
DevOps: Fastlane, GitHub Actions for app store deployment
Quality: flutter analyze, dart format, excellent test coverage
Performance: App size <50MB (iOS), startup <2s

CLI Tool:

Language: Go 1.21 or Python 3.13
Testing: Go's built-in testing or pytest
Packaging: Single binary (Go) or PyPI (Python)
Quality: golangci-lint or ruff, <100MB binary
Performance: <100ms startup time

Library:

Language: TypeScript 5.2 or Python 3.13
Testing: Vitest or pytest, 90%+ coverage (libraries = higher bar)
Package Manager: npm/pnpm or uv
Documentation: TSDoc/JSDoc or Google-style docstrings
Type Safety: TypeScript strict or mypy strict

Data Science:

Language: Python 3.13, Jupyter notebooks
ML Framework: scikit-learn, PyTorch, or TensorFlow
Data: pandas, Polars, DuckDB
Testing: pytest, nbval (notebook validation)
Experiment Tracking: MLflow, Weights & Biases
Quality: 80% code coverage, data validation tests

---

Part 5: Writing Checklists

Product.md Checklist

• Mission statement is 1-2 sentences
• Users are specific (not "developers")
• Problems are ranked by priority
• Success metrics are measurable
• Feature backlog has 3-5 next SPECs
• HISTORY section has v0.1.0

Structure.md Checklist

• Architecture is visualized or clearly described
• Modules map to git directories
• External integrations list auth and failure modes
• Traceability explains TAG system
• Trade-offs are documented (why this design?)
• HISTORY section has v0.1.0

Tech.md Checklist

• Primary language with version range specified
• Quality gates define failure criteria (what blocks merges?)
• Security policy covers secrets, audits, incidents
• Deployment describes full release flow
• Environment profiles (dev/test/prod) included
• HISTORY section has v0.1.0

---

Part 6: Common Mistakes to Avoid

❌ Too Vague

• "Users are developers"
• "We'll measure success by growth"

✅ Specific

• "Solo developers building web apps under time pressure, 3-7 person teams"
• "Measure success by 80% adoption within 2 weeks, 5 features/sprint velocity"

---

❌ Over-Specified in product.md

• Function names, database schemas, API endpoints
• "We'll use Redis cache with 1-hour TTL"

✅ Architecture-Level

• "Caching layer for performance"
• "Integration with external payment provider"

---

❌ Inconsistent Across Documents

• product.md: "5 concurrent users"
• structure.md: "Designed for 10,000 daily users"

✅ Aligned

• All 3 documents agree on target scale, user types, quality standards

---

❌ Outdated

• Last updated 6 months ago
• HISTORY section has no recent entries

✅ Fresh

• HISTORY updated every sprint
• version number incremented on changes

---

---

Level 2: Practical Implementation (Common Patterns)

Metadata

• Name: moai-project-documentation
• Domain: Project Documentation & Planning
• Freedom Level: high
• Target Users: Project owners, architects, tech leads
• Invocation: Skill("moai-project-documentation")
• Progressive Disclosure: Metadata → Content (full guide) → Resources (examples)

---

---

Purpose

Guide interactive creation of three core project documentation files (product.md, structure.md, tech.md) based on project type and user input. Provides templates, examples, checklists, and best practices for each project type (Web App, CLI Tool, Library, Data Science).

---

---

Core Content

Part 1: Project Type Selection

Ask user to identify their project type:

1. Web Application

   • Examples: SaaS, web dashboard, REST API backend
   • Focus: User personas, adoption metrics, real-time features
   • Template style: Business-focused with UX emphasis

2. Mobile Application

   • Examples: iOS/Android app, cross-platform app (Flutter, React Native)
   • Focus: User retention, app store metrics, offline capability
   • Template style: UX-driven with platform-specific performance
   • Frameworks: Flutter, React Native, Swift, Kotlin

3. CLI Tool / Utility

   • Examples: Data validator, deployment tool, package manager
   • Focus: Performance, integration, ecosystem adoption
   • Template style: Technical with use case emphasis

4. Shared Library / SDK

   • Examples: Type validator, data parser, API client
   • Focus: Developer experience, ecosystem adoption, performance
   • Template style: API-first with integration focus

5. Data Science / ML Project

   • Examples: Recommendation system, ML pipeline, analytics
   • Focus: Data quality, model metrics, scalability
   • Template style: Metrics-driven with data emphasis

---

Part 2: Product.md Writing Guide

Document Structure

# Mission & Strategy
- What problem do we solve?
- Who are the users?
- What's our value proposition?

# Success Metrics
- How do we measure impact?
- What are KPIs?
- How often do we measure?

# Next Features (SPEC Backlog)
- What features are coming?
- How are they prioritized?

Writing by Project Type

Web Application Product.md Focus:

• User personas (team lead, individual contributor, customer)
• Adoption targets (80% within 2 weeks)
• Integration capabilities (Slack, GitHub, Jira)
• Real-time collaboration features

Mobile Application Product.md Focus:

• User personas (iOS users, Android users, power users)
• Retention metrics (DAU, MAU, churn rate)
• App store presence (rating target, download goal)
• Offline capability requirements
• Push notification strategy
• Platform-specific features (GPS, camera, contacts)

CLI Tool Product.md Focus:

• Target workflow (validate → deploy → monitor)
• Performance benchmarks (1M records in <5s)
• Multi-format support (JSON, CSV, Avro)
• Ecosystem adoption (GitHub stars, npm downloads)

Library Product.md Focus:

• API design philosophy (composable, type-safe)
• Developer experience (time-to-first-validation <5 min)
• Performance characteristics (zero-cost abstractions)
• Community engagement (issue response time, contributions)

Data Science Product.md Focus:

• Model metrics (accuracy, precision, recall)
• Data quality requirements
• Scalability targets (1B+ records)
• Integration with ML platforms (MLflow, W&B)

---

Part 3: Structure.md Writing Guide

Document Structure

# System Architecture
- What's the overall design pattern?
- What layers/tiers exist?
- How do components interact?

# Core Modules
- What are the main building blocks?
- What's each module responsible for?
- How do they communicate?

# External Integrations
- What external systems do we depend on?
- How do we authenticate?
- What's our fallback strategy?

# Traceability
- How do SPECs map to code?
- How do we trace changes?

Architecture Patterns by Project Type

Web Application Architecture:

Frontend (React/Vue) ↔ API Layer (FastAPI/Node) ↔ Database (PostgreSQL)
    ↓
WebSocket Server (Real-time features)
    ↓
Message Queue (Async jobs)
    ↓
Background Workers

Mobile Application Architecture:

UI Layer (Screens, Widgets)
    ↓
State Management (Bloc, Redux, Riverpod)
    ↓
Data Layer (Local DB: SQLite/Realm, Remote: REST/GraphQL)
    ↓
Authentication (OAuth, JWT)
    ↓
Native Modules (Camera, GPS, Contacts)
    ↓
Offline Sync Engine

CLI Tool Architecture:

Input Parsing → Command Router → Core Logic → Output Formatter
                                    ↓
                           Validation Layer
                                    ↓
                            Caching Layer

Library Architecture:

Public API Surface
    ↓
Type Guards / Validation
    ↓
Core Logic
    ↓
Platform Adapters (Node.js, Browser, Deno)

Data Science Architecture:

Data Ingestion → Feature Engineering → Model Training → Inference
    ↓
Feature Store
    ↓
Model Registry
    ↓
Monitoring & Alerting

---

Part 4: Tech.md Writing Guide

Document Structure

# Technology Stack
- What language(s)?
- What version ranges?
- Why these choices?

# Quality Gates
- What's required to merge?
- How do we measure quality?
- What tools enforce standards?

# Security Policy
- How do we manage secrets?
- How do we handle vulnerabilities?
- What's our incident response?

# Deployment Strategy
- Where do we deploy?
- How do we release?
- How do we rollback?

Tech Stack Examples by Type

Web Application:

Frontend: TypeScript, React 18, Vitest, TailwindCSS
Backend: Python 3.13, FastAPI, pytest (85% coverage)
Database: PostgreSQL 15, Alembic migrations
DevOps: Docker, Kubernetes, GitHub Actions
Quality: TypeScript strict mode, mypy, ruff, GitHub code scanning

Mobile Application:

Framework: Flutter 3.13 or React Native 0.72
Language: Dart or TypeScript
Testing: flutter test or Jest, 80%+ coverage
State Management: Riverpod, Bloc, or Redux
Local Database: SQLite, Hive, or Realm
HTTP Client: Dio or Axios wrapper
UI: Material Design or Cupertino
DevOps: Fastlane, GitHub Actions for app store deployment
Quality: flutter analyze, dart format, excellent test coverage
Performance: App size <50MB (iOS), startup <2s

CLI Tool:

Language: Go 1.21 or Python 3.13
Testing: Go's built-in testing or pytest
Packaging: Single binary (Go) or PyPI (Python)
Quality: golangci-lint or ruff, <100MB binary
Performance: <100ms startup time

Library:

Language: TypeScript 5.2 or Python 3.13
Testing: Vitest or pytest, 90%+ coverage (libraries = higher bar)
Package Manager: npm/pnpm or uv
Documentation: TSDoc/JSDoc or Google-style docstrings
Type Safety: TypeScript strict or mypy strict

Data Science:

Language: Python 3.13, Jupyter notebooks
ML Framework: scikit-learn, PyTorch, or TensorFlow
Data: pandas, Polars, DuckDB
Testing: pytest, nbval (notebook validation)
Experiment Tracking: MLflow, Weights & Biases
Quality: 80% code coverage, data validation tests

---

Part 5: Writing Checklists

Product.md Checklist

• Mission statement is 1-2 sentences
• Users are specific (not "developers")
• Problems are ranked by priority
• Success metrics are measurable
• Feature backlog has 3-5 next SPECs
• HISTORY section has v0.1.0

Structure.md Checklist

• Architecture is visualized or clearly described
• Modules map to git directories
• External integrations list auth and failure modes
• Traceability explains TAG system
• Trade-offs are documented (why this design?)
• HISTORY section has v0.1.0

Tech.md Checklist

• Primary language with version range specified
• Quality gates define failure criteria (what blocks merges?)
• Security policy covers secrets, audits, incidents
• Deployment describes full release flow
• Environment profiles (dev/test/prod) included
• HISTORY section has v0.1.0

---

Part 6: Common Mistakes to Avoid

❌ Too Vague

• "Users are developers"
• "We'll measure success by growth"

✅ Specific

• "Solo developers building web apps under time pressure, 3-7 person teams"
• "Measure success by 80% adoption within 2 weeks, 5 features/sprint velocity"

---

❌ Over-Specified in product.md

• Function names, database schemas, API endpoints
• "We'll use Redis cache with 1-hour TTL"

✅ Architecture-Level

• "Caching layer for performance"
• "Integration with external payment provider"

---

❌ Inconsistent Across Documents

• product.md: "5 concurrent users"
• structure.md: "Designed for 10,000 daily users"

✅ Aligned

• All 3 documents agree on target scale, user types, quality standards

---

❌ Outdated

• Last updated 6 months ago
• HISTORY section has no recent entries

✅ Fresh

• HISTORY updated every sprint
• version number incremented on changes

---

---

Examples by Project Type

Example 1: Web App (TaskFlow)

Product.md excerpt:

---

Quality Gates
- Test coverage: 85% minimum
- Type errors: Zero in strict mode
- Bundle size: <200KB gzipped

---

Example 2: Mobile App (FitTracker)

Product.md excerpt:

---

Deployment
- App Store & Google Play via Fastlane
- TestFlight for beta testing
- Version every 2 weeks

---

Example 3: CLI Tool (DataValidate)

Product.md excerpt:

---

Build
- Binary size: <100MB
- Startup time: <100ms
- Distribution: GitHub Releases + Homebrew

---

Example 4: Library (TypeGuard)

Product.md excerpt:

---

Primary Language: TypeScript 5.2+
- Test coverage: 90% (libraries have higher bar)
- Type checking: Zero errors in strict mode
- Bundle: <50KB gzipped, tree-shakeable

---

Example 5: Data Science (ML Pipeline)

Product.md excerpt:

---

Versioning & Updates

**When to update this Skill:**
- New programming languages added to MoAI
- New project type examples needed
- Quality gate standards change
- Package management tools evolve

**Current version:** 0.1.0 (2025-11-04)

---

---

### Level 3: Advanced Patterns (Expert Reference)

> **Note**: Advanced patterns for complex scenarios.

**Coming soon**: Deep dive into expert-level usage.


---

## 🎯 Best Practices Checklist

**Must-Have:**
- ✅ [Critical practice 1]
- ✅ [Critical practice 2]

**Recommended:**
- ✅ [Recommended practice 1]
- ✅ [Recommended practice 2]

**Security:**
- 🔒 [Security practice 1]


---

## 🔗 Context7 MCP Integration

**When to Use Context7 for This Skill:**

This skill benefits from Context7 when:
- Working with [project]
- Need latest documentation
- Verifying technical details

**Example Usage:**

```python
# Fetch latest documentation
from moai_adk.integrations import Context7Helper

helper = Context7Helper()
docs = await helper.get_docs(
    library_id="/org/library",
    topic="project",
    tokens=5000
)

Relevant Libraries:

Library	Context7 ID	Use Case
[Library 1]	/org/lib1	[When to use]

---

📊 Decision Tree

When to use moai-project-documentation:

Start
  ├─ Need project?
  │   ├─ YES → Use this skill
  │   └─ NO → Consider alternatives
  └─ Complex scenario?
      ├─ YES → See Level 3
      └─ NO → Start with Level 1

---

🔄 Integration with Other Skills

Prerequisite Skills:

• Skill("prerequisite-1") – [Why needed]

Complementary Skills:

• Skill("complementary-1") – [How they work together]

Next Steps:

• Skill("next-step-1") – [When to use after this]

---

📚 Official References

Primary Documentation:

• Official Docs – Complete reference

Best Practices:

• Best Practices Guide – Official recommendations

---

📈 Version History

** .0** (2025-11-12)

• ✨ Context7 MCP integration
• ✨ Progressive Disclosure structure
• ✨ 10+ code examples
• ✨ Primary/secondary agents defined
• ✨ Best practices checklist
• ✨ Decision tree
• ✨ Official references

---

Generated with: MoAI-ADK Skill Factory
Last Updated: 2025-11-12
Maintained by: Primary Agent (alfred)