← Back to Index Dominick DeFazio
Custom Tooling

Skills I've built into Claude.

Custom skills that orchestrate agent teams, scaffold entire projects, run autonomous deliberation, and analyze decision history. The infrastructure that makes work compound.

4-Agent System ~/.claude/skills/atelier

atelier

A multi-agent pipeline that produces visual artwork as code.

Modeled on a real atelier: a Scout researches references, a Composer writes the brief, a Renderer executes it, a Critic drives revision. Every piece is reproducible from a seed and a brief.

Not image generation — this skill writes code that draws. node-canvas stroke painting. GLSL fragment shaders. PptxGenJS geometric layouts. PIL pixel art. The output is a PNG you own, generated by code you can re-run, version, and modify.

The four agents

01
Scout
Researches references, identifies strategy axes, surfaces the visual vocabulary the piece will work in.
02
Composer
Writes the brief — composition, palette, technique, zone structure, rendering parameters.
03
Renderer
Executes the brief in code. Generates the self-contained generator file and renders the output PNG.
04
Critic
Structured, opinionated review. Identifies what's working, what isn't, what to change. Drives the next iteration.

Two-phase workflow

Phase 1 — Shotgun. Scout + Composer + 5 parallel Renderers produce 5 wildly different strategy variants of the same subject. The user picks the direction.

Phase 2 — Polish. The chosen variant iterates through Critic → Composer → Renderer until it hits EXHIBITION READY, then scales to 4K as the final piece. Every 3rd iteration, a 5-question interview gathers direction.

The output

The Great Wave and Gas Giant pieces in my gallery were both produced by this pipeline. Each piece lives under ~/art/<slug>/ with its research, brief, version log, generator code, critiques, and rendered PNGs — fully reproducible months later.

4
Specialized agents
4K
Final render resolution
30-50
Agent spawns per session
18-Agent Pipeline ~/.claude/skills/init-pipeline

init-pipeline

The system that builds the systems.

Initialize a new project with a complete 18-agent, 5-team build pipeline. Creates the .claude/ directory, agent configs, skill manifests, project rules, and tech stack scaffolding from templates — all driven by a short interview about the project domain.

Built because every new project needs the same setup work: agents, skills, rules, branch structure, test framework, CI. This skill collapses what used to be a half-day of yak-shaving into a 10-question interview.

What it sets up

18
Specialized agents
5
Agent teams
10
Interview questions

The interview

A short series of AskUserQuestion prompts gathers: project name + slug, one-sentence description, tech stack (React + Vite default, Next.js, SvelteKit, Vue), styling and component library (Tailwind + shadcn/ui default), data layer (Supabase, Firebase, Prisma + Postgres, Drizzle + PGlite, REST), main entities and their relationships, the primary user view, and a 3-5 word visual direction.

What gets scaffolded

The output is a complete .claude/ directory with agents tuned to the chosen stack, skills wired to the chosen libraries, project rules generated from the domain description, and a CLAUDE.md that reflects everything from the interview. Drop into a fresh git repo and start shipping — no boilerplate session, no stack debate.

Decision Analytics ~/.claude/skills/analyze-decisions

analyze-decisions

Tooling that mines decision history to improve agent alignment.

A PostToolUse hook logs every AskUserQuestion answer to ~/.claude/decisions.db across all projects. This skill harvests the unprocessed entries and extracts actionable insights from the user's choice patterns.

The premise: a user's real preferences are buried in thousands of micro-choices they've already made. Surface the patterns, find the contradictions, propose memory candidates. The agent gets better at working with the human by learning from how the human actually decides.

Five dimensions of analysis

01
Preference Signals
Consistent choices that reveal a rule. Does the user prefer thoroughness over speed? Parallel over sequential? Investigation over retry?
02
Frame Rejections
Answers that don't match any offered option — the user typed something custom. Gold for finding where the framing was wrong.
03
Contradictions
Decisions that conflict with other decisions or with existing CLAUDE.md rules. Surface tensions for resolution.
04
Memory Candidates
High-confidence patterns worth promoting to persistent memory files for cross-session use.
05
Project Signals
Repo-specific patterns that suggest project-level CLAUDE.md updates rather than global memory.

The feedback loop

Every AskUserQuestion answer → logged to decisions.db via hook → harvest unprocessed → analyze across 5 dimensions → propose memory candidates → user approves → write to memory files → mark processed.

Self-improving tooling for an LLM assistant. The agent that works with the user tomorrow is shaped by the agent that worked with the user today.

12-Delegate Council ~/.claude/skills/quick-assembly

quick-assembly

Multi-agent autonomous deliberation in a Model UN format.

Spawns a 12-delegate General Assembly of historical and contemporary thinkers — Peter Thiel, Naval Ravikant, Nassim Taleb, Angela Merkel, Charlie Munger, Ryan Holiday, and others — to deliberate on a single hard question. Delegates research independently, form organic blocs, draft competing resolutions, negotiate amendments, and vote on a binding outcome.

The format borrows from Model UN procedure — opening speeches, bloc dynamics, working papers, sponsor's choice. Every speech and vote is preserved verbatim. The Sponsor reviews the final resolution and can accept, modify, or reject it. The output is a full transcript plus a structured resolution document that captures both the recommendation and the reasoning behind it.

What makes it different

All user interaction is front-loaded into an expanded Chair's Brief. After the assembly is cast and the brief is approved, the entire debate runs fully autonomously — zero interruptions through opening speeches, bloc formation, paper drafting, amendments, and the final vote. The user can walk away for an hour and return to a fully reasoned recommendation.

The eight phases

Phase 1 — Opening Speeches. All 12 delegates deliver simultaneous opening positions on the question.

Phase 2 — Bloc Formation. Delegates with aligned positions self-organize into 2-4 voting blocs.

Phase 3 — Working Papers. Each bloc drafts a competing resolution.

Phase 4 — Cross-Examination. Blocs challenge each other's papers; weak arguments fall, strong ones get sharpened.

Phase 5 — Amendments. Negotiated revisions; coalitions can shift.

Phase 6 — Final Speeches. Each bloc's leader makes the closing case.

Phase 7 — The Vote. A single binding resolution emerges.

Phase 8 — Sponsor's Choice. The Sponsor reviews, modifies, or rejects the final resolution. The only live touchpoint after the brief.

Use cases

Strategic deliberation on questions where the user wants multiple perspectives in tension before committing. The skill is most valuable when the question is genuinely hard, when the user has access to a deep bench of relevant thinkers to draft as delegates, and when the deliberation itself — the cross-examination, the bloc dynamics, the amendments — is as informative as the final vote.

12
Delegates per session
8
Phases of debate
1
Touchpoint after brief