Agent skill

Zoning And Codes

by Abhinavbwj in Abhinavbwj/Urban-Design-Skills-Claude

Analyze zoning regulations and generate form-based codes, including Euclidean zoning analysis, performance zoning parameters, transect-based coding, building envelope controls, and development…

MITAuto-check passedLegal & Compliance

Install Zoning And Codes

skills CLI
$ npx skills add Abhinavbwj/Urban-Design-Skills-Claude --skill zoning-and-codes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Abhinavbwj/Urban-Design-Skills-Claude zoning-and-codes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Abhinavbwj/Urban-Design-Skills-Claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/zoning-and-codes .claude/skills/zoning-and-codes && rm -rf skills-src

Use ~/.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/

Facts

Skill name
zoning-and-codes
GitHub stars
132
Used in
1 other repo
Token cost
~9.5k tokens
SKILL.md length
4,442 words
Files
3 (incl. references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Analyze zoning regulations and generate form-based codes, including Euclidean zoning analysis, performance zoning parameters, transect-based coding, building envelope controls, and development…

  • Works in 7 steps: Zoning System Types → Transect Zone Specifications → Form-Based Code Elements → …
  • The user asks about zoning
  • SKILL.md covers 1. Zoning System Types, 2. Transect Zone Specifications, 3. Form-Based Code Elements and 4. Building Envelope Controls, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Zoning And Codes is an agent skill from Abhinavbwj/Urban-Design-Skills-Claude. Analyze zoning regulations and generate form-based codes, including Euclidean zoning analysis, performance zoning parameters, transect-based coding, building envelope controls, and development standard specification. Use when the user asks about zoning, building codes, development standards, setbacks, height limits, FAR regulations, use permissions, overlay zones, special districts, or form-based codes. Also use when the user needs to create a zoning framework for a masterplan, understand what can be built on a…

Its SKILL.md is about 9.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/code-types.md` and `references/transect-guide.md`).

It sits in Legal & Compliance. The repository describes itself as: Urban Design Skills Claude. The licence is MIT.

When your agent uses it

  • The user asks about zoning
  • Development standards
  • FAR regulations
  • Use permissions

Example prompts

  • “/zoning-and-codes”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Zoning System Types
  2. Transect Zone Specifications
  3. Form-Based Code Elements
  4. Building Envelope Controls
  5. Code Generation Workflow
  6. Output Format
  7. Reference Links

What it can do on your machine

Read from SKILL.md and the folder at commit 666327b. 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.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • transect.org
    • miami21.org
    • denvergov.org
    • formbasedcodes.org
    • cnu.org
    • dpz.com
    • planning.org
    • lincolninst.edu
    • uli.org
    • nacto.org
    • itdp.org
    • placemakers.com
    • pps.org

    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

Zoning And Codes loads about 9.5k tokens when it runs, and up to ~27k if it reads all its reference files. Until then it costs about 147 tokens; SKILL.md has 4,442 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~147
When it runs · the whole SKILL.md, loaded when a task matches
~9.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~27k

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 Abhinavbwj/Urban-Design-Skills-Claude at commit 666327b, republished under its MIT licence (© Abhinavbwj). 4,442 words, ~9,501 tokens.

Download SKILL.mdSave it as .claude/skills/zoning-and-codes/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
zoning-and-codes
description
Analyze zoning regulations and generate form-based codes, including Euclidean zoning analysis, performance zoning parameters, transect-based coding, building envelope controls, and development standard specification. Use when the user asks about zoning, building codes, development standards, setbacks, height limits, FAR regulations, use permissions, overlay zones, special districts, or form-based codes. Also use when the user needs to create a zoning framework for a masterplan, understand what can be built on a site, or translate a design into regulatory language.

Zoning and Codes Skill

This skill provides comprehensive zoning analysis and form-based code generation capabilities for urban design and masterplanning projects. It covers the full spectrum of zoning approaches from conventional Euclidean zoning through transect-based SmartCode, and provides detailed workflows for translating design intent into enforceable regulatory language. The skill draws from the SmartCode, Miami 21, Denver Form-Based Code, and international best practices in development regulation.


1. Zoning System Types

Use the following comparison matrix to select the appropriate zoning approach for a given project context. Each system has distinct strengths and is suited to different planning objectives.

Comparison Matrix
TypePrimary ControlsStrengthsWeaknessesBest For
EuclideanUse categories (residential, commercial, industrial) + dimensional standards (setback, height, lot size, FAR)Simple to administer; predictable outcomes; well-understood by developers and communities; extensive legal precedentRigid separation of uses enforces automobile dependence and sprawl; does not address building form or public realm quality; encourages lowest-common-denominator developmentStable suburban areas; low-density residential neighborhoods; industrial zones; contexts where predictability is the primary goal
PerformanceImpact metrics (traffic generation, noise levels, shadow/daylight access, stormwater runoff, air quality emissions)Highly flexible; focuses on outcomes rather than prescriptions; encourages innovation in design solutions; can accommodate unforeseen usesComplex to administer and enforce; requires technical expertise for review; unpredictable physical outcomes; challenging for community members to understandMixed-use areas where impact matters more than form; transitional zones between incompatible uses; innovation districts; areas with complex environmental constraints
Form-BasedBuilding form (height, setback, coverage, FAR), frontage types, building types, public space standardsProduces predictable physical form and high-quality public realm; enables mixed-use by right; regulates what matters most to communities (physical character); illustrated and accessibleRequires design expertise to draft and administer; less familiar to many planning departments; can be perceived as overly prescriptive for building design; initial adoption requires educationNew development and infill projects; downtown revitalization; transit-oriented development; areas where physical character is the primary concern; urban renewal zones
Transect-Based (SmartCode)Rural-to-urban gradient zones (T1-T6) with calibrated standards for each zone; integrates thoroughfare, civic space, and building standardsHolistic and context-sensitive; addresses the full range of human settlement patterns; internally consistent; treats urbanism as an ecology; comprehensive frameworkRequires paradigm shift from conventional zoning thinking; initial calibration to local context is labor-intensive; may not fit jurisdictions with highly irregular development patternsComprehensive plan implementation; greenfield master-planned communities; complete code replacements; jurisdictions ready for a fundamentally different approach to regulation
HybridCombination of two or more approaches (e.g., form-based for downtown + Euclidean for suburban residential + performance for industrial/environmental overlay)Balanced approach; can tailor regulation to distinct character areas; pragmatic; easier political adoption by preserving familiar systems where they workCan be complex to navigate; risk of internal contradictions between systems; may confuse applicants moving between zones with different regulatory logicMost real-world applications; jurisdictions transitioning from Euclidean to form-based; cities with diverse character areas requiring different regulatory approaches
Selection Decision Tree
  1. Is the project a comprehensive code replacement for an entire jurisdiction? --> Consider Transect-Based (SmartCode)
  2. Is the project focused on a specific plan area (downtown, corridor, TOD)? --> Use Form-Based Code for the plan area
  3. Does the area have complex environmental constraints (floodplain, noise, contamination)? --> Layer Performance standards as an overlay
  4. Are existing suburban residential areas stable and not targeted for change? --> Retain Euclidean zoning for those areas
  5. For most real-world jurisdictions --> Use a Hybrid approach combining the above as appropriate

2. Transect Zone Specifications

The Transect is a cross-section of the human habitat ranging from the most natural (T1 Natural Zone) to the most urban (T6 Urban Core Zone). Each zone has a distinct character defined by calibrated standards for density, building form, frontage, street type, and permitted uses. The following table provides complete specifications for all six zones plus Special Districts (SD).

Complete T1-T6 Parameter Table
ParameterT1 NaturalT2 RuralT3 Sub-UrbanT4 General UrbanT5 Urban CenterT6 Urban Core
CharacterLands in a natural or wilderness condition, including water bodies and wetlandsSparsely settled lands in open or cultivated state, woodland, grassland, agriculturalLow-density residential with deep setbacks, landscaped yards, detached buildingsMedium-density mixed residential and commercial with shallow setbacks, defined streetwallHigher-density mixed-use with ground-floor retail, consistent streetwall, active frontageHighest density and tallest buildings, greatest variety of uses, civic significance
Density (DU/ha)0 (conservation)0.5-2.55-1212-2525-6060-150+
Building Height (stories)N/A1-21-32-54-86-30+ (varies by district)
Building Height (meters max)N/A9121828Per specific district (typically 40-120)
Setback Front (min-max)N/A10-30m5-10m2-5m0-3m0-2m
Setback Side (min)N/A5-10m3-5m0-3m0m0m
Setback Rear (min)N/A10-20m6-10m3-6m3-6m3-6m
Lot Coverage (max %)0-5%10-20%30-50%50-70%70-90%80-100%
FAR (max)N/A0.1-0.30.3-0.81.0-2.52.5-5.05.0-15.0+
Frontage TypeN/AFence, hedge, naturalisticPorch, fence, naturalisticStoop, dooryard, forecourt, porchShopfront, gallery, arcade, terraceShopfront, gallery, arcade
Building TypeN/AEstate house, agricultural building, accessory dwellingDetached house, cottage, duplex, villa, accessory dwellingRowhouse, townhouse, duplex, small apartment, live-workMid-rise apartment, mixed-use building, liner buildingTower, mid-rise, high-rise, civic building
Parking RequirementsN/AOn-site, no minimum1-2 spaces/DU, on-site, driveway0.5-1.5 spaces/DU, rear-loaded garages, shared lotsNo minimum or 0.5/DU max, structured parking required above thresholdNo minimum, structured or underground only
Open Space (min %)95-100%70-90%40-60%20-40%10-20%5-15% (may include rooftop)
Street TypeTrail, pathRural road, rural avenueResidential street, yield streetAvenue, neighborhood street, commercial streetBoulevard, avenue, commercial streetBoulevard, avenue, passage, alley
Permitted UsesConservation, recreation, agricultureAgriculture, single-family residential, bed-and-breakfast, stablesSingle-family, duplex, small office, daycare, small civicResidential (all types), office, retail (<500 sqm), restaurant, civic, live-workAll residential, all retail, office, hotel, entertainment, civic, institutionalAll uses permitted; highest-intensity commercial, office, institutional, residential
Civic Space TypeNature preserve, greenway, wildlife corridorGreenway, park, playgroundGreen, playground, community garden, pocket parkSquare, plaza, playground, community gardenPlaza, square, urban park, promenadePlaza, civic plaza, urban park, promenade, passage
Transect Zone Character Descriptions

T1 Natural Zone: Lands approximating or reverting to a wilderness condition, including lands unsuitable for settlement due to topography, hydrology, or vegetation. These are permanently protected areas that provide ecosystem services (water filtration, carbon sequestration, biodiversity habitat, flood control) and recreational value. No buildings except minor structures for conservation management and passive recreation (trails, observation platforms, restrooms).

T2 Rural Zone: Sparsely settled lands in open or cultivated state. These include woodland, agricultural land, grassland, and scattered buildings. The landscape is the dominant element; buildings are subsidiary. Typical settlement includes farmsteads, rural estates, and very small hamlets. Roads are typically two-lane without curbs, with open swales for drainage. The boundary between T2 and T3 is one of the most important in the transect, as it defines the edge of the neighborhood.

T3 Sub-Urban Zone: Low-density residential areas with predominantly detached buildings set back from tree-lined streets. Yards and landscaping are significant elements of the streetscape. Blocks are larger (150-250m) and streets are curvilinear or grid. This is the typical post-war suburban condition, but the transect version emphasizes connectivity, sidewalks, street trees, and proximity to neighborhood centers.

T4 General Urban Zone: The workhorse zone of a walkable neighborhood. Medium-density, mixed-use (by right), with a defined streetwall of moderate height (2-5 stories). Buildings have shallow front setbacks (2-5m) and form a continuous or near-continuous street edge. Ground floors may be residential or commercial depending on location. Streets are well-connected in a grid or modified grid, with on-street parking, street trees, and sidewalks on both sides.

T5 Urban Center Zone: The main street, town center, or downtown of a neighborhood, district, or small city. Higher density, wider variety of uses, more active ground floors, and taller buildings than T4. The streetwall is consistent and buildings are built to or near the front lot line. Ground floors are predominantly commercial (retail, restaurant, service). Upper floors are residential, office, or hotel. Parking is structured or underground, never surface lots facing the street.

T6 Urban Core Zone: The highest-intensity zone, found in city centers and major regional downtowns. Towers and high-rise buildings of significant height. Maximum variety and intensity of uses. Civic buildings and institutions of regional significance. Major transit infrastructure (rail stations, bus terminals). Public spaces are formal and hardscaped (plazas, civic squares, promenades). This zone typically applies only in the largest cities and in very limited geography.


3. Form-Based Code Elements

A form-based code consists of several integrated components that work together to regulate the physical form of development. Each component addresses a distinct aspect of the built environment.

3.1 Regulating Plan

The regulating plan is the coded map that designates transect zones, civic space locations, special district boundaries, and thoroughfare types for every parcel within the plan area. It is the spatial expression of the code and the primary reference document for any applicant.

  • Maps transect zones (T1-T6) to specific parcels or blocks
  • Identifies mandatory building frontage lines (build-to lines)
  • Designates required ground-floor retail frontages
  • Locates civic space reservations (plaza, green, park)
  • Shows thoroughfare types for every street segment
  • Identifies special districts with unique standards (civic, waterfront, transit, historic)
  • May include sub-area plans for complex sites
3.2 Building Form Standards

Building form standards regulate the physical envelope and configuration of buildings. These are the core of the form-based code and replace the bulk and dimensional standards of conventional zoning.

  • Height: maximum stories and meters, measured from grade to highest occupied floor (or roof peak, depending on code), with exceptions for mechanical equipment, elevator overruns, parapets (typically +1.5m), and architectural features (spires, cupolas)
  • Setback / Build-to Line: front setback is typically expressed as a build-to line (BTL) with a required percentage of building facade that must be located at the BTL (typically 70-90% in urban zones)
  • Coverage: maximum building footprint as percentage of lot area
  • FAR: maximum ratio of total floor area to lot area, with rules for calculation (e.g., structured parking excluded, mechanical rooms excluded, balconies excluded if open)
  • Building Type: the permitted physical configurations (detached house, rowhouse, apartment building, mixed-use building, tower, etc.), each with its own sub-standards
  • Disposition: the placement of the building on the lot (edgeyard, sideyard, rearyard, courtyard) -- determines how the building relates to the street and to open space
3.3 Frontage Type Standards

The frontage is the interface between the building and the public realm. Frontage type standards regulate the configuration of the ground floor and the zone between the facade and the lot line.

Frontage TypeDescriptionDepthHeightApplicability
ShopfrontLarge glazed opening at ground level for retail display, with transom, signage band, and bulkhead; entrance recessed or flush0-0.6m setbackGround floor 4.0-5.0m clearT4, T5, T6 - commercial streets, required retail frontages
GalleryColonnade or covered walkway attached to the building facade, extending over the sidewalk, supported by columns2.4-3.6m depth3.0-4.5m clearT4, T5, T6 - commercial streets, especially in warm/rainy climates
ArcadeCovered walkway within the building volume (building overhangs the sidewalk at upper floors, ground floor is setback creating a covered passage)2.4-3.6m depth3.0-4.5m clearT5, T6 - high-intensity commercial, transit corridors
StoopElevated entry platform with stairs to the sidewalk, providing a semi-private transition zone between public sidewalk and private dwelling0.6-1.8m depth, 1.2-2.4m wide0.6-1.5m above sidewalkT3, T4 - residential streets, rowhouses, townhouses
PorchCovered, unenclosed room attached to the building facade, elevated above the sidewalk, providing a semi-public social space1.8-3.0m depthFull story height, 0.3-0.9m above gradeT3, T4 - residential streets, detached and semi-detached houses
ForecourtA portion of the lot left open between the building facade and the lot line, creating a small semi-public court or garden3.0-6.0m depthN/A (open)T3, T4, T5 - institutional buildings, apartments, restaurants
Common YardThe building is set back substantially from the lot line, with the front yard functioning as a shared community green5.0-10.0m depthN/A (open)T3 - residential clusters, co-housing, campus settings
TerraceThe building is set back from the lot line with an elevated terrace or platform in front, often with a retaining wall or balustrade at the sidewalk edge1.2-3.0m depth0.3-1.0m above sidewalkT4, T5 - residential, mixed-use buildings on sloping sites
DooryardA shallow planted or paved area between the building facade and the sidewalk, defined by a low wall, fence, or hedge0.6-2.4m depthFence/wall 0.3-1.2mT3, T4 - residential streets, cottage and village contexts
Lightwell / AreawayA below-grade court in front of the building, providing light and access to a basement level, protected by a railing or wall at sidewalk level0.9-1.8m depth below gradeRailing 0.9-1.1m at sidewalkT5, T6 - urban buildings with occupied basements
3.4 Public Space Standards

Public space standards regulate the design and programming of the civic realm, including parks, plazas, greens, squares, playgrounds, and community gardens.

Space TypeTypical SizeCharacterKey StandardsApplicability
Plaza0.1-0.5 haHardscaped, formal, framed by building facades on at least two sides, civic or commercial focusMin 50% hardscape, required seating (1 LF per 30 sqm), shade structures or trees on 30%+ of area, water feature or public art encouragedT5, T6
Square0.2-1.0 haFormal green, framed by streets and buildings on all four sides, civic focus with monument or fountain40-60% planted, formal tree planting (allees, bosques), paths, benches, central featureT4, T5, T6
Green0.2-2.0 haInformal open lawn, naturalistic planting, passive recreation, visual relief70%+ planted, informal tree clusters, open lawn for flexible use, minimal hardscapeT3, T4
Pocket Park0.02-0.1 haSmall intimate space on a single lot, seating, shade, respite from urban environmentSeating for 10-30 people, shade trees or structure, low maintenance planting, visible from streetT4, T5
Playground0.1-0.5 haDedicated play space for children, with equipment, safety surfacing, shade, seating for caregiversAge-appropriate equipment (2-5 and 5-12 zones), safety surfacing (rubber, engineered wood fiber), shade 40%+, fencing where adjacent to trafficT3, T4, T5
Community Garden0.05-0.3 haIndividual garden plots, shared tool shed, water supply, compost area, gathering spaceIndividual plots 3x6m typical, shared infrastructure, accessible paths, water supply, perimeter fencing, storageT3, T4
PromenadeLinear, 4-8m wideFormal linear walking path along a waterfront, park edge, or significant corridorMin 4.0m clear width, benches every 30-60m, lighting, trees, separated from vehiclesT4, T5, T6
3.5 Thoroughfare Standards

Thoroughfare standards define the cross-section, character, and design parameters for every street type in the code. These replace conventional transportation engineering standards with context-sensitive designs.

  • Each thoroughfare type gets a full cross-section specification (see the Street Design skill for detailed cross-section methodology)
  • Thoroughfare types are assigned to the regulating plan by segment
  • Standards cover: ROW width, travel lanes (number and width), parking (type and width), bike facilities, sidewalk zones, median, planting, lighting
  • Typical thoroughfare types: boulevard, avenue, commercial street, neighborhood street, residential street, rear lane/alley, passage, shared street, path/trail
3.6 Signage Standards

Signage standards regulate the type, size, placement, and illumination of signs to ensure visual quality and consistency.

  • Projecting signs: perpendicular to facade, max 0.6 sqm per sign, min 2.4m clearance above sidewalk, max projection 1.2m
  • Wall signs: flat on facade, max 10% of facade area or 2.0 sqm (whichever is less in T3-T4, greater in T5-T6), letter height max 300mm (T4), 450mm (T5), 600mm (T6)
  • Awning/canopy signs: text on valance only, max letter height 200mm
  • Window signs: max 25% of window area, no flashing or animated
  • Monument signs: ground-mounted, max 1.2m height (T3), 1.5m (T4), not permitted T5-T6
  • Illumination: external illumination (gooseneck, wash) permitted all zones; internal illumination (backlit channel letters) permitted T5-T6 only; neon permitted T5-T6 only; no flashing, scrolling, or animated signs
3.7 Architectural Standards (Optional Companion)

Architectural standards are typically advisory (guidelines) rather than mandatory (code), but some form-based codes include mandatory provisions for key elements.

  • Materials: primary facade materials (masonry, stucco, wood clapboard, metal panel); prohibited materials (EIFS below 2.4m, vinyl siding in T5-T6, exposed concrete block); material transitions at inside corners only (not outside)
  • Fenestration: minimum ground-floor transparency (60-80% in T5-T6 shopfronts, 30-50% in T4), upper-floor window-to-wall ratio (20-40%), window proportions (vertical orientation preferred), prohibited: mirrored glass, all-glass curtain wall below T6
  • Rooflines: flat roofs with cornice or parapet (T5-T6), pitched roofs 6:12 to 12:12 (T3-T4), roof material standards, mechanical screening required
  • Color: typically advisory, may regulate in historic districts
  • Parking structure facades: must be wrapped with habitable space on all street-facing facades, or designed with architectural facade treatment that conceals the parking structure

Show full SKILL.md (1,734 more words)Show less

4. Building Envelope Controls

Building envelope controls define the three-dimensional volume within which a building may be constructed. These are the most precise regulatory tools in a zoning code.

4.1 Height Controls
ParameterSpecificationNotes
Maximum height in storiesT3: 3, T4: 5, T5: 8, T6: varies (6-30+)Story count is primary control in form-based codes
Maximum height in metersT3: 12m, T4: 18m, T5: 28m, T6: variesMeasured from average grade at building perimeter to highest occupied floor ceiling
Ground floor minimum height3.6m (commercial), 3.0m (residential)Floor-to-floor, ensures future commercial conversion potential
Upper floor height range2.7-3.6m floor-to-floorAllows residential (2.7-3.0m) or commercial (3.3-3.6m)
Datum pointAverage pre-development grade at front lot linePrevents manipulation of grade to gain height
Mechanical exceptionsElevator overruns, mechanical rooms, stair bulkheads: max +4.5m above roof, setback 3.0m from facadeMust be screened from view at street level
Parapet exceptionMax +1.5m above roof height limitArchitectural element, not habitable
Architectural feature exceptionSpires, cupolas, clock towers: max +6.0m, max 10% of roof areaCivic and institutional buildings primarily
4.2 Setback and Build-to-Line Controls
ParameterT3 Sub-UrbanT4 General UrbanT5 Urban CenterT6 Urban Core
Front build-to line (BTL)5-10m from ROW2-5m from ROW0-3m from ROW0-2m from ROW
BTL compliance50% of facade at BTL70% of facade at BTL80% of facade at BTL90% of facade at BTL
Side setback (interior)3-5m0-3m0m0m
Side setback (street-facing)3-5m2-4m0-3m0-2m
Rear setback6-10m3-6m3-6m3-6m
Rear setback to alley3m1.5m0m0m

Build-to-line (BTL) is fundamentally different from a setback. A setback defines a minimum distance from which a building must be placed; a BTL defines a line at which the building facade must be placed. The BTL creates a consistent streetwall. The "compliance percentage" specifies how much of the lot width must have building facade at the BTL (the remainder may be recessed for courtyards, forecourts, or entries).

4.3 Lot Coverage

Maximum percentage of the lot area that may be covered by the building footprint:

  • T3: 30-50% (significant open space on lot)
  • T4: 50-70% (moderate open space)
  • T5: 70-90% (minimal open space, may be on upper levels)
  • T6: 80-100% (nearly full lot coverage, open space on rooftops or at upper setbacks)

Coverage calculations typically include: all roofed structures, covered porches and galleries (if enclosed on three sides), but exclude: uncovered terraces, pergolas (if less than 50% covered), at-grade patios, underground structures.

4.4 Floor Area Ratio (FAR)

FAR = Total Floor Area / Lot Area. This controls the overall bulk and density of development.

ZoneBase FARMaximum FAR (with bonuses)Notes
T30.3-0.81.0Low-density, predominantly residential
T41.0-2.53.0Medium-density, mixed-use
T52.5-5.06.0-8.0Higher-density, mixed-use
T65.0-15.015.0-25.0Highest-density, varies widely

FAR calculation inclusions: all enclosed floor area measured to outside face of exterior walls, mezzanines, occupied basements, enclosed balconies. FAR calculation exclusions: structured parking (often excluded to encourage structured over surface parking), mechanical rooms, unenclosed balconies, residential storage rooms below 5 sqm, ground-floor retail in mixed-use buildings (incentive exclusion in some codes). FAR bonuses: additional FAR may be earned through provision of affordable housing (+0.5-2.0 FAR), public open space (+0.5-1.0 FAR), transit infrastructure contributions (+0.5 FAR), LEED/green certification (+0.5 FAR), heritage preservation (+0.5-1.0 FAR). Bonuses are typically capped and cannot exceed the maximum FAR.

4.5 Sky Exposure Plane

The sky exposure plane is an angular plane that limits building height above a certain base height at the street setback line. It ensures daylight and sky access at the street level.

  • Base height: the height at the setback line at which the angular plane begins (typically the streetwall height: 12-24m depending on zone)
  • Angle: the angle of the plane measured from the horizontal at the setback line (typically 70-80 degrees from horizontal, or equivalently a slope of approximately 2.5:1 to 5.7:1)
  • Application: the building may not penetrate the sky exposure plane on any street-facing facade
  • Calculation: at any point along the facade, maximum height = base height + (distance from setback line x tangent of angle)
  • Exemptions: mechanical bulkheads, elevator overruns, and architectural features (if within permitted exceptions)

Example: Base height 18m, angle 75 degrees from horizontal. At 5m setback from facade line: max height = 18 + (5 x tan75) = 18 + 18.7 = 36.7m.

4.6 Step-Back Requirements

Step-backs require upper portions of a building to be set back from the lower streetwall facade, reducing the visual bulk of taller buildings and preserving the pedestrian-scale streetwall experience.

  • Streetwall height: the height at which the step-back occurs (typically 4-6 stories, or 15-22m)
  • Step-back depth: the minimum horizontal distance the upper floors must be set back from the streetwall facade (typically 3.0-6.0m)
  • Application: required on all street-facing facades (may not be required on alley-facing or interior facades)
  • Rationale: preserves the 1:1 to 1:2 street-width-to-building-height ratio at the pedestrian level, which research identifies as the most comfortable enclosure ratio for urban streets
4.7 Tower Separation

For buildings with tower elements (above the podium/streetwall), minimum separation distances prevent a canyon effect and ensure light, air, and privacy.

  • Tower-to-tower (same site): minimum 24m face-to-face
  • Tower-to-tower (adjacent sites): minimum 24-30m center-to-center
  • Tower floor plate: maximum 750-2,000 sqm (varies by zone; smaller plates improve light penetration and reduce wind effects)
  • Tower lot coverage: maximum 40-50% of lot area (the tower footprint, not the podium footprint)
  • Point tower preferred: slender towers with floor plates under 1,000 sqm minimize shadow, wind, and view impacts
4.8 Lot Dimensions
ParameterT3T4T5T6
Minimum lot width12-18m6-12m6-15m15-30m
Minimum lot area300-600 sqm150-400 sqm200-800 sqm500-2000 sqm
Maximum lot width30-45m24-36m45-60m90-120m
Maximum lot area2000 sqm1500 sqm4000 sqm10000 sqm
Maximum block perimeter500-600m400-500m450-550m500-600m
Maximum block face length150-200m120-150m130-160m150-200m

Maximum lot and block dimensions prevent superblocks and ensure a fine-grained, walkable urban fabric with frequent cross-streets, mid-block passages, and varied building frontages.


5. Code Generation Workflow

This section provides a step-by-step process for producing a form-based code from a masterplan or area plan. Follow these steps sequentially.

Step 1: Define Character Areas and Transect Zones
  • Walk the site and surrounding context (or analyze the masterplan if greenfield)
  • Identify distinct character areas based on intended density, use mix, building scale, and street type
  • Assign a transect zone (T1-T6) to each character area
  • Document the rationale for each zone assignment
  • Map zone boundaries on the regulating plan base (parcel map or block map)
  • Ensure transitions are gradual (do not jump from T2 to T5 without intermediate zones)
Step 2: Assign Building Form Standards
  • For each transect zone, calibrate the dimensional standards (height, setback/BTL, coverage, FAR)
  • Select permitted building types for each zone
  • Define building disposition (edgeyard, sideyard, rearyard, courtyard) for each zone
  • Set ground-floor height minimums (especially for zones requiring commercial ground floors)
  • Define step-back requirements for zones permitting buildings above 4-6 stories
  • Specify tower controls (floor plate, separation, coverage) for T6
Step 3: Define Frontage Types
  • For each transect zone, select the permitted and required frontage types
  • Specify dimensions (depth, height, setback) for each frontage type
  • Identify required retail frontage streets (where shopfront frontage is mandatory)
  • Illustrate each frontage type with a section drawing and photograph (or described equivalent)
  • Define the relationship between frontage type and the sidewalk/furnishing zone
Step 4: Create Thoroughfare Standards
  • Classify every street in the plan area by type (boulevard, avenue, commercial street, neighborhood street, alley, etc.)
  • Assign a cross-section to each street type (use the Street Design skill for detailed specifications)
  • Specify ROW width, travel lanes, parking, bike facilities, sidewalk zones, median, planting, and lighting for each type
  • Map thoroughfare types to the regulating plan
Step 5: Write Public Space Standards
  • Identify all civic spaces in the masterplan (plazas, greens, squares, parks, playgrounds, community gardens)
  • Assign a civic space type to each
  • Specify minimum size, character, required elements, and programming for each
  • Define the relationship between civic spaces and adjacent transect zones (e.g., a plaza must be fronted by T5 or T6 with shopfront frontage)
Step 6: Draft Regulating Plan
  • Combine all layers onto a single regulatory map: transect zones, thoroughfare types, civic space locations, special district boundaries, required retail frontage lines, build-to lines
  • The regulating plan is the applicant's primary reference -- it must be clear, unambiguous, and at a scale that shows individual parcels
  • Include a legend that keys to the code text for all standards
  • Provide both a full-area regulating plan and enlarged sub-area plans for complex zones
Step 7: Add Administrative Procedures
  • Define the review process: by-right approval (administrative, no hearing) for projects that comply with all standards; design review (staff or board) for warrants (minor deviations); variance process for hardship cases
  • Specify which deviations are warrants (minor, staff-approved) versus variances (significant, board-approved)
  • Define the submittal requirements: site plan, building elevations, floor plans, landscape plan, signage plan
  • Establish a pre-application conference process for large projects
  • Include a nonconformities section (existing buildings that do not comply with the new code)
Step 8: Create Design Guidelines Companion Document
  • Produce an illustrated, advisory companion document that shows the intent and aspirations of the code
  • Include precedent photographs, rendered streetscapes, and annotated diagrams
  • Cover topics that are difficult to regulate by code: color palettes, material quality, landscape character, architectural style compatibility
  • This document informs applicants, guides design review, and builds community understanding
  • Design guidelines are advisory, not mandatory -- they supplement the code but do not override it

6. Output Format

When producing a zoning analysis or form-based code, deliver the following specification package:

Zoning Analysis Output Template
SITE: [Address / Location]
EXISTING ZONING: [Current zone designation]
PROPOSED ZONING: [Proposed zone designation, if applicable]

DIMENSIONAL STANDARDS:
+-----------------------+----------+-----------+
| Parameter             | Required | Proposed  |
+-----------------------+----------+-----------+
| Max Height (stories)  |          |           |
| Max Height (meters)   |          |           |
| Front Setback / BTL   |          |           |
| Side Setback          |          |           |
| Rear Setback          |          |           |
| Lot Coverage (max %)  |          |           |
| FAR (max)             |          |           |
| Open Space (min %)    |          |           |
| Parking Requirement   |          |           |
+-----------------------+----------+-----------+

PERMITTED USES:
- Residential: [list]
- Commercial: [list]
- Institutional: [list]
- Other: [list]

BUILDING TYPES PERMITTED:
- [list with max dimensions for each]

FRONTAGE TYPES REQUIRED/PERMITTED:
- [list with dimensions]

SPECIAL CONDITIONS:
- [overlays, special districts, historic designations, etc.]

DEVELOPMENT CAPACITY:
- Lot area: [sqm]
- Buildable area (coverage): [sqm]
- Maximum floor area (FAR): [sqm]
- Estimated dwelling units: [range based on unit size assumptions]
- Estimated commercial area: [sqm, if applicable]

COMPLIANCE NOTES:
- [List any variances or warrants that would be required]
- [List any additional approvals needed (design review, environmental, etc.)]
Form-Based Code Output Template
FORM-BASED CODE: [Project / Plan Area Name]
JURISDICTION: [City, State/Province, Country]
DATE: [Draft date]
VERSION: [Version number]

ARTICLE 1: GENERAL PROVISIONS
- Purpose and intent
- Applicability
- Relationship to other codes
- Definitions

ARTICLE 2: REGULATING PLAN
- [Map with zone designations]
- Zone descriptions and intent

ARTICLE 3: BUILDING FORM STANDARDS
- [Table for each zone: T3, T4, T5, T6]
- Building type specifications
- Building disposition standards

ARTICLE 4: FRONTAGE TYPE STANDARDS
- [Table for each frontage type]
- Illustrations and dimensions

ARTICLE 5: PUBLIC SPACE STANDARDS
- [Specifications for each civic space type]
- Landscape standards

ARTICLE 6: THOROUGHFARE STANDARDS
- [Cross-sections for each street type]
- Intersection standards

ARTICLE 7: PARKING STANDARDS
- Parking requirements by zone and use
- Bicycle parking requirements
- Design standards for parking structures

ARTICLE 8: SIGNAGE STANDARDS
- Sign types by zone
- Dimensional standards
- Illumination standards

ARTICLE 9: ADMINISTRATION
- Review procedures
- Warrants and variances
- Nonconformities
- Definitions

Primary Standards and Model Codes
Supplementary Resources
Foundational Texts
  • Duany, Plater-Zyberk, Alminana. The New Civic Art: Elements of Town Planning. Rizzoli, 2003.
  • Parolek, Parolek, Crawford. Form-Based Codes: A Guide for Planners, Urban Designers, Municipalities, and Developers. Wiley, 2008.
  • Talen, Emily. City Rules: How Regulations Affect Urban Form. Island Press, 2012.
  • Barnett, Jonathan. Redesigning Cities: Principles, Practice, Implementation. APA Planners Press, 2003.
  • SmartCode Manual v9.2. Center for Applied Transect Studies, 2009.

© Abhinavbwj, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/zoning-and-codes of Abhinavbwj/Urban-Design-Skills-Claude.

  • SKILL.md
  • references/code-types.md
  • references/transect-guide.md

Open the folder on GitHubat commit 666327b

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Abhinavbwj/Urban-Design-Skills-Claude, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Zoning And Codes 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.

Zoning And Codes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Zoning And Codes this skillAbhinavbwj/Urban-Design-Skills-Claude1321 repos~9.5kAutomated safety check: PassMIT
Paper to Chinese Patent DrafterYuan1z0825/nature-skills47k1 repos~1.1kAutomated safety check: PassApache-2.0
C15tc15t/c15t1.9k1 repos~1.6kAutomated safety check: PassApache-2.0
Contract Reviewevolsb/claude-legal-skill4641 repos~3.6kAutomated safety check: PassMIT
Legal Clinic Client Intakeanthropics/claude-for-legal9.6k3 repos~3.2kAutomated safety check: PassApache-2.0
Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill1061 repos~959Automated safety check: PassNone

Similar skills

  • Paper to Chinese Patent Drafter

    Yuan1z0825/nature-skills

    Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.

    47k GitHub starsUsed in 1 repo~1.1k tokens
    Legal & ComplianceAuto-check passed
  • C15t

    c15t/c15t

    Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.

    1.9k GitHub starsUsed in 1 repo~1.6k tokens
    Legal & ComplianceAuto-check passed
  • Contract Review

    evolsb/claude-legal-skill

    Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.

    464 GitHub starsUsed in 1 repo~3.6k tokens
    Legal & ComplianceAuto-check passed
  • Legal Clinic Client Intake

    anthropics/claude-for-legal

    Official

    Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

    9.6k GitHub starsUsed in 3 repos~3.2k tokens
    Legal & ComplianceAuto-check passed
  • Paper To Cn Patent

    snipp-zha/Paper-to-patent-Skill

    Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts.

    106 GitHub starsUsed in 1 repo~959 tokens
    Legal & ComplianceAuto-check passed
  • Employment Contract Templates

    ynulihao/AgentSkillOS

    Create employment contracts, offer letters, and HR policy documents following legal best practices.

    617 GitHub starsUsed in 12 repos~4.1k tokens
    Legal & ComplianceAuto-check passed

More from Abhinavbwj/Urban-Design-Skills-Claude

All 18 skills in this repo
  • Cost Estimation

    Abhinavbwj/Urban-Design-Skills-Claude

    Estimate construction costs, infrastructure costs, soft costs, and total development costs for urban design projects.

    132 GitHub starsUsed in 1 repo~5k tokens
    Auto-check passed
  • Urban Calculator

    Abhinavbwj/Urban-Design-Skills-Claude

    Python computational tools for urban design metric calculations including density, FAR, walkability scoring, parking requirements, green space analysis, and block optimization.

    132 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Block And Density

    Abhinavbwj/Urban-Design-Skills-Claude

    Design urban blocks and optimize density using typological analysis, FAR calculations, and building configuration strategies.

    132 GitHub starsUsed in 1 repo~7.5k tokens
    Auto-check passed
  • Design Evaluation

    Abhinavbwj/Urban-Design-Skills-Claude

    Evaluate urban designs against comprehensive criteria drawn from all major global standards, certification systems, and theoretical frameworks.

    132 GitHub starsUsed in 1 repo~9.2k tokens
    Auto-check passed
  • Mobility And Transport

    Abhinavbwj/Urban-Design-Skills-Claude

    Comprehensive mobility and transport planning for urban design including trip generation, mode split targets, street network connectivity, transit planning, cycling network design, pedestrian…

    132 GitHub starsUsed in 1 repo~6.1k tokens
    Auto-check passed
  • Precedent Study

    Abhinavbwj/Urban-Design-Skills-Claude

    Research and analyze urban design precedents systematically.

    132 GitHub starsUsed in 1 repo~5.1k tokens
    Auto-check passed

Questions about Zoning And Codes

What does Zoning And Codes do?

Analyze zoning regulations and generate form-based codes, including Euclidean zoning analysis, performance zoning parameters, transect-based coding, building envelope controls, and development…. Zoning And Codes is an agent skill from Abhinavbwj/Urban-Design-Skills-Claude. Analyze zoning regulations and generate form-based codes, including Euclidean zoning analysis, performance zoning parameters, transect-based coding, building envelope controls, and development standard specification.

When should I use Zoning And Codes?

Zoning And Codes fits situations like: the user asks about zoning; development standards; FAR regulations; use permissions.

How do I install Zoning And Codes in Claude Code?

Run `npx skills add Abhinavbwj/Urban-Design-Skills-Claude --skill zoning-and-codes -a claude-code`. Or copy the skill folder (skills/zoning-and-codes in Abhinavbwj/Urban-Design-Skills-Claude) into .claude/skills/zoning-and-codes in your project. Claude Code loads it when a task matches its description.

How do I install Zoning And Codes in Codex?

Run `npx skills add Abhinavbwj/Urban-Design-Skills-Claude --skill zoning-and-codes -a codex`. Or copy the skill folder (skills/zoning-and-codes in Abhinavbwj/Urban-Design-Skills-Claude) into .agents/skills/zoning-and-codes in your project. Codex loads it when a task matches its description.

Can I use Zoning And Codes 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 Abhinavbwj/Urban-Design-Skills-Claude --skill zoning-and-codes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/zoning-and-codes, .gemini/skills/zoning-and-codes, .github/skills/zoning-and-codes and .opencode/skills/zoning-and-codes in your project.

What does Zoning And Codes need to run?

SKILL.md names no scripts, command-line tools or credentials: Zoning And Codes is instructions for the agent only.

Does Zoning And Codes access the network?

SKILL.md names 13 domains. As links in the text: transect.org, miami21.org, denvergov.org, formbasedcodes.org, cnu.org, dpz.com, planning.org, lincolninst.edu, uli.org, nacto.org, itdp.org, placemakers.com and pps.org. This is read from the text; nothing was executed.

Is Zoning And Codes 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 Zoning And Codes use?

Zoning And Codes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Zoning And Codes use?

About 9.5k tokens (SKILL.md is roughly 38k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.

What are the alternatives to Zoning And Codes?

Skills that share tags, products or a category with Zoning And Codes: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 47k stars), C15t (c15t/c15t, 1.9k stars), Contract Review (evolsb/claude-legal-skill, 464 stars) and Legal Clinic Client Intake (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Zoning And Codes?

Abhinavbwj (a GitHub user) maintains it in Abhinavbwj/Urban-Design-Skills-Claude, which has 132 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on March 12, 2026.

Source: Abhinavbwj/Urban-Design-Skills-Claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.