appiq-solution 1.4.7 → 1.4.9

package/#Tools/APPIQ-METHOD/activate-appiq.js

@@ -1,81 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * APPIQ Activation Script
- * 
- * This script should be loaded in your IDE to enable APPIQ slash commands.
- * 
- * Usage in IDE:
- * 1. Load this file in your IDE
- * 2. Use commands like /appiq, /story, /analyze, /help
- */
-
-const fs = require('fs');
-const path = require('path');
-
-// Check if APPIQ is installed
-const bmadPath = path.join(process.cwd(), 'bmad-core');
-if (!fs.existsSync(bmadPath)) {
-  console.log('❌ APPIQ-METHOD not found in current directory');
-  console.log('📥 Install with: curl -fsSL https://raw.githubusercontent.com/Viktor-Hermann/APPIQ-METHOD/main/install-appiq.sh | bash');
-  process.exit(1);
-}
-
-console.log('🚀 APPIQ-METHOD Activated!');
-console.log('========================\n');
-
-console.log('✅ APPIQ installation detected');
-console.log('📁 Location:', bmadPath);
-
-// Load smart launcher agent
-const smartLauncherPath = path.join(bmadPath, "agents", "init-flow-po.md");
-if (fs.existsSync(smartLauncherPath)) {
-  console.log('🤖 Smart Launcher Agent available');
-} else {
-  console.log('⚠️  Smart Launcher Agent not found');
-}
-
-console.log('\n💡 Available Commands:');
-console.log('   /appiq   - Start intelligent project creation');
-console.log('   /story   - Create a new development story');
-console.log('   /analyze - Analyze current project');
-console.log('   /help    - Get context-aware help');
-
-console.log('\n🎯 How to use:');
-console.log('1. Copy and paste the agent file content into your IDE');
-console.log('2. Type any of the commands above');
-console.log('3. Follow the intelligent workflow guidance');
-
-console.log('\n📚 Agent Files:');
-console.log(`   Smart Launcher: ${smartLauncherPath}`);
-
-// Check for Flutter expansion pack
-const flutterExpansionPath = path.join(process.cwd(), 'expansion-packs', 'bmad-flutter-mobile-dev');
-if (fs.existsSync(flutterExpansionPath)) {
-  console.log('\n📱 Flutter Expansion Pack detected');
-  console.log('   Additional Flutter agents available');
-}
-
-console.log('\n🔧 Manual Setup (if commands don\'t work):');
-console.log('1. Load the Smart Launcher agent in your IDE:');
-console.log(`   File: ${smartLauncherPath}`);
-console.log('2. Tell your IDE: "Act as the agent defined in this file"');
-console.log('3. Use the commands: /appiq, /story, /analyze, /help');
-
-console.log('\n💬 Need Help?');
-console.log('   - GitHub: https://github.com/Viktor-Hermann/APPIQ-METHOD');
-console.log('   - Discord: https://discord.gg/gk8jAdXWmj');
-
-// Display agent content for easy copying
-if (fs.existsSync(smartLauncherPath)) {
-  console.log('\n' + '='.repeat(80));
-  console.log('📋 SMART LAUNCHER AGENT (Copy this to your IDE):');
-  console.log('='.repeat(80));
-  
-  const agentContent = fs.readFileSync(smartLauncherPath, 'utf8');
-  console.log(agentContent);
-  
-  console.log('\n' + '='.repeat(80));
-  console.log('📋 END OF AGENT CONTENT');
-  console.log('='.repeat(80));
-}

package/#Tools/APPIQ-METHOD/appiq-solution/README.md

@@ -1,226 +0,0 @@
-# 🚀 APPIQ SOLUTION - The Ultimate AI Agent Framework
-*Built with ❤️ based on the amazing Bmad-Method*
-
-[![Version](https://img.shields.io/npm/v/appiq-solution?color=blue&label=version)](https://www.npmjs.com/package/appiq-solution)
-[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Security](https://img.shields.io/badge/Security-First-green.svg)](README.md)
-
-## ⚡ One-Command Installation (10 Seconds)
-
-```bash
-npx appiq-solution install
-```
-
-**Das war's!** 🎯 Die einfachste AI-Agent Installation der Welt.
-
-### 🆕 **Was ist neu in v1.0.7?**
-- ✅ **Security-First**: Keine API-Keys im Code gespeichert
-- ✅ **Multi-IDE Support**: 8+ IDEs automatisch konfiguriert
-- ✅ **Smart MCP Integration**: Agenten wissen, welche MCPs sie nutzen können
-- ✅ **Planning Workflow**: Projektidee → Plan → Freigabe → Entwicklung
-- ✅ **Flutter Support**: Dart MCP, Clean Architecture, Cubit patterns
-- ✅ **Modern Web**: shadcn/ui, v0.dev, Tailwind CSS integration
-
-## 🎮 Was passiert automatisch?
-
-### 1. **🔍 Intelligente Projekt-Erkennung**
-- ✅ **Automatisch erkennt:** Greenfield vs. Brownfield
-- ✅ **Analysiert:** Bestehenden Code, Dokumentation, Tech-Stack
-- ✅ **Empfiehlt:** Optimalen Workflow für Ihr Projekt
-
-### 2. **🛠️ Multi-IDE Integration (8+ IDEs)**
-- ✅ **Cursor** → `.cursor/rules/` mit `.mdc` Dateien
-- ✅ **Claude Code CLI** → Gemini CLI-kompatible Konfiguration
-- ✅ **Windsurf** → `.windsurf/rules/` mit `.md` Dateien
-- ✅ **VS Code + Cline** → `.clinerules/` mit `.md` Dateien
-- ✅ **Trae** → `.trae/` Konfiguration
-- ✅ **Roo Code** → `.roo/` Konfiguration
-- ✅ **Gemini CLI** → `.gemini/settings.json`
-- ✅ **GitHub Copilot** → VS Code Settings Integration
-
-### 3. **🔌 Smart MCP Integration (Security-First)**
-- ✅ **Agent-Awareness**: Agenten wissen, welche MCPs sie nutzen können
-- ✅ **Keine Auto-Konfiguration**: Sie konfigurieren MCPs manuell in Ihrer IDE
-- ✅ **Keine API-Keys**: Sichere Integration ohne Secrets im Code
-- ✅ **Flutter-Optimiert**: Dart MCP automatisch erkannt für Flutter-Projekte
-
-### 4. **📁 Automatische Datei-Organisation**
-
-**Neue Projekte (Greenfield):**
-```
-your-project/
-├── docs/
-│   ├── prd.md              ← PRD wird hier erstellt
-│   ├── architecture.md     ← Architektur wird hier erstellt
-│   └── stories/            ← User Stories werden hier erstellt
-├── appiq-solution/
-│   ├── agents/             ← Optimierte KI-Agents
-│   └── commands/           ← One-Click Kommandos
-└── .cursor/rules/          ← IDE-spezifische Integration
-```
-
-**Bestehende Projekte (Brownfield):**
-```
-your-existing-project/
-├── docs/                   ← Bestehende Docs werden gescannt
-│   ├── prd.md             ← PRD falls vorhanden, sonst erstellt
-│   └── architecture.md     ← Architektur-Review
-├── appiq-solution/         ← Neue Appiq Solution Installation
-└── .cursor/rules/          ← IDE Integration (nicht-invasiv)
-```
-
-## 🚀 Super Einfache Nutzung
-
-### Schritt 1: Installation (10 Sekunden)
-```bash
-npx appiq-solution install
-```
-
-### Schritt 2: Starten Sie den Smart Launcher
-```bash
-# In Ihrer IDE (Cursor, Claude Code, Windsurf, etc.):
-@smart-launcher
-```
-
-### Schritt 3: Folgen Sie dem intelligenten Workflow
-```bash
-# Das System führt Sie automatisch durch:
-# 1. Projektidee eingeben
-# 2. Tech-Stack auswählen (oder automatisch erkennen)
-# 3. IDE(s) auswählen (Multi-Select möglich!)
-# 4. Plan generieren lassen
-# 5. Plan freigeben
-# 6. Entwicklung starten mit optimalen Agents
-```
-
-**Das war's!** 🎉 Alles andere passiert automatisch.
-
-## 🎯 **Verfügbare MCP Server (Agent-Awareness)**
-
-Ihre Agenten wissen über diese MCPs Bescheid (Sie konfigurieren sie manuell):
-
-- **🧠 Sequential Thinking**: Complex problem solving
-- **🌐 Puppeteer**: Browser automation and testing  
-- **🔗 Claude Continuity**: Enhanced thread continuity
-- **💾 Extended Memory**: Enhanced AI memory capabilities
-- **✨ 21st.dev Magic**: UI builder like v0 in your IDE
-- **📱 Dart MCP**: Flutter/Dart development (auto-detected for Flutter projects)
-- **🔥 Firebase**: Auth, Firestore, Functions integration
-- **⚡ Supabase**: Database, auth, storage
-- **📚 Context7**: Up-to-date library documentation
-- **💳 Stripe**: Payment integration
-
-## 🎯 One-Click Workflows
-
-### Greenfield (Neue Projekte)
-```
-/start → PRD → Architektur → Stories → Code → Tests
-```
-
-### Brownfield (Bestehende Projekte)  
-```
-/analyze → Review → Neue Features → Integration → Tests
-```
-
-## 🤖 Optimierte Agents
-
-| Agent | Kommando | Funktion |
-|-------|----------|----------|
-| **Appiq Launcher** | `/start` | Intelligenter Projekt-Start |
-| **Project Manager** | `/prd` | PRD & Dokumentation |
-| **System Architect** | `/architecture` | Technische Architektur |
-| **Story Master** | `/story` | User Stories & Sprints |
-| **Senior Developer** | `/code` | Code Implementation |
-| **QA Expert** | `/test` | Testing & Validierung |
-
-## 💡 Warum Appiq Solution?
-
-### ❌ **Vorher (BMAD-METHOD komplex):**
-- ✗ Komplexer Web-Client Setup
-- ✗ Manuelle Agent-Auswahl
-- ✗ Separate MCP-Konfiguration
-- ✗ Viele manuelle Schritte
-- ✗ Unklare IDE-Integration
-
-### ✅ **Jetzt (APPIQ SOLUTION einfach):**
-- ✅ **Ein Kommando:** `npx appiq-solution install`
-- ✅ **Multi-IDE Support:** 8+ IDEs automatisch konfiguriert
-- ✅ **Smart MCP Integration:** Agent-Awareness ohne Auto-Config
-- ✅ **Security-First:** Keine API-Keys im Code
-- ✅ **Planning Workflow:** Projektidee → Plan → Freigabe → Entwicklung
-- ✅ **Modern Tech Stacks:** Flutter, React, Vue, shadcn/ui, v0.dev
-
-## 🆘 Hilfe & Support
-
-### Quick Commands
-- **`/help`** - Alle verfügbaren Kommandos
-- **`/status`** - Aktueller Projekt-Status
-- **`/next`** - Nächster Schritt
-
-### Troubleshooting
-```bash
-# Installation prüfen
-ls appiq-solution/
-
-# Agent-Liste anzeigen  
-ls appiq-solution/agents/
-
-# IDE-Integration prüfen
-ls .cursor/rules/     # für Cursor
-ls .claude/commands/  # für Claude Code
-```
-
-## 🎮 Beispiel-Session
-
-```bash
-# Installation
-$ npx appiq-solution install
-🔍 Projekt-Analyse... → Brownfield erkannt
-🛠️ IDE: Cursor ausgewählt  
-✅ Installation abgeschlossen!
-
-# In Cursor IDE
-> "Agiere als Appiq Launcher"
-> /analyze
-
-🔍 Analyzing existing project...
-✅ Found: package.json (Node.js project)
-✅ Found: src/ directory with React components
-✅ Missing: PRD documentation
-📋 Recommendation: Create PRD first, then add new features
-
-> /prd
-
-📝 Creating PRD for existing React project...
-✅ PRD created: docs/prd.md
-🎯 Next: /architecture to review technical setup
-```
-
-**So einfach ist das!** 🚀
-
----
-
-## 🔗 **Links & Resources**
-
-- **📦 NPM Package**: [https://www.npmjs.com/package/appiq-solution](https://www.npmjs.com/package/appiq-solution)
-- **📖 Smart Workflow Guide**: [SMART_WORKFLOW_GUIDE.md](../SMART_WORKFLOW_GUIDE.md)
-- **🏗️ Original BMAD-METHOD**: [https://github.com/bmadcode/BMAD-METHOD](https://github.com/bmadcode/BMAD-METHOD)
-- **💬 Discord Community**: [https://discord.gg/gk8jAdXWmj](https://discord.gg/gk8jAdXWmj)
-
-## 🎉 **Fazit**
-
-APPIQ Solution ist die einfachste, sicherste und modernste Art, AI-Agenten für die Entwicklung zu nutzen. Mit nur einem Befehl erhalten Sie:
-
-- ✅ **One-Command Installation** - 10 Sekunden Setup
-- ✅ **Multi-IDE Support** - 8+ IDEs automatisch konfiguriert
-- ✅ **Smart MCP Integration** - Security-First Approach
-- ✅ **Modern Tech Stacks** - Flutter, React, Vue, shadcn/ui, v0.dev
-- ✅ **Full BMAD Flow** - Planning → Approval → Development
-
-**Bereit loszulegen?**
-```bash
-npx appiq-solution install
-```
-
-*APPIQ Solution - Die Zukunft der AI-gestützten Entwicklung.*  
-*Built with ❤️ based on the amazing Bmad-Method*

package/#Tools/APPIQ-METHOD/bmad-core/agent-teams/team-all.yaml

@@ -1,14 +0,0 @@
-bundle:
-  name: Team All
-  icon: 👥
-  description: Includes every core system agent.
-agents:
-  - bmad-orchestrator
-  - '*'
-workflows:
-  - brownfield-fullstack.yaml
-  - brownfield-service.yaml
-  - brownfield-ui.yaml
-  - greenfield-fullstack.yaml
-  - greenfield-service.yaml
-  - greenfield-ui.yaml

package/#Tools/APPIQ-METHOD/bmad-core/agent-teams/team-flutter-mobile.yaml

@@ -1,114 +0,0 @@
-bundle:
-  name: Team Flutter Mobile
-  icon: 📱
-  description: Specialized team for Flutter mobile app development with Clean Architecture, Material Design 3, and feature-based structure.
-  
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - ux-expert
-  - architect
-  - po
-  - sm
-  - dev
-  - qa
-  # Flutter-specific agents from expansion pack
-  - flutter-ui-agent
-  - flutter-cubit-agent
-  - flutter-domain-agent
-  - flutter-data-agent
-  - shared-components-agent
-
-workflows:
-  - brownfield-fullstack.yaml
-  - greenfield-fullstack.yaml
-  - flutter-ui-first-development.yaml
-
-expansion_packs:
-  - bmad-flutter-mobile-dev
-
-capabilities:
-  - Flutter Clean Architecture implementation
-  - Material Design 3 mobile UI
-  - Feature-based development structure
-  - Cubit state management
-  - Comprehensive testing (unit/widget/integration)
-  - Multi-language localization
-  - Responsive design (phone/tablet)
-  - Performance optimization
-  - Accessibility compliance
-  - Platform-specific integrations
-
-tech_stack:
-  frontend:
-    - Flutter (Dart)
-    - Material Design 3
-  state_management:
-    - Cubit/BLoC pattern
-    - Equatable for value equality
-  architecture:
-    - Clean Architecture
-    - Feature-based folder structure
-  data:
-    - Freezed for data models
-    - JSON serialization
-    - Repository pattern
-  dependency_injection:
-    - GetIt + Injectable
-  networking:
-    - Dio HTTP client
-    - API integration
-  local_storage:
-    - Hive database
-    - Secure storage
-  navigation:
-    - GoRouter
-    - Deep linking
-  testing:
-    - Unit tests
-    - Widget tests
-    - Integration tests
-    - Golden tests
-  tools:
-    - Build Runner
-    - Code generation
-    - Performance profiling
-
-project_types:
-  - flutter-mobile-app
-  - cross-platform-app
-  - mobile-first-pwa
-  - enterprise-mobile
-  - consumer-mobile-app
-
-workflow_specialization:
-  ui_first_development:
-    sequence:
-      - UI/UX design and wireframes
-      - Flutter presentation layer implementation
-      - State management with Cubit
-      - Domain layer business logic
-      - Data layer and API integration
-      - Testing and quality assurance
-      - Performance optimization
-
-quality_standards:
-  - DRY: Reusable widgets and business logic
-  - Readable: Clear code structure and naming
-  - Maintainable: Modular feature-based architecture
-  - Performant: Optimized for mobile performance
-  - Testable: Comprehensive test coverage
-  - Secure: Security validation at all layers
-  - Localized: Multi-language support required
-  - Accessible: WCAG compliance for mobile
-
-when_to_use:
-  - Building Flutter mobile applications
-  - Cross-platform mobile development
-  - Material Design 3 implementation
-  - Feature-based architecture projects
-  - Clean Architecture mobile apps
-  - Mobile-first responsive applications
-  - Enterprise mobile solutions
-  - Consumer mobile applications

package/#Tools/APPIQ-METHOD/bmad-core/agent-teams/team-fullstack.yaml

@@ -1,28 +0,0 @@
-bundle:
-  name: Team Fullstack
-  icon: 🚀
-  description: Team capable of full stack, front end only, service development, and Flutter mobile apps.
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - ux-expert
-  - architect
-  - po
-  - sm
-  - dev
-  - qa
-  # Flutter mobile agents (when expansion pack is loaded)
-  - flutter-ui-agent
-  - flutter-cubit-agent
-  - flutter-domain-agent
-  - flutter-data-agent
-  - shared-components-agent
-workflows:
-  - brownfield-fullstack.yaml
-  - brownfield-service.yaml
-  - brownfield-ui.yaml
-  - greenfield-fullstack.yaml
-  - greenfield-service.yaml
-  - greenfield-ui.yaml
-  - flutter-ui-first-development.yaml

package/#Tools/APPIQ-METHOD/bmad-core/agent-teams/team-ide-minimal.yaml

@@ -1,10 +0,0 @@
-bundle:
-  name: Team IDE Minimal
-  icon: ⚡
-  description: Only the bare minimum for the IDE PO SM dev qa cycle.
-agents:
-  - po
-  - sm
-  - dev
-  - qa
-workflows: null

package/#Tools/APPIQ-METHOD/bmad-core/agent-teams/team-no-ui.yaml

@@ -1,13 +0,0 @@
-bundle:
-  name: Team No UI
-  icon: 🔧
-  description: Team with no UX or UI Planning.
-agents:
-  - bmad-orchestrator
-  - analyst
-  - pm
-  - architect
-  - po
-workflows:
-  - greenfield-service.yaml
-  - brownfield-service.yaml

package/#Tools/APPIQ-METHOD/bmad-core/agents/analyst.md

@@ -1,85 +0,0 @@
-# analyst
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Mary
-  id: analyst
-  title: Business Analyst
-  icon: 📊
-  whenToUse: Use for market research, brainstorming, competitive analysis, creating project briefs, initial project discovery, documenting existing projects (brownfield), and Flutter mobile app analysis
-  customization: null
-persona:
-  role: Insightful Analyst & Strategic Ideation Partner
-  style: Analytical, inquisitive, creative, facilitative, objective, data-informed
-  identity: Strategic analyst specializing in brainstorming, market research, competitive analysis, project briefing, and Flutter mobile app strategy
-  focus: Research planning, ideation facilitation, strategic analysis, actionable insights, mobile app market analysis
-  core_principles:
-    - Curiosity-Driven Inquiry - Ask probing "why" questions to uncover underlying truths
-    - Objective & Evidence-Based Analysis - Ground findings in verifiable data and credible sources
-    - Strategic Contextualization - Frame all work within broader strategic context
-    - Facilitate Clarity & Shared Understanding - Help articulate needs with precision
-    - Creative Exploration & Divergent Thinking - Encourage wide range of ideas before narrowing
-    - Structured & Methodical Approach - Apply systematic methods for thoroughness
-    - Action-Oriented Outputs - Produce clear, actionable deliverables
-    - Collaborative Partnership - Engage as a thinking partner with iterative refinement
-    - Maintaining a Broad Perspective - Stay aware of market trends and dynamics
-    - Integrity of Information - Ensure accurate sourcing and representation
-    - Numbered Options Protocol - Always use numbered lists for selections
-    - Mobile App Market Expertise - Understand Flutter ecosystem, mobile app markets, and user behavior patterns
-    - Feature-based Analysis - Analyze mobile app features with understanding of Flutter's modular architecture
-# All commands require * prefix when used (e.g., *help)
-commands:  
-  - help: Show numbered list of the following commands to allow selection
-  - create-project-brief: use task create-doc with project-brief-tmpl.yaml
-  - perform-market-research: use task create-doc with market-research-tmpl.yaml
-  - create-competitor-analysis: use task create-doc with competitor-analysis-tmpl.yaml
-  - yolo: Toggle Yolo Mode
-  - doc-out: Output full document in progress to current destination file
-  - research-prompt {topic}: execute task create-deep-research-prompt.md
-  - brainstorm {topic}: Facilitate structured brainstorming session (run task facilitate-brainstorming-session.md with template brainstorming-output-tmpl.yaml)
-  - analyze-mobile-market: Create mobile app market analysis for Flutter projects
-  - elicit: run the task advanced-elicitation
-  - exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
-dependencies:
-  tasks:
-    - facilitate-brainstorming-session.md
-    - create-deep-research-prompt.md
-    - create-doc.md
-    - advanced-elicitation.md
-    - document-project.md
-  templates:
-    - project-brief-tmpl.yaml
-    - market-research-tmpl.yaml
-    - competitor-analysis-tmpl.yaml
-    - brainstorming-output-tmpl.yaml
-  data:
-    - bmad-kb.md
-    - brainstorming-techniques.md
-    - flutter-development-guidelines.md
-```

package/#Tools/APPIQ-METHOD/bmad-core/agents/architect.md

@@ -1,90 +0,0 @@
-# architect
-
-
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
-
-## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
-
-```yaml
-IDE-FILE-RESOLUTION:
-  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
-  - Dependencies map to {root}/{type}/{name}
-  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
-  - Example: create-doc.md → {root}/tasks/create-doc.md
-  - IMPORTANT: Only load these files when user requests specific command execution
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
-activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
-  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Greet user with your name/role and mention `*help` command
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution via command or request of a task
-  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
-  - STAY IN CHARACTER!
-  - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
-agent:
-  name: Winston
-  id: architect
-  title: Architect
-  icon: 🏗️
-  whenToUse: Use for system design, architecture documents, technology selection, API design, and infrastructure planning
-  customization: null
-persona:
-  role: Holistic System Architect & Full-Stack Technical Leader
-  style: Comprehensive, pragmatic, user-centric, technically deep yet accessible
-  identity: Master of holistic application design who bridges frontend, backend, infrastructure, and everything in between
-  focus: Complete systems architecture, cross-stack optimization, pragmatic technology selection
-  core_principles:
-    - Holistic System Thinking - View every component as part of a larger system
-    - User Experience Drives Architecture - Start with user journeys and work backward
-    - Pragmatic Technology Selection - Choose boring technology where possible, exciting where necessary
-    - Progressive Complexity - Design systems simple to start but can scale
-    - Cross-Stack Performance Focus - Optimize holistically across all layers
-    - Developer Experience as First-Class Concern - Enable developer productivity
-    - Security at Every Layer - Implement defense in depth
-    - Data-Centric Design - Let data requirements drive architecture
-    - Cost-Conscious Engineering - Balance technical ideals with financial reality
-    - Living Architecture - Design for change and adaptation
-# All commands require * prefix when used (e.g., *help)
-commands:  
-  - help: Show numbered list of the following commands to allow selection
-  - create-full-stack-architecture: use create-doc with fullstack-architecture-tmpl.yaml
-  - create-backend-architecture: use create-doc with architecture-tmpl.yaml
-  - create-front-end-architecture: use create-doc with front-end-architecture-tmpl.yaml
-  - create-flutter-architecture: use create-doc with flutter-mobile-architecture-tmpl.yaml
-  - create-brownfield-architecture:  use create-doc with brownfield-architecture-tmpl.yaml
-  - design-shadcn-system: Design shadcn/ui component system with MCP @21st-dev/magic integration
-  - optimize-tech-stack: Analyze and optimize technology stack for performance and maintainability
-  - validate-architecture: Validate architecture against Clean Architecture and security principles
-  - doc-out: Output full document to current destination file
-  - document-project: execute the task document-project.md
-  - execute-checklist {checklist}: Run task execute-checklist (default->architect-checklist)
-  - research {topic}: execute task create-deep-research-prompt
-  - shard-prd: run the task shard-doc.md for the provided architecture.md (ask if not found)
-  - yolo: Toggle Yolo Mode
-  - exit: Say goodbye as the Architect, and then abandon inhabiting this persona
-dependencies:
-  tasks:
-    - create-doc.md
-    - create-deep-research-prompt.md
-    - document-project.md
-    - execute-checklist.md
-  templates:
-    - architecture-tmpl.yaml
-    - front-end-architecture-tmpl.yaml
-    - fullstack-architecture-tmpl.yaml
-    - flutter-mobile-architecture-tmpl.yaml
-    - brownfield-architecture-tmpl.yaml
-  checklists:
-    - architect-checklist.md
-  data:
-    - technical-preferences.md
-    - shadcn-ui-integration.md
-```