sinapse-ai 9.2.0 → 9.3.0

package/docs/en/sinapse-workflows/brownfield-fullstack-workflow.md

@@ -1,50 +0,0 @@
-# Brownfield Fullstack Workflow
-
-> **EN** | [PT](../../sinapse-workflows/brownfield-fullstack-workflow.md) | [ES](../../es/sinapse-workflows/brownfield-fullstack-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/brownfield-fullstack-workflow.md)
-
----
-
-## Summary
-
-The **Brownfield Fullstack Workflow** is designed for evolving existing full-stack applications. It handles:
-
-- Impact analysis across frontend and backend
-- Coordinated changes between layers
-- Backward compatibility considerations
-- Migration strategies
-- Regression prevention
-
-### When to Use
-
-- Adding features to existing full-stack applications
-- Refactoring across multiple layers
-- Major enhancements requiring frontend and backend changes
-- After completing brownfield-discovery
-
-### Prerequisites
-
-- Run `brownfield-discovery` first if unfamiliar with the project
-- Understand existing architecture and patterns
-
-### Key Agents
-
-- `@architect` - Change impact analysis
-- `@dev` - Implementation across layers
-- `@data-engineer` - Database migrations
-- `@qa` - Regression testing
-
-### Main Phases
-
-1. **Impact Analysis** - Understanding affected areas
-2. **Planning** - Coordinated change strategy
-3. **Backend Changes** - API and service modifications
-4. **Frontend Changes** - UI updates and integration
-5. **Validation** - End-to-end testing
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/brownfield-fullstack-workflow.md).*

package/docs/en/sinapse-workflows/brownfield-service-workflow.md

@@ -1,51 +0,0 @@
-# Brownfield Service Workflow
-
-> **EN** | [PT](../../sinapse-workflows/brownfield-service-workflow.md) | [ES](../../es/sinapse-workflows/brownfield-service-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/brownfield-service-workflow.md)
-
----
-
-## Summary
-
-The **Brownfield Service Workflow** is designed for evolving existing backend services and APIs. It focuses on:
-
-- API versioning and backward compatibility
-- Database migration strategies
-- Service refactoring patterns
-- Performance optimization
-- Security enhancements
-
-### When to Use
-
-- Extending existing APIs with new endpoints
-- Refactoring backend services
-- Database schema evolution
-- Performance improvements in services
-- After completing brownfield-discovery
-
-### Prerequisites
-
-- Run `brownfield-discovery` first if unfamiliar with the project
-- Understand existing API contracts
-
-### Key Agents
-
-- `@architect` - Service evolution strategy
-- `@dev` - Backend implementation
-- `@data-engineer` - Migration planning
-- `@qa` - API contract testing
-
-### Main Phases
-
-1. **Contract Analysis** - Existing API review
-2. **Migration Planning** - Data and API versioning strategy
-3. **Implementation** - Service changes
-4. **Data Migration** - Database updates
-5. **Validation** - Contract and regression tests
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/brownfield-service-workflow.md).*

package/docs/en/sinapse-workflows/brownfield-ui-workflow.md

@@ -1,51 +0,0 @@
-# Brownfield UI Workflow
-
-> **EN** | [PT](../../sinapse-workflows/brownfield-ui-workflow.md) | [ES](../../es/sinapse-workflows/brownfield-ui-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/brownfield-ui-workflow.md)
-
----
-
-## Summary
-
-The **Brownfield UI Workflow** is designed for evolving existing frontend applications. It addresses:
-
-- Component refactoring and modernization
-- Design system integration
-- State management improvements
-- Accessibility enhancements
-- Performance optimization
-
-### When to Use
-
-- Adding features to existing frontend applications
-- UI/UX improvements and modernization
-- Component library migration
-- Design system adoption
-- After completing brownfield-discovery
-
-### Prerequisites
-
-- Run `brownfield-discovery` first if unfamiliar with the project
-- Understand existing component patterns
-
-### Key Agents
-
-- `@ux-design-expert` - Design guidance
-- `@architect` - Frontend architecture evolution
-- `@dev` - UI implementation
-- `@qa` - Visual regression testing
-
-### Main Phases
-
-1. **Component Audit** - Existing UI review
-2. **Design Alignment** - Design system mapping
-3. **Refactoring** - Component modernization
-4. **Enhancement** - New feature implementation
-5. **Polish** - Accessibility and performance
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/brownfield-ui-workflow.md).*

package/docs/en/sinapse-workflows/design-system-build-quality-workflow.md

@@ -1,53 +0,0 @@
-# Design System Build Quality Workflow
-
-> **EN** | [PT](../../sinapse-workflows/design-system-build-quality-workflow.md) | [ES](../../es/sinapse-workflows/design-system-build-quality-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/design-system-build-quality-workflow.md)
-
----
-
-## Summary
-
-The **Design System Build Quality Workflow** guides the creation and maintenance of design systems. It ensures:
-
-- Consistent design tokens and variables
-- Reusable component library
-- Documentation and usage guidelines
-- Accessibility standards
-- Visual regression testing
-
-### When to Use
-
-- Creating a new design system
-- Evolving existing component libraries
-- Establishing UI consistency across projects
-
-### Key Agents
-
-- `@ux-design-expert` - Design leadership
-- `@architect` - Component architecture
-- `@dev` - Component implementation
-- `@qa` - Visual and accessibility testing
-
-### Main Phases
-
-1. **Foundation** - Design tokens and base styles
-2. **Primitives** - Basic UI elements
-3. **Components** - Complex component patterns
-4. **Documentation** - Usage guides and examples
-5. **Quality** - Testing and validation
-
-### Key Components
-
-- Color system and typography
-- Spacing and layout tokens
-- Icon system
-- Form elements
-- Navigation patterns
-- Feedback components
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/design-system-build-quality-workflow.md).*

package/docs/en/sinapse-workflows/greenfield-fullstack-workflow.md

@@ -1,45 +0,0 @@
-# Greenfield Fullstack Workflow
-
-> **EN** | [PT](../../sinapse-workflows/greenfield-fullstack-workflow.md) | [ES](../../es/sinapse-workflows/greenfield-fullstack-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/greenfield-fullstack-workflow.md)
-
----
-
-## Summary
-
-The **Greenfield Fullstack Workflow** is designed for creating new full-stack applications from scratch. It orchestrates the complete development lifecycle including:
-
-- Project scaffolding and structure setup
-- Backend API development
-- Frontend UI development
-- Database schema design
-- Integration between layers
-- CI/CD pipeline configuration
-
-### When to Use
-
-- Starting a brand new full-stack project
-- Building applications with both frontend and backend components
-- Projects requiring coordinated development across all layers
-
-### Key Agents
-
-- `@architect` - System architecture and design
-- `@dev` - Implementation
-- `@data-engineer` - Database design
-- `@qa` - Quality assurance
-
-### Main Phases
-
-1. **Discovery** - Requirements gathering and architecture planning
-2. **Setup** - Project scaffolding and configuration
-3. **Development** - Iterative story-driven development
-4. **Integration** - Component integration and testing
-5. **Deployment** - CI/CD and release preparation
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/greenfield-fullstack-workflow.md).*

package/docs/en/sinapse-workflows/greenfield-service-workflow.md

@@ -1,45 +0,0 @@
-# Greenfield Service Workflow
-
-> **EN** | [PT](../../sinapse-workflows/greenfield-service-workflow.md) | [ES](../../es/sinapse-workflows/greenfield-service-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/greenfield-service-workflow.md)
-
----
-
-## Summary
-
-The **Greenfield Service Workflow** is designed for creating new backend services and APIs from scratch. It focuses on:
-
-- API design and specification
-- Service architecture patterns
-- Database modeling
-- Authentication and authorization
-- API documentation (OpenAPI/Swagger)
-- Testing strategies for services
-
-### When to Use
-
-- Building a new backend service or microservice
-- Creating REST or GraphQL APIs
-- Developing backend-only projects without frontend components
-
-### Key Agents
-
-- `@architect` - Service architecture and API design
-- `@dev` - Backend implementation
-- `@data-engineer` - Database schema design
-- `@qa` - API testing and quality
-
-### Main Phases
-
-1. **API Design** - Contract-first API specification
-2. **Architecture** - Service patterns and structure
-3. **Data Layer** - Database design and migrations
-4. **Implementation** - Service logic development
-5. **Testing** - Integration and contract tests
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/greenfield-service-workflow.md).*

package/docs/en/sinapse-workflows/greenfield-ui-workflow.md

@@ -1,45 +0,0 @@
-# Greenfield UI Workflow
-
-> **EN** | [PT](../../sinapse-workflows/greenfield-ui-workflow.md) | [ES](../../es/sinapse-workflows/greenfield-ui-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/greenfield-ui-workflow.md)
-
----
-
-## Summary
-
-The **Greenfield UI Workflow** is designed for creating new frontend applications from scratch. It covers:
-
-- UI/UX design integration
-- Component architecture
-- Design system setup
-- State management patterns
-- Responsive and accessible design
-- Frontend testing strategies
-
-### When to Use
-
-- Building a new frontend application
-- Creating SPAs or static sites
-- Projects consuming existing APIs without backend development
-
-### Key Agents
-
-- `@ux-design-expert` - UX/UI design guidance
-- `@architect` - Frontend architecture
-- `@dev` - UI implementation
-- `@qa` - Visual and functional testing
-
-### Main Phases
-
-1. **Design Review** - UX/UI requirements and design system
-2. **Architecture** - Component structure and state management
-3. **Component Development** - Building UI components
-4. **Integration** - API integration and data flow
-5. **Polish** - Accessibility, responsiveness, and performance
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/greenfield-ui-workflow.md).*

package/docs/en/sinapse-workflows/qa-loop-workflow.md

@@ -1,50 +0,0 @@
-# QA Loop Workflow
-
-> **EN** | [PT](../../sinapse-workflows/qa-loop-workflow.md) | [ES](../../es/sinapse-workflows/qa-loop-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/qa-loop-workflow.md)
-
----
-
-## Summary
-
-The **QA Loop Workflow** defines the quality assurance cycle within SINAPSE development. It ensures:
-
-- Comprehensive test coverage
-- Code quality standards
-- Performance validation
-- Security checks
-- Accessibility compliance
-
-### When to Use
-
-- During the QA phase of story-development-cycle
-- For dedicated quality review sessions
-- Before release preparation
-
-### Key Agents
-
-- `@qa` - Primary quality assurance
-- `@dev` - Bug fixes and improvements
-- `@architect` - Architecture review
-
-### Main Phases
-
-1. **Test Planning** - Test strategy and coverage goals
-2. **Automated Testing** - Unit, integration, E2E tests
-3. **Manual Review** - Code review and exploratory testing
-4. **Issue Tracking** - Bug identification and prioritization
-5. **Resolution** - Fix implementation and verification
-
-### Quality Gates
-
-- All tests passing
-- Linting and type checking clean
-- Code coverage thresholds met
-- No critical security issues
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/qa-loop-workflow.md).*

package/docs/en/sinapse-workflows/spec-pipeline-workflow.md

@@ -1,48 +0,0 @@
-# Spec Pipeline Workflow
-
-> **EN** | [PT](../../sinapse-workflows/spec-pipeline-workflow.md) | [ES](../../es/sinapse-workflows/spec-pipeline-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/spec-pipeline-workflow.md)
-
----
-
-## Summary
-
-The **Spec Pipeline Workflow** manages the specification and requirements process before development begins. It covers:
-
-- Requirements gathering and refinement
-- Technical specification creation
-- Architecture decisions
-- Story creation and prioritization
-- Stakeholder approval
-
-### When to Use
-
-- Before starting new features or projects
-- For complex requirements needing formal specification
-- When stakeholder alignment is required
-
-### Key Agents
-
-- `@pm` - Product management
-- `@po` - Story creation
-- `@architect` - Technical specification
-- `@analyst` - Requirements research
-
-### Main Phases
-
-1. **Discovery** - Requirements gathering
-2. **Analysis** - Feasibility and impact assessment
-3. **Specification** - Technical spec creation
-4. **Review** - Stakeholder approval
-5. **Handoff** - Story creation for development
-
-### Output
-
-Approved specification documents and stories ready for story-development-cycle.
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/spec-pipeline-workflow.md).*

package/docs/en/sinapse-workflows/story-development-cycle-workflow.md

@@ -1,50 +0,0 @@
-# Story Development Cycle Workflow
-
-> **EN** | [PT](../../sinapse-workflows/story-development-cycle-workflow.md) | [ES](../../es/sinapse-workflows/story-development-cycle-workflow.md)
-
----
-
-**Full documentation available in:** [Portuguese Version](../../sinapse-workflows/story-development-cycle-workflow.md)
-
----
-
-## Summary
-
-The **Story Development Cycle Workflow** is the core development process in SINAPSE. It orchestrates the complete lifecycle of implementing a user story:
-
-- Story breakdown and task creation
-- Test-first development approach
-- Iterative implementation
-- Code review and quality gates
-- Documentation updates
-
-### When to Use
-
-- For every story implementation in SINAPSE
-- Called by greenfield and brownfield workflows
-- After spec-pipeline approval
-
-### Key Agents
-
-- `@po` - Story management
-- `@dev` - Implementation
-- `@qa` - Quality assurance
-- `@devops` - Deployment
-
-### Main Phases
-
-1. **Preparation** - Story review and task breakdown
-2. **Development** - Test-first implementation cycle
-3. **Quality** - Code review and testing
-4. **Integration** - Merge and deployment preparation
-5. **Closure** - Story completion and documentation
-
-### Execution Modes
-
-- **YOLO** - Fully autonomous execution
-- **Interactive** - Human checkpoints at key decisions
-- **Pre-Flight** - Planning only, no execution
-
----
-
-*For complete details, diagrams, and step-by-step instructions, see the [Portuguese documentation](../../sinapse-workflows/story-development-cycle-workflow.md).*

package/docs/how-to-contribute-with-pull-requests.md

@@ -1,158 +0,0 @@
-# Como Contribuir com Pull Requests
-
-> 🌐 **EN** | [PT](./pt/how-to-contribute-with-pull-requests.md) | [ES](./es/how-to-contribute-with-pull-requests.md)
-
----
-
-**Novo no GitHub e em pull requests?** Este guia irá orientá-lo através dos conceitos básicos passo a passo.
-
-## O Que é um Pull Request?
-
-Um pull request (PR) é como você propõe mudanças para um projeto no GitHub. Pense nisso como dizer "Aqui estão algumas mudanças que eu gostaria de fazer - por favor, revise e considere adicioná-las ao projeto principal."
-
-## Antes de Começar
-
-⚠️ **Importante**: Por favor, mantenha suas contribuições pequenas e focadas! Preferimos muitas mudanças pequenas e claras ao invés de uma única mudança massiva.
-
-**Obrigatório antes de submeter PRs:**
-
-- **Para correções de bugs**: Crie uma issue usando o [template de bug report](https://github.com/SinapseAIinc/sinapse-ai/issues/new?template=bug_report.md)
-- **Para novas features**:
-  1. Discuta no Discord no [canal #general-dev](https://discord.gg/gk8jAdXWmj)
-  2. Crie uma issue usando o [template de feature request](https://github.com/SinapseAIinc/sinapse-ai/issues/new?template=feature_request.md)
-- **Para mudanças grandes**: Sempre abra uma issue primeiro para discutir o alinhamento
-
-## Guia Passo a Passo
-
-### 1. Fazer Fork do Repositório
-
-1. Vá para o [repositório SINAPSE](https://github.com/SinapseAIinc/sinapse-ai)
-2. Clique no botão "Fork" no canto superior direito
-3. Isso cria sua própria cópia do projeto
-
-### 2. Clonar Seu Fork
-
-```bash
-# Substitua SEU-USUARIO pelo seu nome de usuário real do GitHub
-git clone https://github.com/SEU-USUARIO/sinapse-ai.git
-cd sinapse-ai
-```
-
-### 3. Criar uma Nova Branch
-
-**Nunca trabalhe diretamente na branch `main`!** Sempre crie uma nova branch para suas mudanças:
-
-```bash
-# Criar e mudar para uma nova branch
-git checkout -b fix/typo-in-readme
-# ou
-git checkout -b feature/add-new-agent
-```
-
-**Dicas de nomenclatura de branches:**
-
-- `fix/descricao` - para correções de bugs
-- `feature/descricao` - para novas funcionalidades
-- `docs/descricao` - para mudanças na documentação
-
-### 4. Fazer Suas Mudanças
-
-- Edite os arquivos que você deseja alterar
-- Mantenha as mudanças pequenas e focadas em uma coisa
-- Teste suas mudanças se possível
-
-### 5. Fazer Commit das Suas Mudanças
-
-```bash
-# Adicionar suas mudanças
-git add .
-
-# Commit com uma mensagem clara
-git commit -m "Corrigir erro de digitação no README.md"
-```
-
-**Boas mensagens de commit:**
-
-- "Corrigir erro de digitação nas instruções de instalação"
-- "Adicionar exemplo de uso de novo agente"
-- "Atualizar link quebrado na documentação"
-
-**Más mensagens de commit:**
-
-- "coisas"
-- "mudanças"
-- "atualizar"
-
-### 6. Fazer Push para Seu Fork
-
-```bash
-# Fazer push da sua branch para seu fork
-git push origin fix/typo-in-readme
-```
-
-### 7. Criar o Pull Request
-
-1. Vá para seu fork no GitHub
-2. Você verá um botão verde "Compare & pull request" - clique nele
-3. Selecione a branch de destino correta:
-   - **Branch `next`** para a maioria das contribuições (features, docs, melhorias)
-   - **Branch `main`** apenas para correções críticas
-4. Preencha a descrição do PR usando o template em CONTRIBUTING.md:
-   - **O Quê**: 1-2 frases descrevendo o que mudou
-   - **Por Quê**: 1-2 frases explicando o motivo
-   - **Como**: 2-3 bullets sobre a implementação
-   - **Testes**: Como você testou
-5. Referencie o número da issue relacionada (ex: "Fixes #123")
-
-### 8. Aguardar Revisão
-
-- Um mantenedor irá revisar seu PR
-- Eles podem pedir mudanças
-- Seja paciente e responsivo ao feedback
-
-## O Que Torna um Pull Request Bom?
-
-✅ **PRs Bons:**
-
-- Mudam uma coisa por vez
-- Têm títulos claros e descritivos
-- Explicam o quê e por quê na descrição
-- Incluem apenas os arquivos que precisam mudar
-
-❌ **Evite:**
-
-- Mudar a formatação de arquivos inteiros
-- Múltiplas mudanças não relacionadas em um PR
-- Copiar seu projeto/repositório inteiro no PR
-- Mudanças sem explicação
-
-## Erros Comuns a Evitar
-
-1. **Não reformate arquivos inteiros** - mude apenas o que é necessário
-2. **Não inclua mudanças não relacionadas** - foque em uma correção/feature por PR
-3. **Não cole código em issues** - crie um PR apropriado ao invés disso
-4. **Não submeta seu projeto inteiro** - contribua com melhorias específicas
-
-## Precisa de Ajuda?
-
-- 🐛 Reporte bugs usando o [template de bug report](https://github.com/SinapseAIinc/sinapse-ai/issues/new?template=bug_report.md)
-- 💡 Sugira features usando o [template de feature request](https://github.com/SinapseAIinc/sinapse-ai/issues/new?template=feature_request.md)
-- 📖 Leia as [Diretrizes de Contribuição](../CONTRIBUTING.md) completas
-
-## Exemplo: PRs Bons vs Ruins
-
-### 😀 Exemplo de PR Bom
-
-**Título**: "Corrigir link quebrado para guia de instalação"
-**Mudanças**: Um arquivo, uma linha alterada
-**Descrição**: "O link no README.md estava apontando para o arquivo errado. Atualizado para apontar para o guia de instalação correto."
-
-### 😞 Exemplo de PR Ruim
-
-**Título**: "Atualizações"
-**Mudanças**: 50 arquivos, codebase inteira reformatada
-**Descrição**: "Fiz algumas melhorias"
-
----
-
-**Lembre-se**: Estamos aqui para ajudar! Não tenha medo de fazer perguntas. Todo especialista já foi iniciante um dia.