Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-08 | ✗→✓ | ▲ Improved | 37% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 82% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 70% | 0% |
| case-14 | ✗→✓ | ▲ Improved | 85% | 0% |
| case-17 | ✗→✓ | ▲ Improved | 46% | 0% |
Comprehensive project management system integrating documentation generation, multilingual support, and template optimization into a unified architecture with intelligent automation and Claude Code integration.
Scope: Consolidates documentation management, language initialization, and template optimization into a single cohesive system supporting complete project lifecycle from initialization to maintenance.
Target: Claude Code agents for project setup, documentation generation, multilingual support, and performance optimization.
Core Capabilities:
Key Features:
Supported Project Types: web applications, mobile applications, CLI tools, libraries, ML projects.
Three capability areas:
Three workflows: project initialization, documentation generation from SPEC, template performance optimization. Each follows a 3-step pattern (configure → execute → review results).
See core workflow walkthroughs for detailed step-by-step procedures.
Automatic Language Detection: analyzes file content, configuration files, system locale, and directory structure.
Multilingual Documentation: language-specific directories (e.g., docs/ko, docs/en), language negotiation, automatic redirection.
Agent Prompt Localization: language-specific instructions, cultural context, token cost optimization.
See language and localization detail for token cost analysis and locale configuration.
Performance Analysis: file size, complexity, performance bottlenecks, optimization opportunities, resource usage, backup recommendations.
Optimization Techniques: whitespace reduction, structure optimization, complexity reduction, performance caching.
Integrated configuration covers project metadata, language settings + costs, documentation status, template optimization results, module initialization states.
Language Settings: conversation_language (user-facing), agent_prompt_language (internal, often English for cost), documentation language (per language).
Updates trigger configuration file modifications, documentation structure updates, template localization.
See configuration schema and language fields for full field reference and supported language metadata.
For advanced patterns (custom templates, performance caching, batch processing, integration workflows), see references/reference.md and references/examples.md.
| Operation | Typical Duration | |-----------|------------------| | Complete documentation generation | 2-5 seconds | | Language detection analysis | ~500 ms | | Template optimization | 10-30 seconds | | Configuration updates | ~100 ms |
Memory: base ~50MB, large projects +10-50MB, optimization cache 5-20MB.
File sizes: documentation 50-200KB per project, optimization backups match originals, configuration 5-10KB.
<!-- moai:evolvable-start id="rationalizations" -->
| Rationalization | Reality | |---|---| | "project docs are a one-time setup, no need to keep them current" | Stale product.md and tech.md mislead every SPEC written against them. They are living documents. | | "structure.md will stay accurate since the codebase does not change much" | Every PR that adds a directory invalidates structure.md. Sync on every /moai project invocation. | | "I know the tech stack, I do not need tech.md" | tech.md is not for you. It is for every agent that consults the project context before acting. | | "codemaps take too long to generate" | codemaps are the only artifact that gives agents file-level awareness without reading every file. The cost pays for itself. | | "I will write project docs after the feature is done" | Post-hoc docs capture what was built, not what was intended. Pre-feature docs guide the build. |
<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="red-flags" -->
<!-- moai:evolvable-end -->
<!-- moai:evolvable-start id="verification" -->
ls output of the project root<!-- moai:evolvable-end -->
Code boilerplates, feedback templates, scaffolding, and project template optimization.
Analysis metrics: file size, complexity score, redundancy ratio, load performance. Optimization techniques: whitespace reduction, deduplication, structure simplification. Always create backup before applying optimization (backup: true).
Technical docs generation using Sphinx, MkDocs, TypeDoc, OpenAPI, and Nextra. Covers project configuration discovery, how to integrate with existing docs sites, and best practices for keeping framework documentation and technology guide content current.
| Generator | Use Case | Primary Format | |-----------|----------|----------------| | Sphinx | Python projects, API docs | RST / Markdown | | MkDocs | General projects | Markdown | | TypeDoc | TypeScript libraries | TypeScript JSDoc | | OpenAPI / Swagger | REST APIs | YAML / JSON | | Nextra | Next.js docs sites | MDX |
.moai/config/sections/language.yaml/moai sync artifacts: README, CHANGELOG, API referenceJIT docs (just in time docs) — on-demand documentation discovery and loading based on user intent and conversation context.
.moai/, README, SPEC documents)Token budget: 5000 tokens per JIT load. Summarize if source exceeds budget.
Other measured skills in the registry, with their headline benchmark lift.