ABHILASH ANUKU Applied AI · Ambient Systems The Office · v4 · 2026-05-21
Saved

The Office

Internal dashboard for the landing-v8 rebuild — 20 Marvel-themed agents working in parallel. Project state, daily logs, agent performance, pending checklist, recent commits. Each card opens with the agent's full persona; copy and drop into your own .claude/agents/.

Project · At a glance
Sprint Timeline
Today · 2026-05-21
Performance + Commits
Project Glance · live at-a-glance

Agent Work Matrix · 25 agents

Recent File Edits · 0 in last 24h

    Library Versions · 0 deps

    Agent Roster · 25 cards

    Each card is a real .claude/agents/<slug>.md file in this repo. Hit Copy persona to grab the system prompt for your own AI workflow.

    Agent Interaction · Handoff diagram
    Founder Tony · Iron Man (AI-CEO) Doctor Strange Cap America · Designer Spider-Man · Frontend Black Panther · Backend Aria · PM spec spec Hulk · QA gates Black Widow · Inspector Thor · DevOps Carol · Delivery enforce Fury · Ops Director Loki · writes Hela · validates Veronica · rollback tracks solid arrow = handoff · dashed = async/tracking · colors match character palette
    Founder ↓ Tony · Iron Man (AI-CEO) ↓ dispatches all specialists Doctor Strange (spec) → Cap America (design spec) → Spider-Man (build) → QA (gates) Black Panther (backend) → QA (gates) → Thor (deploy) Loki (writes) → Hela (validates) Aria (tracks all) → Carol (enforces delivery) Fury (ops) → Veronica (rollback if needed)
    UML · Architecture diagrams

    1. Component Diagram — Agent team structure (UML 2.5)

    «component» stereotypes · provided / required interfaces · pairs (─◆─) · hand-offs (──▷)

    «actor» Founder «component» AI-CEO Tony · Iron Man dispatches · orchestrates · commits «component» Delivery Carol · Captain Marvel ship gate · FAIL authority «component» Operations Fury · Nick Fury deploy gate · BLOCK authority «component» Orchestrator Aria · PM roster · tracking · audit «pairs» — Aria tracks, Carol enforces «layer» Specialist tier — 13 components «component» Strange · Arch «component» Cap · Designer «component» Bucky · Spec «component» Peter · FE «component» Miles · Motion «component» Gwen · A11y «component» Panther · BE «component» Shuri · Eng «component» QA Hulk + Hulkbuster «component» Sec Rocket · Weapons «component» Tree Groot · DepTree «parallel · AND-gate» «component» Bugs Widow · Inspect «component» Deploy Thor · DevOps «component» Words Loki · Writes «component» Audit Hela · Cuts «layer» Tony's AI subordinates — 5 components «AI» Knowledge JARVIS «AI» Ops state FRIDAY «AI» Containment Veronica «AI» Red-team · sandboxed Ultron «AI» Synthesis Vision Notation: dispatch / call pairs / co-owns async tracking / depends-on «stereotype» = role category Layers: Founder → AI-CEO → Delivery/Ops/PM rail → 13 Specialists → 5 AI Subordinates · 25 components total Pairs marked: Cap◆Bucky · Peter◆Miles · Peter◆Gwen · Hulk◆Rocket◆Groot (triple) · Panther◆Shuri · Loki◆Hela · Carol◆Aria Authority: Carol can FAIL a deliverable Aria marked complete · Fury can BLOCK a deploy mid-pipeline · Hulk/Rocket/Groot AND-gate on QA
    Notation summary (UML 2.5 Component diagram): Components are bounded rectangles with «component» stereotypes. Solid arrows are call/dispatch relationships. Diamond-ended lines are «pairs» bidirectional partnerships. Dashed lines are async tracking / depends-on. The triple-pair Hulk◆Rocket◆Groot is the AND-gated parallel QA pattern — any sub-FAIL blocks the merge.

    2. Sequence Diagram — Parallel QA dispatch (UML 2.5)

    Lifelines · activation bars · sync (▷) + async (─▸) messages · par fragment · alt fragment for verdict

    :Founder :Tony :Hulk :Rocket :Groot :Thor 1: ship(v9 phase 1) par parallel — three QA paths in one dispatch 2: runStandardGates() 3: runSecurityArtillery() 4: walkDependencyTree() Hulk: lint + tsc + build + route + theme + a11y Rocket: secrets + CVE + headers + cookies + HMAC + fuzz Groot: bundleDelta + unusedExports + cycles + treeShake 5: PASS · 252 KB · all themes 6: PASS · 0 secrets · 0 CVE ≥ moderate 7: GREEN · -55 KB vs r1 · 0 cycles alt verdict — three reports AND-gated [ all PASS ] 8: triggerDeploy() [ else any FAIL ] 9: BLOCKED · <reason> 10: shipReport(domain, hash, lighthouse)
    Notation (UML 2.5 Sequence): Lifelines are the dashed verticals. Solid filled rectangles on a lifeline are activation bars (the agent is busy). Solid arrows are synchronous sync messages (1-7). Dashed arrows are async returns (5-7, 9, 10). The par fragment denotes parallel execution — Hulk, Rocket, Groot run concurrently. The alt fragment is the AND-gated verdict — only the [ all PASS ] branch reaches Thor's deploy.

    3. Deployment Diagram — Hostinger Docker stack (UML 2.5)

    «device» VPS · «execution environment» Docker · «artifact» containers · TLS via Caddy · two domains, one reverse proxy

    «device» User Browser Chrome · Safari · Firefox «external» DNS / Hostinger abhilashanuku.com / .de HTTPS :443 A record «device» VPS · Hostinger KVM · 4 vCPU · 16 GB RAM · Ubuntu 24.04 «execution environment» Docker Engine 27.x · docker compose v2 «artifact» container caddy:2-alpine :80 + :443 · auto-TLS · Let's Encrypt reverse-proxy both .com + .de → landing:3000 «artifact» container landing-v8:latest node:20-alpine · next start :3000 Next.js 16.1.1 · R3F · 252 KB FLJ «artifact» container panel-normal:latest node:20 · next start :3010 multi-user UI · auth + dashboard «artifact» MCP mcp_chat:7878 Groq · NVIDIA · Cerebras · Google · Ollama «artifact» MCP mcp_rag:7879 ChromaDB · embed + rerank «artifact» MCP mcp_voice:7880 Whisper · ElevenLabs Flash «artifact» MCP mcp_features:7881 weather · yt · todos · health «artifact» database postgres:16 + pgvector :5432 · users · memory · vectors volume: /var/lib/lisa/pg «artifact» vector DB chromadb:0.5 :8000 · embeddings during dev migrate → pgvector prod «artifact» Docker volume caddy_data TLS certs · ACME state persistent «external» GitHub deploy-hostinger.yml on push main · rsync + docker compose up -d SSH :22
    Notation (UML 2.5 Deployment): Outer rectangles are «device» nodes (physical or VM). Inner shaded rectangles are «execution environment» (Docker engine here). Small boxes are «artifact» containers — what runs in production. Dashed lines are communication / network calls. The double-domain stack (`abhilashanuku.com` + `.de`) is served by one Caddy reverse-proxy fronting one Node container — no separate build per domain.
    Setup guide · How to fork this office

    Fork this office in 6 steps

    Each agent card is a real .md file for your AI agent runtime. Download them, drop them in, and your AI team is live.

    1. Hit Download all personas (zip) above — your customizations (renamed slugs, overridden descriptions, checked addons) are baked in.
    2. Extract the ZIP into your project's .claude/agents/ directory. The folder structure is .claude/agents/tony.md, .claude/agents/frontend.md, etc.
    3. Open LISA (or your AI of choice — Cursor, Windsurf, Codex) (or your AI tool of choice). Restart the session so it picks up the new agent files.
    4. Verify agents are registered: each .md file should appear as a callable subagent type. Type /agents to list them.
    5. Rename slugs and tune descriptions via the Customize toggle on each card above — then re-download before using. Addons extend each agent's behavior when checked.
    6. (Optional) Run an all-hands kickoff: ask Tony "summarise all agents and the first sprint goal" to confirm the team is coherent and your context is wired up correctly.

    Compatible AI tools

    LISA · native OpenAI Agents SDK (port required) Google Gemini (Gem instructions) Blackbox AI (system prompt import) n8n AI Agent nodes AutoGen (agent personas)