@uoyo/mvtt 2.0.0-beta.0 → 2.0.0-beta.1

package/sources/knowledge/patterns/manifest.yaml

@@ -1,113 +0,0 @@
-patterns:
-  id: patterns
-  name: Architecture Patterns
-  version: "1.0"
-  description: Collection of architecture patterns for software design
-
-loading:
-  priority: 2
-  auto_load: false
-  load_rule: "Load patterns/{active}/* based on config.yaml pattern.active"
-
-available:
-  - id: ddd
-    name: Domain-Driven Design
-    path: ddd/
-    manifest: ddd/manifest.yaml
-    description: Tactical and strategic patterns for complex domain modeling
-    suitable_for:
-      - complex-domain
-      - enterprise-application
-      - bounded-contexts
-    files:
-      - tactical-patterns.md
-      - review-checklist.md
-
-  - id: clean-architecture
-    name: Clean Architecture
-    path: clean-architecture/
-    manifest: clean-architecture/manifest.yaml
-    description: Dependency inversion and layer separation patterns
-    suitable_for:
-      - enterprise-application
-      - long-term-project
-      - multi-interface-system
-    files:
-      - review-checklist.md
-
-  - id: frontend-react
-    name: Frontend (React)
-    path: frontend-react/
-    manifest: frontend-react/manifest.yaml
-    description: Modern React frontend application patterns
-    suitable_for:
-      - web-app
-      - spa
-      - pwa
-      - next.js
-    frameworks:
-      - react
-      - next.js
-      - remix
-    files:
-      - overview.md
-      - component-patterns.md
-      - review-checklist.md
-
-# Custom patterns will be added here during #init analyze
-# Example:
-# custom:
-#   - id: my-custom-pattern
-#     name: My Custom Pattern
-#     path: my-custom-pattern/
-#     generated: true
-#     generated_at: "2026-03-08T12:00:00Z"
-
-custom: []
-
-discovery:
-  description: |
-    To discover available patterns:
-    1. List subdirectories of knowledge/patterns/
-    2. Each subdirectory is a pattern pack
-    3. Read {pattern}/manifest.yaml for pattern details
-
-  to_add_pattern: |
-    1. Create knowledge/patterns/{pattern}/ directory
-    2. Add manifest.yaml with pattern metadata
-    3. Add pattern documentation files
-    4. Register in config.yaml under pattern.available
-    5. Add to this file's available or custom list
-
-pattern_selection_guide:
-  description: |
-    During #init, analyze project and suggest appropriate pattern:
-
-  decision_tree: |
-    1. Is this a frontend web application?
-       → If React/Next.js/Remix: suggest frontend-react
-       → If Vue/Svelte: suggest generic (or add more patterns)
-
-    2. Is this a CLI tool, library, or simple service?
-       → Suggest generic
-
-    3. Does the domain have complex business rules?
-       → Suggest DDD
-
-    4. Is this a long-term enterprise application?
-       → Suggest Clean Architecture or DDD
-
-    5. Uncertain or unique architecture?
-       → Offer "analyze" option to create custom pattern
-
-  user_options:
-    - id: yes
-      description: Accept recommended pattern
-    - id: "{pattern_id}"
-      description: Select specific pattern by ID
-    - id: analyze
-      description: Analyze project and create custom pattern
-    - id: generic
-      description: Use generic pattern
-    - id: none
-      description: Proceed without architecture pattern

package/sources/skills/mvt-add-context/business.md

@@ -1,47 +0,0 @@
-## Execution Flow
-
-### Step 1: Assess Current State
-- Read project-context.yaml and evaluate completeness:
-  - Project name empty -> Mark as "not initialized"
-  - Requirements empty -> Mark as "no requirements"
-  - Architecture empty -> Mark as "no architecture"
-- Read config.yaml:
-  - Check `pattern.active`
-- Calculate and display context completeness percentage
-
-### Step 2: Guided Information Collection
-Based on what is missing, guide the user through relevant sections:
-
-**If not initialized** (project basics):
-- Project name, type, description
-- Tech stack (language, framework, build tool, test framework)
-- Suggest running `/mvt-init` for automatic detection
-
-**If no requirements** (requirements & background):
-- Main features and goals
-- User roles and use cases
-- Known constraints and limitations
-
-**If no architecture** (architecture info):
-- Architecture pattern (DDD / Clean Architecture / etc.)
-- Module structure
-- Key technical decisions
-
-**Supplementary information** (always available):
-- Project-specific coding standards
-- Team conventions
-- Third-party integration details
-
-### Step 3: Write Context
-Based on information collected:
-1. Update `.ai-agents/workspace/project-context.yaml` (matching fields)
-2. Update `.ai-agents/workspace/session.yaml` (if initialization changed)
-3. If coding standards provided -> Write to `.ai-agents/knowledge/principle/`
-4. If project knowledge provided -> Write to `.ai-agents/knowledge/project/`
-5. Update `config.yaml` `pattern.active` if user confirmed architecture pattern
-
-### Step 4: Verification Report
-- Show updated context summary
-- Display completeness change (before vs after)
-- If context is large -> Suggest running `/mvt-check-context`
-- Suggest next steps

package/sources/skills/mvt-add-context/manifest.yaml

@@ -1,83 +0,0 @@
-name: mvt-add-context
-output: .claude/skills/mvt-add-context/SKILL.md
-
-frontmatter:
-  name: mvt-add-context
-  description: "Interactively add or update project context information to the MVTT workspace. Use when user wants to manually add project details, requirements, architecture info, coding standards, or team conventions."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Context Add
-
-      ## Purpose
-
-      Guide users through adding or updating project context information in the MVTT workspace. This is a user-driven, interactive process complementary to `/mvt-sync-context` (which is code-driven and automatic).
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "Project not initialized -> Suggest `/mvt-init` first, but allow manual context entry"
-        - rule: "Missing project basics -> Guide through project info collection"
-        - rule: "Missing requirements -> Guide through requirements entry"
-        - rule: "Missing architecture -> Guide through architecture info"
-        - rule: "User provides coding standards -> Write to knowledge/principle/"
-        - rule: "User provides project knowledge -> Write to knowledge/project/"
-      boundaries:
-        - scope: "analyze code automatically"
-          skill: "/mvt-sync-context or /mvt-analyze-code"
-        - scope: "make architecture decisions"
-          skill: "/mvt-design"
-        - scope: "write implementation code"
-          skill: "/mvt-implement"
-
-  - type: shared
-    source: sections/activation-load-context.md
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: inline
-    content: |
-      ### Step 3: Pre-flight Checks
-      - No blocking checks required.
-
-      ### Step 4: Execute
-      Proceed to Execution Flow below.
-
-  - type: file
-    source: ./business.md
-
-  - type: inline
-    content: |
-      ## Output Format
-
-      No external template -- output is inline:
-
-      ```markdown
-      ## Context Updated
-
-      ### Completeness
-      - **Before**: {pct_before}%
-      - **After**: {pct_after}%
-
-      ### Changes Made
-      | Section | Status | Details |
-      |---------|--------|---------|
-      | Project Info | {Updated/Unchanged} | {summary} |
-      | Requirements | {Updated/Unchanged} | {summary} |
-      | Architecture | {Updated/Unchanged} | {summary} |
-      | Knowledge | {Updated/Unchanged} | {summary} |
-
-      ### Files Modified
-      - {list of modified files}
-
-      ---
-      **Suggested Next Steps**:
-      - `/mvt-check-context` -- Analyze context load if context is large
-      - `/mvt-analyze` -- Start requirements analysis
-      - `/mvt-status` -- View current project status
-      ```

package/sources/templates/analyze-code-output/body.md

@@ -1,44 +0,0 @@
-## Codebase Analysis Report
-
-### Project: {name}
-- **Root**: `{root_path}`
-- **Primary Language**: {language}
-- **Detected Framework**: {framework}
-
-### Architecture Discovery
-
-#### Module Structure
-| Module | Path | Responsibility | Type |
-|--------|------|----------------|------|
-| {module} | `{path}` | {description} | {Domain/Application/Infrastructure/Interface} |
-
-#### Entity Inventory
-| Entity | Location | Relationships |
-|--------|----------|---------------|
-| {entity} | `{file}` | {related_entities} |
-
-#### Service Inventory
-| Service | Location | Dependencies | Methods |
-|---------|----------|--------------|---------|
-| {service} | `{file}` | {deps} | {methods} |
-
-### Dependency Analysis
-```mermaid
-graph TD
-    A[Module A] --> B[Module B]
-    B --> C[Module C]
-```
-
-### Key Findings
-| # | Finding | Type | Severity |
-|---|---------|------|----------|
-| 1 | {finding} | {architecture/code-quality/dependency} | {info/warning/concern} |
-
-### Workspace Updated
-- [x] project-context.yaml updated with discovered structure
-- [x] session.yaml updated
-
----
-**Suggested Next Steps**:
-- `/mvt-analyze {requirements}` to add requirements on top of discovered structure
-- `/mvt-design` to design new features for existing architecture

package/sources/templates/analyze-code-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: analyze-code-output
-output: .ai-agents/skills/_templates/analyze-code-output.md
-
-frontmatter:
-  id: analyze-code-output
-  version: "1.0"
-  skill: mvt-analyze-code
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/cleanup-output/body.md

@@ -1,9 +0,0 @@
-## Workspace Cleanup
-
-### Cleanup Candidates
-| Item | Current Size | Action | Result |
-|------|-------------|--------|--------|
-| {artifact} | ~{tokens} tokens | {Summarize/Remove} | ~{reduced} tokens |
-| **Total** | **~{total} tokens** | | **~{new_total} tokens ({savings} saved)** |
-
-Proceed with cleanup? [Y/n]

package/sources/templates/cleanup-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: cleanup-output
-output: .ai-agents/skills/_templates/cleanup-output.md
-
-frontmatter:
-  id: cleanup-output
-  version: "1.0"
-  skill: mvt-cleanup
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/config-output/body.md

@@ -1,11 +0,0 @@
-## Configuration Manager
-
-| # | Category | Current Settings |
-|---|----------|------------------|
-| 1 | System | Language: {lang}, Mode: {mode} |
-| 2 | Output | Format: {format}, Emojis: {on/off} |
-| 3 | Pattern | Active: {pattern} |
-| 4 | Wizard | Start guided setup |
-| 5 | Reset | Reset to defaults |
-
-**Select (1-5):**

package/sources/templates/config-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: config-output
-output: .ai-agents/skills/_templates/config-output.md
-
-frontmatter:
-  id: config-output
-  version: "1.0"
-  skill: mvt-config
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/context-check-output/body.md

@@ -1,32 +0,0 @@
-## Context Load Analysis Report
-
-### Overall Assessment
-- **Total Context Size**: ~{total_tokens} tokens
-- **Health Status**: {Good / Moderate / High / Overloaded}
-
-### Breakdown by Category
-| Category | Files | Est. Tokens | Percentage |
-|----------|-------|-------------|------------|
-| Core (session + context) | {n} | {tokens} | {pct}% |
-| Knowledge | {n} | {tokens} | {pct}% |
-| Artifacts | {n} | {tokens} | {pct}% |
-| Skills | {n} | {tokens} | {pct}% |
-| **Total** | **{n}** | **{tokens}** | **100%** |
-
-### Top 5 Largest Files
-| Rank | File | Est. Tokens | Suggestion |
-|------|------|-------------|------------|
-| 1 | {file} | {tokens} | {suggestion} |
-| 2 | {file} | {tokens} | {suggestion} |
-| 3 | {file} | {tokens} | {suggestion} |
-| 4 | {file} | {tokens} | {suggestion} |
-| 5 | {file} | {tokens} | {suggestion} |
-
-### Optimization Recommendations
-1. {recommendation_1}
-2. {recommendation_2}
-
----
-**Suggested Next Steps**:
-- `/mvt-cleanup` - Clean up old artifacts to reduce context size
-- `/mvt-context-add` - Update project context if information is outdated

package/sources/templates/context-check-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: context-check-output
-output: .ai-agents/skills/_templates/context-check-output.md
-
-frontmatter:
-  id: context-check-output
-  version: "1.0"
-  skill: mvt-context-check
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/fix-output/body.md

@@ -1,30 +0,0 @@
-## Bug Fix: {Issue Description}
-
-### Issue Analysis
-- **Symptom**: {what_user_observes}
-- **Root Cause**: {why_it_happens}
-- **Impact**: {what_is_affected}
-
-### Root Cause Analysis
-| # | Hypothesis | Evidence | Result |
-|---|-----------|----------|--------|
-| 1 | {hypothesis} | {evidence} | {confirmed/rejected} |
-
-### Fix Applied
-| File | Line | Before | After |
-|------|------|--------|-------|
-| `{file}` | {line} | {old_code} | {new_code} |
-
-### Implementation
-```{language}
-{fix_code}
-```
-
-### Verification
-- {how_to_verify_fix}
-- {test_command_if_applicable}
-
----
-**Suggested Next Steps**:
-- `/mvt-review` to verify the fix
-- `/mvt-test` to add regression tests

package/sources/templates/fix-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: fix-output
-output: .ai-agents/skills/_templates/fix-output.md
-
-frontmatter:
-  id: fix-output
-  version: "1.0"
-  skill: mvt-fix
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/init-output/body.md

@@ -1,34 +0,0 @@
-## Project Initialization Complete
-
-### Project: {name}
-- **Type**: {type}
-- **Pattern**: {pattern}
-- **Tech Stack**: {language} / {framework}
-
-### Architecture Pattern Selection
-
-| Detected Pattern | Confidence |
-|------------------|------------|
-| {pattern_name} | {high/medium/low} |
-
-**Available Patterns**:
-1. `ddd` - Domain-Driven Design
-2. `clean-architecture` - Layer separation with dependency inversion
-3. `frontend-react` - React/Next.js frontend
-4. `generic` - Simple projects without specific architecture
-
-**Recommended**: `{suggested_pattern}`
-
-- Reply `yes` to accept
-- Reply with pattern name to select different
-- Reply `analyze` to create a custom pattern from project analysis
-- Reply `none` to proceed without a pattern
-
-### Workspace Updated
-- [x] project-context.yaml
-- [x] session.yaml
-
----
-**Suggested Next Steps**:
-- `/mvt-analyze {requirements}` - Start analyzing requirements
-- `/mvt-status` - View project status

package/sources/templates/init-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: init-output
-output: .ai-agents/skills/_templates/init-output.md
-
-frontmatter:
-  id: init-output
-  version: "1.0"
-  skill: mvt-init
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/refactor-output/body.md

@@ -1,32 +0,0 @@
-## Refactoring: {Target}
-
-### Refactoring Type
-{type from: Extract Method/Class, Rename, Move, Decompose Conditional, Replace Inheritance with Composition, Change Interface/API}
-
-### Goals
-- {goal_1}
-- {goal_2}
-
-### Risk Assessment
-- **Risk Level**: {Low | Medium | High}
-- **Impact Scope**: {number} files in {number} modules
-- **Test Coverage**: {Covered | Partial | None}
-
-### Changes
-| File | Action | Before | After |
-|------|--------|--------|-------|
-| `{file}` | {Create/Modify/Delete} | {description} | {description} |
-
-### Implementation
-```{language}
-{refactored_code}
-```
-
-### Behavior Verification
-- {how_behavior_is_preserved}
-- {test_commands_or_manual_verification_steps}
-
----
-**Suggested Next Steps**:
-- `/mvt-review` to verify changes
-- `/mvt-test` to run tests

package/sources/templates/refactor-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: refactor-output
-output: .ai-agents/skills/_templates/refactor-output.md
-
-frontmatter:
-  id: refactor-output
-  version: "1.0"
-  skill: mvt-refactor
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/status-output/body.md

@@ -1,36 +0,0 @@
-## Project Status
-
-### Current: {phase} Phase ({agent})
-
-```mermaid
-flowchart LR
-    A[analyze] ===> B[design] ---> C[implement] ---> D[review] ---> E[test]
-    style A fill:#90EE90
-    style B fill:#FFD700
-    style C fill:#E0E0E0
-    style D fill:#E0E0E0
-    style E fill:#E0E0E0
-```
-
-### Project: {name}
-- **Type**: {type}
-- **Initialized**: {date}
-- **Tech Stack**: {language} / {framework}
-
-### Progress This Session
-| Phase | Status | Completed |
-|-------|--------|-----------|
-| Analyze | {status} | {time} |
-| Design | {status} | {time} |
-| Implement | {status} | {time} |
-| Review | {status} | {time} |
-| Test | {status} | {time} |
-
-### Active Change
-- **Change ID**: {change_id}
-- **Title**: {title}
-- **Started**: {date}
-
----
-**Suggested Next Steps**:
-- {relevant_next_step}

package/sources/templates/status-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: status-output
-output: .ai-agents/skills/_templates/status-output.md
-
-frontmatter:
-  id: status-output
-  version: "1.0"
-  skill: mvt-status
-
-sections:
-  - type: file
-    source: ./body.md

package/sources/templates/sync-context-output/body.md

@@ -1,16 +0,0 @@
-## Context Sync Complete
-
-### Files Analyzed
-| File | Change Type | Entities | Services |
-|------|-------------|----------|----------|
-| {file_path} | {Modified/Added/Deleted} | {entities} | {services} |
-
-### Index Updates
-- **Topics added**: {count}
-- **Entities added**: {count}
-- **Keywords added**: {count}
-
----
-**Suggested Next Steps**:
-- Continue with your current task
-- `/mvt-status` to verify context state

package/sources/templates/sync-context-output/manifest.yaml

@@ -1,11 +0,0 @@
-name: sync-context-output
-output: .ai-agents/skills/_templates/sync-context-output.md
-
-frontmatter:
-  id: sync-context-output
-  version: "1.0"
-  skill: mvt-sync-context
-
-sections:
-  - type: file
-    source: ./body.md