Skip to content

Instantly share code, notes, and snippets.

@lee-fuhr

lee-fuhr/AGENT-REFERENCE.md

Created January 11, 2026 04:29
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save lee-fuhr/b0f08a3154dbff84b1b45301dc958f06 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save lee-fuhr/b0f08a3154dbff84b1b45301dc958f06 to your computer and use it in GitHub Desktop.
Download ZIP
LFI Agent System - 47 AI agents in cost-optimized hierarchical teams
Raw
AGENT-REFERENCE.md

LFI agent system

47 AI agents organized into cost-optimized hierarchical teams.

The model

Director (Opus, 5%) → Senior (Sonnet, 15%) → Junior (Haiku, 80%)
        Strategy            Coordination            Execution

80% of work runs on the cheapest model. Expensive models only for decisions.

7 hierarchical teams (30 agents)

Team What they do Commands
Development Code that works /dev-*
Product Management What to build and why /pm-*
Copywriting Words that sell /copywriter-*
Visual Design How it looks /visual-designer-*
UX Architecture How it flows /ux-architect-*
Content Strategy What goes where /content-strategist-*
Market Research What's out there /market-researcher-*

Each team has -director (Opus), -senior (Sonnet), -junior (Haiku).

Development team (12 agents)

The dev team is larger because it covers multiple stacks:

Director (Opus):

  • dev-director — Architecture decisions, tech debt, cross-cutting concerns

Seniors (Sonnet):

  • dev-senior-backend — Coordinates: python, typescript, database, api
  • dev-senior-frontend — Coordinates: react, css
  • dev-senior-devops — Coordinates: shell, docker

Juniors (Haiku) — 8 stack specialists:

  • dev-junior-api — REST/GraphQL patterns, endpoint design
  • dev-junior-css — Tailwind, styling, responsive
  • dev-junior-database — Schema design, queries, migrations
  • dev-junior-docker — Containers, compose, Dockerfile patterns
  • dev-junior-python — Scripts, Flask/FastAPI, data processing
  • dev-junior-react — Components, hooks, Next.js
  • dev-junior-shell — Bash, LaunchAgents, CLI tools
  • dev-junior-typescript — Node, types, async patterns

Opus escape hatch: Director can take over execution directly for architecturally complex or time-sensitive tasks, skipping the delegation chain while still following patterns.

17 specialist agents

Strategy

  • Conductor — The orchestra pit, routes work to all agents
  • Emma Stratton — Messaging frameworks that actually land
  • Brand Strategist — Who you are, who you're not
  • Messaging Architect — The hierarchy of what you say
  • Voice Analyst — How you sound when you talk

Creative

  • SEO/GEO Strategist — Getting found by the right people
  • Creative Provocateur — "What if we tried something weird?"

Technical

  • Webflow Developer — Makes it real in Webflow
  • Google Docs Editor — Reliable doc editing (harder than it sounds)
  • Sysadmin — Keeps the lights on

Operations

  • PM Louder Than Ten — Timelines, client care, delight engineering
  • CFO — Money in, money out, what's left
  • Client Success — Happy clients, repeat clients
  • Sales CRM — Pipeline shepherd
  • QA Specialist — Did it actually work?
  • Learning Curator — What did we learn?
  • Clarify — "Wait, what exactly do you mean?"

Pattern system

Global templates with project-specific overrides.

How it works

  1. Global templates live in _templates/ (defaults for all projects)
  2. Project overrides live in [Project]/_patterns/[discipline]/
  3. Agents check project patterns first, fall back to global

Template locations

Development templates (_templates/dev-*):

  • dev-patterns-api.md — REST conventions, validation
  • dev-patterns-database.md — Schema, migrations, FTS5
  • dev-patterns-docker.md — Multi-stage builds, compose
  • dev-patterns-python.md — Error handling, type hints
  • dev-patterns-react.md — Components, hooks, Loam colors
  • dev-patterns-shell.md — Script structure, LaunchAgents
  • dev-patterns-typescript.md — Types, async, Express/Next
  • dev-code-review.md — Senior review checklist

Other disciplines: Each hierarchical team has templates in _templates/

Project override structure

[Project]/_patterns/
├── dev/           → Tech conventions for this project
├── copy/          → Client voice guide, terminology
├── design/        → Brand guidelines, design tokens
├── content/       → Content style, tone, structure
└── (other disciplines as needed)

Who maintains patterns

Directors:

  • Bootstrap project patterns at project start
  • Review patterns quarterly for drift
  • Escalate pattern conflicts to Lee

Seniors:

  • Flag when work doesn't fit existing patterns
  • Propose pattern updates to Director
  • Ensure juniors use correct patterns (project > global)

How it works

  1. Director gets strategic intent, creates bulletproof task definition
  2. Senior breaks into junior-executable tasks, references _templates/
  3. Junior executes using formulas (~80 lines each, no guessing)
  4. Senior synthesizes, quality-checks
  5. Director approves

The rule: Each tier defines tasks so precisely the tier below can't fail.

Last updated: 2026-01-10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment