abhinavbwj/site-analysis
>- Conduct comprehensive multi-scale site analysis from regional to neighborhood to site scale. Generates structured analysis reports covering physical context, infrastructure, demographics, environmental conditions, regulatory framework, and design opportunities and constraints. Use when the user asks to analyze a site, understand site context, assess a location for development, conduct due diligence on a parcel, evaluate site conditions, create a site analysis report, or study the urban context of a project area. Covers topography, hydrology, vegetation, solar and wind analysis, noise mapping, infrastructure audit, zoning review, circulation analysis, visual assessment, SWOT analysis, and stakeholder mapping.
npx skills add https://github.com/Abhinavbwj/Urban-Design-Skills-Claude --skill site-analysis
Comprehensive multi-scale site analysis for urban design and architectural
projects. This skill guides the systematic evaluation of a site and its context
across three nested scales, twelve analytical layers, and a structured synthesis
framework that translates raw data into actionable design implications.
Every site exists within nested contexts. Effective analysis moves from the
broad regional frame down to the specific parcel, ensuring that no critical
external force is overlooked before design begins.
START
|
v
Is the project a masterplan, new neighborhood, or infrastructure project?
YES --> Conduct FULL three-scale analysis (Regional + Neighborhood + Site)
NO --> Continue
|
v
Is the project an infill building, renovation, or single-parcel development?
YES --> Conduct TWO-SCALE analysis (Neighborhood + Site)
NO --> Continue
|
v
Is the project an interior renovation or tenant fit-out?
YES --> Conduct SITE-SCALE analysis only (immediate context + parcel)
NO --> Default to TWO-SCALE analysis
Purpose: Understand the site's position within metropolitan systems.
their capacity/planned upgrades. Identify the site's travel-time isochrones
to major employment centers (15 min, 30 min, 60 min by car and transit).
hospital anchors, innovation districts, and economic development zones.
landscapes, green belts, agricultural land, air quality zones, and climate
risk areas (sea-level rise, wildfire, seismic).
authorities, tax increment financing zones, enterprise zones.
declining industrial area, or a rural fringe? What regional plans affect it?
Purpose: Map the immediate urban fabric the project must integrate with.
intersection density (target: >100 per km2 for walkable areas), block size
distribution, and connectivity index.
frontage, location of institutional anchors, vacant or underutilized parcels.
income brackets, ethnic diversity, education attainment within the walkshed.
stops. Map 5-minute (400 m) and 10-minute (800 m) walksheds to each.
character, era of development, and perceived identity. Name each area.
Purpose: Document every physical and perceptual attribute of the land itself.
elevation range, slope and aspect, soil type, bearing capacity.
water body). Note edge conditions: hard/soft, public/private, active/passive.
new access points, visibility from approaching routes.
and summer solstice at 9:00, 12:00, and 15:00. Wind exposure vs. shelter.
Identify frost pockets, heat traps, and comfortable outdoor zones.
views IN to the site from public vantage points. Note landmark visibility.
structures, foundations, contamination history, demolition requirements.
Follow this 10-step sequential workflow. Each step builds upon the previous.
Do not skip steps; mark any step "Not Applicable" with justification if data
is unavailable.
centroid, adjusted for barriers like highways or rivers).
or the commuter catchment, whichever is more relevant).
Classify: 0-2% flat, 2-5% gentle, 5-10% moderate, 10-15% steep,
>15% very steep. Map aspect (N/S/E/W facing).
500-year), drainage direction, watershed boundaries, groundwater depth.
diameter >30 cm), protected habitats, invasive species.
bedrock depth, seismic classification.
projected demand. Fire flow requirements.
Note combined vs. separate storm sewer.
planned upgrades. Assess renewable energy potential.
proximity for smart building applications.
waste-to-energy or renewable energy sources.
special permit), density limits (FAR and units/hectare), height limits,
setback requirements, parking minimums/maximums.
code, accessibility code.
protection, transit-oriented development, planned unit development.
status, archaeological potential.
future land use designation, infrastructure improvement plans.
at 9:00, 12:00, and 15:00 local time. Calculate hours of direct sunlight
on site at winter solstice (critical for northern/southern latitudes).
wind direction by season. Note wind speed distribution. Identify potential
channeling effects from surrounding buildings or topography.
industrial). Estimate noise levels at site boundary in dB(A). Note any
noise ordinance thresholds.
sources of pollution. Note prevailing wind direction relative to sources.
and 500-year flood extents on site plan.
projected), age distribution, household size, ethnic composition.
rate, comparison to metro median.
median rent, housing cost burden (% spending >30% on housing).
share), job-housing balance ratio.
area over 5, 10, and 20 years from official planning documents.
LOS at key intersections, planned road projects, speed limits.
crossing facilities, pedestrian counts if available, Walk Score.
bike share stations, Bike Score, planned cycling projects.
ridership, distance to nearest stop/station, Transit Score, planned
service changes or new lines.
access, emergency vehicle access.
the primary approach routes to the site. Document the sequence of existing
views, enclosure, deflection, and anticipation.
the site. Note any protected view corridors.
Document prevailing materials, colors, heights, setbacks, roof forms.
(parks, waterfronts), and transition zones. Map gateways and nodes.
this place distinctive? What should be preserved, enhanced, or transformed?
neighborhood study area.
districts, advocacy groups, cultural organizations.
environmental agencies, utilities, economic development office.
institutions, cultural institutions within the study area.
on development, relevant referenda or ballot measures.
response, categorized as:
Each of the 12 analysis layers below follows a consistent structure: what data
to collect, what questions to answer, what metrics to apply, and how to
synthesize findings into design implications.
What is the dominant aspect? Are there ridgelines or valleys that create
natural drainage or view corridors?
Cut-and-fill volume estimate for level pad scenarios.
stepped foundations or retaining walls; >15% should be preserved as open
space or used for dramatic architectural expression. South-facing slopes
(northern hemisphere) receive more solar energy. Ridgelines offer views
but wind exposure; valleys offer shelter but potential flooding.
centerlines, groundwater monitoring data, stormwater infrastructure maps.
direction? Where does stormwater go? What is groundwater depth?
(hectares), groundwater depth below grade, required stormwater detention
volume per local code (typically 10-25 mm for first flush).
groundwater limits basement construction. Stormwater management can become
an amenity (rain gardens, bioswales, constructed wetlands). Riparian
buffers (typically 15-30 m from waterways) must be maintained.
habitat maps, protected species records.
significant trees or habitats that must be protected? Are there ecological
corridors that should be maintained or created?
biodiversity index, ecological connectivity score.
retained where possible (each large tree provides ~$50-100/year in
ecosystem services). Ecological corridors should be at least 10 m wide to
be functional. Green infrastructure targets: 30% canopy cover, 15%
permeable surface for new development.
site latitude, wind rose data, temperature and humidity records.
are prevailing wind directions by season? Where are sheltered zones? Where
are heat traps? What is the heating/cooling degree day balance?
direction, annual temperature range, heating degree days, cooling degree
days, annual precipitation, design storm intensity.
west street orientation maximizes south-facing frontage in northern
hemisphere). Shelter outdoor spaces from prevailing cold-season winds.
Use building mass to create wind shadows for plazas and parks. Maximize
cross-ventilation in cooling-dominated climates.
maps and schedules (GTFS), cycling network maps, pedestrian counts.
congestion points? What is the pedestrian quality of surrounding streets?
What transit frequency serves the site?
(vehicles/hour), Walk Score, Transit Score, Bike Score, distance to
nearest transit stop (m), parking supply ratio (spaces per 1000 m2).
justifies reduced parking ratios. High ADT roads (>15,000) create noise
and air quality barriers requiring building setbacks or noise walls.
Pedestrian connectivity gaps reveal opportunities for new connections.
from utility providers, planned capital improvement projects.
What upgrades are needed? What are the connection costs? Are there any
easements or restrictions?
(liters/day), electrical capacity (kVA), broadband speed (Mbps),
estimated connection/upgrade costs.
feasible density. Sewer capacity is frequently the binding constraint.
On-site systems (water recycling, solar+storage, package treatment plants)
can supplement limited municipal capacity. Utility easements may constrain
building footprints.
use map, overlay district maps, recent variance and rezoning records.
approval? Is the comprehensive plan consistent with current zoning? Are
there pending changes that could affect the project?
required setbacks (front/side/rear in meters), min parking ratio, max lot
coverage (%), min open space (%).
zoning capacity (max FAR x lot area) with the program requirement. If
the program exceeds zoning, a variance or rezoning strategy is needed.
Overlay districts may impose additional design review or restrictions.
condition, assessed value), heritage listings, land use per parcel.
height, setback, and lot coverage? What is the condition of existing
structures? Are there heritage constraints?
average lot coverage (%), building age distribution, vacancy rate (%),
heritage listing density.
and character. Identify transition zones where height changes are needed.
Vacant or underutilized parcels may present consolidation opportunities.
Heritage buildings constrain demolition but can anchor neighborhood
identity.
equivalent, economic development reports, housing market data.
is the income profile? Is there housing affordability stress? What are the
commute patterns?
housing cost burden (%), poverty rate (%), age dependency ratio, mode
share for commuting, jobs-housing ratio.
needs playgrounds; aging population needs accessible design). Income data
informs affordability requirements and market positioning. Commute
patterns inform parking and transit investment priorities.
inventories, indigenous land acknowledgment records, local history sources.
the site in a conservation area? Is there archaeological potential? What
cultural narratives are associated with this place?
area status (yes/no), archaeological potential (high/medium/low/none).
facade retention, or impose design review. Archaeological potential may
require pre-construction investigation and can delay timelines. Cultural
narratives should inform placemaking and public art strategies.
viewshed analysis from key vantage points, streetscape measurements.
the key views to protect or create? What is the sense of enclosure on
surrounding streets? Where are the gateways and nodes?
sky exposure plane, viewshed area from key points, number of landmark
views, streetscape width composition (building-sidewalk-road-sidewalk-
building in meters).
for most urban streets. Landmark views should be protected through height
controls and view corridors. Gateways mark transitions and should be
architecturally expressed. Serial vision analysis reveals the experiential
sequence that new development should enhance.
data, economic forecasts, feasibility benchmarks.
achievable rents and sale prices? What is the development pipeline? Is
there a gap in supply for any use type?
retail rent ($/m2/year), residential rent ($/month/unit), capitalization
rates by use type, development pipeline (m2 by use type), absorption
rate (m2/year).
Oversupplied uses should be minimized. Undersupplied uses represent
opportunities. Achievable rents determine feasible construction quality
and affordable housing contribution capacity.
Solar geometry varies dramatically by latitude. The table below provides solar
altitude angles at solar noon for key latitudes at solstices and equinoxes.
Use these to calculate shadow lengths and solar access.
| Latitude | Winter Solstice (noon) | Equinox (noon) | Summer Solstice (noon) |
|----------|----------------------|-----------------|------------------------|
| 0 (Equator) | 66.5 deg | 90.0 deg | 66.5 deg |
| 23 (Tropics) | 43.5 deg | 67.0 deg | 90.0 deg |
| 35 (Subtropics) | 31.5 deg | 55.0 deg | 78.5 deg |
| 45 (Mid-latitude) | 21.5 deg | 45.0 deg | 68.5 deg |
| 55 (High latitude) | 11.5 deg | 35.0 deg | 58.5 deg |
Shadow length formula: Shadow Length = Object Height / tan(solar altitude)
Example: A 20 m building at latitude 45 at winter solstice noon casts a shadow
of 20 / tan(21.5) = 20 / 0.394 = 50.8 m.
Key analysis times: Evaluate shadows at 9:00, 12:00, and 15:00 on:
Solar access rule of thumb: Ensure that outdoor spaces and south-facing
facades receive at least 2 hours of direct sunlight at winter solstice. This
is a common planning standard in many jurisdictions (e.g., BRE guidelines in
the UK specify 2+ hours on March 21).
meteorological station (ideally within 10 km and at similar elevation).
Disaggregate by season. Identify the dominant wind direction, the secondary
wind direction, and the calm frequency.
(Venturi effect). If prevailing wind aligns with a street canyon or building
gap, expect wind speeds to increase by 20-50% at the gap.
shadows extending approximately 5-10x their height on the leeward side.
Porous screens (e.g., perforated walls, deciduous trees) are more effective
than solid barriers because they reduce turbulence.
high wind speeds at ground level. Buildings over 25 m should include wind
mitigation measures (canopies, podiums, setbacks at upper levels).
Classify the site and its surroundings into microclimate zones:
below the base flood elevation (BFE) plus freeboard (typically 0.3-0.6 m).
low points where ponding will occur. Size on-site detention to local code
(typically detain the first 15-25 mm of rainfall on site).
development. Use bioswales, rain gardens, permeable paving, and green roofs
to manage stormwater at source.
approximately 68 dB(A) at 15 m distance. Each doubling of distance reduces
noise by approximately 3 dB in open conditions, 6 dB in urban canyons.
45 dB(A) nighttime (WHO guidelines). Outdoor amenity spaces target
50-55 dB(A).
noise by 5-15 dB. Sealed facades with mechanical ventilation can achieve
25-35 dB reduction.
from highways with >100,000 ADT for sensitive uses like schools and
housing). Industrial sources require case-by-case assessment.
station. Compare to WHO guidelines (PM2.5: 5 ug/m3 annual mean; NO2:
10 ug/m3 annual mean).
convenience -- transit stops, corner shops, playgrounds. Calculate using
network distance (not Euclidean) along the pedestrian network.
for most trips -- schools, supermarkets, parks, community facilities.
to generate isochrones. Exclude routes that cross barriers without
crossings (highways, rail lines). Penalize steep slopes (reduce effective
speed by 10% for each 5% gradient over 5%).
gaps -- directions with no grocery store, park, or transit within 800 m.
Compute a composite transit accessibility score:
Transit Score = SUM over each route [
(Service frequency in vehicles/hour)
x (Capacity weighting: heavy rail=3, light rail=2, BRT=1.5, bus=1)
x (Walk distance decay: 1.0 if <400m, 0.5 if 400-800m, 0 if >800m)
]
Interpretation:
Evaluate sight distances at each (min 45 m for 50 km/h roads, 90 m for
70 km/h roads). Note any turn restrictions or median barriers.
within 200 m. Note pricing and time limits. Estimate current utilization
(survey at 10:00 for commercial, 22:00 for residential).
demand benchmarks. Build the case for parking reduction if transit access
supports it. Consider shared parking between uses with complementary peaks.
classified as: protected bike lane, painted bike lane, shared lane/
sharrow, shared-use path, or no facility.
the site. These are opportunities for developer-funded improvements.
residential (secure, covered) and 1 short-term space per 500 m2 retail
(visible, accessible).
1 per 2,500 m2, retail: 1 per 500 m2, residential: 0.1 per unit).
compactor) and required truck access (minimum 3.5 m width, 4.5 m height,
12 m turning radius for standard refuse vehicles).
building points (typical fire code requirement). Minimum 6 m clear width
for fire lanes.
The site analysis report should follow the standardized template located at:
templates/site-analysis-report.md
The template provides a complete report structure with the following sections:
When generating a report, populate every section with site-specific data. Use
quantitative metrics wherever possible. Include specific numbers, distances,
areas, and measurements rather than vague qualitative statements.
Detailed definitions, data requirements, analysis methods, output formats, and
design decision connections for all 12 analysis layers are documented in:
references/analysis-layers.md
This reference provides the complete analytical framework including:
A comprehensive directory of open data sources organized by category, including
GIS portals, census databases, transportation data, environmental data,
property records, and analysis tools is maintained in:
references/data-sources.md
This reference covers:
references/data-sources.md to identifyavailable data for the project location.
references/analysis-layers.md for thestandardized method and output format.
templates/site-analysis-report.md to structure the final deliverable.from the intersection of multiple layers (e.g., slope + drainage + flood
risk, or transit access + demographics + market demand).
Take abhinavbwj/site-analysis from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.