aios-core 2.1.0

package/.aios-core/product/templates/ide-rules/trae-rules.md

@@ -0,0 +1,104 @@
+# AIOS-FULLSTACK Development Rules for Trae
+
+You are working with AIOS-FULLSTACK, an AI-Orchestrated System for Full Stack Development.
+
+## Core Framework Understanding
+
+AIOS-FULLSTACK is a meta-framework that orchestrates AI agents to handle complex development workflows. Always recognize and work within this architecture.
+
+## Agent System
+
+### Agent Activation
+- Agents are activated with @agent-name syntax: @dev, @qa, @architect, @pm, @po, @sm, @analyst
+- The master agent is activated with @aios-master
+- Agent commands use the * prefix: *help, *create-story, *task, *exit
+
+### Agent Context
+When an agent is active:
+- Follow that agent's specific persona and expertise
+- Use the agent's designated workflow patterns
+- Maintain the agent's perspective throughout the interaction
+
+## Development Methodology
+
+### Story-Driven Development
+1. **Work from stories** - All development starts with a story in `docs/stories/`
+2. **Update progress** - Mark checkboxes as tasks complete: [ ] → [x]
+3. **Track changes** - Maintain the File List section in the story
+4. **Follow criteria** - Implement exactly what the acceptance criteria specify
+
+### Code Standards
+- Write clean, self-documenting code
+- Follow existing patterns in the codebase
+- Include comprehensive error handling
+- Add unit tests for all new functionality
+- Use TypeScript/JavaScript best practices
+
+### Testing Requirements
+- Run all tests before marking tasks complete
+- Ensure linting passes: `npm run lint`
+- Verify type checking: `npm run typecheck`
+- Add tests for new features
+- Test edge cases and error scenarios
+
+## AIOS Framework Structure
+
+```
+aios-core/
+├── agents/         # Agent persona definitions (YAML/Markdown)
+├── tasks/          # Executable task workflows
+├── workflows/      # Multi-step workflow definitions
+├── templates/      # Document and code templates
+├── checklists/     # Validation and review checklists
+└── rules/          # Framework rules and patterns
+
+docs/
+├── stories/        # Development stories (numbered)
+├── prd/            # Product requirement documents
+├── architecture/   # System architecture documentation
+└── guides/         # User and developer guides
+```
+
+## Workflow Execution
+
+### Task Execution Pattern
+1. Read the complete task/workflow definition
+2. Understand all elicitation points
+3. Execute steps sequentially
+4. Handle errors gracefully
+5. Provide clear feedback
+
+### Interactive Workflows
+- Workflows with `elicit: true` require user input
+- Present options clearly
+- Validate user responses
+- Provide helpful defaults
+
+## Best Practices
+
+### When implementing features:
+- Check existing patterns first
+- Reuse components and utilities
+- Follow naming conventions
+- Keep functions focused and testable
+- Document complex logic
+
+### When working with agents:
+- Respect agent boundaries
+- Use appropriate agent for each task
+- Follow agent communication patterns
+- Maintain agent context
+
+## Trae-Specific Configuration
+
+### Agent Rules Location
+- Rules are stored in `.trae/rules/`
+- Use @agent-name to activate agents in chat
+
+### Performance Tips
+- Use Trae's inline suggestions for quick edits
+- Leverage the chat panel for complex discussions
+- Use context providers to include relevant files
+
+---
+*AIOS-FULLSTACK Trae Configuration v2.1*

package/.aios-core/product/templates/ide-rules/windsurf-rules.md

@@ -0,0 +1,80 @@
+# AIOS-FULLSTACK Development Rules for Windsurf
+
+## AIOS Agent Integration
+
+When working with AIOS agents in Windsurf:
+- Use `@agent-name` to activate specific agents (e.g., `@dev`, `@qa`, `@architect`)
+- Agent commands always start with `*` (e.g., `*help`, `*create-story`)
+- Follow the agent's specific workflow and commands
+
+## Development Workflow
+
+### Story-Driven Development
+1. Stories are your primary work units - always reference the current story
+2. Update story checkboxes as you complete tasks
+3. Keep the File List section updated with all changes
+4. Follow the story's acceptance criteria exactly
+
+### Code Standards
+- Write clean, self-documenting code
+- Follow existing patterns in the codebase
+- Add comprehensive error handling
+- Include unit tests for new functionality
+
+### Testing Requirements
+- Run tests before marking any task complete
+- Use `npm test` or equivalent for your tech stack
+- Ensure all tests pass before updating story status
+- Add new tests for new functionality
+
+### Documentation
+- Update relevant documentation when changing functionality
+- Keep README files current
+- Document complex logic with clear comments
+- Update API documentation for endpoint changes
+
+## AIOS-Specific Patterns
+
+### Working with Workflows
+- Workflows are in `aios-core/workflows/`
+- Tasks are in `aios-core/tasks/`
+- Follow YAML frontmatter conventions
+- Use elicit: true for interactive workflows
+
+### Agent Commands
+Common commands across agents:
+- `*help` - Show available commands
+- `*exit` - Exit current agent
+- `*task {name}` - Execute specific task
+- `*create-doc {template}` - Create document from template
+
+### File Organization
+```
+project/
+├── aios-core/          # AIOS framework files
+│   ├── agents/         # Agent definitions
+│   ├── tasks/          # Executable tasks
+│   ├── workflows/      # Workflow definitions
+│   └── templates/      # Document templates
+├── docs/               # Project documentation
+│   ├── stories/        # Development stories
+│   └── architecture/   # Architecture docs
+└── src/                # Your source code
+```
+
+## Best Practices
+
+1. **Always backup before major changes**
+2. **Test in isolation before integration**
+3. **Follow the story acceptance criteria**
+4. **Update documentation as you code**
+5. **Communicate blockers immediately**
+
+## GitHub Integration
+- Ensure GitHub CLI is installed: `gh --version`
+- Authenticate before pushing: `gh auth status`
+- Follow conventional commit messages
+- Reference story IDs in commits
+
+---
+*AIOS-FULLSTACK Configuration v1.0* 

package/.aios-core/product/templates/index-strategy-tmpl.yaml

@@ -0,0 +1,53 @@
+---
+template_name: "Indexing Strategy"
+template_version: "1.0.0"
+output_format: "markdown"
+destination: "index-strategy.md"
+description: "Purpose-built index plan tied to access patterns"
+
+sections:
+  - id: overview
+    title: "Indexing Overview"
+    instruction: |
+      - Goals: latency targets, load profile
+      - Read/Write trade-offs
+      - Engine features in use (B-Tree, GIN, GiST, BRIN, partial, covering)
+    elicit: true
+
+  - id: patterns
+    title: "Access Patterns Mapping"
+    instruction: |
+      For each frequent query:
+      - Query shape & filters
+      - ORDER BY requirements
+      - Estimated cardinality/selectivity
+      - Proposed index(es) with rationale
+    elicit: true
+
+  - id: catalog
+    title: "Index Catalog"
+    instruction: |
+      For each table:
+      ## table_name
+      - Existing indexes (name → columns, where, include)
+      - Proposed new indexes
+      - Partial indexes (predicates)
+      - Covering indexes (INCLUDE)
+      - Maintenance notes (bloat risk, reindex cadence)
+    elicit: true
+
+  - id: fulltext
+    title: "Full-Text & Search"
+    instruction: |
+      - tsvector generated columns
+      - GIN/Trigram usage
+      - Ranking functions and query samples
+    elicit: true
+
+  - id: maintenance
+    title: "Monitoring & Maintenance"
+    instruction: |
+      - pg_stat_user_indexes + idx scan ratio targets
+      - Unused index detection policy
+      - Reindex strategy, autovacuum considerations
+    elicit: true

package/.aios-core/product/templates/market-research-tmpl.yaml

@@ -0,0 +1,252 @@
+template:
+  id: market-research-template-v2
+  name: Market Research Report
+  version: 2.0
+  output:
+    format: markdown
+    filename: docs/market-research.md
+    title: "Market Research Report: {{project_product_name}}"
+
+workflow:
+  mode: interactive
+  elicitation: advanced-elicitation
+  custom_elicitation:
+    title: "Market Research Elicitation Actions"
+    options:
+      - "Expand market sizing calculations with sensitivity analysis"
+      - "Deep dive into a specific customer segment"
+      - "Analyze an emerging market trend in detail"
+      - "Compare this market to an analogous market"
+      - "Stress test market assumptions"
+      - "Explore adjacent market opportunities"
+      - "Challenge market definition and boundaries"
+      - "Generate strategic scenarios (best/base/worst case)"
+      - "If only we had considered [X market factor]..."
+      - "Proceed to next section"
+
+sections:
+  - id: executive-summary
+    title: Executive Summary
+    instruction: Provide a high-level overview of key findings, market opportunity assessment, and strategic recommendations. Write this section LAST after completing all other sections.
+
+  - id: research-objectives
+    title: Research Objectives & Methodology
+    instruction: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.
+    sections:
+      - id: objectives
+        title: Research Objectives
+        instruction: |
+          List the primary objectives of this market research:
+          - What decisions will this research inform?
+          - What specific questions need to be answered?
+          - What are the success criteria for this research?
+      - id: methodology
+        title: Research Methodology
+        instruction: |
+          Describe the research approach:
+          - Data sources used (primary/secondary)
+          - Analysis frameworks applied
+          - Data collection timeframe
+          - Limitations and assumptions
+
+  - id: market-overview
+    title: Market Overview
+    sections:
+      - id: market-definition
+        title: Market Definition
+        instruction: |
+          Define the market being analyzed:
+          - Product/service category
+          - Geographic scope
+          - Customer segments included
+          - Value chain position
+      - id: market-size-growth
+        title: Market Size & Growth
+        instruction: |
+          Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
+          - Top-down: Start with industry data, narrow down
+          - Bottom-up: Build from customer/unit economics
+          - Value theory: Based on value provided vs. alternatives
+        sections:
+          - id: tam
+            title: Total Addressable Market (TAM)
+            instruction: Calculate and explain the total market opportunity
+          - id: sam
+            title: Serviceable Addressable Market (SAM)
+            instruction: Define the portion of TAM you can realistically reach
+          - id: som
+            title: Serviceable Obtainable Market (SOM)
+            instruction: Estimate the portion you can realistically capture
+      - id: market-trends
+        title: Market Trends & Drivers
+        instruction: Analyze key trends shaping the market using appropriate frameworks like PESTEL
+        sections:
+          - id: key-trends
+            title: Key Market Trends
+            instruction: |
+              List and explain 3-5 major trends:
+              - Trend 1: Description and impact
+              - Trend 2: Description and impact
+              - etc.
+          - id: growth-drivers
+            title: Growth Drivers
+            instruction: Identify primary factors driving market growth
+          - id: market-inhibitors
+            title: Market Inhibitors
+            instruction: Identify factors constraining market growth
+
+  - id: customer-analysis
+    title: Customer Analysis
+    sections:
+      - id: segment-profiles
+        title: Target Segment Profiles
+        instruction: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay
+        repeatable: true
+        sections:
+          - id: segment
+            title: "Segment {{segment_number}}: {{segment_name}}"
+            template: |
+              - **Description:** {{brief_overview}}
+              - **Size:** {{number_of_customers_market_value}}
+              - **Characteristics:** {{key_demographics_firmographics}}
+              - **Needs & Pain Points:** {{primary_problems}}
+              - **Buying Process:** {{purchasing_decisions}}
+              - **Willingness to Pay:** {{price_sensitivity}}
+      - id: jobs-to-be-done
+        title: Jobs-to-be-Done Analysis
+        instruction: Uncover what customers are really trying to accomplish
+        sections:
+          - id: functional-jobs
+            title: Functional Jobs
+            instruction: List practical tasks and objectives customers need to complete
+          - id: emotional-jobs
+            title: Emotional Jobs
+            instruction: Describe feelings and perceptions customers seek
+          - id: social-jobs
+            title: Social Jobs
+            instruction: Explain how customers want to be perceived by others
+      - id: customer-journey
+        title: Customer Journey Mapping
+        instruction: Map the end-to-end customer experience for primary segments
+        template: |
+          For primary customer segment:
+          
+          1. **Awareness:** {{discovery_process}}
+          2. **Consideration:** {{evaluation_criteria}}
+          3. **Purchase:** {{decision_triggers}}
+          4. **Onboarding:** {{initial_expectations}}
+          5. **Usage:** {{interaction_patterns}}
+          6. **Advocacy:** {{referral_behaviors}}
+
+  - id: competitive-landscape
+    title: Competitive Landscape
+    sections:
+      - id: market-structure
+        title: Market Structure
+        instruction: |
+          Describe the overall competitive environment:
+          - Number of competitors
+          - Market concentration
+          - Competitive intensity
+      - id: major-players
+        title: Major Players Analysis
+        instruction: |
+          For top 3-5 competitors:
+          - Company name and brief description
+          - Market share estimate
+          - Key strengths and weaknesses
+          - Target customer focus
+          - Pricing strategy
+      - id: competitive-positioning
+        title: Competitive Positioning
+        instruction: |
+          Analyze how competitors are positioned:
+          - Value propositions
+          - Differentiation strategies
+          - Market gaps and opportunities
+
+  - id: industry-analysis
+    title: Industry Analysis
+    sections:
+      - id: porters-five-forces
+        title: Porter's Five Forces Assessment
+        instruction: Analyze each force with specific evidence and implications
+        sections:
+          - id: supplier-power
+            title: "Supplier Power: {{power_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: buyer-power
+            title: "Buyer Power: {{power_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: competitive-rivalry
+            title: "Competitive Rivalry: {{intensity_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: threat-new-entry
+            title: "Threat of New Entry: {{threat_level}}"
+            template: "{{analysis_and_implications}}"
+          - id: threat-substitutes
+            title: "Threat of Substitutes: {{threat_level}}"
+            template: "{{analysis_and_implications}}"
+      - id: adoption-lifecycle
+        title: Technology Adoption Lifecycle Stage
+        instruction: |
+          Identify where the market is in the adoption curve:
+          - Current stage and evidence
+          - Implications for strategy
+          - Expected progression timeline
+
+  - id: opportunity-assessment
+    title: Opportunity Assessment
+    sections:
+      - id: market-opportunities
+        title: Market Opportunities
+        instruction: Identify specific opportunities based on the analysis
+        repeatable: true
+        sections:
+          - id: opportunity
+            title: "Opportunity {{opportunity_number}}: {{name}}"
+            template: |
+              - **Description:** {{what_is_the_opportunity}}
+              - **Size/Potential:** {{quantified_potential}}
+              - **Requirements:** {{needed_to_capture}}
+              - **Risks:** {{key_challenges}}
+      - id: strategic-recommendations
+        title: Strategic Recommendations
+        sections:
+          - id: go-to-market
+            title: Go-to-Market Strategy
+            instruction: |
+              Recommend approach for market entry/expansion:
+              - Target segment prioritization
+              - Positioning strategy
+              - Channel strategy
+              - Partnership opportunities
+          - id: pricing-strategy
+            title: Pricing Strategy
+            instruction: |
+              Based on willingness to pay analysis and competitive landscape:
+              - Recommended pricing model
+              - Price points/ranges
+              - Value metric
+              - Competitive positioning
+          - id: risk-mitigation
+            title: Risk Mitigation
+            instruction: |
+              Key risks and mitigation strategies:
+              - Market risks
+              - Competitive risks
+              - Execution risks
+              - Regulatory/compliance risks
+
+  - id: appendices
+    title: Appendices
+    sections:
+      - id: data-sources
+        title: A. Data Sources
+        instruction: List all sources used in the research
+      - id: calculations
+        title: B. Detailed Calculations
+        instruction: Include any complex calculations or models
+      - id: additional-analysis
+        title: C. Additional Analysis
+        instruction: Any supplementary analysis not included in main body