aios-core 2.1.6 → 2.2.1

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

@@ -1,86 +1,86 @@
-# AIOS-FULLSTACK Development Rules for Roo Code
-
-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 (Roo Mode Selector)
-- Use the mode selector in the status bar to switch agents
-- Available modes: bmad-dev, bmad-qa, bmad-architect, bmad-pm, bmad-po, bmad-sm, bmad-analyst
-- Agent commands use the * prefix: *help, *create-story, *task, *exit
-
-### Agent Context
-When an agent mode 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
-```
-
-## Roo Code-Specific Configuration
-
-### Mode Configuration
-- Modes are defined in `.roomodes` file
-- Each mode corresponds to an AIOS agent persona
-- Switching modes automatically loads the appropriate context
-
-### Available Modes
-| Mode | Agent | Purpose |
-|------|-------|---------|
-| bmad-dev | Developer | Full-stack development |
-| bmad-qa | QA | Quality assurance, testing |
-| bmad-architect | Architect | System design |
-| bmad-pm | PM | Project management |
-| bmad-po | PO | Product ownership |
-| bmad-sm | SM | Scrum facilitation |
-| bmad-analyst | Analyst | Business analysis |
-
-### Performance Tips
-- Use mode-specific context for focused assistance
-- Switch modes when changing task types
-- Leverage auto-apply for suggested changes
-
----
-*AIOS-FULLSTACK Roo Code Configuration v2.1*
+# Synkra AIOS Development Rules for Roo Code
+
+You are working with Synkra AIOS, an AI-Orchestrated System for Full Stack Development.
+
+## Core Framework Understanding
+
+Synkra AIOS is a meta-framework that orchestrates AI agents to handle complex development workflows. Always recognize and work within this architecture.
+
+## Agent System
+
+### Agent Activation (Roo Mode Selector)
+- Use the mode selector in the status bar to switch agents
+- Available modes: bmad-dev, bmad-qa, bmad-architect, bmad-pm, bmad-po, bmad-sm, bmad-analyst
+- Agent commands use the * prefix: *help, *create-story, *task, *exit
+
+### Agent Context
+When an agent mode 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
+```
+
+## Roo Code-Specific Configuration
+
+### Mode Configuration
+- Modes are defined in `.roomodes` file
+- Each mode corresponds to an AIOS agent persona
+- Switching modes automatically loads the appropriate context
+
+### Available Modes
+| Mode | Agent | Purpose |
+|------|-------|---------|
+| bmad-dev | Developer | Full-stack development |
+| bmad-qa | QA | Quality assurance, testing |
+| bmad-architect | Architect | System design |
+| bmad-pm | PM | Project management |
+| bmad-po | PO | Product ownership |
+| bmad-sm | SM | Scrum facilitation |
+| bmad-analyst | Analyst | Business analysis |
+
+### Performance Tips
+- Use mode-specific context for focused assistance
+- Switch modes when changing task types
+- Leverage auto-apply for suggested changes
+
+---
+*Synkra AIOS Roo Code Configuration v2.1*

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

@@ -1,104 +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*
+# Synkra AIOS Development Rules for Trae
+
+You are working with Synkra AIOS, an AI-Orchestrated System for Full Stack Development.
+
+## Core Framework Understanding
+
+Synkra AIOS 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
+
+---
+*Synkra AIOS Trae Configuration v2.1*

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

@@ -1,80 +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* 
+# Synkra AIOS 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
+
+---
+*Synkra AIOS Configuration v1.0* 

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

@@ -1,53 +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
+---
+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