@defai.digital/automatosx 12.8.7 → 13.1.3

package/examples/teams/design.yaml

@@ -1,58 +0,0 @@
-# Design Team Configuration
-# UX/UI design and technical writing
-
-name: design
-displayName: "Design Team"
-description: "UX/UI design and technical writing"
-
-# Provider Configuration
-provider:
-  primary: gemini
-  fallback: claude
-  fallbackChain:
-    - gemini
-    - claude
-    - codex
-
-# Shared Abilities
-sharedAbilities:
-  - design-principles
-  - documentation
-  - user-research
-
-# Team Capabilities (v4.11.0 - Self-assessment for intelligent delegation)
-capabilities:
-  canDo:
-    - UX/UI design and prototyping
-    - User research and testing
-    - Visual design and branding
-    - Technical writing and documentation
-    - README and user guide writing
-    - Content creation and editing
-    - Documentation quality assessment
-    - Design system development
-    - Accessibility and usability review
-
-  shouldDelegate:
-    - Code implementation → coder (engineering team)
-    - Backend development → backend (engineering team)
-    - Frontend implementation → frontend (engineering team)
-    - Security audits → security (core team)
-    - Testing automation → quality (core team)
-    - Product strategy → product (design team)
-
-# Orchestration Defaults
-orchestration:
-  maxDelegationDepth: 2  # v4.11.0: Enforced limit
-  canWriteToShared: true
-  canReadWorkspaces:
-    - design
-    - writer
-    - product
-
-# Metadata
-metadata:
-  color: "#EC4899"
-  icon: "🎨"
-  priority: 4
-version: "1.0.0"

package/examples/teams/engineering.yaml

@@ -1,69 +0,0 @@
-# Engineering Team Configuration
-# Software engineers, data engineers, and infrastructure specialists
-
-name: engineering
-displayName: "Engineering Team"
-description: "Software engineers, data engineers, and infrastructure specialists"
-
-# Provider Configuration
-provider:
-  primary: codex
-  fallback: gemini
-  fallbackChain:
-    - codex
-    - gemini
-    - claude
-
-# Shared Abilities (all team members inherit these)
-sharedAbilities:
-  - our-coding-standards
-  - our-project-structure
-  - our-architecture-decisions
-  - code-generation
-  - refactoring
-  - testing
-
-# Team Capabilities (v4.11.0 - Self-assessment for intelligent delegation)
-capabilities:
-  canDo:
-    - Code implementation (TypeScript, Python, Go, Rust, etc.)
-    - Test-driven development (TDD)
-    - API design and implementation
-    - Bug fixing and debugging
-    - Performance optimization
-    - Architecture design
-    - Code refactoring
-    - Database design and optimization
-    - Infrastructure and DevOps automation
-    - CI/CD pipeline management
-
-  shouldDelegate:
-    - Documentation writing and review → writer (design team)
-    - User-facing content creation → writer (design team)
-    - README quality assessment → writer (design team)
-    - Product strategy and planning → product (design team)
-    - Business analysis → ceo (business team)
-    - Security audits (when specialized review needed) → security (core team)
-    - QA strategy and testing (when specialized review needed) → quality (core team)
-    - Code review (when independent review needed) → reviewer (core team)
-
-# Orchestration Defaults
-orchestration:
-  maxDelegationDepth: 2  # v4.11.0: Reduced from 3 to 2
-  canWriteToShared: true
-  canReadWorkspaces:
-    - backend
-    - frontend
-    - devops
-    - data
-    - data-pipeline
-    - security
-    - coder
-    - coder-lean
-
-# Metadata
-metadata:
-  color: "#3B82F6"
-  icon: "⚙️"
-  priority: 1
-version: "1.0.0"

package/examples/teams/research.yaml

@@ -1,56 +0,0 @@
-# Research Team Configuration
-# Research and feasibility analysis specialists
-
-name: research
-displayName: "Research Team"
-description: "Research, feasibility analysis, and evidence-driven decision making"
-
-# Provider Configuration
-provider:
-  primary: openai        # OpenAI for structured research and analysis
-  fallback: gemini-cli   # Gemini as secondary
-  fallbackChain:
-    - openai
-    - gemini-cli
-    - claude
-
-# Shared Abilities
-sharedAbilities:
-  - idea-evaluation
-  - logical-analysis
-  - feasibility-study
-  - risk-assessment
-  - literature-review
-
-# Team Capabilities
-capabilities:
-  canDo:
-    - Idea validation and evaluation
-    - Feasibility analysis (technical, operational, economic)
-    - Risk assessment and mitigation strategies
-    - Literature review and citation
-    - Long-form research reports
-    - Logical reasoning and assumption analysis
-    - Evidence-based recommendations
-
-  shouldDelegate:
-    - Technical implementation → backend (engineering team)
-    - Data analysis → data (leadership team)
-    - Design work → design (content team)
-    - Documentation → writer (content team)
-
-# Orchestration Defaults
-orchestration:
-  maxDelegationDepth: 0  # Researchers execute research themselves
-  canWriteToShared: true
-  canReadWorkspaces:
-    - backend
-    - frontend
-    - data
-
-# Metadata
-metadata:
-  color: "#10B981"
-  icon: "🔬"
-  priority: 4
-version: "1.0.0"

package/examples/use-cases/01-web-app-development.md

@@ -1,374 +0,0 @@
-# Use Case: Web Application Development
-
-Complete workflow for building a web application with AutomatosX.
-
-## Scenario
-
-Building a task management web app with user authentication, CRUD operations, and real-time updates.
-
-## Prerequisites
-
-```bash
-# Initialize project
-mkdir task-manager
-cd task-manager
-npm init -y
-
-# Initialize AutomatosX
-automatosx setup
-
-# Set up API keys
-automatosx config --set providers.claude.apiKey --value "sk-ant-..."
-```
-
-## Step 1: Project Planning
-
-```bash
-automatosx chat backend
-
-> "I want to build a task management web app with:
-  - User authentication (JWT)
-  - Task CRUD operations
-  - Real-time updates (WebSocket)
-  - RESTful API (Express.js)
-  - React frontend
-
-  Please help me plan the architecture and tech stack."
-
-# Agent will suggest:
-# - Project structure
-# - Technology choices
-# - API design
-# - Database schema
-# - Security considerations
-```
-
-## Step 2: Backend Setup
-
-### Generate Express.js Server
-
-```bash
-automatosx run backend "Create an Express.js server with:
-- TypeScript configuration
-- Basic middleware (cors, helmet, morgan)
-- Error handling
-- Environment variables setup"
-
-# Creates:
-# - src/server.ts
-# - src/config/env.ts
-# - src/middleware/errorHandler.ts
-# - tsconfig.json
-```
-
-### Database Schema
-
-```bash
-automatosx run backend "Create Prisma schema for:
-- User model (id, email, password, name, createdAt)
-- Task model (id, title, description, status, userId, createdAt, updatedAt)
-- Relationships between User and Tasks"
-
-# Creates:
-# - prisma/schema.prisma
-# - Migration files
-```
-
-### Authentication System
-
-```bash
-automatosx run backend "Implement JWT authentication with:
-- User registration endpoint
-- Login endpoint
-- Password hashing with bcrypt
-- JWT token generation
-- Auth middleware for protected routes"
-
-# Creates:
-# - src/controllers/auth.controller.ts
-# - src/middleware/auth.middleware.ts
-# - src/utils/jwt.ts
-# - src/routes/auth.routes.ts
-```
-
-## Step 3: API Development
-
-### Task CRUD Operations
-
-```bash
-automatosx run backend "Create RESTful API for tasks:
-- GET /api/tasks - List user's tasks
-- GET /api/tasks/:id - Get single task
-- POST /api/tasks - Create task
-- PUT /api/tasks/:id - Update task
-- DELETE /api/tasks/:id - Delete task
-
-Include:
-- Request validation
-- Error handling
-- Pagination for list endpoint"
-
-# Creates:
-# - src/controllers/tasks.controller.ts
-# - src/routes/tasks.routes.ts
-# - src/validators/task.validator.ts
-```
-
-## Step 4: Code Review
-
-```bash
-# Review authentication logic
-automatosx run quality "Review src/controllers/auth.controller.ts for:
-- Security vulnerabilities
-- Error handling
-- Best practices"
-
-# Review API endpoints
-automatosx run quality "Review src/routes/ directory for:
-- RESTful design
-- Validation
-- Error responses"
-```
-
-## Step 5: Testing
-
-### Unit Tests
-
-```bash
-automatosx run backend "Create unit tests for authentication controller using Jest:
-- Test user registration with valid data
-- Test registration with existing email
-- Test login with valid credentials
-- Test login with invalid credentials
-- Test JWT token generation"
-
-# Creates:
-# - src/controllers/__tests__/auth.controller.test.ts
-```
-
-### Integration Tests
-
-```bash
-automatosx run backend "Create integration tests for task API:
-- Test creating task (authenticated)
-- Test listing tasks (authenticated)
-- Test updating task (owner only)
-- Test deleting task (owner only)
-- Test 401 for unauthenticated requests"
-
-# Creates:
-# - src/routes/__tests__/tasks.routes.test.ts
-```
-
-## Step 6: Frontend Development
-
-### React Components
-
-```bash
-automatosx run backend "Create React components for task management:
-- TaskList component with pagination
-- TaskItem component with edit/delete actions
-- TaskForm component for create/edit
-- Include TypeScript types
-- Use React hooks (useState, useEffect)"
-
-# Creates:
-# - src/components/TaskList.tsx
-# - src/components/TaskItem.tsx
-# - src/components/TaskForm.tsx
-# - src/types/task.ts
-```
-
-### Authentication UI
-
-```bash
-automatosx run backend "Create authentication components:
-- LoginForm with email/password validation
-- RegisterForm with password confirmation
-- Protected route wrapper
-- Auth context for global state"
-
-# Creates:
-# - src/components/auth/LoginForm.tsx
-# - src/components/auth/RegisterForm.tsx
-# - src/contexts/AuthContext.tsx
-# - src/components/ProtectedRoute.tsx
-```
-
-## Step 7: WebSocket Integration
-
-```bash
-automatosx run backend "Add WebSocket support for real-time task updates:
-- Socket.io server setup
-- Emit events on task create/update/delete
-- Client-side socket connection
-- Auto-update UI on socket events"
-
-# Creates:
-# - src/socket/server.ts
-# - src/socket/client.ts
-# - Event handlers
-```
-
-## Step 8: Documentation
-
-```bash
-# API Documentation
-automatosx run writer "Create API documentation for all endpoints:
-- Authentication endpoints
-- Task endpoints
-- Request/response examples
-- Error codes
-- Use OpenAPI/Swagger format"
-
-# Creates:
-# - docs/api.md
-# - swagger.yaml
-
-# Setup Guide
-automatosx run writer "Create development setup guide including:
-- Prerequisites
-- Installation steps
-- Environment variables
-- Database setup
-- Running the app
-- Running tests"
-
-# Creates:
-# - docs/setup.md
-```
-
-## Step 9: Debugging
-
-```bash
-# If you encounter errors:
-automatosx run debugger "I'm getting this error when creating a task:
-Error: Cannot read property 'userId' of undefined
-at createTask (src/controllers/tasks.controller.ts:45)"
-
-# Agent will:
-# - Analyze the error
-# - Identify the root cause
-# - Suggest fixes
-# - Provide code corrections
-```
-
-## Step 10: Deployment Preparation
-
-```bash
-# Environment Configuration
-automatosx run backend "Create production-ready configuration:
-- Separate dev/prod configs
-- Docker Compose setup
-- Environment variables validation
-- Health check endpoint
-- Graceful shutdown"
-
-# Creates:
-# - docker-compose.yml
-# - Dockerfile
-# - .env.example
-# - src/health.ts
-
-# Deployment Guide
-automatosx run writer "Create deployment guide for:
-- Docker deployment
-- Environment setup
-- Database migrations
-- SSL/TLS configuration
-- Monitoring and logging"
-
-# Creates:
-# - docs/deployment.md
-```
-
-## Complete Project Structure
-
-After following this workflow, you'll have:
-
-```
-task-manager/
-├── src/
-│   ├── server.ts
-│   ├── config/
-│   ├── controllers/
-│   ├── middleware/
-│   ├── routes/
-│   ├── validators/
-│   ├── socket/
-│   ├── components/
-│   └── types/
-├── prisma/
-│   └── schema.prisma
-├── docs/
-│   ├── api.md
-│   ├── setup.md
-│   └── deployment.md
-├── tests/
-├── docker-compose.yml
-├── Dockerfile
-└── package.json
-```
-
-## Tips for Success
-
-1. **Start with Planning**: Always use assistant/chat mode to plan before coding
-2. **Incremental Development**: Build one feature at a time, test, then move on
-3. **Regular Reviews**: Review code after each major component
-4. **Documentation First**: Document as you build, not after
-5. **Use Memory**: AutomatosX remembers context across sessions
-6. **Iterate**: Don't expect perfect code first time, refine iteratively
-
-## Common Issues
-
-### Agent Gives Generic Code
-
-**Problem**: Generated code is too generic
-**Solution**: Provide more context and specific requirements
-
-```bash
-# Instead of:
-automatosx run backend "Create user model"
-
-# Do this:
-automatosx run backend "Create Prisma User model with:
-- UUID primary key
-- Email (unique, validated)
-- Password (hashed with bcrypt, min 8 chars)
-- Name (required)
-- Role (enum: user, admin)
-- CreatedAt, UpdatedAt timestamps
-- Soft delete support"
-```
-
-### Code Doesn't Match Project Style
-
-**Problem**: Generated code doesn't follow your conventions
-**Solution**: Create a custom agent with style guidelines
-
-```yaml
-# .automatosx/agents/project-coder.yaml
-name: project-coder
-systemPrompt: |
-  You are a code generator for this specific project.
-
-  Code Style:
-  - Use functional components (React)
-  - Async/await (no promises)
-  - Named exports (no default)
-  - 2 spaces indentation
-  - Single quotes
-  - Trailing commas
-
-  Follow these patterns exactly when generating code.
-```
-
-## Next Steps
-
-- Explore [API Design Use Case](./02-api-design.md)
-- Learn about [Code Migration](./03-code-migration.md)
-- See [Security Audit Workflow](./04-security-audit.md)
-
----
-
-**Questions?** Open an issue at [GitHub Issues](https://github.com/defai-digital/automatosx/issues) (use "question" label)

package/examples/workflows/analyst.yaml

@@ -1,60 +0,0 @@
-# Business Analyst Agent Template
-# Pre-configured for business analysis and product management
-# Team: Business
-# v5.0+
-
-name: "{{AGENT_NAME}}"
-displayName: "{{DISPLAY_NAME}}"
-team: business
-role: "{{ROLE | default: Business Analyst}}"
-description: "{{DESCRIPTION | default: Expert in business analysis, requirements gathering, and product strategy}}"
-
-# Business analysis abilities (business team shared abilities will be added automatically)
-abilities:
-  - requirements-analysis
-  - user-stories
-  - business-strategy
-  - market-research
-  # Add custom abilities here
-
-# Configuration
-temperature: 0.7  # Balanced for creative and analytical thinking
-maxTokens: 4000
-
-# Orchestration
-orchestration:
-  maxDelegationDepth: 2
-  canReadWorkspaces:
-    - product
-    - marketing
-    - design
-  canWriteToShared: true
-
-# System Prompt
-systemPrompt: |
-  You are {{DISPLAY_NAME}}, a {{ROLE | default: Business Analyst}}.
-
-  {{DESCRIPTION | default: You are an expert business analyst with strong skills in requirements gathering, stakeholder management, and product strategy.}}
-
-  Your expertise includes:
-  - Requirements elicitation and documentation
-  - User story creation and backlog management
-  - Business process modeling
-  - Market research and competitive analysis
-  - ROI analysis and business case development
-  - Stakeholder communication and alignment
-
-  ## Multi-agent collaboration:
-  - Delegate design tasks to UX/UI designers
-  - Delegate technical feasibility to engineering team
-  - Delegate market research to marketing specialists
-  - Delegate data analysis to data analysts
-
-  ## Approach:
-  1. Understand business objectives and stakeholder needs
-  2. Gather and analyze requirements
-  3. Document clear and actionable specifications
-  4. Validate with stakeholders
-  5. Track and measure outcomes
-
-  Communication style: Clear, business-focused, and stakeholder-oriented

package/examples/workflows/assistant.yaml

@@ -1,48 +0,0 @@
-# Assistant Agent - Alex
-# General purpose AI assistant for everyday tasks
-
-name: assistant
-displayName: Alex
-role: General Assistant
-description: |
-  A versatile AI assistant for general purpose tasks, questions, and conversations.
-
-  ⚠️ TEMPLATE ROLE NOTICE (v5.0.11+):
-  This is a GENERAL-PURPOSE agent template for temporary use.
-  - Only create if you need a general assistant for tasks outside specialized domains
-  - Avoid using alongside specialized agents to prevent delegation cycles
-  - This agent was moved to templates to prevent conflicts with domain specialists
-
-# Provider preference
-provider: openai
-fallbackProvider: claude-code
-
-# Abilities
-abilities:
-  - problem-solving
-  - task-planning
-  - technical-writing
-  - content-creation
-
-# v5.0.11: Removed temperature/maxTokens - let provider CLIs use optimized defaults
-
-# System prompt
-systemPrompt: |
-  You are a helpful, friendly, and knowledgeable AI assistant.
-
-  Your role is to:
-  - Answer questions accurately and concisely
-  - Help users solve problems
-  - Provide explanations and guidance
-  - Assist with planning and organization
-
-  Always:
-  - Be clear and concise
-  - Ask clarifying questions when needed
-  - Admit when you don't know something
-  - Provide actionable advice
-
-  Communication style:
-  - Friendly but professional
-  - Patient and understanding
-  - Focused on helping the user succeed

package/examples/workflows/basic-agent.yaml

@@ -1,28 +0,0 @@
-# Basic Agent Template
-# Minimal configuration for creating a custom agent
-# v5.0+
-
-name: "{{AGENT_NAME}}"
-displayName: "{{DISPLAY_NAME}}"
-team: {{TEAM | default: core}}
-role: "{{ROLE | default: AI Assistant}}"
-description: "{{DESCRIPTION | default: A helpful AI assistant}}"
-
-# Abilities (add custom abilities here)
-abilities:
-  - general-knowledge
-  # Add more abilities as needed
-
-# System Prompt
-systemPrompt: |
-  You are {{DISPLAY_NAME}}, a {{ROLE | default: AI Assistant}}.
-
-  {{DESCRIPTION | default: You are a helpful AI assistant ready to assist with various tasks.}}
-
-  Your approach:
-  - Listen carefully to understand the user's needs
-  - Provide clear and concise responses
-  - Ask clarifying questions when needed
-  - Be professional and helpful
-
-  Communication style: Clear, friendly, and professional