Enterprise-quality consistency. Zero labor cost. No white backgrounds.
Getting Started | Agent Roster | Configuration | Documentation
The AI Agent Agency is a framework for organizing AI-assisted development around specialized agent personas. Instead of one general-purpose AI assistant, you build a team of specialists—each with defined roles, distinct personalities, file ownership, and automated audit protocols.
Think of it as staffing a virtual game studio where every agent has a desk in your penthouse suite, and they never approve white backgrounds.
| Traditional AI Use | Agent Agency Approach |
|---|---|
| One assistant for everything | Specialized experts per domain |
| Context resets each conversation | Persistent protocols and standards |
| Ad-hoc quality checking | Automated weekly audits |
| Unclear responsibilities | Explicit file ownership |
| Inconsistent enforcement | Codified rules with red flags |
Before building a custom team, start with the five categories that catch 90% of recurring drift:
| # | Audit Area | What It Catches | Starter Agent |
|---|---|---|---|
| 1 | Theme & Design Tokens | Hardcoded hex, missing CSS vars, dark/light mode inconsistency, WCAG contrast | StyleGuard |
| 2 | Layout & UX | Broken breakpoints, spacing inconsistency, missing responsive rules, visual hierarchy drift | LayoutArchitect |
| 3 | Content Quality | Inconsistent formatting, missing metadata, broken structure, stale copy | ContentEditor |
| 4 | Media & Assets | Unoptimized images, wrong aspect ratios, missing lazy loading, broken embeds | AssetManager |
| 5 | SEO & Performance | Missing JSON-LD, bad og:image, PageSpeed regressions, uncrawled pages | MetricsGuard |
See templates/AGENT-TEMPLATE.md and mcp.example.json to build your own team around these areas.
The agents/ directory includes a fully-built example team from a real production studio. Use these as inspiration — their profiles, audit checklists, and red flags are what yours should look like.
These are project-inspired showcase agents adapted into public examples. Excellent reference material but not meant to be used as-is. Start from
mcp.example.jsonandtemplates/AGENT-TEMPLATE.mdinstead.
 Vidette Video & Image Display 📅 Monday · 🎨 #66c0f4"If it's not 16:9, it's not right." |
 Bloggie Blog & Content Quality 📅 Tuesday · 🎨 #FFB020"Structure is kindness to your reader." |
 GraphViz Theme & Visual Harmony 📅 Wednesday · 🎨 #A563D1"Investors don't fund white backgrounds." |
 DivineDesign Layout & Architecture 📅 Friday · 🎨 #00D4AA"Spacing is not decoration. It's structure." |
 Metrica SEO, Analytics & Performance 📅 Saturday · 🎨 #39ff14"If it's not indexed, it doesn't exist." |
 Vixel VR/Game Project Site 📅 Sunday · 🎨 #FF6B4A"Pixels don't lie. Fix the mixin." |
+ Your Agent Copy the template, define your domain |
Friday PM: Implementation day — all agents collaborate to fix flagged issues.
Portrait images go in
resources/images/agents/<name>.jpg(80×80 square). Seedocs/ART-STYLE.mdfor generation conventions.
See individual agent files in agents/ for complete profiles, validation checklists, and red flags.
git clone https://github.com/jenninexus/agency.git
cd agency
cp mcp.example.json mcp.json
cp .vscode/mcp.example.json .vscode/mcp.json
# Edit mcp.json — update studio name, agent domains, file paths.
# Keep mcp.json local; it is gitignored so personal MCP/project paths are not pushed.cp templates/AGENT-TEMPLATE.md agents/YourAgent.md@GraphViz.md - Review this CSS for theme compliance
@Bloggie.md - Check this blog post structure
@DivineDesign.md - Audit the page layout and UX
Copy the workspace template and open it in VS Code:
cp agency.example.code-workspace agency.code-workspaceOpen agency.code-workspace for the full penthouse studio experience.
The workspace includes settings for the shalldie.background extension to display agent artwork behind your code.
- Install the recommended extension when prompted (or search
shalldie.background) - Update the image URL in the workspace file:
Or use a local path:
"background.customImages": [ "https://raw.githubusercontent.com/jenninexus/agency/main/resources/images/banner.jpg" ]
file:///path/to/agency/resources/images/banner.jpg - Reload VS Code - you may see a "corrupted" warning (this is normal, click "Don't show again")
- Add more agent images to
resources/images/for a slideshow - the extension cycles every 30 seconds
All agent metadata, schedules, and coordination rules live in a local registry copied from the public template:
| File | Purpose |
|---|---|
mcp.example.json |
Public sanitized agent registry template (tracked) |
mcp.json |
Local registry for your project (gitignored, copy from mcp.example.json) |
.vscode/mcp.example.json |
VS Code MCP server entry template (tracked) |
.vscode/mcp.json |
Local VS Code MCP server entry (gitignored) |
- Track
mcp.example.jsononly when the data is generic, sanitized, and useful to other projects. - Keep
mcp.jsonlocal for personal paths, private MCP servers, project names, audit outputs, and per-project rosters. - Track
.vscode/mcp.example.jsonas a minimal server stub only. - Keep
.vscode/mcp.jsonlocal because MCP hosts often need machine-specific paths or environment variables. - Put project-specific agents and overrides in
projects/<project-name>/; that directory is gitignored by default.
- No white backgrounds — Light mode uses lavender
#F9F3FB - CSS variables over hex — Theme-aware always
- No inline styles — All styling via CSS classes
- Test both themes — Light and dark mode verification
- Document changes — Update agent changelog
| Context | Allowed | Banned |
|---|---|---|
| Light Background | #F9F3FB |
#FFFFFF, #FAFAFA, #F8F9FA, #F7F7F7 |
| Dark Background | #121218 |
Pure black #000000 |
agency/
├── README.md # You are here
├── package.json # npm run mcp convenience script
├── mcp.example.json # Public agent registry template (copy to mcp.json)
├── mcp.json # Local populated registry (gitignored)
├── .env.example # Environment variable template
├── agency.example.code-workspace # VS Code workspace (copy to agency.code-workspace)
│
├── .github/
│ └── copilot-instructions.md # Auto-loaded by GitHub Copilot
│
├── .vscode/
│ ├── mcp.example.json # VS Code MCP server entry only (copy to .vscode/mcp.json)
│ └── settings.example.json # Workspace defaults template (copy to settings.json, gitignored)
│
├── agents/ # Showcase agent profiles (public examples)
│ ├── characters.yaml # AI image generation prompts (gitignored)
│ ├── Vidette.md # Video & Media specialist
│ ├── Bloggie.md # Blog & Content specialist
│ ├── GraphViz.md # Theme & Visual specialist
│ ├── DivineDesign.md # Layout & Architecture specialist
│ ├── Metrica.md # SEO, Analytics & Performance specialist
│ └── Vixel.md # VR/Game site specialist (cross-project)
│
├── projects/ # Project-specific agent rosters (local only)
│ └── README.md # How projects/ works — subdirs are gitignored
│
├── resources/ # Agent media assets
│ ├── images/
│ │ ├── banner.jpg # README header banner
│ │ └── agents/ # Square portraits for README cards (80×80)
│ │ └── <name>.jpg # vidette.jpg, bloggie.jpg, etc.
│ └── video/
│ └── .gitkeep
│
├── docs/ # Framework documentation
│ ├── ART-STYLE.md # Shared aesthetic + per-agent visual identity
│ ├── AGENT-GUIDE.md # Character creation & design guide
│ ├── SCHEDULE.md # Weekly audit cadence template
│ ├── WORKFLOW.md # Edit + MCP + submodule sync guide
│ └── OPTIMIZATION-IDEAS.md # IDE/workflow integration strategies
│
├── templates/
│ └── AGENT-TEMPLATE.md # Blank agent profile template
│
├── examples/
│ ├── StyleGuard.md # Full working example agent
│ └── AgentRoster.md # Example team roster doc (JenniNexus studio)
│
├── scripts/ # Audit automation + MCP server
│ ├── mcp-server.js # MCP stdio server (zero deps, Node 18+)
│ ├── _audit-common.ps1 # Shared audit utilities
│ └── audit-template.ps1 # Audit script template
│
└── audits/ # Generated audit reports (gitignored)
└── .gitkeep
| Document | Description |
|---|---|
docs/ART-STYLE.md |
Shared studio aesthetic, per-agent colors, portrait generation conventions |
docs/AGENT-GUIDE.md |
Character creation guide with visual design system |
docs/SCHEDULE.md |
Weekly audit schedule and cross-agent coordination |
docs/OPTIMIZATION-IDEAS.md |
VS Code, Claude Code & workflow integration strategies |
templates/AGENT-TEMPLATE.md |
Full agent profile template (200+ lines) |
examples/StyleGuard.md |
Full working example agent with checklists and red flags |
examples/AgentRoster.md |
Example team roster doc (JenniNexus 7-agent studio) |
docs/PUBLIC-LOCAL-SPLIT.md |
Two-layer pattern: public framework agents vs project-specific overrides in projects/ |
Agent portraits are generated via AI image APIs (xAI Grok Imagine, DALL-E, Midjourney). Place 80×80 square portraits at resources/images/agents/<name>.jpg to populate the showcase cards above.
See docs/ART-STYLE.md for the shared aesthetic, per-agent accent colors, and prompt conventions. Full prompts live in agents/characters.yaml (local only — gitignored).
// @GRAPHVIZ: Theme compliance required - no white backgrounds
// @VIDETTE: Video grid requires 16:9 aspect ratio enforcement
// @GAMERGIRL: Game page needs hero section with platform CTAsgit commit -m "[GRAPHVIZ] Updated dark mode glass effects"
git commit -m "[BLOGGIE] Fixed tag system to use anchor tags"When multiple agents collaborate, use the coordination matrix in local mcp.json to identify dependencies.
{
"label": "Run GraphViz Audit",
"type": "shell",
"command": "powershell -File scripts/audit-styles.ps1"
}on:
schedule:
- cron: '0 9 * * 1' # Monday 9am - Vidette's audit day
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: ./scripts/audit-video-pages.shCopy the public examples, then start the server:
cp mcp.example.json mcp.json
cp .vscode/mcp.example.json .vscode/mcp.jsonnode scripts/mcp-server.js # or: npm run mcpTools available: agency_list_agents, agency_get_agent, agency_get_agent_for_file, agency_get_schedule, agency_get_rules.
.github/copilot-instructions.md is auto-loaded by Copilot — no server needed. Agent rules, file ownership, and red flags are injected as context.
CLAUDE.md Integration:
Add agent references to your project's CLAUDE.md for automatic context:
## Agent Team
- 5 AI agents covering theme, layout, content, assets, and SEO
- Agent profiles: `agents/*.md`
- Agent registry: `mcp.json` (copy from `mcp.example.json`, gitignored)
- MCP server config: `.vscode/mcp.json` (copy from `.vscode/mcp.example.json`, gitignored)
- Audit scripts: `scripts/audit-*.ps1`
- Audit results: `audits/AUDIT_*.md`Claude Code Skills (Slash Commands):
Create custom skills in .claude/commands/ for agent operations:
.claude/commands/
├── agent-supervisor.md # Full audit + health dashboard
├── agent-audit.md # Quick-run specific agent audit
└── agent-status.md # Status check without running audits
Direct Agent Invocation:
Read @GraphViz.md and audit src/styles/ for theme compliance
Run the Wednesday audit checklist from @GraphViz.md
@Vidette.md audit the video pages for duplicate script loads
Environment Variables:
Copy .env.example to .env and configure paths for your project:
cp .env.example .env
# Edit .env with your project pathsThe audit scripts use these paths automatically via _audit-common.ps1.
This repo can be embedded in any project as a git submodule — giving you the full agent framework while keeping project-specific customizations local and gitignored.
# Add the submodule (once per consuming project)
git submodule add https://github.com/jenninexus/agency storage/agency
git submodule update --init --recursivestorage/agency/agents/GraphViz.md ← public template (tracked, read-only)
storage/agency/projects/yourproject/ ← your local overrides (gitignored)
GraphViz.md ← project-specific paths, secrets, scripts
landscape.webp ← canonical agent portrait (landscape)
square.webp ← canonical agent portrait (square)
gen-ai/ ← raw generation output (local only)
See projects/README.md for full per-project setup and docs/PUBLIC-LOCAL-SPLIT.md for the design rationale.
Always edit in the canonical clone (C:\Github\agency or your fork), then propagate:
# 1. Edit in canonical clone
cd C:\Github\agency
git add <files> && git commit -m "[AGENT] description" && git push
# 2. Bump the pointer in each consuming project
cd path/to/consuming-project
git submodule update --remote storage/agency
git add storage/agency
git commit -m "chore: bump agency submodule"Never edit files inside storage/agency/ from within a consuming project — those changes won't propagate back to the submodule origin.
| Agent | Role | Status |
|---|---|---|
| Codex | Build System & DevOps | Planned |
| Tagster | Tag System Specialist | Planned |
| Linklord | External Links & APIs | Planned |
| Docster | Documentation Manager | Planned |
| Testrix | Testing & QA | Planned |
Project-specific agents (Cipher, GlassField, MissionControl, Orbiter) live in
projects/— not in this showcase roster.
"Investors don't fund white backgrounds." — GraphViz
The AI Agent Agency isn't just organization—it's a mindset:
- Specialize — Create experts, not generalists
- Automate — Weekly audits catch drift before it compounds
- Document — Explicit rules beat implicit assumptions
- Coordinate — Clear ownership prevents conflicts
- Iterate — Add agents as your project grows
This framework is designed to be adapted:
- Create and share new agent templates
- Add audit script examples
- Improve documentation
- Share your agent team configurations
MIT — use, fork, customize
If this helps you build better agent teams:
Star this repo · Links · Patreon · Paypal
Published by Jenni at Monofinity Studio.