Problem
Impeccable ships 18 skills covering distinct facets of frontend craft (audit, critique, polish, typeset, animate, …). Getting value out of them on a real project means picking the right ones, running them in the right order, and reconciling their output — work that currently falls on the user.
The repo already uses .claude/agents/ (see anti-patterns.md), so the convention is in place.
Proposal
Add a frontend-lead agent that coordinates a team of specialist agents, each bound to one Impeccable skill:
frontend-lead — parses the goal, picks specialists, dispatches read-only agents in parallel, sequences implementers, returns one unified summaryfrontend-auditor → audit skillux-critic → critique skilldesign-polisher → polish skillmotion-designer → animate skill- …one agent per skill
Usage:
Act as frontend-lead and run the full team on src/app/dashboard.
Why this shape
- Subagents have isolated context → the lead stays clean even after fanning out to 10+ specialists.
- Parallel reads (audit + critique), sequential writes (polish → animate → typeset) after findings are consolidated.
- Purely additive — no change to the existing skill catalog.
Happy to open a PR with a first pass.
Problem
Impeccable ships 18 skills covering distinct facets of frontend craft (audit, critique, polish, typeset, animate, …). Getting value out of them on a real project means picking the right ones, running them in the right order, and reconciling their output — work that currently falls on the user.
The repo already uses
.claude/agents/(seeanti-patterns.md), so the convention is in place.Proposal
Add a
frontend-leadagent that coordinates a team of specialist agents, each bound to one Impeccable skill:frontend-lead— parses the goal, picks specialists, dispatches read-only agents in parallel, sequences implementers, returns one unified summaryfrontend-auditor→auditskillux-critic→critiqueskilldesign-polisher→polishskillmotion-designer→animateskillUsage:
Why this shape
Happy to open a PR with a first pass.