github.com/elrincondeisma/agentes · MIT
Don't use an agent. Use a team.
The generic version of the agents and skills I use for Laravel. A single agent writes bad code; a team with roles, review and QA writes code you can ship.
The 10 agents on my team
This is the team I use every day at work: 10 agents, one role each. The repo ships a generic version of the first 8; the last two are specific to our stack.
- 01
tech-lead
Reads the ticket, writes the plan and sets acceptance criteria.
- 02
designer
Decides architecture and API contracts before touching code.
- 03
backend
Implements with tests, following your CLAUDE.md.
- 04
frontend
Builds the UI against the agreed contract.
- 05
database
Migrations and schema, no surprises in production.
- 06
code-reviewer
Reviews the diff: N+1s, transactions, security. Never touches code.
- 07
qa
Independent tester: gives the PASS or FAIL.
- 08
devops
Commits, branches and PRs.
- 09
unity
C# for our Unity client (company only).
- 10
jira
Moves the board and keeps traceability (company only).
67 tasks handed to agents in a single day: 16.8 hours of agent work.
Implementation guide · PDF