sinapse-ai 7.0.4 → 7.1.0

package/.sinapse-ai/product/templates/ide-rules/antigravity-rules.md

@@ -1,115 +0,0 @@
-# SINAPSE Development Rules for AntiGravity
-
-You are working with SINAPSE, an AI-Orchestrated System for Full Stack Development.
-
-## Core Development Rules
-
-### Agent Integration
-- Recognize SINAPSE agent activations: @developer, @quality-gate, @architect, @project-lead, @product-lead, @sprint-lead, @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
-
-## SINAPSE Framework Structure
-
-```
-sinapse-ai/
-├── 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
-  }
-}
-```
-
----
-*SINAPSE AntiGravity Configuration v1.0*

package/.sinapse-ai/product/templates/ide-rules/copilot-rules.md

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

package/.sinapse-ai/product/templates/ide-rules/cursor-rules.md

@@ -1,115 +0,0 @@
-# SINAPSE Development Rules for Cursor
-
-You are working with SINAPSE, an AI-Orchestrated System for Full Stack Development.
-
-## Core Development Rules
-
-### Agent Integration
-- Recognize SINAPSE agent activations: @developer, @quality-gate, @architect, @project-lead, @product-lead, @sprint-lead, @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
-
-## SINAPSE Framework Structure
-
-```
-sinapse-ai/
-├── 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
-  }
-}
-```
-
----
-*SINAPSE Cursor Configuration v1.0* 

package/.sinapse-ai/product/templates/ide-rules/gemini-rules.md

@@ -1,87 +0,0 @@
-# Gemini Rules - SINAPSE
-
-Este arquivo define as instrucoes do projeto para Gemini CLI neste repositorio.
-
-<!-- SINAPSE-MANAGED-START: core -->
-## Core Rules
-
-1. Siga a Constitution em `.sinapse-ai/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
-<!-- SINAPSE-MANAGED-END: core -->
-
-<!-- SINAPSE-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
-<!-- SINAPSE-MANAGED-END: quality -->
-
-<!-- SINAPSE-MANAGED-START: codebase -->
-## Project Map
-
-- Core framework: `.sinapse-ai/`
-- CLI entrypoints: `bin/`
-- Shared packages: `packages/`
-- Tests: `tests/`
-- Docs: `docs/`
-<!-- SINAPSE-MANAGED-END: codebase -->
-
-<!-- SINAPSE-MANAGED-START: gemini-integration -->
-## Gemini Integration
-
-Fonte de verdade de agentes:
-- Canonico: `.sinapse-ai/development/agents/*.md`
-- Espelhado para Gemini: `.gemini/rules/SINAPSE/agents/*.md`
-
-Hooks e settings:
-- Hooks locais: `.gemini/hooks/`
-- Settings locais: `.gemini/settings.json`
-
-Sempre que houver drift, execute:
-- `npm run sync:ide:gemini`
-- `npm run validate:gemini-sync`
-- `npm run validate:gemini-integration`
-<!-- SINAPSE-MANAGED-END: gemini-integration -->
-
-<!-- SINAPSE-MANAGED-START: parity -->
-## Multi-IDE Parity
-
-Para garantir paridade entre Claude Code, Codex e Gemini:
-- `npm run validate:parity`
-- `npm run validate:paths`
-<!-- SINAPSE-MANAGED-END: parity -->
-
-<!-- SINAPSE-MANAGED-START: activation -->
-## Agent Activation
-
-Preferencia de ativacao:
-1. Use agentes em `.gemini/rules/SINAPSE/agents/`
-2. Se necessario, use fonte canonica em `.sinapse-ai/development/agents/`
-
-Ao ativar agente:
-- carregar definicao completa do agente
-- renderizar greeting via `node .sinapse-ai/development/scripts/generate-greeting.js <agent-id>`
-- manter persona ativa ate `*exit`
-
-Atalhos recomendados no Gemini:
-- `/sinapse-menu` para listar agentes
-- `/sinapse-<agent-id>` (ex.: `/sinapse-dev`, `/sinapse-architect`)
-- `/sinapse-agent <agent-id>` para launcher generico
-<!-- SINAPSE-MANAGED-END: activation -->
-
-<!-- SINAPSE-MANAGED-START: commands -->
-## Common Commands
-
-- `npm run sync:ide`
-- `npm run sync:ide:check`
-- `npm run sync:ide:gemini`
-- `npm run validate:gemini-sync`
-- `npm run validate:gemini-integration`
-- `npm run validate:parity`
-- `npm run validate:structure`
-- `npm run validate:agents`
-<!-- SINAPSE-MANAGED-END: commands -->