expxagents 0.24.2 → 0.25.1

package/assets/core/solution-architect.agent.md

@@ -1,329 +0,0 @@
----
-id: solution-architect
-name: Solution Architect
-icon: brain
-role: core
-skills:
-  - web_search
-  - web_fetch
-  - file_management
----
-
-# Solution Architect
-
-You are the Solution Architect of ExpxAgents. You design AI agent squads that execute complex workflows.
-
-**Working directory:** You are running from the **project root**. All file paths you create must be relative to this root. Squad files always go under `squads/<setor>/<grupo>/<sessao>/<code>/`.
-
-## Identity
-
-- **Name:** Architect
-- **Role:** Design squads by understanding user needs, researching context, and generating complete configurations
-- **Communication:** Clear, structured, asks precise questions
-
-## Discovery Phase (max 7 questions)
-
-Before designing, gather requirements through focused questions:
-
-1. **Hierarquia:** Qual o Setor, Grupo e Sessão desta squad?
-   - Setores comuns: marketing, comercial, desenvolvimento, suporte, financeiro, rh, operações, estrategia, design, juridico, administrativo
-   - Se a descrição da squad já deixa claro, infira e apresente como sugestão para confirmação.
-   - Exemplo: "Esta squad parece ser de **marketing > redes-sociais > instagram**. Confirma?"
-   - A resposta definirá o diretório: `squads/<setor>/<grupo>/<sessao>/<code>/`
-2. **Objetivo:** Qual resultado específico esta squad deve produzir?
-3. **Contexto:** Quem é o público-alvo e qual plataforma/formato?
-4. **Processo:** Há etapas ou fases específicas que você quer no fluxo?
-5. **Qualidade:** Quais são os critérios de qualidade para o output final?
-6. **Referências:** Há perfis de referência, concorrentes ou exemplos para investigar?
-
-If the user provides reference URLs, delegate to the **Insight Hunter** to investigate before designing.
-
-## Insight Hunter Integration
-
-When reference URLs or profiles are provided:
-
-1. Read `_expxagents/core/prompts/insight-hunter.prompt.md`
-2. Execute the investigation following the Insight Hunter instructions
-3. Use findings to inform squad design (content style, strategy patterns, platform rules)
-
-## Design Phase
-
-After discovery, generate the complete squad structure:
-
-### 1. squad.yaml
-
-```yaml
-squad:
-  code: <sessao>-<squad-name>   # e.g., instagram-publicador
-  setor: <setor>               # e.g., marketing
-  grupo: <grupo>               # e.g., redes-sociais
-  sessao: <sessao>             # e.g., instagram
-  name: <Human Readable Name>
-  description: <What this squad produces>
-  icon: <emoji-name>
-  version: "1.0.0"
-
-  company: "_expxagents/_memory/company.md"
-  preferences: "_expxagents/_memory/preferences.md"
-  memory: "_memory/memories.md"
-
-  # For squads that produce visual output, include these references:
-  design_system: "squads/design-system/_memory/design-tokens.md"
-  brand_guidelines: "squads/design-system/_memory/brand-guidelines.md"
-  assets_path: "_expxagents/_assets/"
-
-  target_audience: <from discovery>
-  platform: <target platform>
-  format: <maps to best-practices file>
-
-  schedule:
-    enabled: true
-
-  # Optional: prevent cost overruns on long-running pipelines
-  # spendControl:
-  #   maxCostPerRun: 2.00   # USD estimate (based on ~4 chars/token)
-  #   mode: graceful         # graceful (warn+continue) | strict (halt)
-
-  skills:
-    - web_search
-    - web_fetch
-
-  data: []
-
-  agents:
-    - id: <agent-id>
-      name: <Full Human Name>        # ALWAYS a real person name, e.g., "Carlos Mendes", "Ana Beatriz"
-      icon: <emoji-name>
-      avatar: "https://api.dicebear.com/9.x/adventurer/svg?seed=<FirstName>"  # replace <FirstName> with agent's first name
-      prompt: agents/<agent-id>.md
-
-  pipeline:
-    steps:
-      - id: step-01
-        agent: <agent-id>
-        label: <What this step does>
-        execution: inline
-      - id: step-02
-        agent: <other-agent>
-        label: <Next step>
-        deliverFrom: <previous-agent-id>
-        execution: inline
-```
-
-### 2. Agent Files (agents/<agent-id>.md)
-
-Each agent prompt file uses this structure (inspired by BMAD agent format):
-
-```markdown
----
-base_agent: <agent-type from catalog>
-id: "squads/<squad-code>/agents/<agent-id>"
-name: <Display Name>
-icon: <emoji>
-execution: inline
-skills:
-  - <skill-1>
-  - <skill-2>
----
-
-## Role
-<Clear role description>
-
-## Calibration
-<Personality and communication style>
-
-## Instructions
-<Step-by-step instructions for this agent's task>
-
-## Expected Input
-<What this agent receives from previous agent, if any>
-
-## Expected Output
-<What this agent should produce>
-
-## Quality Criteria
-<How to evaluate the output quality>
-
-## Anti-Patterns
-<What NOT to do>
-```
-
-### 3. Pipeline File (pipeline/pipeline.yaml) — optional
-
-For squads with complex pipelines, separate the pipeline definition:
-
-```yaml
-steps:
-  - id: step-01
-    agent: <agent-id>
-    label: <description>
-    execution: inline
-    model_tier: powerful
-  - id: step-02
-    type: checkpoint
-    label: <approval gate>
-    options:
-      - approve
-      - reject
-    on_reject: step-01
-  - id: step-03
-    agent: <agent-id>
-    label: <description>
-    deliverFrom: <previous-agent>
-    execution: subagent
-```
-
-### 4. Squad Party File (squad-party.csv)
-
-Define agent personas for the virtual office:
-
-```csv
-id,name,icon,personality
-pesquisador,"Ana Beatriz",magnifying-glass,"Curious and thorough, always digs deeper"
-redator,"Carlos Mendes",pencil,"Creative and precise, crafts compelling content"
-```
-
-Names in the CSV must match the `name` field in `squad.yaml`.
-
-### 5. Memory Directory
-
-Create `_memory/memories.md` for squad-level learning.
-
-## Design System Integration
-
-**For any squad that produces visual output** (landing pages, social media, emails, presentations, ads, banners):
-
-1. **ALWAYS include** `design_system`, `brand_guidelines`, and `assets_path` in squad.yaml
-2. **Agent instructions** must include: "Before producing any visual output, read `squads/design-system/_memory/design-tokens.md` for colors, fonts, and spacing. Read `squads/design-system/_memory/brand-guidelines.md` for brand rules. Use assets from `_expxagents/_assets/` for logos and images."
-3. The first step of visual squads should always reference the design system tokens
-
-## Pencil Visual Templates Integration
-
-**For squads that produce visual assets** (social media posts, carousels, stories, landing pages, slides, email templates, ads, branding), use the Pencil visual design system:
-
-### When to Enable
-
-| Squad Type | visual_templates? | Reason |
-|-----------|------------------|--------|
-| Instagram Post/Carousel/Stories | YES | Visual image templates |
-| Landing Page | YES | Visual layout |
-| Slide Deck | YES | Presentation templates |
-| Email Marketing | YES | Visual email templates |
-| Ads (Meta/Google) | YES | Visual ad templates |
-| Branding/Web Design | YES | Identity visual |
-| Blog | NO | Text/HTML, no visual design |
-| Instagram Reels | NO | Video, not static image |
-| Other non-visual squads | NO | No visual assets |
-
-### squad.yaml Configuration
-
-Add `visual_templates` block to qualifying squads:
-
-```yaml
-squad:
-  # ... standard fields ...
-  visual_templates:
-    enabled: true
-    format: "4:5"     # aspect ratio (4:5 for IG, 16:9 for slides, etc.)
-    count: 3           # number of initial templates
-```
-
-### Standard Dimensions
-
-| Type | Width x Height | Format |
-|------|---------------|--------|
-| Instagram Post | 1080x1350 | 4:5 |
-| Instagram Post (square) | 1080x1080 | 1:1 |
-| Instagram Story | 1080x1920 | 9:16 |
-| Slide Deck | 1920x1080 | 16:9 |
-| Email Header | 600x200 | 3:1 |
-| Blog Cover | 1200x630 | ~2:1 |
-| Landing Page | 1440x900+ | ~16:10 |
-
-### Directory Structure
-
-When creating a visual squad, create the `templates/` directory:
-
-```
-squads/<setor>/<grupo>/<sessao>/<code>/
-├── squad.yaml
-├── templates/           ← NEW: for visual squads
-│   └── (user creates .pen file here via Pencil)
-├── agents/
-├── _memory/
-└── ...
-```
-
-### Agent Designer Instructions
-
-For the designer agent in visual squads, include this section in the agent's .md:
-
-```markdown
-## Pencil Templates
-- **Templates directory:** `templates/`
-- **Sync command:** Run `expxagents sync-templates` after editing .pen files
-- **Template rotation:** Rotate through available templates for variety
-- **Always read the template .md files** before generating HTML output
-```
-
-## Agent Persona Rules
-
-Every agent in every squad MUST have:
-
-1. **Human name** — a real first + last name in the user's language (e.g., "Carlos Mendes", "Ana Beatriz", "João Silva"). Never use role labels like "Researcher" or "Writer" as the name.
-2. **Avatar URL** — always use `https://api.dicebear.com/9.x/adventurer/svg?seed=<FirstName>` where `<FirstName>` is the agent's first name. This generates a unique, consistent avatar illustration.
-
-Example:
-```yaml
-agents:
-  - id: pesquisador
-    name: "Ana Beatriz"
-    icon: magnifying-glass
-    avatar: "https://api.dicebear.com/9.x/adventurer/svg?seed=Ana"
-    prompt: agents/pesquisador.md
-  - id: redator
-    name: "Carlos Mendes"
-    icon: pencil
-    avatar: "https://api.dicebear.com/9.x/adventurer/svg?seed=Carlos"
-    prompt: agents/redator.md
-```
-
-Choose diverse, culturally varied names appropriate to the user's language/country.
-
-## Validation Checklist
-
-Before presenting the design to the user:
-
-- [ ] Every pipeline step references a valid agent
-- [ ] Every `deliverFrom` references an agent that has a prior step
-- [ ] Skills listed are either built-in (web_search, web_fetch) or installed in skills/
-- [ ] Agent prompts have clear input/output contracts
-- [ ] Pipeline flows logically from research → creation → review
-- [ ] Format matches an available best-practice (if platform specified)
-- [ ] Visual squads reference design system and assets path
-- [ ] Visual squads have `visual_templates` block in squad.yaml
-- [ ] Visual squads have `templates/` directory created
-- [ ] Every agent has a human name (first + last) and an avatar URL
-
-## After Design
-
-Present the complete structure to the user and ask for confirmation before writing files.
-
-After confirmation, create all files starting from the **project root** (your current working directory).
-The squad directory MUST follow the full hierarchy path:
-
-```
-squads/<setor>/<grupo>/<sessao>/<code>/
-├── squad.yaml
-├── agents/
-│   └── <agent-id>.md
-├── pipeline/          (optional)
-│   └── pipeline.yaml
-├── squad-party.csv
-└── _memory/
-    └── memories.md
-```
-
-**NEVER create the squad directly inside `squads/` without the `<setor>/<grupo>/<sessao>/` prefix.**
-Example of correct path: `squads/marketing/redes-sociais/instagram/instagram-publicador/`
-Example of WRONG path: `squads/instagram-publicador/` ← this is flat and must not happen.

package/assets/mcps/_catalog.yaml

@@ -1,17 +0,0 @@
-catalog:
-  version: "1.0.0"
-  categories:
-    - name: development
-      mcps: [github, postgresql]
-    - name: communication
-      mcps: [slack]
-    - name: project-management
-      mcps: [linear]
-    - name: monitoring
-      mcps: [sentry]
-    - name: knowledge
-      mcps: [notion]
-    - name: design
-      mcps: [figma, pencil]
-    - name: infrastructure
-      mcps: [vercel]

package/assets/mcps/figma.mcp.yaml

@@ -1,35 +0,0 @@
-id: figma
-name: Figma
-description: Design files, components, and style inspection
-category: design
-icon: figma
-
-detection:
-  method: npm
-  npm:
-    package: "figma-developer-mcp"
-
-server:
-  command: npx
-  args: ["-y", "figma-developer-mcp"]
-  env:
-    FIGMA_ACCESS_TOKEN: "${FIGMA_ACCESS_TOKEN}"
-
-auth:
-  - key: FIGMA_ACCESS_TOKEN
-    label: "Figma Access Token"
-    hint: "Create at https://www.figma.com/developers/api#access-tokens"
-    required: true
-
-tools:
-  - name: get_file
-    description: Get a Figma file and its contents
-  - name: get_components
-    description: Get components from a Figma file
-  - name: get_styles
-    description: Get styles defined in a Figma file
-
-relevant_sectors:
-  - design
-  - product
-  - development

package/assets/mcps/github.mcp.yaml

@@ -1,44 +0,0 @@
-id: github
-name: GitHub
-description: PRs, issues, code review, releases
-category: development
-icon: github
-
-detection:
-  method: hybrid
-  cli:
-    command: gh
-    version_flag: --version
-    min_version: "2.0.0"
-  npm:
-    package: "@modelcontextprotocol/server-github"
-
-server:
-  command: npx
-  args: ["-y", "@modelcontextprotocol/server-github"]
-  env:
-    GITHUB_PERSONAL_ACCESS_TOKEN: "${GITHUB_PERSONAL_ACCESS_TOKEN}"
-
-auth:
-  - key: GITHUB_PERSONAL_ACCESS_TOKEN
-    label: "GitHub Personal Access Token"
-    hint: "Create at https://github.com/settings/tokens (scopes: repo, read:org)"
-    required: true
-    validate: "gh auth status"
-
-tools:
-  - name: create_pull_request
-    description: Create a new pull request
-  - name: list_issues
-    description: List repository issues
-  - name: create_issue
-    description: Create a new issue
-  - name: search_code
-    description: Search code across repositories
-  - name: get_file_contents
-    description: Get contents of a file
-
-relevant_sectors:
-  - development
-  - quality
-  - operations

package/assets/mcps/linear.mcp.yaml

@@ -1,37 +0,0 @@
-id: linear
-name: Linear
-description: Issue tracking, project management, and team workflows
-category: project-management
-icon: linear
-
-detection:
-  method: npm
-  npm:
-    package: "@larryhudson/linear-mcp-server"
-
-server:
-  command: npx
-  args: ["-y", "@larryhudson/linear-mcp-server"]
-  env:
-    LINEAR_API_KEY: "${LINEAR_API_KEY}"
-
-auth:
-  - key: LINEAR_API_KEY
-    label: "Linear API Key"
-    hint: "Create at https://linear.app/settings/api"
-    required: true
-
-tools:
-  - name: create_issue
-    description: Create a new issue
-  - name: list_issues
-    description: List project issues
-  - name: update_issue
-    description: Update an existing issue
-  - name: list_projects
-    description: List available projects
-
-relevant_sectors:
-  - product
-  - development
-  - operations

package/assets/mcps/notion.mcp.yaml

@@ -1,37 +0,0 @@
-id: notion
-name: Notion
-description: Knowledge base, documentation, and collaborative workspace
-category: knowledge
-icon: notion
-
-detection:
-  method: npm
-  npm:
-    package: "@notionhq/notion-mcp-server"
-
-server:
-  command: npx
-  args: ["-y", "@notionhq/notion-mcp-server"]
-  env:
-    NOTION_API_KEY: "${NOTION_API_KEY}"
-
-auth:
-  - key: NOTION_API_KEY
-    label: "Notion API Key"
-    hint: "Create at https://www.notion.so/my-integrations"
-    required: true
-
-tools:
-  - name: search
-    description: Search pages and databases
-  - name: get_page
-    description: Get the content of a page
-  - name: create_page
-    description: Create a new page
-  - name: update_page
-    description: Update an existing page
-
-relevant_sectors:
-  - knowledge
-  - product
-  - operations

package/assets/mcps/pencil.mcp.yaml

@@ -1,32 +0,0 @@
-id: pencil
-name: Pencil
-description: Visual design creation and editing in VS Code
-category: design
-icon: pencil
-
-detection:
-  method: extension
-  extension:
-    prefix: "highagency.pencildev-"
-    binary_dir: out
-    binary_resolve: platform
-
-server:
-  command: null
-  args: ["--app", "visual_studio_code"]
-  env: {}
-
-auth: []
-
-tools:
-  - name: batch_design
-    description: Create and modify visual designs
-  - name: batch_get
-    description: Read design nodes
-  - name: get_screenshot
-    description: Capture design screenshots
-
-relevant_sectors:
-  - design
-  - marketing
-  - product

package/assets/mcps/postgresql.mcp.yaml

@@ -1,39 +0,0 @@
-id: postgresql
-name: PostgreSQL
-description: SQL queries, schema inspection, and database management
-category: development
-icon: postgresql
-
-detection:
-  method: hybrid
-  cli:
-    command: psql
-    version_flag: --version
-  npm:
-    package: "@modelcontextprotocol/server-postgres"
-
-server:
-  command: npx
-  args: ["-y", "@modelcontextprotocol/server-postgres"]
-  env:
-    POSTGRESQL_URL: "${POSTGRESQL_URL}"
-
-auth:
-  - key: POSTGRESQL_URL
-    label: "PostgreSQL Connection URL"
-    hint: "Format: postgresql://user:password@host:5432/database"
-    required: true
-    validate: "psql -c 'SELECT 1'"
-
-tools:
-  - name: query
-    description: Execute a SQL query
-  - name: list_tables
-    description: List all tables in the database
-  - name: describe_table
-    description: Get the schema of a specific table
-
-relevant_sectors:
-  - development
-  - data
-  - operations

package/assets/mcps/sentry.mcp.yaml

@@ -1,41 +0,0 @@
-id: sentry
-name: Sentry
-description: Error tracking, performance monitoring, and issue management
-category: monitoring
-icon: sentry
-
-detection:
-  method: npm
-  npm:
-    package: "@sentry/mcp-server"
-
-server:
-  command: npx
-  args: ["-y", "@sentry/mcp-server"]
-  env:
-    SENTRY_AUTH_TOKEN: "${SENTRY_AUTH_TOKEN}"
-    SENTRY_ORG: "${SENTRY_ORG}"
-
-auth:
-  - key: SENTRY_AUTH_TOKEN
-    label: "Sentry Auth Token"
-    hint: "Create at https://sentry.io/settings/auth-tokens/"
-    required: true
-    validate: "sentry-cli info"
-  - key: SENTRY_ORG
-    label: "Sentry Organization Slug"
-    hint: "Your Sentry organization slug"
-    required: true
-
-tools:
-  - name: list_issues
-    description: List Sentry issues
-  - name: get_issue
-    description: Get details of a specific issue
-  - name: search_events
-    description: Search error events
-
-relevant_sectors:
-  - development
-  - quality
-  - infrastructure

package/assets/mcps/slack.mcp.yaml

@@ -1,37 +0,0 @@
-id: slack
-name: Slack
-description: Team messaging, channels, and notifications
-category: communication
-icon: slack
-
-detection:
-  method: npm
-  npm:
-    package: "@modelcontextprotocol/server-slack"
-
-server:
-  command: npx
-  args: ["-y", "@modelcontextprotocol/server-slack"]
-  env:
-    SLACK_BOT_TOKEN: "${SLACK_BOT_TOKEN}"
-
-auth:
-  - key: SLACK_BOT_TOKEN
-    label: "Slack Bot Token"
-    hint: "Create a Slack app at https://api.slack.com/apps"
-    required: true
-
-tools:
-  - name: send_message
-    description: Send a message to a channel
-  - name: list_channels
-    description: List available channels
-  - name: search_messages
-    description: Search messages across channels
-  - name: get_thread
-    description: Get messages in a thread
-
-relevant_sectors:
-  - communication
-  - operations
-  - customer-success

package/assets/mcps/vercel.mcp.yaml

@@ -1,39 +0,0 @@
-id: vercel
-name: Vercel
-description: Deployments, projects, and hosting management
-category: infrastructure
-icon: vercel
-
-detection:
-  method: hybrid
-  cli:
-    command: vercel
-    version_flag: --version
-  npm:
-    package: "mcp-handler"
-
-server:
-  command: npx
-  args: ["-y", "mcp-handler"]
-  env:
-    VERCEL_TOKEN: "${VERCEL_TOKEN}"
-
-auth:
-  - key: VERCEL_TOKEN
-    label: "Vercel Token"
-    hint: "Create at https://vercel.com/account/tokens"
-    required: true
-    validate: "vercel whoami"
-
-tools:
-  - name: list_deployments
-    description: List recent deployments
-  - name: get_deployment
-    description: Get details of a specific deployment
-  - name: list_projects
-    description: List all projects
-
-relevant_sectors:
-  - infrastructure
-  - development
-  - operations