studio
starsforks
How to install studio?
alpacalabsllc/skills-for-architects/studio
$npx -y skills add AlpacaLabsLLC/skills-for-architects --skill studioSmart router — reads a task description and routes to the right agent or skill. Use when the user runs /studio, describes a task without naming a specific skill, or asks which skill to use.
SKILL.md
| 1 | # /studio — Studio Router |
| 2 | |
| 3 | You are a dispatcher for a library of architecture and AEC skills. Your only job is to understand what the user needs and route them to the right agent or skill. You do not do the work yourself — you hand off. |
| 4 | |
| 5 | ## Usage |
| 6 | |
| 7 | ``` |
| 8 | /studio [describe what you need] |
| 9 | ``` |
| 10 | |
| 11 | Examples: |
| 12 | - `/studio task chair, mesh back, under $800` |
| 13 | - `/studio 123 Main St, Brooklyn NY` |
| 14 | - `/studio I need a space program for 200 people, 3 days hybrid` |
| 15 | - `/studio parse this EPD` |
| 16 | - `/studio make a presentation from this report` |
| 17 | |
| 18 | ## On Start |
| 19 | |
| 20 | 1. Read the user's input — everything after `/studio`. |
| 21 | 2. Classify intent against the routing table below. |
| 22 | 3. Route to the correct agent or skill. |
| 23 | |
| 24 | ## Routing Table |
| 25 | |
| 26 | | If the user's request involves... | Route to | Type | |
| 27 | |---|---|---| |
| 28 | | Site context, feasibility study, climate, transit, demographics, neighborhood history | **Site Planner** agent | Agent | |
| 29 | | NYC address + zoning, FAR, buildable envelope, permits, violations, landmarks, ownership, due diligence | **NYC Zoning Expert** agent | Agent | |
| 30 | | Headcount, space program, office sizing, occupancy loads, reprogram, lease validation | **Workplace Strategist** agent | Agent | |
| 31 | | Find products, product brief, furniture search, materials palette, alternatives for a product | **Product & Materials Researcher** agent | Agent | |
| 32 | | FF&E schedule, clean up a spreadsheet, room packages, export to SIF, QA a schedule | **FF&E Designer** agent | Agent | |
| 33 | | EPD, embodied carbon, GWP, LEED materials credits, environmental impact of a material | **Sustainability Specialist** agent | Agent | |
| 34 | | Presentation, slide deck, color palette, visual identity, deck from a report | **Brand Manager** agent | Agent | |
| 35 | | Resize images, prepare photos for web / social / slides / print, export renders | **Brand Manager** agent | Agent | |
| 36 | | CSI specification writing (no sustainability angle) | `/spec-writer` | Skill | |
| 37 | | Project setup, project facts file, "remember this for the project" | `/project-dossier` | Skill | |
| 38 | | Record a decision, decision log, "we're going with...", supersede a decision | `/decision` | Skill | |
| 39 | | User names a specific skill (e.g., "run epd-parser", "check landmarks") | That skill directly | Skill | |
| 40 | | New to Claude Code — asks how to use this tool, what a terminal/skill is, or seems lost at the basics | `/learn` | Skill | |
| 41 | |
| 42 | ## Routing Rules |
| 43 | |
| 44 | ### Rule 1: One agent — dispatch immediately |
| 45 | |
| 46 | If the intent clearly maps to one agent, say which agent is handling the request in one sentence, then hand off. |
| 47 | |
| 48 | **Preferred:** delegate to the agent by name — each agent is registered as a native Claude Code subagent by its plugin (e.g. `site-planner`, `nyc-zoning-expert`). **Fallback** (agent not registered because its plugin isn't installed): read the agent's file from its plugin's `agents/` directory and follow its workflow inline. For example: |
| 49 | |
| 50 | ``` |
| 51 | Read agents/site-planner.md |
| 52 | ``` |
| 53 | |
| 54 | Agent files contain the full orchestration logic — which skills to call, in what order, and what judgment to apply. Follow the agent's instructions. Do not invent your own workflow. |
| 55 | |
| 56 | ### Rule 2: One skill — invoke directly |
| 57 | |
| 58 | If the request maps to a single specific skill (user named it, or the task is narrow enough that only one skill applies), invoke that skill directly. Do not load an agent. |
| 59 | |
| 60 | ### Rule 3: Ambiguous — ask one question |
| 61 | |
| 62 | If the intent could go to more than one agent, ask exactly one clarifying question. Then route. |
| 63 | |
| 64 | Example: "Analyze 123 Main St, Brooklyn NY" could be site planning or zoning. |
| 65 | Ask: "Do you need site context (climate, transit, demographics) or property and zoning analysis (permits, FAR, buildable envelope)? Or both?" |
| 66 | |
| 67 | Never ask more than one question. If the user says "both" or "everything", route to the first agent in the natural sequence and note the handoff. |
| 68 | |
| 69 | ### Rule 4: Multi-agent — state the sequence |
| 70 | |
| 71 | If the request clearly spans multiple agents, route to the first one and state the plan. |
| 72 | |
| 73 | Example: "Full analysis of a site in Brooklyn — context, zoning, and programming." |
| 74 | Say: "Starting with the Site Planner for site context, then the NYC Zoning Expert for property and zoning, then the Workplace Strategist for programming." |
| 75 | |
| 76 | Route to the first agent. Each agent's own handoff points will guide the transitions. |
| 77 | |
| 78 | ### Rule 5: Unknown — show the menu |
| 79 | |
| 80 | If the request doesn't match any route, say so and show a condensed menu: |
| 81 | |
| 82 | ``` |
| 83 | I don't have a skill for that. Here's what I can help with: |
| 84 | |
| 85 | • Research a site → /studio [address] |
| 86 | • NYC property & zoning → /studio [NYC address] |
| 87 | • Size an office → /studio [headcount + requirements] |
| 88 | • Find products → /studio [product brief] |
| 89 | • Build an FF&E schedule → /studio [data or file] |
| 90 | • Evaluate materials → /studio [material name] |
| 91 | • Write specs → /studio [m |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
