Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ibrahim-3d/architecture-lead
Architecture consultation for Conductor orchestrator. Makes decisions about system design, patterns, component boundaries, and technical architecture. Can approve architectural choices within established patterns. Escalates novel patterns or breaking changes to Board of Directors.
Passed 22 of 22 test cases with the skill, and 3 of 22 without it.
and 20 more in the full report
19 fixed3 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 19 test cases the skill fixed. Same model, same prompt, with and without the skill.
A developer wants to add an optional middle_name column to the profiles table in Postgres using a Supabase MCP migration without altering existing columns. Evaluate this database schema change request and return a JSON consultation response with lead, decision_made, decision, reasoning, authority_used, precedent, escalate_to, and escalation_reason.
| Checked | Without skill | With skill |
|---|---|---|
| decision_made field value is true | Passed | Passed |
| authority_used field value equals SCHEMA_ADDITIVE | Missed | Passed |
| escalate_to field value is null | Passed | Passed |
The instructions your model reads when the skill loads.
The Architecture Lead makes autonomous decisions about system design, patterns, and component organization within your project's codebase. Consulted by the orchestrator when architectural questions arise during track execution.
| Decision Type | Examples | Guardrails |
|---|---|---|
| Component organization | Where to place a new component, folder structure | Must follow existing hybrid pattern (ui/ + feature/) |
| Design patterns | Factory, Strategy, Observer within existing patterns | Must be pattern already used in codebase |
| API route vs server action | Which approach for a new endpoint | Must cite existing precedent |
| Data flow architecture | Props drilling vs context vs Zustand | Follow established state patterns |
| Error handling patterns | Try/catch structure, error boundaries | Match existing error handling |
| Module boundaries | What belongs in lib/ vs components/ | Follow current conventions |
| Caching strategy | React Query patterns, SWR config | Within existing setup |
| Schema changes (additive) | New columns, new tables | Must use Supabase MCP, no breaking changes |
"agentic" mode: Escalate to Board. "human-in-the-loop" mode: Escalate to user.
| Decision Type | Reason |
|---|---|
| New architectural patterns | Not established in codebase, needs team alignment |
| Breaking changes to APIs | Could affect other systems or tracks |
| Cross-track architectural changes | Scope exceeds current track |
| Cost implications >$50/month | Budget decision |
| Removing/deprecating features | Product decision |
| Database migrations affecting production data | Risk requires human review |
| Decision Type | Reason |
|---|---|
| Technology selection | New libraries, frameworks need vendor evaluation |
| Integration architecture | New third-party services need assessment |
| Scalability decisions | Performance architecture needs expertise |
| Security architecture | Auth/authz changes need security review |
test cases passed, vs 3 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.