sinapse-ai 7.7.11 → 8.0.0

package/squads/claude-code-mastery/agents/roadmap-sentinel.md

@@ -753,14 +753,14 @@ Type `*help` to see all commands, or `*guide` for comprehensive usage instructio
 
 **I collaborate with:**
 
-- **@devops (Gage):** For applying version upgrades, managing MCP infrastructure, and deploying configuration changes
-- **@architect (Aria):** For evaluating architectural impact of new Claude Code features
+- **@devops (Pipeline):** For applying version upgrades, managing MCP infrastructure, and deploying configuration changes
+- **@architect (Stratum):** For evaluating architectural impact of new Claude Code features
 - **@config-engineer (Sigil):** For settings.json, CLAUDE.md, and .claude/rules/ optimization when adopting new features
-- **@developer (Dex):** Receives adoption strategies and plan-first workflows for implementation
+- **@developer (Pixel):** Receives adoption strategies and plan-first workflows for implementation
 
 **I delegate to:**
 
-- **@devops (Gage):** For executing `claude update`, applying managed settings, and infrastructure changes
+- **@devops (Pipeline):** For executing `claude update`, applying managed settings, and infrastructure changes
 - **@config-engineer (Sigil):** For implementing configuration changes recommended by migration guides
 
 **When to use others:**
@@ -921,10 +921,10 @@ Run `*sdk-guide` for comprehensive SDK documentation.
 
 ### Related Agents
 
-- **@devops (Gage)** - Executes version upgrades and infrastructure changes
-- **@architect (Aria)** - Evaluates architectural impact of new features
+- **@devops (Pipeline)** - Executes version upgrades and infrastructure changes
+- **@architect (Stratum)** - Evaluates architectural impact of new features
 - **@config-engineer (Sigil)** - Implements configuration changes for feature adoption
-- **@developer (Dex)** - Primary consumer of plan-first workflows and adoption strategies
+- **@developer (Pixel)** - Primary consumer of plan-first workflows and adoption strategies
 
 ---
 ---

package/squads/claude-code-mastery/agents/skill-craftsman.md

@@ -1104,15 +1104,15 @@ Type `*help` to see all commands, or `*guide` for detailed usage.
 
 **I collaborate with:**
 
-- **@developer (Dex):** Implements application code that skills reference
-- **@architect (Aria):** Provides system architecture context for skill design
-- **@quality-gate (Quinn):** Reviews skill quality and validates trigger accuracy
-- **@devops (Gage):** Handles plugin publishing and marketplace deployment
+- **@developer (Pixel):** Implements application code that skills reference
+- **@architect (Stratum):** Provides system architecture context for skill design
+- **@quality-gate (Litmus):** Reviews skill quality and validates trigger accuracy
+- **@devops (Pipeline):** Handles plugin publishing and marketplace deployment
 
 **I delegate to:**
 
-- **@devops (Gage):** For git push, PR creation, and plugin marketplace deployment
-- **@developer (Dex):** For implementation of application features beyond skill scope
+- **@devops (Pipeline):** For git push, PR creation, and plugin marketplace deployment
+- **@developer (Pixel):** For implementation of application features beyond skill scope
 
 **When to use others:**
 
@@ -1239,10 +1239,10 @@ Type `*help` to see all commands, or `*guide` for detailed usage.
 
 ### Related Agents
 
-- **@developer (Dex)** - Application code implementation
-- **@architect (Aria)** - System architecture
-- **@devops (Gage)** - Publishing and deployment
-- **@quality-gate (Quinn)** - Quality review
+- **@developer (Pixel)** - Application code implementation
+- **@architect (Stratum)** - System architecture
+- **@devops (Pipeline)** - Publishing and deployment
+- **@quality-gate (Litmus)** - Quality review
 - **@squad-creator (Craft)** - SINAPSE squad creation (complementary)
 
 ---

package/squads/claude-code-mastery/agents/swarm-orqx.md

@@ -937,13 +937,13 @@ Type `*guide` for comprehensive usage instructions.
 
 **I collaborate with:**
 
-- **@architect (Aria):** Validates multi-agent topology decisions and system design alignment
-- **@developer (Dex):** Receives subagent definitions and team configurations for implementation use
-- **@quality-gate (Quinn):** Reviews agent team findings through QA gate validation
+- **@architect (Stratum):** Validates multi-agent topology decisions and system design alignment
+- **@developer (Pixel):** Receives subagent definitions and team configurations for implementation use
+- **@quality-gate (Litmus):** Reviews agent team findings through QA gate validation
 
 **I delegate to:**
 
-- **@devops (Gage):** For git push, PR creation, and CI/CD integration of agent configurations
+- **@devops (Pipeline):** For git push, PR creation, and CI/CD integration of agent configurations
 
 **When to use others:**
 

package/squads/squad-brand/agents/brand-creative-engineer.md

@@ -176,7 +176,7 @@ integration:
     - agent: "brand-auditor (Sentinel)"
       when: "Assets criados, precisam de validacao de coerencia"
       context_passed: "lista de assets gerados, guidelines utilizadas, API usada"
-    - agent: "@developer (Dex)"
+    - agent: "@developer (Pixel)"
       when: "Asset SVG ou web template precisa ser integrado em codebase"
       context_passed: "arquivo SVG/HTML/CSS, contexto de uso, responsividade"
   receives_from:

package/squads/squad-brand/agents/brand-motion-vfx.md

@@ -126,7 +126,7 @@ commands:
 
 integration:
   delegates_to:
-    - agent: "@developer (Dex)"
+    - agent: "@developer (Pixel)"
       when: "Motion specs prontas para implementacao"
       context_passed: "easing curves, durations, codigo CSS/JS, Lottie files"
     - agent: "brand-auditor (Sentinel)"

package/squads/squad-brand/agents/brand-sonic-designer.md

@@ -159,7 +159,7 @@ integration:
     - agent: "brand-auditor (Sentinel)"
       when: "Sound system criado, precisa de validacao"
       context_passed: "audio files, sonic DNA docs, sound system specs"
-    - agent: "@developer (Dex)"
+    - agent: "@developer (Pixel)"
       when: "Notification sounds prontos para integracao em app"
       context_passed: "audio files, formato, evento de trigger, specs de implementacao"
   receives_from:

package/squads/squad-brand/agents/brand-system-architect.md

@@ -115,10 +115,10 @@ knowledge_bases:
 
 integration:
   delegates_to:
-    - agent: "@architect (Aria)"
+    - agent: "@architect (Stratum)"
       when: "Design system precisa de decisao arquitetural sobre tech stack"
       context_passed: "tokens, componentes, formato de export desejado"
-    - agent: "@developer (Dex)"
+    - agent: "@developer (Pixel)"
       when: "Design system pronto para implementacao"
       context_passed: "tokens CSS, componentes documentados, grid specs"
     - agent: "brand-auditor (Sentinel)"

package/docs/FEATURE_PROCESS.md

@@ -1,93 +0,0 @@
-# Feature Request Process
-
-> 🌐 **EN** | [PT](./pt/FEATURE_PROCESS.md) | [ES](./es/FEATURE_PROCESS.md)
-
----
-
-This document explains how to propose new features for SINAPSE.
-
-## Quick Ideas
-
-For quick ideas or small improvements:
-
-1. Open a Discussion in the "Ideas" category
-2. Describe the problem and proposed solution
-3. Community and maintainers will discuss
-4. If there's interest, it may be promoted to RFC
-
-## RFC Process (For Significant Features)
-
-For larger features that require design decisions:
-
-### When to Write an RFC
-
-- New major features
-- Breaking changes
-- Significant architectural changes
-- Changes affecting many users
-
-### RFC Lifecycle
-
-1. **Draft**: Author writes RFC using our [RFC Template](../.github/RFC_TEMPLATE.md)
-2. **Under Review**: 2-week comment period
-3. **Decision**: Maintainers accept/reject
-4. **Implementation**: If accepted, implementation begins
-
-### Criteria for Acceptance
-
-- Aligns with project vision
-- Technically feasible
-- Has clear implementation path
-- Community demand demonstrated
-- Maintainable long-term
-
-## Voting
-
-- Use :+1: reactions to show support
-- Top-voted ideas are prioritized
-- Maintainers have final decision
-
-## Timeline
-
-- Ideas: No fixed timeline
-- RFCs: 2-week minimum review period
-- Implementation: Based on roadmap capacity
-
-## From Idea to Implementation
-
-```text
-Community Idea (Discussion)
-        │
-        │ [Approved by maintainers]
-        ▼
-Internal Backlog Item
-        │
-        │ [Prioritized by Product Owner]
-        ▼
-Sprint Planning
-        │
-        │ [Implemented by Development Team]
-        ▼
-Release (credited in CHANGELOG.md)
-```
-
-### Who Can Add to Backlog?
-
-The Product Owner (@product-lead) is the sole authority for adding items to the internal backlog.
-This ensures proper prioritization and alignment with project goals.
-
-### Contributor Credit
-
-Contributors whose ideas are implemented will be credited in:
-
-- The CHANGELOG.md release notes
-- The PR that implements the feature
-- Our contributors page (if applicable)
-
-## Questions?
-
-Ask in GitHub Discussions or Discord.
-
----
-
-_See also: [Community Handbook](../COMMUNITY.md) | [Contributing Guide](../CONTRIBUTING.md)_

package/docs/GUIDING-PRINCIPLES.md

@@ -1,95 +0,0 @@
-# SINAPSE Method Guiding Principles
-
-> 🌐 **EN** | [PT](./pt/GUIDING-PRINCIPLES.md) | [ES](./es/GUIDING-PRINCIPLES.md)
-
----
-
-The SINAPSE Method is a natural language framework for AI-assisted software development. These principles ensure contributions maintain the method's effectiveness.
-
-## Core Principles
-
-### 1. Dev Agents Must Be Lean
-
-- **Minimize dev agent dependencies**: Development agents that work in IDEs must have minimal context overhead
-- **Save context for code**: Every line counts - dev agents should focus on coding, not documentation
-- **Web agents can be larger**: Planning agents (PRD Writer, Architect) used in web UI can have more complex tasks and dependencies
-- **Small files, loaded on demand**: Multiple small, focused files are better than large files with many branches
-
-### 2. Natural Language First
-
-- **Everything is markdown**: Agents, tasks, templates - all written in plain English
-- **No code in core**: The framework itself contains no programming code, only natural language instructions
-- **Self-contained templates**: Templates are defined as YAML files with structured sections that include metadata, workflow configuration, and detailed instructions for content generation
-
-### 3. Agent and Task Design
-
-- **Agents define roles**: Each agent is a persona with specific expertise (e.g., Frontend Developer, API Developer)
-- **Tasks are procedures**: Step-by-step instructions an agent follows to complete work
-- **Templates are outputs**: Structured documents with embedded instructions for generation
-- **Dependencies matter**: Explicitly declare only what's needed
-
-## Practical Guidelines
-
-### When to Add to Core
-
-- Universal software development needs only
-- Doesn't bloat dev agent contexts
-- Follows existing agent/task/template patterns
-
-### When to Create Squads
-
-- Domain-specific needs beyond software development
-- Non-technical domains (business, wellness, education, creative)
-- Specialized technical domains (games, infrastructure, mobile)
-- Heavy documentation or knowledge bases
-- Anything that would bloat core agents
-
-See [Squads Overview](./guides/squads-overview.md) for detailed examples and ideas.
-
-### Agent Design Rules
-
-1. **Web/Planning Agents**: Can have richer context, multiple tasks, extensive templates
-2. **Dev Agents**: Minimal dependencies, focused on code generation, lean task sets
-3. **All Agents**: Clear persona, specific expertise, well-defined capabilities
-
-### Task Writing Rules
-
-1. Write clear step-by-step procedures
-2. Use markdown formatting for readability
-3. Keep dev agent tasks focused and concise
-4. Planning tasks can be more elaborate
-5. **Prefer multiple small tasks over one large branching task**
-   - Instead of one task with many conditional paths
-   - Create multiple focused tasks the agent can choose from
-   - This keeps context overhead minimal
-6. **Reuse common tasks** - Don't create new document creation tasks
-   - Use the existing `create-doc` task
-   - Pass the appropriate YAML template with structured sections
-   - This maintains consistency and reduces duplication
-
-### Template Rules
-
-Templates follow the [SINAPSE Document Template](../common/utils/sinapse-doc-template.md) specification using YAML format:
-
-1. **Structure**: Templates are defined in YAML with clear metadata, workflow configuration, and section hierarchy
-2. **Separation of Concerns**: Instructions for LLMs are in `instruction` fields, separate from content
-3. **Reusability**: Templates are agent-agnostic and can be used across different agents
-4. **Key Components**:
-   - `template` block for metadata (id, name, version, output settings)
-   - `workflow` block for interaction mode configuration
-   - `sections` array defining document structure with nested subsections
-   - Each section has `id`, `title`, and `instruction` fields
-5. **Advanced Features**:
-   - Variable substitution using `{{variable_name}}` syntax
-   - Conditional sections with `condition` field
-   - Repeatable sections with `repeatable: true`
-   - Agent permissions with `owner` and `editors` fields
-   - Examples arrays for guidance (never included in output)
-6. **Clean Output**: YAML structure ensures all processing logic stays separate from generated content
-
-## Remember
-
-- The power is in natural language orchestration, not code
-- Dev agents code, planning agents plan
-- Keep dev agents lean for maximum coding efficiency
-- Starter squads handle specialized domains