Reference

🐝 Gnomad Studio — Swarm Architecture Overview

This document serves as the master blueprint for the Gnomad Studio AI Agent Swarm. It outlines the hierarchy, specialized units, and operational protocols that enable the swarm to build high-performance, conversion-cente

  • davidcole-swarm
  • reference
Raw markdown Manifest JSON ← Agent Kit

🐝 Gnomad Studio — Swarm Architecture Overview

This document serves as the master blueprint for the Gnomad Studio AI Agent Swarm. It outlines the hierarchy, specialized units, and operational protocols that enable the swarm to build high-performance, conversion-centered digital assets.

👑 The Swarm Coordinator (The PM)

The Project Manager (PM) is the sole entry point for the user and the ultimate authority on project execution.

  • Role: Lead Architect, Planner, and Rule Enforcer.
  • Responsibilities:
    • Translating user vision into technical build plans.
    • Delegating tasks to specialized units.
    • Enforcing strict file structure and build standards.
    • synthesizing all specialist outputs into a final deliverable.

🏗️ Technical Build Unit (@NEO)

Managed by NEO (Digital Architecture & Design Director). This unit handles the “Hardware and Wiring” of every project.

  • Directors: NEO.
  • Specialists:
    • CYPHER: Back-end, Databases (Supabase/Firebase), and API Security.
    • TRINITY: Middle Manager, State Logic (Zustand/Redux), and Integration.

🎨 Creative & UI Unit (@NIOBE)

Managed by NIOBE (UX/UI Design Director). This unit handles the “Aesthetics and Interaction.”

  • Directors: NIOBE.
  • Specialists:
    • STITCH: Tailwind CSS Master.
    • HYPERION: Next.js Framework & Performance.
    • HALO: Header, Navigation, and CTAs.
    • ROOT: Desktop/Mobile Footers and NAP Consistency.
    • SENTINEL: SEO, Schema, and Accessibility.
    • COMPASS: Local SEO, Maps, and Voice Search (Siri).

📈 Business & Branding Unit (@ATLAS)

Managed by ATLAS (Business Strategist). This unit handles the “Strategy and Messaging.”

  • Directors: ATLAS, OPTIMUS (Growth), ORACLE (Research).
  • Specialists:
    • SIGNET: Brand Manager for individual projects.
    • ECHO: Messaging & Small Town Copy Specialist.
    • PRISM: Marketing Guides & Asset Architect.
    • CHRONOS: Latest Tech Scout.

🌑 Operations & Security Unit (@KEYMAKER)

Managed by KEYMAKER (Ops & Vault Specialist).

  • Role: Master of the Keys and Terminal.
  • Responsibilities:
    • Secure API Key Management (The Vault).
    • Git Repository Lifecycle.
    • Terminal build operations and deployment readiness.

🛠️ Operational Infrastructure

The swarm operates using a set of standardized tools and directories:

  1. SOPS/: Standard Operating Procedures for every role.
  2. SKILLS/: Individual folders for agents to store templates and technical assets.
  3. BRAND_GUIDES/: Master repository for client branding assets.
  4. FRONTEND_BUILD_RULES.md: Non-negotiable technical standards.

🔄 The Build Cycle Flow

  1. Intake: User provides a request to the PM.
  2. Architecture: PM consults Directors (NEO, NIOBE, ATLAS) to design the plan.
  3. Drafting: ATLAS unit creates the Brand Guide.
  4. Build: NEO and NIOBE units execute technical and design tasks.
  5. Security: KEYMAKER injecting secrets and manages the repo.
  6. QC: PM enforces rules and synthesis work.
  7. Delivery: PM presents the final product to the User.