create-genia-os 2.4.0 → 3.0.0

package/template/.aiox-core/product/templates/ide-rules/antigravity-rules.md

@@ -0,0 +1,115 @@
+# Synkra AIOX Development Rules for AntiGravity
+
+You are working with Synkra AIOX, an AI-Orchestrated System for Full Stack Development.
+
+## Core Development Rules
+
+### Agent Integration
+- Recognize AIOX 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
+
+## AIOX Framework Structure
+
+```
+aiox-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
+  }
+}
+```
+
+---
+*Synkra AIOX AntiGravity Configuration v1.0*

package/template/.aiox-core/product/templates/ide-rules/claude-rules.md

@@ -0,0 +1,356 @@
+# Synkra AIOX Development Rules for Claude Code
+
+You are working with Synkra AIOX, an AI-Orchestrated System for Full Stack Development.
+
+<!-- AIOX-MANAGED-START: core-framework -->
+## Core Framework Understanding
+
+Synkra AIOX is a meta-framework that orchestrates AI agents to handle complex development workflows. Always recognize and work within this architecture.
+<!-- AIOX-MANAGED-END: core-framework -->
+
+<!-- AIOX-MANAGED-START: constitution -->
+## Constitution
+
+O AIOX possui uma **Constitution formal** com princípios inegociáveis e gates automáticos.
+
+**Documento completo:** `.aiox-core/constitution.md`
+
+**Princípios fundamentais:**
+
+| Artigo | Princípio | Severidade |
+|--------|-----------|------------|
+| I | CLI First | NON-NEGOTIABLE |
+| II | Agent Authority | NON-NEGOTIABLE |
+| III | Story-Driven Development | MUST |
+| IV | No Invention | MUST |
+| V | Quality First | MUST |
+| VI | Absolute Imports | SHOULD |
+
+**Gates automáticos bloqueiam violações.** Consulte a Constitution para detalhes completos.
+<!-- AIOX-MANAGED-END: constitution -->
+
+<!-- AIOX-MANAGED-START: sistema-de-agentes -->
+## Sistema de Agentes
+
+### Ativação de Agentes
+Use `@agent-name` ou `/AIOX:agents:agent-name`:
+
+| Agente | Persona | Escopo Principal |
+|--------|---------|------------------|
+| `@dev` | Dex | Implementação de código |
+| `@qa` | Quinn | Testes e qualidade |
+| `@architect` | Aria | Arquitetura e design técnico |
+| `@pm` | Morgan | Product Management |
+| `@po` | Pax | Product Owner, stories/epics |
+| `@sm` | River | Scrum Master |
+| `@analyst` | Alex | Pesquisa e análise |
+| `@data-engineer` | Dara | Database design |
+| `@ux-design-expert` | Uma | UX/UI design |
+| `@devops` | Gage | CI/CD, git push (EXCLUSIVO) |
+
+### Comandos de Agentes
+Use prefixo `*` para comandos:
+- `*help` - Mostrar comandos disponíveis
+- `*create-story` - Criar story de desenvolvimento
+- `*task {name}` - Executar task específica
+- `*exit` - Sair do modo agente
+<!-- AIOX-MANAGED-END: sistema-de-agentes -->
+
+<!-- AIOX-MANAGED-START: agent-system -->
+## Agent System
+
+### Agent Activation
+- Agents are activated with @agent-name syntax: @dev, @qa, @architect, @pm, @po, @sm, @analyst
+- The master agent is activated with @aiox-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
+<!-- AIOX-MANAGED-END: agent-system -->
+
+## 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
+
+<!-- AIOX-MANAGED-START: framework-structure -->
+## AIOX Framework Structure
+
+```
+aiox-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
+```
+<!-- AIOX-MANAGED-END: framework-structure -->
+
+<!-- AIOX-MANAGED-START: framework-boundary -->
+## Framework vs Project Boundary
+
+O AIOX usa um modelo de 4 camadas (L1-L4) para separar artefatos do framework e do projeto. Deny rules em `.claude/settings.json` reforçam isso deterministicamente.
+
+| Camada | Mutabilidade | Paths | Notas |
+|--------|-------------|-------|-------|
+| **L1** Framework Core | NEVER modify | `.aiox-core/core/`, `.aiox-core/constitution.md`, `bin/aiox.js`, `bin/aiox-init.js` | Protegido por deny rules |
+| **L2** Framework Templates | NEVER modify | `.aiox-core/development/tasks/`, `.aiox-core/development/templates/`, `.aiox-core/development/checklists/`, `.aiox-core/development/workflows/`, `.aiox-core/infrastructure/` | Extend-only |
+| **L3** Project Config | Mutable (exceptions) | `.aiox-core/data/`, `agents/*/MEMORY.md`, `core-config.yaml` | Allow rules permitem |
+| **L4** Project Runtime | ALWAYS modify | `docs/stories/`, `packages/`, `squads/`, `tests/` | Trabalho do projeto |
+
+**Toggle:** `core-config.yaml` → `boundary.frameworkProtection: true/false` controla se deny rules são ativas (default: true para projetos, false para contribuidores do framework).
+
+> **Referência formal:** `.claude/settings.json` (deny/allow rules), `.claude/rules/agent-authority.md`
+<!-- AIOX-MANAGED-END: framework-boundary -->
+
+<!-- AIOX-MANAGED-START: rules-system -->
+## Rules System
+
+O AIOX carrega regras contextuais de `.claude/rules/` automaticamente. Regras com frontmatter `paths:` só carregam quando arquivos correspondentes são editados.
+
+| Rule File | Description |
+|-----------|-------------|
+| `agent-authority.md` | Agent delegation matrix and exclusive operations |
+| `agent-handoff.md` | Agent switch compaction protocol for context optimization |
+| `agent-memory-imports.md` | Agent memory lifecycle and CLAUDE.md ownership |
+| `coderabbit-integration.md` | Automated code review integration rules |
+| `ids-principles.md` | Incremental Development System principles |
+| `mcp-usage.md` | MCP server usage rules and tool selection priority |
+| `story-lifecycle.md` | Story status transitions and quality gates |
+| `workflow-execution.md` | 4 primary workflows (SDC, QA Loop, Spec Pipeline, Brownfield) |
+
+> **Diretório:** `.claude/rules/` — rules são carregadas automaticamente pelo Claude Code quando relevantes.
+<!-- AIOX-MANAGED-END: rules-system -->
+
+<!-- AIOX-MANAGED-START: code-intelligence -->
+## Code Intelligence
+
+O AIOX possui um sistema de code intelligence opcional que enriquece operações com dados de análise de código.
+
+| Status | Descrição | Comportamento |
+|--------|-----------|---------------|
+| **Configured** | Provider ativo e funcional | Enrichment completo disponível |
+| **Fallback** | Provider indisponível | Sistema opera normalmente sem enrichment — graceful degradation |
+| **Disabled** | Nenhum provider configurado | Funcionalidade de code-intel ignorada silenciosamente |
+
+**Graceful Fallback:** Code intelligence é sempre opcional. `isCodeIntelAvailable()` verifica disponibilidade antes de qualquer operação. Se indisponível, o sistema retorna o resultado base sem modificação — nunca falha.
+
+**Diagnóstico:** `aiox doctor` inclui check de code-intel provider status.
+
+> **Referência:** `.aiox-core/core/code-intel/` — provider interface, enricher, client
+<!-- AIOX-MANAGED-END: code-intelligence -->
+
+<!-- AIOX-MANAGED-START: graph-dashboard -->
+## Graph Dashboard
+
+O CLI `aiox graph` visualiza dependências, estatísticas de entidades e status de providers.
+
+### Comandos
+
+```bash
+aiox graph --deps                        # Dependency tree (ASCII)
+aiox graph --deps --format=json          # Output como JSON
+aiox graph --deps --format=html          # Interactive HTML (abre browser)
+aiox graph --deps --format=mermaid       # Mermaid diagram
+aiox graph --deps --format=dot           # DOT format (Graphviz)
+aiox graph --deps --watch                # Live mode com auto-refresh
+aiox graph --deps --watch --interval=10  # Refresh a cada 10 segundos
+aiox graph --stats                       # Entity stats e cache metrics
+```
+
+**Formatos de saída:** ascii (default), json, dot, mermaid, html
+
+> **Referência:** `.aiox-core/core/graph-dashboard/` — CLI, renderers, data sources
+<!-- AIOX-MANAGED-END: graph-dashboard -->
+
+## 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`
+
+<!-- AIOX-MANAGED-START: aiox-patterns -->
+## AIOX-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();
+```
+<!-- AIOX-MANAGED-END: aiox-patterns -->
+
+## Environment Setup
+
+### Required Tools
+- Node.js 18+
+- GitHub CLI
+- Git
+- Your preferred package manager (npm/yarn/pnpm)
+
+### Configuration Files
+- `.aiox/config.yaml` - Framework configuration
+- `.env` - Environment variables
+- `aiox.config.js` - Project-specific settings
+
+<!-- AIOX-MANAGED-START: common-commands -->
+## Common Commands
+
+### AIOX 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
+<!-- AIOX-MANAGED-END: common-commands -->
+
+## Debugging
+
+### Enable Debug Mode
+```bash
+export AIOX_DEBUG=true
+```
+
+### View Agent Logs
+```bash
+tail -f .aiox/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
+
+---
+*Synkra AIOX Claude Code Configuration v2.0*

package/template/.aiox-core/product/templates/ide-rules/codex-rules.md

@@ -0,0 +1,65 @@
+# AGENTS.md - Synkra AIOX (Codex CLI)
+
+Este arquivo define as instrucoes do projeto para o Codex CLI.
+
+<!-- AIOX-MANAGED-START: core -->
+## Core Rules
+
+1. Siga a Constitution em `.aiox-core/constitution.md`
+2. Priorize `CLI First -> Observability Second -> UI Third`
+3. Trabalhe por stories em `docs/stories/`
+4. Nao invente requisitos fora dos artefatos existentes
+<!-- AIOX-MANAGED-END: core -->
+
+<!-- AIOX-MANAGED-START: quality -->
+## Quality Gates
+
+- Rode `npm run lint`
+- Rode `npm run typecheck`
+- Rode `npm test`
+- Atualize checklist e file list da story antes de concluir
+<!-- AIOX-MANAGED-END: quality -->
+
+<!-- AIOX-MANAGED-START: codebase -->
+## Project Map
+
+- Core framework: `.aiox-core/`
+- CLI entrypoints: `bin/`
+- Shared packages: `packages/`
+- Tests: `tests/`
+- Docs: `docs/`
+<!-- AIOX-MANAGED-END: codebase -->
+
+<!-- AIOX-MANAGED-START: commands -->
+## Common Commands
+
+- `npm run sync:ide`
+- `npm run sync:ide:check`
+- `npm run sync:skills:codex`
+- `npm run sync:skills:codex:global` (opcional; neste repo o padrao e local-first)
+- `npm run validate:structure`
+- `npm run validate:agents`
+<!-- AIOX-MANAGED-END: commands -->
+
+<!-- AIOX-MANAGED-START: shortcuts -->
+## Agent Shortcuts
+
+Preferencia de ativacao no Codex CLI:
+1. Use `/skills` e selecione `aiox-<agent-id>` vindo de `.codex/skills` (ex.: `aiox-architect`)
+2. Se preferir, use os atalhos abaixo (`@architect`, `/architect`, etc.)
+
+Interprete os atalhos abaixo carregando o arquivo correspondente em `.aiox-core/development/agents/` (fallback: `.codex/agents/`), renderize o greeting via `generate-greeting.js` e assuma a persona ate `*exit`:
+
+- `@architect`, `/architect`, `/architect.md` -> `.aiox-core/development/agents/architect.md`
+- `@dev`, `/dev`, `/dev.md` -> `.aiox-core/development/agents/dev.md`
+- `@qa`, `/qa`, `/qa.md` -> `.aiox-core/development/agents/qa.md`
+- `@pm`, `/pm`, `/pm.md` -> `.aiox-core/development/agents/pm.md`
+- `@po`, `/po`, `/po.md` -> `.aiox-core/development/agents/po.md`
+- `@sm`, `/sm`, `/sm.md` -> `.aiox-core/development/agents/sm.md`
+- `@analyst`, `/analyst`, `/analyst.md` -> `.aiox-core/development/agents/analyst.md`
+- `@devops`, `/devops`, `/devops.md` -> `.aiox-core/development/agents/devops.md`
+- `@data-engineer`, `/data-engineer`, `/data-engineer.md` -> `.aiox-core/development/agents/data-engineer.md`
+- `@ux-design-expert`, `/ux-design-expert`, `/ux-design-expert.md` -> `.aiox-core/development/agents/ux-design-expert.md`
+- `@squad-creator`, `/squad-creator`, `/squad-creator.md` -> `.aiox-core/development/agents/squad-creator.md`
+- `@aiox-master`, `/aiox-master`, `/aiox-master.md` -> `.aiox-core/development/agents/aiox-master.md`
+<!-- AIOX-MANAGED-END: shortcuts -->

package/template/.aiox-core/product/templates/ide-rules/copilot-rules.md

@@ -0,0 +1,92 @@
+# Synkra AIOX Agent for GitHub Copilot
+
+You are working with Synkra AIOX, an AI-Orchestrated System for Full Stack Development.
+
+## Core Framework Understanding
+
+Synkra AIOX 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
+
+## AIOX Framework Structure
+
+```
+aiox-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 AIOX agent mode you need
+
+### Available Agent Modes
+| Mode | Purpose |
+|------|---------|
+| aiox-dev | Full-stack development |
+| aiox-qa | Quality assurance |
+| aiox-architect | System design |
+| aiox-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
+
+---
+*Synkra AIOX GitHub Copilot Configuration v4.0.4*