building-spec
Read and apply a project-specific BUILDING_SPEC.md or DIMENSIONS.md file before generating any architectural elements. Use when: generating floor plans, 3D buildings, or any spatial design where the project has defined custom dimensions, room requirements, or design standards.
What this skill does
# Building Spec ## Overview Before generating any building, floor plan, or spatial design, always look for a project-specific specification file. This skill defines the workflow for finding, parsing, and applying custom dimension constraints so that every generated element matches client requirements. When no spec file exists, fall back to defaults from the `architectural-dimensions` skill. ## Instructions ### Step 1: Find the Spec File Search the project root (and parent directories) for any of these filenames: - `BUILDING_SPEC.md` - `DIMENSIONS.md` - `building-spec.md` - `dimensions.md` If found, load it and treat it as ground truth for all dimensions. ### Step 2: Parse the Spec Extract structured parameters from the spec file: - **Units**: metric (meters) or imperial (feet/inches) - **Floor heights**: ground, upper, basement ceiling heights - **Wall thicknesses**: external, load-bearing, partition - **Door dimensions**: main entrance, internal, bathroom (width x height) - **Window dimensions**: sill height, standard size, room-specific overrides - **Room requirements**: minimum area and width per room type - **Special requirements**: accessibility, max height, setbacks, parking ### Step 3: Apply During Generation When generating building geometry: 1. Use spec values as absolute constraints for all dimensions 2. Fill any gaps with defaults (ceiling 2.7 m, exterior wall 0.25 m, partition 0.10 m, door 0.9 m x 2.1 m) 3. Every room must meet the spec minimum area and width 4. All doors and windows must use spec-defined sizes ### Step 4: Validate Against Spec After generation, check every element: - Ceiling heights match spec per level type (ground vs upper) - Wall thicknesses match spec (exterior vs partition) - Door widths meet spec minimums - Room areas meet spec minimums per room type - Any violations must be reported or auto-corrected before output ### Standard BUILDING_SPEC.md Template Projects should create this file in the root directory: ```markdown # Building Dimensions Specification ## Project Information - **Project name:** [Your Project Name] - **Standard:** Metric (meters) | Imperial (feet/inches) - **Building type:** Residential | Commercial | Mixed-use ## Floor Heights - Ground floor: 2.7m - Upper floors: 2.7m - Basement: 2.4m ## Wall Thicknesses - External walls: 0.25m - Internal load-bearing: 0.20m - Internal partitions: 0.10m ## Doors - Main entrance: 1.0m wide x 2.1m tall - Standard internal: 0.9m x 2.1m - Bathroom: 0.8m x 2.1m ## Windows - Standard sill height: 0.9m from floor - Standard window: 1.2m wide x 1.2m tall ## Room Requirements | Room | Min Area | Min Width | |------|----------|-----------| | Bedroom | 10m2 | 2.7m | | Master bedroom | 16m2 | 3.2m | | Kitchen | 8m2 | 2.4m | | Bathroom | 4m2 | 1.5m | | Living room | 20m2 | 3.5m | | Corridor | -- | 1.0m | ``` ### Default Fallback Values When no spec file is found, use these defaults: | Parameter | Value | |---|---| | Ceiling height (ground/upper) | 2.7 m | | Ceiling height (basement) | 2.4 m | | External wall | 0.25 m | | Partition | 0.10 m | | Main entrance door | 0.9 m x 2.1 m | | Bathroom door | 0.8 m x 2.1 m | | Window sill height | 0.9 m | | Standard window | 1.2 m x 1.2 m | | Bedroom min area | 10 m2 | | Kitchen min area | 8 m2 | | Living room min area | 20 m2 | | Corridor min width | 1.0 m | ## Examples ### Example 1: Generate a Building from a Custom Spec A project has `BUILDING_SPEC.md` with ground floor height 3.5 m (retail), upper floors 2.7 m, external walls 0.30 m, and minimum bedroom area 12 m2. 1. Find spec: `BUILDING_SPEC.md` exists in project root 2. Parse: ground=3.5 m, upper=2.7 m, ext_wall=0.30 m, bedroom_min=12 m2 3. Generate: ground floor level with 3.5 m ceiling, 0.30 m exterior walls, all bedrooms >= 12 m2 4. Validate: check each element against spec values 5. Result: all rooms meet custom minimums, ground floor has retail-height ceiling ### Example 2: Validate an Existing Model Against Spec A model has a bedroom at 9 m2 but the spec requires minimum 10 m2: 1. Load spec: bedroom min area = 10 m2 2. Scan model rooms: bedroom R-bed2 has area 9.0 m2 3. Violation detected: "Room Bedroom 2: area 9.0 m2 < spec minimum 10 m2" 4. Auto-fix: expand room width from 2.5 m to 2.8 m, increasing area to 11.2 m2 5. Re-validate: all rooms now pass ### Example 3: No Spec File Found No `BUILDING_SPEC.md` or `DIMENSIONS.md` in the project: 1. Search project root and parent directories -- not found 2. Fall back to default values (2.7 m ceiling, 0.25 m ext wall, 0.10 m partition) 3. Generate using defaults from the `architectural-dimensions` skill 4. Validate against standard minimums ## Guidelines - Always search for a spec file before generating any architectural elements - Spec values override all defaults -- treat the spec as ground truth - If a spec value is missing for a particular element, use the default fallback - Report all spec violations as errors, not warnings - Pair this skill with `architectural-dimensions` for comprehensive validation - When creating a new project, generate the `BUILDING_SPEC.md` template for the client to fill in - Keep spec files in the project root for easy discovery
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.