Synkra AIOX Core Framework

The @architect agent (named Aria, the Visionary) is responsible for high-level system design, impact analysis, and documentation. It operates with a Read-only Git restriction: it cannot push code directly; instead, it delegates push operations to the @devops agent.

Key capabilities include:

• Architecture Design: Creating fullstack, backend, frontend, or brownfield architectures.
• Analysis: Assessing complexity, researching requirements, and analyzing impact.
• Documentation: Generating project documentation, executing checklists, and creating docs.
• Collaboration: Works alongside @pm, @ux-design-expert, @db-sage, @devops, and @analyst.
• External Tool Integration: Uses exa, context7, git, supabase-cli, railway-cli, and coderabbit.

The @data-engineer (Dara) agent serves as the Database Architect & Operations Engineer within the AIOX ecosystem. It is responsible for schema design, migrations, security (RLS), performance optimization, and DBA operations.

Core Principles:

• Correctness over speed: Prioritize accuracy before optimization.
• Versioned & Reversible: All changes must include snapshots and rollback scripts.
• Security by Default: Implementation of RLS, constraints, and triggers.
• Idempotency: Operations are designed to be safe to execute multiple times.
• Domain-Oriented Design: Modeling data based on business requirements and access patterns.

The @sm (River) agent acts as the technical Scrum Master within the AIOX ecosystem. Its primary responsibility is to prepare detailed, actionable user stories that developer agents can implement with minimal additional research.

Key Responsibilities:

• Creating and refining user stories.
• Managing epics and requirement breakdown.
• Facilitating sprint planning and agile process guidance.
• Preparing handoffs for developers.
• Managing local Git branches during development.

Communication Style: Empathetic, collaborative, and fluid (Archetype: Facilitator/Pisces).

The Greenfield Full-Stack Workflow is the primary AIOX workflow for building full-stack applications from concept to development. It supports both comprehensive planning for complex projects and rapid prototyping for simpler ones.

Supported Project Types

• web-app: Modern web applications
• saas: Software as a Service
• enterprise-app: Corporate applications
• prototype: Prototypes and POCs
• mvp: Minimum Viable Products

When to Use

Use this workflow for production-ready applications, multi-member team projects, complex functional requirements, projects requiring extensive documentation, or long-term maintenance applications.

The UX-Design Expert (Uma) is a hybrid agent designed for artificial intelligence orchestration in UX/UI workflows. It combines Sally's UX Principles (empathy, user research, user-centered design) with Brad Frost's System Principles (Atomic Design, design tokens, metrics, and ROI).

Key capabilities include:

• Conducting user research and creating personas.
• Creating wireframes and interaction flows.
• Auditing existing codebases for UI redundancies.
• Extracting and consolidating design tokens.
• Building atomic components (atoms, molecules, organisms).
• Ensuring WCAG AA/AAA accessibility.
• Calculating ROI and design system savings.

The AIOX Autonomous Development Engine (ADE) is an autonomous development system designed to transform vague requirements into functional code using structured pipelines and specialized agents.

Its core architecture consists of:

• Spec Pipeline: Converts ideas into executable specifications.
• Execution Engine: Executes subtasks with mandatory self-critique.
• Recovery System: Automatically recovers from failures.
• QA Evolution: Provides structured 10-phase reviews.
• Memory Layer: Learns and documents patterns and insights.

The @devops agent, also known as Gage, is the infrastructure and operations specialist within the AIOX framework. It is responsible for managing the Model Context Protocol (MCP) ecosystem, CI/CD pipelines, releases, repository maintenance, security audits, and project bootstrapping.

Critical Rule: All MCP infrastructure operations must be managed exclusively by the @devops agent. Other agents (such as Dev or Architect) are consumers of MCP, not administrators.

@analyst (Atlas) serves as the Researcher within the AIOX agent system. Its primary responsibilities include:

• Conducting research and analysis tasks.
• Gathering and synthesizing information.
• Providing data-driven insights to support decision-making.
• Supporting other agents by providing research capabilities.

The Brownfield UI/Frontend Enhancement Workflow (ID: brownfield-ui, Version: 1.0) is a structured process designed to improve existing frontend applications. It is used for modernizing legacy interfaces, migrating between frameworks (e.g., jQuery to React), performing design refreshes, or adding new features to an existing frontend codebase.

Key benefits include:

• Structured analysis of the existing system before making changes.
• Safe integration with legacy code.
• Quality validation at every stage.
• Complete documentation of architectural decisions.

The Product Manager (PM) agent, known as Morgan (ID: pm), is designed to manage the product lifecycle within AIOX. Its primary responsibilities include:

• Creating and managing Product Requirements Documents (PRDs) for both greenfield (new) and brownfield (existing) projects.
• Defining and structuring epics with integrated quality planning.
• Conducting strategic research and market analysis.
• Correcting project deviations during development.
• Fragmenting large documents into manageable parts.
• Collaborating with other agents (like @architect and @ux-expert) to ensure strategic alignment.

The Design System Build Quality Pipeline (Workflow ID: design-system-build-quality) is a post-migration workflow designed to ensure the quality and measurable value of a Design System. It sequentially executes build, documentation, accessibility auditing, and ROI calculation.

Supported Project Types

• design-system
• component-library
• pattern-library
• ui-migration

Recommended Usage Scenarios

• Mandatory: After Design System migration, new Pattern Library releases, and pre-production component validation.
• Recommended: Periodic quality audits (e.g., quarterly).
• As Needed: Generating metrics for stakeholders.