DavidCho1999/archaiflow-skills / bundles/code-life-safety/skills/zoning-summary
zoning-summary
VerifiedThis skill should be used when the user provides a site address, parcel info, or zoning lookup text and needs a structured zoning summary for early design. Trigger on 'zoning summary', 'zoning lookup', 'site zoning for [address]', or pasted zoning portal output. Targets North American projects (US + Canada). Generates a worksheet markdown in `docs/zoning/` and updates the project zoning index.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| assets/zoning-template.md | markdown | 3.1 KB |
| references/design_implications.md | markdown | 2.8 KB |
| references/na_zoning.md | markdown | 8.0 KB |
| scripts/append_to_index.py | script | 1.5 KB |
| scripts/init_zoning_workspace.py | script | 783 B |
references/design_implications.md
View on GitHub# Constraint → Design Move
Each zoning constraint is also an early-design instruction. Use this when filling the worksheet so every line item carries a one-sentence implication, not just a number.
---
## High FAR / FSI (>5)
- Implication: Tower or stacked typology. Core efficiency drives plate size; section diagram dominates design.
## Low FAR / FSI (<2)
- Implication: Low-rise spread. Plan logic and outdoor rooms become the project; section is secondary.
## Tight side setbacks (<5 ft / <1.5 m)
- Implication: Treat side walls as blind party walls; daylight comes from front, rear, or skylights/light wells.
## Generous front setback / front yard
- Implication: Front yard becomes the public-private threshold. Landscape and entry sequence matter more than facade.
## Sky exposure plane / daylight plane / angular plane
- Implication: Upper-floor stepbacks. Terraces fall out naturally; design them as program, not residual.
## Height limit in stories AND feet/metres
- Implication: Floor-to-floor budget tightens. Trades off ceiling height vs. mechanical depth — decide early.
## Historic / Heritage Conservation District overlay
- Implication: Material palette, window proportions, and roof form are not free variables. Lead with context analysis.
## Floodplain overlay
- Implication: First-floor elevation requirement may push the building up — entry sequence, ramp/stair, and mechanical placement re-think.
## Transit overlay / MTSA with reduced parking
- Implication: Free up ground floor and basement for active program. Reconsider whether parking is needed at all.
## Inclusionary zoning trigger
- Implication: Unit mix changes — affordable units affect plan modules and mechanical zoning.
## Conditional use / discretionary review / Committee of Adjustment
- Implication: Add 6-12 months to schedule; design must be community-presentable, not just permit-ready, by an earlier date.
## Form-based code (active ground floor, transparency %)
- Implication: Ground-floor section, ceiling height, and glazing ratio become regulatory, not stylistic.
## Required parking minimum (high)
- Implication: Below-grade parking levels become a cost driver. Test whether reducing units or shifting use can drop a level.
## Shadow study requirement
- Implication: Mass placement and stepbacks must be tested against adjacent open space at solstice/equinox before locking massing.
## Section 37 / Community Benefits Charge (Toronto)
- Implication: Density bonus is paid for in cash or community space. Decide early whether to push for the bonus or design within base FSI.
---
## Cross-region principle
A constraint is only a design driver when it is *binding*. If FAR/FSI is generous and the program doesn't need it, FAR is not the design driver — the tighter constraint (height, setback, parking, angular plane) is. Identify which 2-3 constraints actually bind, and design from those.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |