AlpacaLabsLLC/skills-for-architects / skills/learn
learn
UnverifiedGuided, hands-on course teaching architects how to use Codex or Claude Code — six short modules, each built around an exercise on a bundled sandbox project (a fictional Brooklyn art museum expansion). Resumable across sessions via PROGRESS.md. Use when the user runs $learn or /as:learn, says they're new to AI-assisted project work, or asks how to learn it.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 3.6 KB |
| SKILL.md | skill md | 23.3 KB |
| host-contract.json | config | 1.5 KB |
| sandbox/art-museum/IMG_4032.txt | markdown | 1.2 KB |
| sandbox/art-museum/RE_ RE_ RE_ quick question.txt | markdown | 1.4 KB |
| sandbox/art-museum/Scan_001.txt | markdown | 1.4 KB |
| sandbox/art-museum/notes final FINAL (2).txt | markdown | 680 B |
| sandbox/art-museum/program_v2_FINAL_final.csv | other | 658 B |
| sandbox/art-museum/site-visit-jun12.txt | markdown | 1.2 KB |
| templates/office-CLAUDE.md | markdown | 2.3 KB |
templates/office-CLAUDE.md
View on GitHub# Office Standards — {your firm name}
<!-- This is your office's standards binder. Claude reads it at the start of
every session in this folder and follows it without being asked.
Everything below is a sensible default — edit each ← line to match how
YOUR office actually works, and delete anything you don't care about.
Derived from the Arch Studio rules:
https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/rules -->
## Identity
- Firm: {name} ← edit
- Document attribution block: {firm name, address, line format} ← edit (this is a header/footer block — AI-generated documents are never signed or sealed)
- Default project location / jurisdiction: {city} ← edit
- Project phases: SD / DD / CD / CA ← edit if your office uses different phase names
- Date format in filenames and documents: {e.g. 2026-07-20} ← edit
## Units & measurements
- Default to US customary (imperial) units ← or metric — pick one
- Architectural notation: feet-inches with dash (`12'-6"`), never decimal feet
- Always specify area type: GSF / USF / RSF / NSF — never a bare number
- Never mix unit systems within one table, calculation, or paragraph
## Terminology & abbreviations
- Use standard AEC terms (program, adjacency, circulation, egress, millwork)
- Define every abbreviation on first use, then abbreviate: "Gross Square Feet (GSF)" → "GSF"
## Codes & sources
- Cite codes with edition year and section: `{verified code} {edition} §{section}` (format placeholder only), never "the building code"
- Note that codes are adopted and amended locally: "(check local amendments)"
- Say "appears consistent with [section]" — never "complies with code"
- Every data point from an external source gets a citation
## Documents
- Descriptive filenames: `maple-st-zoning-summary.md`, never `output.md` or `doc1.md`
- Tables for all comparative data; units in column headers, not in every cell
- Site-visit report format: {header, observations, open items — in your order; "observed", never "inspected"} ← edit
## Disclaimer
End every document containing code, zoning, or life-safety analysis with:
> **Disclaimer:** This is an AI-generated analysis for preliminary planning purposes. All findings must be verified by a licensed professional before use in design, permitting, or regulatory submissions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |