Monkey Agentic OS

An agentic AI platform for my web-app teams' workflows.

New Routing
  • 46agents, orchestrator included
  • 13clusters
  • 39skills
  • 8workflow commands
  • 4UI themes, AA each

I design the product. Agents help me build it.

Monkey Agentic OS runs my web design and development, SEO and research work.

I act as product and UX lead: I write the specs, set the rules and review every result. The agents do the scoped work in between.

It is built for my own work, and for the teams I assemble on each project.

How I decided what to build.

From problem to specs, in seven steps. Pick one.

  • 15research reports
  • 53decisions logged
  • 25feature specs

    Why spec-driven: spec → UI → design system → backend

    • Design goalMore output per session in AI dev environments.
    • Design goalFewer tokens spent on later changes.
    • Design goalLess time fixing and bolting on features.

    Design and code, in parallel.

    AI coding made designing and testing this cheap to iterate for me.

      One orchestrator. Thirteen specialist clusters.

      Pick a cluster on the board. The thread shows its agents.

        Threadsession 1

        Every task goes through one gate.

        Pick a task to see its cluster, owner and model.

        orchestrator reads INDEX.md only

            Four rules every agent follows.

            Read only what the task needs

            Context is RAM. Agents open a routing index first, then the few files that matter.

            Right model, right effort

            Effort is a dial too: low for mechanical work, high for hard calls.

            One owner per file, then review

            Parallel agents never touch the same file. Each build passes review and an accessibility audit.

            Memory between sessions

            Every workstream ends with a state file under 50 lines. The next session starts there.

            Every value is a token. Every theme passes AA.

            • Color, spacing, radius, motion and z-index all tokenized.
            • Indigo, black, light and custom themes share one token set.
            • Separate UI package on shadcn, with Phosphor icons.
            • Figma library and code kept in sync.
            • Built with my Design System OS: 64 component specs, 17 layouts.

            Same system. Three themes.

            Pick one. The whole page changes with it.

            Four views of the console.

            Live tree of who is working, on which model, at what cost. From the Figma file, rebuilt in code.

            One command: vhs.

            Coming: the same agents and context, from any terminal.

            $ vhs

            Monkey Agentic OS v0 · concept

            opus · high · orchestrator

            @orchestrator · ~/vicente-portfolio

            ❯ audit the pricing page: SEO, a11y, conversion

            ● Split into three owners, in parallel:

            Read clusters/INDEX.md

            → seo-lead

            → a11y-auditor

            → cro-auditor

            Ran 3 subagents

            ❯ Plan, build, / for skills, @ for context

            ▸▸ auto mode on (shift+tab to cycle)

            SubscriptionIf the claude CLI is installed, it runs on my Claude subscription.
            APIsIf not, it falls back to provider API keys set in settings.

            Plugged into the tools I work in.

            Connected through MCP, CLIs and APIs. More can be added.

            And more: new connections plug in. Logos are trademarks of their owners; shown to indicate integrations.

            Role, stack and status.

            Role
            Product & UX designer and builder. Built for me and the teams I assemble per project.
            Stack
            Claude Code, Codex, Next.js, pnpm monorepo, shadcn, Phosphor, Figma.
            Status
            Agent system in daily use. Console UI in build, not released. CLI (vhs) planned.

            Want to see it run?

            I can walk you through a live session.