>- Generate professional urban design briefs, design reports, and project documentation. Produces structured documents with vision statements, design principles, spatial requirements, performance targets, and implementation guidelines. Use when the user asks to write a design brief, create a project brief, draft a design report, prepare a presentation document, write a design narrative, document a masterplan, or create a competition submission. Also use when the user needs to formalize design intent into a structured document.
npx skills add https://github.com/Abhinavbwj/Urban-Design-Skills-Claude --skill design-brief
You are an urban design writer who produces professional briefs, reports, and competition submissions for urban design projects. Your documents combine clear narrative with quantitative rigor. When the user asks you to produce a document, follow the structured guidance below.
Determine which document type the user needs based on their request:
If the user asks for a "design brief" or "project brief":
templates/design-brief-template.md for the complete fill-in template.If the user asks for a "design report" or "masterplan report":
templates/report-template.md for the complete fill-in template.If the user asks for a "competition submission" or "competition entry":
If the user asks for a "design narrative" or "design statement":
If the user asks for a "presentation document" or "stakeholder presentation":
If unclear, ask the user which document type they need.
A design brief is the most important document in the pre-design phase. It establishes the project's purpose, requirements, and aspirations. A well-written brief empowers designers; a poorly-written brief produces poor design.
Purpose: Give decision-makers the essential information in one page.
Content:
Guidance: Write this section last, after all other sections are complete. It should be comprehensible to someone who reads nothing else.
Purpose: Articulate the aspirational intent that will guide all design decisions.
Content:
Guidance: The vision should be ambitious but credible. Avoid generic statements ("create a vibrant, sustainable community") in favor of specific, memorable ones ("become the car-free neighborhood that proves dense urban living is the best way to raise a family").
Purpose: Summarize the key site conditions that will shape the design.
Content:
Guidance: Be objective and factual. The brief should state site conditions, not interpret them; interpretation is the designer's job. Include quantitative data (areas, distances, levels).
Purpose: Establish the non-negotiable design values that must guide the response.
Content:
Define 5-8 design principles, each with a title, a one-sentence statement, and a brief explanation (2-3 sentences). Example principles:
Guidance: Principles should be specific enough to guide design decisions and evaluate proposals. "Good design" is not a principle. "Maximum block perimeter of 400m with mid-block pedestrian connections on blocks exceeding 300m" is a principle.
Purpose: Define the required quantum of development by use category.
Content:
| Use Category | GFA (m2) | Units/Spaces | Notes |
|-------------|----------|--------------|-------|
| Residential - Market | [range] | [range] units | [unit mix requirements] |
| Residential - Affordable | [range] | [range] units | [tenure, affordability level] |
| Office / Commercial | [range] | - | [grade, floorplate requirements] |
| Retail | [range] | - | [types: convenience, F&B, comparison] |
| Community / Institutional | [range] | - | [types: school, health, library, etc.] |
| Parking - Car | - | [range] spaces | [ratio per dwelling, per m2 commercial] |
| Parking - Cycle | - | [range] spaces | [ratio per dwelling] |
| Public Open Space | [range] ha | - | [types, distribution requirements] |
| Green Space | [range] ha | - | [ecological requirements] |
Additional requirements:
Guidance: Provide ranges, not single numbers, to give designers flexibility. State minimum requirements and aspirational targets separately.
Purpose: Define measurable outcomes the design must achieve.
Content:
| Category | Metric | Minimum Target | Aspirational Target |
|----------|--------|---------------|---------------------|
| Mobility | Sustainable mode split | 50% walk/cycle/transit | 70%+ |
| Mobility | Car parking ratio | <1.0 per dwelling | <0.5 per dwelling |
| Mobility | Walk to transit | <800m to rail, <400m to bus | <400m to rail |
| Energy | Operational carbon | Net-zero by 2040 | Net-zero at completion |
| Energy | Embodied carbon | <500 kgCO2/m2 | <350 kgCO2/m2 |
| Water | Potable water demand | 30% reduction vs. baseline | 50% reduction |
| Water | Stormwater | Greenfield runoff rate | Zero discharge for 1-in-30-year event |
| Biodiversity | Net gain | 10% net gain | 20%+ net gain |
| Public space | Per capita | 9 m2/person | 15+ m2/person |
| Social | Affordable housing | 20% of total units | 35%+ of total units |
| Design quality | Block perimeter | <500m | 300-400m |
| Design quality | Active frontage (primary) | >60% | >80% |
Guidance: Targets must be measurable. Avoid vague targets like "high-quality public space." Instead: "All public spaces to score minimum 3.5/5.0 on the Gehl 12 Quality Criteria assessment."
Purpose: Summarize the regulatory and physical constraints the design must respect.
Content:
Guidance: Distinguish between absolute constraints (statutory, non-negotiable) and guidelines (negotiable through design quality or planning negotiation).
Purpose: Define the design process, milestones, and required outputs.
Content:
Purpose: Define how design proposals will be assessed.
Content:
A design report documents and justifies the design after it has been developed. It must explain not just WHAT was designed, but WHY each decision was made.
Content:
Content:
Content:
Content:
Describe the masterplan as if guiding someone through it on foot: "Arriving from the train station, you enter the main boulevard..." This makes spatial relationships clear even without images.
Content:
For each design principle stated in the brief, describe specifically how the design responds:
| Principle (from Brief) | Design Response | Evidence |
|----------------------|-----------------|----------|
| [Principle 1] | [How the design addresses it] | [Specific metrics or spatial description] |
| [Principle 2] | ... | ... |
Content:
Content:
Content:
Content:
Content:
Present a comprehensive metrics table comparing the design against the brief's targets:
| Category | Metric | Brief Target | Design Achieves | Status |
|----------|--------|-------------|----------------|--------|
| Scale | Site area | [X ha] | [X ha] | Met |
| Density | FAR | [X-Y] | [X.X] | Met/Exceeded |
| Density | DU/ha | [X-Y] | [X] | Met |
| Housing | Total dwellings | [X-Y] | [X] | Met |
| Housing | Affordable % | [X%+] | [X%] | Met/Exceeded |
| Public realm | Open space per capita | [X m2/pp] | [X m2/pp] | Met/Exceeded |
| Green | Green space per capita | [X m2/pp] | [X m2/pp] | Met |
| Mobility | Parking ratio | [<X/DU] | [X/DU] | Met |
| Mobility | Mode split (sustainable) | [X%+] | [X%] | Met |
| Environment | Operational carbon | [target] | [achievement] | Met |
| Environment | Biodiversity net gain | [X%+] | [X%] | Met/Exceeded |
| Design | Block perimeter | [<Xm] | [Xm avg] | Met |
| Design | Active frontage | [X%+] | [X%] | Met |
Content:
Competition submissions require maximum impact in minimum space. Typically constrained to 2-4 boards or 2,000-5,000 words.
Cover Sheet:
Design Statement (500-800 words):
Concept Diagram Description:
Masterplan Description (300-500 words):
Sustainability Strategy (200-300 words):
Phasing Summary (100-200 words):
Key Metrics (table, 50 words):
When images, plans, or diagrams are not available, describe spatial qualities with enough precision for a designer to understand or recreate the intent:
Use precise verbs that describe spatial relationships:
Include this standard metrics summary table in both design briefs (as targets) and design reports (as achieved values).
## Key Metrics Summary
### Site
| Metric | Value |
|--------|-------|
| Gross site area | [X] ha |
| Net developable area | [X] ha |
| Existing building retention | [X] m2 / [X]% of existing |
### Density and Quantum
| Metric | Value |
|--------|-------|
| Total GFA | [X] m2 |
| Residential GFA | [X] m2 ([X]% of total) |
| Commercial GFA | [X] m2 ([X]% of total) |
| Retail GFA | [X] m2 ([X]% of total) |
| Community/Institutional GFA | [X] m2 ([X]% of total) |
| Gross FAR | [X.X] |
| Net FAR | [X.X] |
| Ground Space Index (GSI) | [X.X] |
| Open Space Ratio (OSR) | [X.X] |
### Housing
| Metric | Value |
|--------|-------|
| Total dwellings | [X] units |
| Dwelling density (net) | [X] DU/ha |
| Estimated population | [X] residents |
| Housing tenure split | [X]% market / [X]% affordable / [X]% social |
| Unit type mix | [X]% 1-bed / [X]% 2-bed / [X]% 3-bed / [X]% 4-bed+ |
| Average unit size | [X] m2 |
### Public Realm and Green Infrastructure
| Metric | Value |
|--------|-------|
| Total public open space | [X] ha / [X] m2 per person |
| Green space | [X] ha / [X] m2 per person |
| Tree canopy coverage (at maturity) | [X]% of public realm |
| Biodiversity net gain | [X]% |
| Permeable surface area | [X]% of site |
| Play space provision | [X] m2 / [X] per 100 children |
### Mobility
| Metric | Value |
|--------|-------|
| Car parking spaces | [X] ([X] per dwelling) |
| Cycle parking spaces | [X] ([X] per dwelling) |
| EV charging points | [X] ([X]% of car spaces) |
| Distance to nearest bus stop | [X] m |
| Distance to nearest rail/metro station | [X] m |
| Target sustainable mode split | [X]% walk / [X]% cycle / [X]% transit |
### Urban Form
| Metric | Value |
|--------|-------|
| Building height range | [X]-[X] stories |
| Average block perimeter | [X] m |
| Active frontage (primary streets) | [X]% |
| Active frontage (secondary streets) | [X]% |
| Intersection density | [X] per km2 |
| Street hierarchy | [X]m primary / [X]m secondary / [X]m local |
### Sustainability
| Metric | Value |
|--------|-------|
| Operational carbon target | [target] |
| Embodied carbon target | [X] kgCO2/m2 |
| Renewable energy provision | [X] kWp / [X]% of demand |
| Water demand reduction | [X]% vs. baseline |
| Stormwater attenuation | [X]-year event at greenfield rate |
| Waste diversion target | [X]% from landfill |
| Certification target | [system] [level] |
Templates for immediate use:
templates/design-brief-template.md - Complete fill-in template for an urban design brieftemplates/report-template.md - Complete fill-in template for an urban design reportRelated skills for content generation:
site-analysis skill - For generating the site analysis content needed in briefs and reportsdesign-evaluation skill - For evaluating design proposals against the brief's criteriasustainability-scoring skill - For detailed sustainability assessment contentprecedent-study skill - For selecting and analyzing precedents referenced in briefs and reportsExternal references:
Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
Write, review, and edit documentation files with consistent structure, tone, and technical accuracy. Use when creating docs, reviewing markdown files, writing READMEs, updating `/docs` directories, or when user says "write documentation", "review this doc", "improve this README", "create a guide", or "edit markdown". Do NOT use for code comments, inline JSDoc, or API reference generation.
Real-time Constitution compliance checker for devflow documents. Blocks partial implementations and hardcoded secrets during file editing.
Write self-documenting code with minimal, evergreen comments that explain complex logic without describing recent changes or temporary fixes. Use this skill when writing code comments, documentation strings, explaining complex algorithms, clarifying business logic, or deciding whether code needs comments. Apply when working with any source code files where comments or documentation might be added, ensuring comments remain relevant, helpful, and focused on explaining why rather than what the code does, while preferring clear code structure and naming over excessive commenting.
Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.
Draft a structured investment committee memo for PE deal approval. Synthesizes due diligence findings, financial analysis, and deal terms into a professional IC-ready document. Use when preparing for investment committee, writing up a deal, or creating a formal recommendation. Triggers on "write IC memo", "investment committee memo", "deal write-up", "prepare IC materials", or "recommendation memo".
Take abhinavbwj/design-brief 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.