appiq-solution 1.4.7 → 1.4.9

package/bmad-core/data/technical-preferences.md

@@ -1,149 +1,3 @@
 # User-Defined Preferred Patterns and Preferences
 
-## Frontend Frameworks
-
-### Web Development
-- **React**: Latest stable version with TypeScript
-- **Next.js**: Full-stack React framework with App Router
-- **Vue 3**: Composition API with TypeScript
-- **Angular**: Latest LTS version with standalone components
-- **Svelte/SvelteKit**: Modern reactive framework
-
-### UI Component Libraries
-- **shadcn/ui**: Modern React components with Tailwind CSS
-- **Material UI**: React components following Material Design
-- **Ant Design**: Enterprise-class UI design language
-- **Chakra UI**: Modular and accessible component library
-- **Headless UI**: Unstyled, accessible UI components
-
-### CSS Frameworks
-- **Tailwind CSS**: Utility-first CSS framework
-- **CSS Modules**: Localized CSS
-- **Styled Components**: CSS-in-JS library
-- **Emotion**: Performant and flexible CSS-in-JS
-
-## Mobile Development
-
-### Flutter
-- **Framework**: Flutter 3.24+ with Dart 3.5+
-- **State Management**: Cubit/BLoC pattern with flutter_bloc
-- **Architecture**: Clean Architecture with dependency injection
-- **Code Generation**: Freezed + json_serializable + injectable
-- **Networking**: Dio HTTP client
-- **Local Storage**: Hive for complex data, SharedPreferences for simple data
-- **Routing**: GoRouter for declarative routing
-- **Localization**: flutter_localizations with ARB files
-- **Testing**: flutter_test + bloc_test + mocktail
-
-## Backend Services
-
-### Firebase
-- **Authentication**: Firebase Auth with multi-provider support
-- **Database**: Firestore for NoSQL, Realtime Database for real-time features
-- **Storage**: Firebase Storage for file uploads
-- **Functions**: Cloud Functions for serverless backend logic
-- **Hosting**: Firebase Hosting for web deployment
-- **Analytics**: Firebase Analytics and Crashlytics
-
-### Supabase
-- **Database**: PostgreSQL with Row Level Security (RLS)
-- **Authentication**: Supabase Auth with social providers
-- **Storage**: Supabase Storage for file management
-- **Real-time**: Real-time subscriptions
-- **Edge Functions**: Deno-based serverless functions
-- **API**: Auto-generated REST and GraphQL APIs
-
-### Traditional Backend
-- **Node.js**: Express.js or Fastify with TypeScript
-- **Python**: FastAPI or Django with type hints
-- **Database**: PostgreSQL for relational, MongoDB for document-based
-- **API**: REST with OpenAPI documentation or GraphQL
-
-## Development Tools
-
-### Build Tools
-- **Vite**: Fast build tool for modern web development
-- **Webpack**: Module bundler for complex configurations
-- **Turbo**: High-performance build system for monorepos
-- **esbuild**: Extremely fast JavaScript bundler
-
-### State Management
-- **Web**: Redux Toolkit, Zustand, or Valtio
-- **Mobile**: Cubit/BLoC for Flutter, Redux for React Native
-
-### Testing
-- **Unit Testing**: Jest, Vitest, or Flutter Test
-- **Integration Testing**: Cypress, Playwright, or Flutter Integration Tests
-- **E2E Testing**: Playwright or Detox for mobile
-
-### Code Quality
-- **Linting**: ESLint for JavaScript/TypeScript, flutter_lints for Flutter
-- **Formatting**: Prettier for web, dart format for Flutter
-- **Type Checking**: TypeScript strict mode, Dart null safety
-
-## Architecture Patterns
-
-### Clean Architecture
-- **Presentation Layer**: UI components and state management
-- **Domain Layer**: Business logic and entities
-- **Data Layer**: Data sources and repository implementations
-- **Infrastructure**: External services and frameworks
-
-### Design Patterns
-- **Repository Pattern**: Abstract data access
-- **Dependency Injection**: Inversion of control
-- **Observer Pattern**: State management and reactive programming
-- **Factory Pattern**: Object creation
-- **Singleton Pattern**: Shared services and utilities
-
-## Security Preferences
-
-### Authentication
-- **Multi-factor Authentication**: Always enabled for production
-- **OAuth 2.0**: Preferred for third-party authentication
-- **JWT Tokens**: With proper expiration and refresh mechanisms
-- **Biometric Authentication**: For mobile applications where applicable
-
-### Data Protection
-- **Encryption at Rest**: All sensitive data encrypted
-- **Encryption in Transit**: HTTPS/TLS for all communication
-- **Input Validation**: Server-side validation for all inputs
-- **SQL Injection Prevention**: Parameterized queries or ORM
-
-### API Security
-- **Rate Limiting**: Prevent abuse and DoS attacks
-- **CORS Configuration**: Proper cross-origin resource sharing
-- **API Keys**: Secure API key management
-- **Certificate Pinning**: For mobile applications
-
-## Performance Preferences
-
-### Web Performance
-- **Core Web Vitals**: Optimize for LCP, FID, and CLS
-- **Code Splitting**: Lazy loading for better performance
-- **Image Optimization**: WebP format with fallbacks
-- **Caching Strategy**: Service workers and CDN caching
-
-### Mobile Performance
-- **60 FPS**: Maintain smooth animations and scrolling
-- **Memory Management**: Efficient memory usage and garbage collection
-- **Battery Optimization**: Minimize battery drain
-- **Offline Support**: Graceful offline functionality
-
-## Localization Preferences
-
-### Multi-language Support
-- **Internationalization**: Built-in from project start
-- **Translation Keys**: Descriptive and hierarchical
-- **RTL Support**: Right-to-left language support
-- **Date/Time Formatting**: Locale-specific formatting
-- **Number Formatting**: Currency and number localization
-
-## MCP Tool Integrations
-
-### Available MCP Tools
-- **@21st-dev/magic**: For shadcn/ui component generation and management
-- **supabase-mcp**: For Supabase backend integration and management
-- **firebase-mcp**: For Firebase services integration
-- **sequential-thinking**: For complex problem analysis and decision making
-- **dart-mcp**: For Dart code analysis and Flutter development assistance
+None Listed

package/bmad-core/templates/fullstack-architecture-tmpl.yaml

@@ -158,21 +158,15 @@ sections:
           - ["Frontend Language", "{{fe_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Frontend Framework", "{{fe_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["UI Component Library", "{{ui_library}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["UI Design System", "{{ui_design_system}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["State Management", "{{state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["Mobile Framework", "{{mobile_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["Mobile State Management", "{{mobile_state_mgmt}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Backend Language", "{{be_language}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Backend Framework", "{{be_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["Backend Service", "{{backend_service}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["API Style", "{{api_style}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Database", "{{database}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Cache", "{{cache}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["File Storage", "{{storage}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Authentication", "{{auth}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["Real-time", "{{realtime}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Frontend Testing", "{{fe_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["Mobile Testing", "{{mobile_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Backend Testing", "{{be_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["E2E Testing", "{{e2e_test}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Build Tool", "{{build_tool}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
@@ -182,7 +176,6 @@ sections:
           - ["Monitoring", "{{monitoring}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["Logging", "{{logging}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
           - ["CSS Framework", "{{css_framework}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
-          - ["Localization", "{{localization}}", "{{version}}", "{{purpose}}", "{{why_chosen}}"]
 
   - id: data-models
     title: Data Models
@@ -678,11 +671,11 @@ sections:
         type: code
         language: text
         template: |
-          Testing Pyramid Structure:
-          
-          Level 3: E2E Tests (Few)
-          Level 2: Integration Tests (Some)  
-          Level 1: Unit Tests (Many - Frontend & Backend)
+                  E2E Tests
+                 /        \
+            Integration Tests
+               /            \
+          Frontend Unit  Backend Unit
       - id: test-organization
         title: Test Organization
         sections:

package/bmad-core/workflows/brownfield-fullstack.yaml

@@ -54,15 +54,7 @@ workflow:
       action: analyze existing project and use task document-project
       creates: brownfield-architecture.md (or multiple documents)
       condition: documentation_inadequate
-      notes: |
-        Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation.
-        
-        For Flutter projects, analyze:
-        - Current Flutter architecture (Clean Architecture compliance)
-        - Feature-based organization structure
-        - State management patterns (Cubit/BLoC usage)
-        - Dependencies and version compatibility
-        - Performance and accessibility compliance
+      notes: "Run document-project to capture current system state, technical debt, and constraints. Pass findings to PRD creation."
 
     - agent: pm
       creates: prd.md
@@ -72,12 +64,6 @@ workflow:
         Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis.
         If skipped, use existing project documentation.
         SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
-        
-        For Flutter projects, use flutter-mobile-prd-tmpl.yaml to ensure:
-        - Feature-based requirements organization
-        - Clean Architecture layer specifications
-        - Material Design 3 compliance requirements
-        - Mobile-specific performance and accessibility criteria
 
     - step: architecture_decision
       agent: pm/architect

package/bmad-core/workflows/greenfield-fullstack.yaml

@@ -11,7 +11,6 @@ workflow:
     - enterprise-app
     - prototype
     - mvp
-    - flutter-mobile-app
 
   sequence:
     - agent: analyst
@@ -24,35 +23,14 @@ workflow:
     - agent: pm
       creates: prd.md
       requires: project-brief.md
-      notes: |
-        Creates PRD from project brief using prd-tmpl (or flutter-mobile-prd-tmpl for Flutter projects).
-        
-        For Flutter mobile apps:
-        - Use flutter-mobile-prd-tmpl.yaml template
-        - Focus on feature-based architecture requirements
-        - Include Material Design 3 specifications
-        - Define mobile-specific performance criteria
-        - Plan Clean Architecture layers (data/domain/presentation)
-        
-        SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
+      notes: "Creates PRD from project brief using prd-tmpl. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder."
 
     - agent: ux-expert
       creates: front-end-spec.md
       requires: prd.md
       optional_steps:
         - user_research_prompt
-      notes: |
-        Creates UI/UX specification using front-end-spec-tmpl (or flutter-ui-spec-tmpl for Flutter projects).
-        
-        For Flutter mobile apps:
-        - Use flutter-ui-spec-tmpl.yaml template
-        - Design with Material Design 3 principles
-        - Plan responsive layouts for phone/tablet
-        - Define custom widget specifications
-        - Include accessibility and localization requirements
-        - Consider mobile-specific user interactions
-        
-        SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder.
+      notes: "Creates UI/UX specification using front-end-spec-tmpl. SAVE OUTPUT: Copy final front-end-spec.md to your project's docs/ folder."
 
     - agent: ux-expert
       creates: v0_prompt (optional)
@@ -68,21 +46,7 @@ workflow:
       optional_steps:
         - technical_research_prompt
         - review_generated_ui_structure
-      notes: |
-        Creates comprehensive architecture using fullstack-architecture-tmpl (or flutter-mobile-architecture-tmpl for Flutter projects).
-        
-        For Flutter mobile apps:
-        - Use flutter-mobile-architecture-tmpl.yaml template
-        - Define Clean Architecture with feature-based structure
-        - Plan Cubit state management architecture
-        - Specify dependency injection setup
-        - Include testing strategy across all layers
-        - Define performance and security considerations
-        
-        If user generated UI with v0/Lovable, can incorporate the project structure into architecture.
-        May suggest changes to PRD stories or new stories.
-        
-        SAVE OUTPUT: Copy final fullstack-architecture.md to your project's docs/ folder.
+      notes: "Creates comprehensive architecture using fullstack-architecture-tmpl. If user generated UI with v0/Lovable, can incorporate the project structure into architecture. May suggest changes to PRD stories or new stories. SAVE OUTPUT: Copy final fullstack-architecture.md to your project's docs/ folder."
 
     - agent: pm
       updates: prd.md (if needed)
@@ -126,9 +90,8 @@ workflow:
       repeats: for_each_epic
       notes: |
         Story creation cycle:
-        - SM Agent (New Chat): @sm → *create (or *create-flutter-story for Flutter projects)
+        - SM Agent (New Chat): @sm → *create
         - Creates next story from sharded docs
-        - For Flutter: Uses flutter-story-tmpl.yaml with all three architecture layers
         - Story starts in "Draft" status
 
     - agent: analyst/pm
@@ -148,14 +111,7 @@ workflow:
       creates: implementation_files
       requires: story.md
       notes: |
-        Dev Agent (New Chat): @dev (or Flutter-specific agents for complex features)
-        
-        For Flutter projects:
-        - Use @flutter-ui-agent for presentation layer
-        - Use @flutter-cubit-agent for state management  
-        - Use @flutter-domain-agent for business logic
-        - Use @flutter-data-agent for data layer
-        - Or use general @dev with Flutter expertise
+        Dev Agent (New Chat): @dev
         - Implements approved story
         - Updates File List with all changes
         - Marks story as "Review" when complete

package/bmad-core/working-in-the-brownfield.md

@@ -51,29 +51,20 @@ If you have just completed an MVP with BMad, and you want to continue with post-
 
 #### Phase 1: Define Requirements First
 
-**Create PRD.md file directly:**
+**In Gemini Web (with your flattened-codebase.xml uploaded):**
 
-Instead of asking questions, simply create a `docs/prd.md` file in your project with your enhancement requirements. The AI agents (PO, PM, Architect) can then work with this existing document.
-
-**PRD.md Template:**
-```markdown
-# Project Requirements Document
-
-## Project Overview
-- **Project Name**: [Your project name]
-- **Enhancement**: [Brief description of what you want to add]
+```bash
+@pm
+*create-brownfield-prd
+```
 
-## Requirements
-- [List your specific requirements]
-- [Integration needs]
-- [Constraints]
+The PM will:
 
-## Existing System
-- [Brief description of current system]
-- [Key components that will be affected]
-```
+- **Ask about your enhancement** requirements
+- **Explore the codebase** to understand current state
+- **Identify affected areas** that need documentation
+- **Create focused PRD** with clear scope
 
-**Key Advantage**: AI agents can immediately work with your PRD without needing to ask questions about project details!
 **Key Advantage**: The PRD identifies which parts of your monorepo/large codebase actually need documentation!
 
 #### Phase 2: Focused Documentation

package/dist/agents/bmad-orchestrator.txt

@@ -77,7 +77,6 @@ persona:
     - Always remind users that commands require * prefix
 commands:
   help: Show this guide with available agents and workflows
-  start: Universal project launcher with smart detection and guided workflow selection
   chat-mode: Start conversational mode for detailed assistance
   kb-mode: Load full BMad knowledge base
   status: Show current context, active agent, and progress
@@ -99,7 +98,6 @@ help-display-template: |
 
   Core Commands:
   *help ............... Show this guide
-  *start .............. 🚀 Universal project launcher (RECOMMENDED FOR BEGINNERS)
   *chat-mode .......... Start conversational mode for detailed assistance
   *kb-mode ............ Load full BMad knowledge base
   *status ............. Show current context, active agent, and progress
@@ -161,115 +159,6 @@ workflow-guidance:
   - Adapt questions to the specific domain (e.g., game dev vs infrastructure vs web dev)
   - Only recommend workflows that actually exist in the current bundle
   - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
-start-behavior:
-  step1-project-status:
-    question: |
-      🚀 APPIQ Method Universal Launcher
-
-      Arbeiten wir an einem neuen oder bestehenden Projekt?
-
-      1. 🆕 Neues Projekt (Greenfield) - Wir bauen von Grund auf
-      2. 🔧 Bestehendes Projekt (Brownfield) - Wir erweitern/verbessern etwas
-
-      Antworte mit 1 oder 2:
-    responses:
-      '1': new_project
-      '2': existing_project
-  step2-project-type:
-    question: |
-      📋 Lass mich verstehen, was wir bauen...
-
-      Was für eine Art von Anwendung ist das?
-
-      1. 🌐 Web-Anwendung (läuft im Browser)
-      2. 💻 Desktop-Anwendung (Electron, Windows/Mac App)
-      3. 📱 Mobile App (iOS/Android)
-      4. ⚙️ Backend/API Service (Server, Database)
-      5. 🤔 Bin mir nicht sicher - lass APPIQ entscheiden
-
-      Antworte mit 1, 2, 3, 4 oder 5:
-    responses:
-      '1': web_app
-      '2': desktop_app
-      '3': mobile_app
-      '4': backend_service
-      '5': auto_detect
-  workflow-mapping:
-    new_project:
-      web_app: greenfield-fullstack.yaml
-      desktop_app: greenfield-fullstack.yaml
-      mobile_app: mobile-platform-selection
-      backend_service: greenfield-service.yaml
-      auto_detect: project-description-analysis
-    existing_project:
-      web_app: brownfield-fullstack.yaml
-      desktop_app: brownfield-fullstack.yaml
-      mobile_app: mobile-platform-detection
-      backend_service: brownfield-service.yaml
-      auto_detect: project-structure-analysis
-  auto-detection:
-    new-project-analysis:
-      prompt: |
-        🔍 Lass uns gemeinsam herausfinden, was das beste für dein Projekt ist...
-
-        Beschreibe kurz dein Projekt in 1-2 Sätzen:
-        (z.B. "Eine Ecommerce-Website mit Admin-Panel" oder "Eine Todo-App für Windows")
-      keywords:
-        web:
-          - website
-          - web
-          - browser
-          - online
-          - webapp
-          - ecommerce
-          - cms
-        desktop:
-          - desktop
-          - electron
-          - windows
-          - mac
-          - app
-          - gui
-          - standalone
-        mobile:
-          - mobile
-          - ios
-          - android
-          - app store
-          - phone
-          - tablet
-        backend:
-          - api
-          - server
-          - backend
-          - database
-          - service
-          - microservice
-    existing-project-analysis:
-      message: |
-        🔍 Analysiere dein bestehendes Projekt...
-
-        Ich schaue mir deine Projekt-Struktur an...
-      file-patterns:
-        desktop:
-          - package.json + electron dependency
-        mobile-react-native:
-          - package.json + react-native dependency
-        mobile-flutter:
-          - pubspec.yaml present
-        web:
-          - package.json + (next|react|vue|angular)
-        backend-node:
-          - package.json + (express|fastify|koa)
-        backend-python:
-          - requirements.txt + (flask|django|fastapi)
-        backend-java:
-          - pom.xml or build.gradle
-  context-messages:
-    desktop: Fokus auf Electron Desktop-Anwendung mit plattformspezifischen Optimierungen
-    mobile: Plattform-Erkennung erforderlich (Flutter/React Native)
-    web: Full-Stack Web-Anwendung mit Frontend und Backend Komponenten
-    backend: API-Design und Datenarchitektur im Fokus
 dependencies:
   tasks:
     - advanced-elicitation.md

package/dist/agents/pm.txt

@@ -74,6 +74,8 @@ commands:
   - help: Show numbered list of the following commands to allow selection
   - create-prd: run task create-doc.md with template prd-tmpl.yaml
   - create-brownfield-prd: run task create-doc.md with template brownfield-prd-tmpl.yaml
+  - create-brownfield-epic: run task brownfield-create-epic.md
+  - create-brownfield-story: run task brownfield-create-story.md
   - create-epic: Create epic for brownfield projects (task brownfield-create-epic)
   - create-story: Create user story from requirements (task brownfield-create-story)
   - doc-out: Output full document to current destination file

package/dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt

@@ -157,7 +157,6 @@ persona:
     - Always remind users that commands require * prefix
 commands:
   help: Show this guide with available agents and workflows
-  start: Universal project launcher with smart detection and guided workflow selection
   chat-mode: Start conversational mode for detailed assistance
   kb-mode: Load full BMad knowledge base
   status: Show current context, active agent, and progress
@@ -179,7 +178,6 @@ help-display-template: |
 
   Core Commands:
   *help ............... Show this guide
-  *start .............. 🚀 Universal project launcher (RECOMMENDED FOR BEGINNERS)
   *chat-mode .......... Start conversational mode for detailed assistance
   *kb-mode ............ Load full BMad knowledge base
   *status ............. Show current context, active agent, and progress
@@ -241,115 +239,6 @@ workflow-guidance:
   - Adapt questions to the specific domain (e.g., game dev vs infrastructure vs web dev)
   - Only recommend workflows that actually exist in the current bundle
   - When *workflow-guidance is called, start an interactive session and list all available workflows with brief descriptions
-start-behavior:
-  step1-project-status:
-    question: |
-      🚀 APPIQ Method Universal Launcher
-
-      Arbeiten wir an einem neuen oder bestehenden Projekt?
-
-      1. 🆕 Neues Projekt (Greenfield) - Wir bauen von Grund auf
-      2. 🔧 Bestehendes Projekt (Brownfield) - Wir erweitern/verbessern etwas
-
-      Antworte mit 1 oder 2:
-    responses:
-      '1': new_project
-      '2': existing_project
-  step2-project-type:
-    question: |
-      📋 Lass mich verstehen, was wir bauen...
-
-      Was für eine Art von Anwendung ist das?
-
-      1. 🌐 Web-Anwendung (läuft im Browser)
-      2. 💻 Desktop-Anwendung (Electron, Windows/Mac App)
-      3. 📱 Mobile App (iOS/Android)
-      4. ⚙️ Backend/API Service (Server, Database)
-      5. 🤔 Bin mir nicht sicher - lass APPIQ entscheiden
-
-      Antworte mit 1, 2, 3, 4 oder 5:
-    responses:
-      '1': web_app
-      '2': desktop_app
-      '3': mobile_app
-      '4': backend_service
-      '5': auto_detect
-  workflow-mapping:
-    new_project:
-      web_app: greenfield-fullstack.yaml
-      desktop_app: greenfield-fullstack.yaml
-      mobile_app: mobile-platform-selection
-      backend_service: greenfield-service.yaml
-      auto_detect: project-description-analysis
-    existing_project:
-      web_app: brownfield-fullstack.yaml
-      desktop_app: brownfield-fullstack.yaml
-      mobile_app: mobile-platform-detection
-      backend_service: brownfield-service.yaml
-      auto_detect: project-structure-analysis
-  auto-detection:
-    new-project-analysis:
-      prompt: |
-        🔍 Lass uns gemeinsam herausfinden, was das beste für dein Projekt ist...
-
-        Beschreibe kurz dein Projekt in 1-2 Sätzen:
-        (z.B. "Eine Ecommerce-Website mit Admin-Panel" oder "Eine Todo-App für Windows")
-      keywords:
-        web:
-          - website
-          - web
-          - browser
-          - online
-          - webapp
-          - ecommerce
-          - cms
-        desktop:
-          - desktop
-          - electron
-          - windows
-          - mac
-          - app
-          - gui
-          - standalone
-        mobile:
-          - mobile
-          - ios
-          - android
-          - app store
-          - phone
-          - tablet
-        backend:
-          - api
-          - server
-          - backend
-          - database
-          - service
-          - microservice
-    existing-project-analysis:
-      message: |
-        🔍 Analysiere dein bestehendes Projekt...
-
-        Ich schaue mir deine Projekt-Struktur an...
-      file-patterns:
-        desktop:
-          - package.json + electron dependency
-        mobile-react-native:
-          - package.json + react-native dependency
-        mobile-flutter:
-          - pubspec.yaml present
-        web:
-          - package.json + (next|react|vue|angular)
-        backend-node:
-          - package.json + (express|fastify|koa)
-        backend-python:
-          - requirements.txt + (flask|django|fastapi)
-        backend-java:
-          - pom.xml or build.gradle
-  context-messages:
-    desktop: Fokus auf Electron Desktop-Anwendung mit plattformspezifischen Optimierungen
-    mobile: Plattform-Erkennung erforderlich (Flutter/React Native)
-    web: Full-Stack Web-Anwendung mit Frontend und Backend Komponenten
-    backend: API-Design und Datenarchitektur im Fokus
 dependencies:
   tasks:
     - advanced-elicitation.md