street-design
Provides design standards for pedestrian, cycling, and traffic infrastructure.
Install
mkdir -p .claude/skills/street-design && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11454" && unzip -o skill.zip -d .claude/skills/street-design && rm skill.zipInstalls to .claude/skills/street-design
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Design complete streets with proper cross-sections, lane allocation, pedestrian and cycling infrastructure, intersection design, and streetscape elements using NACTO and global standards. Use when the user asks to design a street, create a cross-section, determine road width, design an intersection, plan a bike lane, design a sidewalk, create a boulevard, design a shared street, plan traffic calming, or specify streetscape elements. Also use for street hierarchy classification, right-of-way allocation, or any question about street dimensions and standards.Key capabilities
- →Classify street hierarchy based on ADT and function
- →Apply contextual modifiers to adjust cross-section priorities
- →Design cross-sections layer by layer from building face to centerline
- →Specify dimensions for frontage, pedestrian, furnishing, cycle, parking, and travel lanes
- →Generate a detailed street design specification
How it works
The skill guides street design by first classifying the street based on ADT and function, then applying contextual modifiers, and finally designing the cross-section layer by layer according to NACTO and global standards.
Inputs & outputs
When to use street-design
- →Design bike lane
- →Cross section planning
- →Street traffic calming
About this skill
Street Design Skill
This skill provides comprehensive street design guidance based on NACTO Urban Street Design Guide, Global Designing Cities Initiative (GDCI), AASHTO Green Book, and international best practices. It covers the full workflow from street hierarchy classification through cross-section dimensioning, intersection design, streetscape specification, and traffic calming.
1. Street Hierarchy Classification
Use the following decision tree to classify any street. Start with the Average Daily Traffic (ADT) count, then apply contextual modifiers.
Primary Classification by ADT and Function
Arterial (>15,000 ADT)
- Right-of-Way (ROW): 30-40m
- Lanes: 2-3 per direction (3.0-3.3m each)
- Design speed: 40-50 km/h (urban), 50-60 km/h (suburban)
- Transit: dedicated bus/BRT lanes strongly recommended
- Cycling: protected bike lanes required (physically separated)
- Pedestrian: wide sidewalks 3.6-6.0m, pedestrian refuge islands at crossings
- Median: 3.0-6.0m landscaped or transit median
- Signal spacing: 200-400m typical
- Role: city-wide movement, connects districts, carries transit trunk routes
Collector (3,000-15,000 ADT)
- ROW: 22-30m
- Lanes: 1-2 per direction (3.0-3.3m each)
- Design speed: 30-40 km/h
- Transit: on-street bus stops with boarding islands
- Cycling: protected bike lanes or buffered bike lanes
- Pedestrian: generous sidewalks 2.4-3.6m
- Median: optional, 1.8-3.0m where present
- Role: connects neighborhoods to arterials, local commercial corridors
Local Street (<3,000 ADT)
- ROW: 15-22m
- Lanes: 1 per direction (2.7-3.0m each)
- Design speed: 30 km/h
- Transit: typically no fixed-route transit
- Cycling: shared lane markings (sharrows) or separated bike lanes depending on context
- Pedestrian: standard sidewalks 1.8-2.4m
- Parking: parallel one or both sides
- Role: neighborhood access, residential frontage, low-speed environment
Shared Street / Woonerf (<1,000 ADT)
- ROW: 8-15m
- Lanes: single surface, no lane markings
- Design speed: 10-20 km/h
- Cycling: shared surface, cyclists and pedestrians together
- Pedestrian: priority over vehicles, no curb separation
- Surface: textured paving, bollards, planters as speed controls
- Role: residential living streets, market streets, festival routes
Pedestrian Priority Street (variable ADT, typically <500)
- ROW: variable (4-20m)
- Vehicles: no through-traffic, emergency and service access only
- Design speed: 5-10 km/h (service vehicles only)
- Surface: high-quality paving, level, no curbs
- Role: retail promenades, civic spaces, historic cores
Contextual Modifiers
Apply these modifiers after primary classification to adjust cross-section priorities:
| Context | Modifier |
|---|---|
| Commercial / Retail | +1.2-2.4m sidewalk width, continuous retail frontage, on-street parking or loading zones, wider furnishing zone for outdoor dining |
| Residential | Prioritize tree canopy coverage (>40%), reduce travel lane widths to minimum, add traffic calming, reduce noise through surface treatment |
| Mixed-Use | Adaptive curbside management (flex zones for parking/loading/transit by time of day), wider pedestrian zones at ground-floor retail |
| Industrial / Logistics | Wider travel lanes (3.3-3.6m) for trucks, larger corner radii, reinforced pavement, limit pedestrian/cyclist exposure to truck movements |
| School Zone | 20-30 km/h speed limit, raised crossings at every intersection, flashing beacons, wide clear sidewalks, no on-street parking within 30m of entrance |
| Hospital / Institutional | Accessible design priority, generous drop-off zones, clear wayfinding, audible pedestrian signals, level surfaces throughout |
| Historic District | Narrower ROW acceptable, special materials and furnishings, heritage lighting, preservation of existing tree canopy and setbacks |
| Waterfront / Park Edge | Wider promenade (4.5-6.0m+), separated multi-use path, enhanced landscape buffer, view corridor preservation |
2. Cross-Section Design Methodology
Design cross-sections layer by layer, working from the building face toward the street centerline. Each layer has a defined function and dimensional range.
Layer Sequence (Building Face to Centerline)
BUILDING FACE
|
|--> [A] Building Setback (context-dependent)
|--> [B] Frontage Zone (0.3 - 0.9m)
|--> [C] Pedestrian Clear Zone (1.8 - 3.6m)
|--> [D] Furnishing / Planting Zone (0.6 - 1.8m)
|--> [E] Cycle Track + Buffer (optional: 1.5-2.5m track + 0.3-0.6m buffer)
|--> [F] Parking Lane (optional: 2.1 - 2.4m parallel, 4.5-5.5m angled)
|--> [G] Travel Lane(s) (3.0 - 3.3m each)
|--> [H] Median (optional: 1.2 - 6.0m)
|
CENTERLINE (mirror layers G through A for opposite side)
Layer Definitions
[A] Building Setback Not part of the public ROW but affects street enclosure. Zero setback for urban retail frontage, 1.5-3.0m for residential, 3.0-6.0m+ for suburban or institutional.
[B] Frontage Zone (0.3 - 0.9m) The strip immediately adjacent to the building face. Accommodates door swings, window displays, awning drip lines, basement vault covers. In commercial areas, may include outdoor dining or merchandise display (with permit, requiring wider dimension of 1.2-2.4m).
[C] Pedestrian Clear Zone (1.8 - 3.6m) The unobstructed walking path. This is the most critical pedestrian dimension. No street furniture, signs, trees, or other obstructions. Minimum 1.8m allows two wheelchairs to pass. Recommended 2.4m for residential, 3.0m for commercial, 3.6m+ for high-volume pedestrian areas. Must comply with ADA/accessibility requirements: maximum cross-slope 2%, smooth and continuous surface.
[D] Furnishing / Planting Zone (0.6 - 1.8m) Contains street trees, light poles, sign posts, parking meters, benches, trash receptacles, bicycle racks, utility access covers. Serves as a buffer between pedestrians and the roadway. Tree wells minimum 1.5m x 1.5m, continuous tree trench preferred. Bioswales and rain gardens can be integrated here.
[E] Cycle Track + Buffer (optional) One-way protected bike lane: 1.5m minimum, 2.0m recommended, 2.5m for high-volume. Two-way cycle track: 2.4m minimum, 3.0m recommended, 3.6m+ for high-volume. Buffer between cycle track and travel/parking lane: 0.3m minimum (painted), 0.6m recommended (with vertical elements such as bollards, planters, or curb).
[F] Parking Lane (optional) Parallel parking: 2.1m minimum, 2.4m recommended (allows door opening without encroaching on bike lane). Angled parking (45-degree): 4.5-5.5m. Angled parking (60-degree): 5.2-5.8m. Perpendicular parking (90-degree): 5.5-6.0m. Consider flex zones: parking by day, loading in morning, outdoor dining in evening.
[G] Travel Lane(s) General travel lane: 3.0m minimum urban, 3.3m standard (NACTO). Bus/transit lane: 3.3-3.6m. Right-turn lane: 2.7-3.0m. Left-turn lane: 3.0-3.3m. Never exceed 3.6m for any urban lane (wider lanes induce higher speeds). Reduce to 2.7m for yield streets and very low-speed environments.
[H] Median (optional) Pedestrian refuge: 1.8m minimum (2.4m with accessibility), allows stroller or wheelchair to wait. Landscaped median: 2.4-6.0m, with trees, ground cover, stormwater management. Transit median: 3.6-5.0m for center-running BRT/LRT with platforms. Left-turn pocket in median: 3.0-3.3m wide, 30-45m long.
Worked Example: Urban Collector Street (26m ROW)
2.4m | 3.0m | 1.2m |2.0m|0.6| 2.4m | 3.0m | 3.0m | 3.0m | 2.4m |0.6|2.0m| 1.2m | 3.0m | 2.4m
Frontage | Ped CZ | Furn |Bike|Buf| Park | Lane | Lane | Lane | Park |Buf|Bike| Furn | Ped CZ | Frontage
| | Zone | | | | EB | EB | WB | | | | Zone | |
BLDG ---+--------+------+----+---+------+------+------+------+------+---+----+------+--------+--- BLDG
Wait -- the above totals to more than 26m. Let me provide a corrected, realistic example:
Worked Example: Urban Collector (26m ROW, Commercial Context)
0.6 | 3.0 | 1.2 | 2.0+0.6 | 2.4 | 3.0 | 3.0 | 2.4 | 0.6+2.0 | 1.2 | 3.0 | 0.6
Front|PedCZ | Furn | Bike+Buf | Park | Lane | Lane | Park | Buf+Bike | Furn | PedCZ|Front
| | Zone | | | EB | WB | | | Zone | |
BLDG-+------+------+----------+------+------+------+------+----------+------+------+-BLDG
= 0.6+3.0+1.2+2.6+2.4+3.0+3.0+2.4+2.6+1.2+3.0+0.6 = 25.6m (~26m)
Worked Example: Residential Local Street (18m ROW)
0.3 | 1.8 | 1.2 | 2.1 | 3.0 | 3.0 | 2.1 | 1.2 | 1.8 | 0.3
Front|PedCZ | Furn | Park | Lane | Lane | Park | Furn | PedCZ|Front
| | Zone | | NB | SB | | Zone | |
BLDG-+------+------+------+------+------+------+------+------+-BLDG
= 0.3+1.8+1.2+2.1+3.0+3.0+2.1+1.2+1.8+0.3 = 17.8m (~18m)
Worked Example: Arterial Boulevard (36m ROW)
0.6 | 3.6 | 1.5 | 2.0+0.6 | 3.3 | 3.3 | 3.3 | 4.8 | 3.3 | 3.3 | 0.6+2.0 | 1.5 | 3.6 | 0.6
Front|PedCZ | Furn | Bike+Buf | Lane | Lane | Lane | Med | Lane | Lane | Buf+Bike | Furn | PedCZ|Front
| | Zone | | EB | EB | EB | | WB | WB | | Zone | |
BLDG-+------+------+----------+------+------+------+------+------+------+----------+------+------+-BLDG
= 0.6+3.6+1.5+2.6+3.3+3.3+3.3+4.8+3.3+3.3+2.6+1.5+3.6+0.6 = 37.9m (~38m, adjust median to 2.9m for 36m)
Worked Example: Shared Street / Woonerf (12m ROW)
1.5 | 9.0 single shared surface | 1.5
Planter| pedestrians + cyclists + vehicles at 15km/h |Planter
zone | textured paving, flush, no curbs, bollards | zone
BLDG---+----------------------------------------------+---BLDG
= 1.5+9.0+1.5 = 12.0m
3. Complete Street Elements Table
Pedestrian Zone Elements
| Element | Minimum | Recommended | Maximum | Notes |
|---|---|---|---|---|
| Sidewalk clear zone (residential) | 1.8m | 2.4m | 3.0 |
Content truncated.
When not to use it
- →When the user needs to design a street without considering NACTO or global standards
- →When the user wants to ignore contextual modifiers for cross-section design
- →When the user wants to bypass the layer-by-layer design methodology
Limitations
- →Based on NACTO Urban Street Design Guide, Global Designing Cities Initiative (GDCI), AASHTO Green Book, and international best practices
- →Requires ADT count for primary classification
- →Cross-section design follows a specific layer sequence
How it compares
This skill provides a structured, standards-based methodology for street design, automating the application of classification, contextual adjustments, and layer-by-layer dimensioning, which is more systematic than ad-hoc design.
Compared to similar skills
street-design side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| street-design (this skill) | 0 | 5mo | No flags | Advanced |
| ui-ux-pro-max | 1,909 | 5mo | Review | Intermediate |
| penpot-uiux-design | 27 | 6mo | Review | Advanced |
| ui-ux-designer | 41 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ui-ux-pro-max
nextlevelbuilder
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
penpot-uiux-design
github
Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing pages, (4) Applying accessibility standards and best practices, (5) Following platform guidelines (iOS, Android, Material Design), (6) Reviewing or improving existing Penpot designs for usability. Triggers: "design a UI", "create interface", "build layout", "design dashboard", "create form", "design landing page", "make it accessible", "design system", "component library".
ui-ux-designer
sickn33
Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.
interactive-portfolio
davila7
Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities. Use when: portfolio, personal website, showcase work, developer portfolio, designer portfolio.
paywall-upgrade-cro
davila7
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," or "in-app pricing." Distinct from public pricing pages (see page-cro) — this skill focuses on in-product upgrade moments where the user has already experienced value.
aesthetic
mrgoonie
Create aesthetically beautiful interfaces following proven design principles. Use when building UI/UX, analyzing designs from inspiration sites, generating design images with ai-multimodal, implementing visual hierarchy and color theory, adding micro-interactions, or creating design documentation. Includes workflows for capturing and analyzing inspiration screenshots with chrome-devtools and ai-multimodal, iterative design image generation until aesthetic standards are met, and comprehensive design system guidance covering BEAUTIFUL (aesthetic principles), RIGHT (functionality/accessibility), SATISFYING (micro-interactions), and PEAK (storytelling) stages. Integrates with chrome-devtools, ai-multimodal, media-processing, ui-styling, and web-frameworks skills.