aios-core 2.1.0

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

@@ -0,0 +1,221 @@
+# AIOS-FULLSTACK Development Rules for Claude 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
+- 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
+
+### When handling errors:
+```javascript
+try {
+  // Operation
+} catch (error) {
+  console.error(`Error in ${operation}:`, error);
+  // Provide helpful error message
+  throw new Error(`Failed to ${operation}: ${error.message}`);
+}
+```
+
+## Git & GitHub Integration
+
+### Commit Conventions
+- Use conventional commits: `feat:`, `fix:`, `docs:`, `chore:`, etc.
+- Reference story ID: `feat: implement IDE detection [Story 2.1]`
+- Keep commits atomic and focused
+
+### GitHub CLI Usage
+- Ensure authenticated: `gh auth status`
+- Use for PR creation: `gh pr create`
+- Check org access: `gh api user/memberships`
+
+## AIOS-Specific Patterns
+
+### Working with Templates
+```javascript
+const template = await loadTemplate('template-name');
+const rendered = await renderTemplate(template, context);
+```
+
+### Agent Command Handling
+```javascript
+if (command.startsWith('*')) {
+  const agentCommand = command.substring(1);
+  await executeAgentCommand(agentCommand, args);
+}
+```
+
+### Story Updates
+```javascript
+// Update story progress
+const story = await loadStory(storyId);
+story.updateTask(taskId, { status: 'completed' });
+await story.save();
+```
+
+## Environment Setup
+
+### Required Tools
+- Node.js 18+ 
+- GitHub CLI
+- Git
+- Your preferred package manager (npm/yarn/pnpm)
+
+### Configuration Files
+- `.aios/config.yaml` - Framework configuration
+- `.env` - Environment variables
+- `aios.config.js` - Project-specific settings
+
+## Common Commands
+
+### AIOS Master Commands
+- `*help` - Show available commands
+- `*create-story` - Create new story
+- `*task {name}` - Execute specific task
+- `*workflow {name}` - Run workflow
+
+### Development Commands
+- `npm run dev` - Start development
+- `npm test` - Run tests
+- `npm run lint` - Check code style
+- `npm run build` - Build project
+
+## Debugging
+
+### Enable Debug Mode
+```bash
+export AIOS_DEBUG=true
+```
+
+### View Agent Logs
+```bash
+tail -f .aios/logs/agent.log
+```
+
+### Trace Workflow Execution
+```bash
+npm run trace -- workflow-name
+```
+
+## Claude Code Specific Configuration
+
+### Performance Optimization
+- Prefer batched tool calls when possible for better performance
+- Use parallel execution for independent operations
+- Cache frequently accessed data in memory during sessions
+
+### Tool Usage Guidelines
+- Always use the Grep tool for searching, never `grep` or `rg` in bash
+- Use the Task tool for complex multi-step operations
+- Batch file reads/writes when processing multiple files
+- Prefer editing existing files over creating new ones
+
+### Session Management
+- Track story progress throughout the session
+- Update checkboxes immediately after completing tasks
+- Maintain context of the current story being worked on
+- Save important state before long-running operations
+
+### Error Recovery
+- Always provide recovery suggestions for failures
+- Include error context in messages to user
+- Suggest rollback procedures when appropriate
+- Document any manual fixes required
+
+### Testing Strategy
+- Run tests incrementally during development
+- Always verify lint and typecheck before marking complete
+- Test edge cases for each new feature
+- Document test scenarios in story files
+
+### Documentation
+- Update relevant docs when changing functionality
+- Include code examples in documentation
+- Keep README synchronized with actual behavior
+- Document breaking changes prominently
+
+---
+*AIOS-FULLSTACK Claude Code Configuration v2.0* 

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

@@ -0,0 +1,84 @@
+# AIOS-FULLSTACK Development Rules for Cline
+
+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
+```
+
+## Cline-Specific Configuration
+
+### Agent Rules Location
+- Rules are stored in `.cline/rules/`
+- Use @agent-name to activate agents in chat
+
+### Tool Permissions
+Cline requires explicit approval for:
+- File creation/modification
+- Terminal commands
+- Browser actions
+
+### Performance Tips
+- Use the task panel for complex multi-step operations
+- Leverage diff view for reviewing changes
+- Enable auto-approve for trusted operations
+
+### MCP Integration
+- Cline supports MCP servers for extended functionality
+- Configure in Cline settings for additional tools
+
+---
+*AIOS-FULLSTACK Cline Configuration v2.1*

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

@@ -0,0 +1,92 @@
+# AIOS-FULLSTACK Agent for GitHub Copilot
+
+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 (Chat Modes)
+- Select agent mode from the chat mode selector in VS Code
+- Available agents: dev, qa, architect, pm, po, sm, 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
+```
+
+## GitHub Copilot-Specific Configuration
+
+### Requirements
+- VS Code 1.101+ required
+- Enable `chat.agent.enabled: true` in settings
+
+### Chat Modes Location
+- Agent modes defined in `.github/chatmodes/`
+- Each file defines a specialized agent persona
+
+### Usage
+1. Open Chat view: `Ctrl+Alt+I` (Windows/Linux) or `⌃⌘I` (Mac)
+2. Select **Agent** from the chat mode selector
+3. Choose the AIOS agent mode you need
+
+### Available Agent Modes
+| Mode | Purpose |
+|------|---------|
+| aios-dev | Full-stack development |
+| aios-qa | Quality assurance |
+| aios-architect | System design |
+| aios-pm | Project management |
+
+### Performance Tips
+- Use inline completions for quick code suggestions
+- Use chat for complex explanations and refactoring
+- Reference files with @file syntax
+- Use @workspace for project-wide context
+
+---
+*AIOS-FULLSTACK GitHub Copilot Configuration v2.1*

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

@@ -0,0 +1,115 @@
+# AIOS-FULLSTACK Development Rules for Cursor
+
+You are working with AIOS-FULLSTACK, an AI-Orchestrated System for Full Stack Development.
+
+## Core Development Rules
+
+### Agent Integration
+- Recognize AIOS agent activations: @dev, @qa, @architect, @pm, @po, @sm, @analyst
+- Agent commands use * prefix: *help, *create-story, *task, *exit
+- Follow agent-specific workflows and patterns
+
+### Story-Driven Development
+1. **Always work from a story file** in docs/stories/
+2. **Update story checkboxes** as you complete tasks: [ ] → [x]
+3. **Maintain the File List** section with all created/modified files
+4. **Follow acceptance criteria** exactly as written
+
+### Code Quality Standards
+- Write clean, maintainable code following project conventions
+- Include comprehensive error handling
+- Add unit tests for all new functionality
+- Follow existing patterns in the codebase
+
+### Testing Protocol
+- Run all tests before marking tasks complete
+- Ensure linting passes: `npm run lint`
+- Verify type checking: `npm run typecheck`
+- Add tests for new features
+
+## AIOS Framework Structure
+
+```
+aios-core/
+├── agents/       # Agent persona definitions
+├── tasks/        # Executable task workflows
+├── workflows/    # Multi-step workflows
+├── templates/    # Document templates
+└── checklists/   # Validation checklists
+
+docs/
+├── stories/      # Development stories
+├── prd/          # Sharded PRD sections
+└── architecture/ # Sharded architecture
+```
+
+## Development Workflow
+
+1. **Read the story** - Understand requirements fully
+2. **Implement sequentially** - Follow task order
+3. **Test thoroughly** - Validate each step
+4. **Update story** - Mark completed items
+5. **Document changes** - Update File List
+
+## Best Practices
+
+### When implementing:
+- Check existing patterns first
+- Reuse components and utilities
+- Follow naming conventions
+- Keep functions focused and small
+
+### When testing:
+- Write tests alongside implementation
+- Test edge cases
+- Verify error handling
+- Run full test suite
+
+### When documenting:
+- Update README for new features
+- Document API changes
+- Add inline comments for complex logic
+- Keep story File List current
+
+## Git & GitHub
+
+- Use conventional commits: `feat:`, `fix:`, `docs:`, etc.
+- Reference story ID in commits: `feat: implement IDE detection [Story 2.1]`
+- Ensure GitHub CLI is configured: `gh auth status`
+- Push regularly to avoid conflicts
+
+## Common Patterns
+
+### Error Handling
+```javascript
+try {
+  // Operation
+} catch (error) {
+  console.error(`Error in ${operation}:`, error);
+  throw new Error(`Failed to ${operation}: ${error.message}`);
+}
+```
+
+### File Operations
+```javascript
+const fs = require('fs-extra');
+const path = require('path');
+
+// Always use absolute paths
+const filePath = path.join(__dirname, 'relative/path');
+```
+
+### Async/Await
+```javascript
+async function operation() {
+  try {
+    const result = await asyncOperation();
+    return result;
+  } catch (error) {
+    // Handle error appropriately
+  }
+}
+```
+
+---
+*AIOS-FULLSTACK Cursor Configuration v1.0* 

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

@@ -0,0 +1,85 @@
+# AIOS-FULLSTACK Development Rules for Gemini CLI
+
+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
+- Mention the agent persona in your prompt: "As the dev agent..." or "Acting as @dev..."
+- Available agents: dev, qa, architect, pm, po, sm, analyst
+- Agent commands use the * prefix: *help, *create-story, *task, *exit
+
+### Agent Context
+When referencing an agent:
+- 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
+```
+
+## Gemini CLI-Specific Configuration
+
+### Rules Location
+- Rules are stored in `.gemini/rules.md`
+- Include agent context in your prompts
+
+### Usage Pattern
+```bash
+# Example: Activate dev agent context
+gemini "As the AIOS dev agent, help me implement the user authentication feature from docs/stories/auth-story.md"
+```
+
+### Performance Tips
+- Include relevant file context in prompts
+- Use clear, specific requests
+- Reference story files for context
+
+### Integration
+- Gemini CLI can execute shell commands
+- Use for code generation and analysis
+- Leverage multimodal capabilities for diagrams
+
+---
+*AIOS-FULLSTACK Gemini CLI Configuration v2.1*

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

@@ -0,0 +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*