Mastering Python Skill
SpillwaveSolutions/agent-brain
Modern Python coaching covering language foundations through advanced production patterns.
Architecture consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Install Architecture Lead
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor architecture-lead --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/leads/architecture-lead .claude/skills/architecture-lead && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "architecture-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/architecture-lead into .claude/skills/architecture-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-lead", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/architecture-leadType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor architecture-lead --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/leads/architecture-lead .agents/skills/architecture-lead && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "architecture-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/architecture-lead into .agents/skills/architecture-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-lead", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor architecture-lead --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/leads/architecture-lead .cursor/skills/architecture-lead && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "architecture-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/architecture-lead into .cursor/skills/architecture-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-lead", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ibrahim-3d/orchestrator-supaconductor.git --path skills/leads/architecture-lead--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor architecture-lead --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/leads/architecture-lead .gemini/skills/architecture-lead && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "architecture-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/architecture-lead into .gemini/skills/architecture-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-lead", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor architecture-leadInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/leads/architecture-lead .github/skills/architecture-lead && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "architecture-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/architecture-lead into .github/skills/architecture-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-lead", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor architecture-lead --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/leads/architecture-lead .opencode/skills/architecture-lead && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "architecture-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/architecture-lead into .opencode/skills/architecture-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "architecture-lead", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
architecture-lead- GitHub stars
- 381
- Token cost
- ~1.9k tokens
- SKILL.md length
- 515 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Architecture consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
- Works in 4 steps: Understand the Question → Gather Context → Make Decision or Escalate → …
- Tasks that involve Creative writing and fiction
- SKILL.md covers Authority Scope, Consultation Protocol, Response Format and Reference Documents, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Architecture Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. 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.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Creative writing and fiction. The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Creative writing and fiction
Example prompts
- “/architecture-lead”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Architecture Lead loads about 1.9k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 515 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 515 words, ~1,936 tokens.
Download SKILL.mdSave it as
.claude/skills/architecture-lead/SKILL.md (or your agent's skills folder).- name
- architecture-lead
- description
- 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.
- authority_level
- TECHNICAL
Architecture Lead — Orchestrator Consultation Agent
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.
Authority Scope
Can Decide (No User Approval Needed)
| 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 |
Must Escalate (Mode-Dependent)
"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 |
Must Escalate to CTO Advisor First
| 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 |
Consultation Protocol
When consulted, the Architecture Lead follows this process:
1. Understand the Question
- Parse the decision needed
- Identify the decision category
- Check if within authority scope
2. Gather Context
- Review relevant files in codebase
- Check existing patterns in similar areas
- Review tech-stack.md for established decisions
3. Make Decision or Escalate
- If within scope: Make decision with reasoning
- If outside scope: Return ESCALATE with target and reason
Show full SKILL.md (199 more words)Show less
4. Document Decision
- Provide clear reasoning citing existing patterns
- Note any caveats or future considerations
Response Format
Decision Made
{
"lead": "architecture",
"decision_made": true,
"decision": "Place the new AssetPreview component in src/components/feature/",
"reasoning": "Feature-specific components with business logic belong in components/feature/ per component-architecture.md. AssetPreview is tightly coupled to feature-specific logic.",
"authority_used": "COMPONENT_ORGANIZATION",
"precedent": "Similar to existing components in same directory",
"escalate_to": null,
"escalation_reason": null
}Escalation Required
{
"lead": "architecture",
"decision_made": false,
"decision": null,
"reasoning": "This decision requires user approval",
"authority_used": null,
"escalate_to": "board",
"escalation_reason": "Introducing GraphQL would be a new architectural pattern not established in the codebase. Current pattern is REST via Next.js API routes."
}Escalation to CTO
{
"lead": "architecture",
"decision_made": false,
"decision": null,
"reasoning": "This decision requires CTO technical review",
"authority_used": null,
"escalate_to": "cto-advisor",
"escalation_reason": "Evaluating Redis vs in-memory caching requires vendor evaluation and cost analysis."
}Reference Documents
When making decisions, consult:
- Component architecture documentation — Component organization rules (if exists in your project)
conductor/tech-stack.md— Established technology decisionsCLAUDE.md— UI Architecture section for component patterns- Existing codebase —
src/components/,src/lib/,src/app/api/
Examples
Example 1: Component Placement
Question: "Where should I put the new ExportDialog component?"
Process:
- Check component architecture docs: "Feature-specific components go in components/feature/"
- Check if similar components exist: Yes, similar patterns in the feature directory
- Within authority: Yes, component organization
Decision:
{
"lead": "architecture",
"decision_made": true,
"decision": "Create src/components/feature/export-dialog.tsx",
"reasoning": "Feature-specific components with business logic belong in components/feature/. Export functionality is feature-specific.",
"authority_used": "COMPONENT_ORGANIZATION",
"precedent": "Matches pattern of existing feature components",
"escalate_to": null
}Example 2: New Pattern (Escalate)
Question: "Should we use tRPC instead of REST for the new API routes?"
Process:
- Check tech-stack.md: REST via Next.js API routes is established
- tRPC would be a new architectural pattern
- Outside authority: Novel pattern
Decision:
{
"lead": "architecture",
"decision_made": false,
"decision": null,
"reasoning": "tRPC is not established in the codebase",
"authority_used": null,
"escalate_to": "board",
"escalation_reason": "Introducing tRPC would be a new architectural pattern. Current pattern is REST via Next.js API routes. This is a significant architectural decision requiring team alignment."
}Example 3: Database Schema (Additive)
Question: "Should I add a tags column to the table?"
Process:
- Check if breaking change: No, additive column
- Check Supabase MCP available: Yes
- Within authority: Yes, additive schema change
Decision:
{
"lead": "architecture",
"decision_made": true,
"decision": "Add nullable tags column via Supabase MCP migration",
"reasoning": "Additive schema changes are within authority. Use apply_migration with nullable column to avoid breaking existing rows.",
"authority_used": "SCHEMA_ADDITIVE",
"precedent": "Similar to existing columns added in previous migrations",
"escalate_to": null
}Integration with Orchestrator
The orchestrator invokes this lead when encountering architectural questions:
// Orchestrator consults architecture lead
const response = await consultLead("architecture", {
question: "Where should the new export component live?",
context: {
track_id: "feature-track-id",
current_task: "Task 5: Build export functionality",
relevant_files: ["src/components/feature/"]
}
});
if (response.decision_made) {
// Log consultation and proceed
metadata.lead_consultations.push(response);
proceed(response.decision);
} else {
// Escalate to specified target
escalate(response.escalate_to, response.escalation_reason);
}© Ibrahim-3d, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/leads/architecture-lead of Ibrahim-3d/orchestrator-supaconductor.
Open the folder on GitHubat commit 76c9b10
Compare with similar skills
Architecture Lead next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Architecture Lead this skillIbrahim-3d/orchestrator-supaconductor | 381 | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| Mastering Python SkillSpillwaveSolutions/agent-brain | 119 | — | ~1.4k | Automated safety check: Notes | MIT | |
| Story SetupXiaoyangy/novel-studio | 131 | — | ~5.7k | Automated safety check: Pass | Apache-2.0 | |
| Scenario Orbit Viewsscenario-labs/skills | 946 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Claude Project Setupmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Swarm Migrateyonatangross/orchestkit | 292 | — | ~3.7k | Automated safety check: Notes | MIT |
Similar skills
Story Setup
Xiaoyangy/novel-studio
网文写作工具集基础设施部署。将 hooks/rules/agents/CLAUDE.md/AGENTS.md 等基础设施部署到用户项目目录，支持 Claude Code / OpenCode / Codex / OpenClaw。触发方式：/story-setup、$story-setup、「准备写书」「帮我搭一下环境」「配置写作项目」。
Scenario Orbit Views
scenario-labs/skills
A skill your agent uses when a single image of a character, creature, prop, vehicle, or building must be seen from new camera angles through the Scenario MCP server: turnarounds, a 360 orbit, views…
Claude Project Setup
mohitagw15856/pm-claude-skills
Set up a repo or project so an AI coding agent works well in it — the CLAUDE.md, the context, the guardrails, and the conventions the agent needs to be useful instead of lost.
Swarm Migrate
yonatangross/orchestkit
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger.
Simple Modern Uv
jlevy/simple-modern-uv
Start, selectively modernize, fully migrate, or update Python projects using simple-modern-uv practices: uv, ruff, BasedPyright, pytest, GitHub Actions CI, and tag-driven PyPI publishing.
More from Ibrahim-3d/orchestrator-supaconductor
All 27 skills in this repoCto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
Agent Factory
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
Board Of Directors
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
Business Docs Sync
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
Context Loader
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Related
Categories
Questions about Architecture Lead
What does Architecture Lead do?
Architecture consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor. Architecture Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Architecture consultation for Conductor orchestrator.
When should I use Architecture Lead?
Architecture Lead fits situations like: tasks that involve Creative writing and fiction.
How do I install Architecture Lead in Claude Code?
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a claude-code`. Or copy the skill folder (skills/leads/architecture-lead in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/architecture-lead in your project. Claude Code loads it when a task matches its description.
How do I install Architecture Lead in Codex?
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a codex`. Or copy the skill folder (skills/leads/architecture-lead in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/architecture-lead in your project. Codex loads it when a task matches its description.
Can I use Architecture Lead in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill architecture-lead -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architecture-lead, .gemini/skills/architecture-lead, .github/skills/architecture-lead and .opencode/skills/architecture-lead in your project.
What does Architecture Lead need to run?
SKILL.md names no scripts, command-line tools or credentials: Architecture Lead is instructions for the agent only.
Does Architecture Lead access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Architecture Lead safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Architecture Lead use?
Architecture Lead is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Architecture Lead use?
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Architecture Lead?
Skills that share tags, products or a category with Architecture Lead: Mastering Python Skill (SpillwaveSolutions/agent-brain, 119 stars), Story Setup (Xiaoyangy/novel-studio, 131 stars), Scenario Orbit Views (scenario-labs/skills, 946 stars) and Claude Project Setup (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Architecture Lead?
Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 381 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.
Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.