Stats
Actions
Tags
From computational-design-skills
Delivers foundational paradigms like parametric and generative design, pioneers, tools landscape, core concepts, and skill routing for AEC computational design tasks. Auto-activates on detection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/computational-design-skills:cd-foundationsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill auto-activates whenever a computational design context is detected. It provides the foundational knowledge layer, paradigm classification, tool routing, and anti-pattern awareness that underpins every other skill in the Computational Design Skills Plugin.
This skill auto-activates whenever a computational design context is detected. It provides the foundational knowledge layer, paradigm classification, tool routing, and anti-pattern awareness that underpins every other skill in the Computational Design Skills Plugin.
Computational design is not a single methodology but a spectrum of interrelated paradigms. Each paradigm carries distinct assumptions about the relationship between the designer, the algorithm, and the artifact. Understanding which paradigm applies to a given problem is the first critical decision in any computational design workflow.
Definition: Parametric design establishes explicit relationships between design elements through variable parameters and constraints, enabling the exploration of a continuous design space by adjusting input values. The geometry is not drawn; it is described as a system of dependencies.
Key Characteristics:
When to Use: When the design problem has well-defined variables and the goal is to explore a constrained solution space — e.g., facade panel optimization, structural member sizing, massing studies with fixed programmatic requirements, and any scenario where rapid iteration across known parameters is valuable.
Definition: Generative design delegates part of the design ideation to algorithmic processes that produce novel solutions based on goals, constraints, and evaluation criteria. The designer defines the problem space and fitness criteria; the algorithm proposes solutions the designer may not have conceived.
Key Characteristics:
When to Use: When the solution space is too large for manual exploration, when multiple conflicting objectives must be balanced (structural performance vs. daylighting vs. cost), when design innovation is prioritized over predictability, or when the problem can be meaningfully quantified.
Definition: Algorithmic design uses step-by-step computational procedures — loops, conditionals, recursion, data transformations — to generate or manipulate geometry and spatial configurations. It treats design as a computational process expressible in code or visual programming.
Key Characteristics:
When to Use: When the design can be described by a set of rules or procedures — e.g., space allocation by adjacency matrix, facade patterning by rule sets, urban block generation from regulatory codes, structural branching systems, or any design task that benefits from codified logic.
Definition: Data-driven design integrates real-world datasets — environmental, demographic, geospatial, behavioral, sensor-based — directly into the design process, allowing external information to inform or drive geometric and spatial decisions.
Key Characteristics:
When to Use: When site-specific conditions must directly inform design — e.g., solar exposure driving facade design, wind data informing massing, population density shaping program distribution, traffic data determining access points, or sensor data driving adaptive building systems.
Definition: Performance-driven design places quantifiable performance metrics — structural efficiency, energy consumption, daylight autonomy, acoustic quality, thermal comfort — at the center of the design process, using simulation feedback loops to iteratively refine form and materiality.
Key Characteristics:
When to Use: When building performance is a primary driver — e.g., net-zero energy targets, structural weight minimization, acoustic optimization for concert halls, daylight optimization for workplaces, wind comfort in urban canyons, or any project where quantifiable metrics must be met or optimized.
The following table provides a rapid lookup of the most influential figures in computational design. For detailed biographies, projects, and publications, see references/pioneers-and-movements.md.
| # | Name | Key Contribution | Primary Domain | Relevance to Practice |
|---|---|---|---|---|
| 1 | Patrik Schumacher | Parametricism manifesto; codified parametric design as an architectural movement and style | Architectural Theory, Parametric Design | Provided theoretical framework for parametric architecture as a unified design language for the 21st century |
| 2 | Greg Lynn | Animate Form (1999); pioneered blob architecture and calculus-based form generation | Digital Morphogenesis | Introduced time-based, force-driven form generation to architecture; catalyzed NURBS-based design |
| 3 | Neri Oxman | Material Ecology; multi-material 3D printing; biology-informed computational fabrication | Material Computation, Bio-Design | Bridged computational design, biology, and material science; redefined fabrication paradigms |
| 4 | Achim Menges | ICD/ITKE Stuttgart research pavilions; material computation; robotic fabrication | Material Computation, Fabrication | Demonstrated that material behavior and fabrication constraints can drive design form generation |
| 5 | Mark Burry | Digital completion of Sagrada Familia; pioneered practical application of parametric modeling to complex geometry | Parametric Modeling, Heritage | Proved parametric tools could resolve geometries impossible to build by traditional means |
| 6 | Zaha Hadid | Parametric architecture at building and urban scale; fluid formal language through computational methods | Parametric Architecture | Demonstrated computational design at the highest level of architectural practice and cultural ambition |
| 7 | Toyo Ito | Algorithmic structural systems; Sendai Mediatheque; Serpentine Pavilion algorithm | Algorithmic Structure | Showed how algorithmic thinking produces structurally innovative, spatially rich architecture |
| 8 | Cecil Balmond | Informal structural design; non-linear structural logic; collaboration with OMA, Toyo Ito | Structural Design | Redefined structural engineering as a creative, algorithmic discipline inseparable from architecture |
| 9 | Frei Otto | Form-finding with physical models (soap films, hanging chains); Institute for Lightweight Structures | Form-Finding, Minimal Surfaces | Established the foundational methods of form-finding that digital tools now simulate computationally |
| 10 | Buckminster Fuller | Geodesic domes; tensegrity structures; synergetics; design science | Structural Systems, Systems Thinking | Pioneered systematic, geometry-driven approaches to structural efficiency at every scale |
| 11 | Sergio Musmeci | Ponte sul Basento; sculptural structural form-finding through physical and mathematical models | Structural Art | Demonstrated that structural optimization produces forms of extraordinary beauty and efficiency |
| 12 | Mike Weinstock | Morphogenetic design theory; Emergence and Design Group at AA | Morphogenetic Design, Theory | Provided theoretical framework connecting biological morphogenesis to architectural design processes |
| 13 | Skylar Tibbits | Self-Assembly Lab MIT; 4D printing; programmable materials | Self-Assembly, Smart Materials | Extended computational design into time-based material behavior and autonomous construction |
| 14 | Mario Carpo | The Digital Turn in Architecture (2012); The Second Digital Turn (2017); historiography of digital design | Theory, History | Articulated the cultural and epistemological implications of computational design for architecture |
| 15 | Antoine Picon | Digital Culture in Architecture; Smart Cities: A Spatialised Intelligence | Theory, Digital Culture | Connected computational design to broader cultural, political, and philosophical frameworks |
| 16 | Kostas Terzidis | Algorithmic Architecture (2006); Expressive Form; rigorous computational approaches to design | Algorithmic Design, Theory | Provided rigorous definitions distinguishing algorithmic, parametric, and computational design |
| 17 | Branko Kolarevic | Architecture in the Digital Age (2003); digital manufacturing and mass customization | Digital Fabrication | Documented and theorized the link between digital design and digitally controlled manufacturing |
| 18 | Philippe Block | Block Research Group ETHZ; funicular structures; 3D graphic statics; COMPAS framework | Structural Design, Form-Finding | Revived and digitized graphic statics; enabled unreinforced masonry shell design through computation |
| 19 | Sigrid Adriaenssens | Form-finding and structural optimization; computational mechanics for thin shells | Structural Optimization | Advanced computational methods for form-finding of structurally efficient thin-shell structures |
| 20 | Caitlin Mueller | Digital Structures Group MIT; structural optimization; machine learning for structural design | Structural Optimization, ML | Pioneered the integration of machine learning with structural design optimization for early-stage design |
| 21 | Michael Hansmeyer | Computational architecture and ornament; subdivided columns; Grotto project | Algorithmic Ornament | Demonstrated that computation enables geometric complexity far beyond human manual capacity |
| 22 | Jenny Sabin | Jenny Sabin Studio; material research through knitting and weaving; bio-inspired pavilions | Material Computation, Textiles | Bridged textile fabrication, biology, and computational design at architectural scale |
| 23 | Ronald Rael | Emerging Objects; large-scale 3D printing with sustainable materials (clay, salt, cement) | Additive Manufacturing | Pioneered sustainable material palettes for large-scale architectural 3D printing |
The computational design tools ecosystem spans parametric modeling, simulation, fabrication, and interoperability. For detailed tool descriptions, version info, and workflows, see references/tools-ecosystem.md.
| Tool | Platform | Primary Use | Learning Curve (1-5) | Community Size | Notes |
|---|---|---|---|---|---|
| Grasshopper | Rhino 7/8 | Visual parametric modeling, algorithmic design | 3 | Very Large | De facto standard for computational design in architecture |
| Dynamo | Revit, Civil 3D, Advance Steel | BIM automation, parametric modeling within Revit | 3 | Large | Tightly integrated with Autodesk BIM ecosystem |
| Marionette | Vectorworks | Parametric modeling within Vectorworks | 2 | Small | Python-based; good for Vectorworks-centric firms |
| GenerativeComponents | Bentley MicroStation | Parametric infrastructure and building design | 4 | Small | Strong in infrastructure; less common in architecture |
| Houdini | Standalone (SideFX) | Procedural modeling, simulation, VFX-grade geometry | 5 | Medium (growing in AEC) | Extremely powerful procedural engine; steep learning curve |
| Tool | Platform | Primary Use | Learning Curve (1-5) | Community Size |
|---|---|---|---|---|
| Grasshopper | Rhino | Full visual programming for geometry and data | 3 | Very Large |
| Dynamo | Revit | Visual programming for BIM workflows | 3 | Large |
| Sverchok | Blender | Parametric geometry nodes for Blender | 3 | Medium |
| Geometry Nodes | Blender 3.0+ | Native procedural geometry system in Blender | 3 | Large (growing) |
| Nodes | Various | General-purpose visual programming | 2 | Small |
| Tool | Platform | Primary Use | Learning Curve (1-5) | Community Size |
|---|---|---|---|---|
| Ladybug | Grasshopper, Dynamo | Weather data visualization, sun path, radiation | 3 | Large |
| Honeybee | Grasshopper, Dynamo | Energy modeling (EnergyPlus/OpenStudio), daylight (Radiance) | 4 | Large |
| Butterfly | Grasshopper | CFD simulation (OpenFOAM wrapper) | 4 | Medium |
| Dragonfly | Grasshopper | Urban-scale energy modeling, urban heat island | 4 | Medium |
| ClimateStudio | Rhino | Annual daylight, thermal, glare simulation | 3 | Medium |
| DIVA for Rhino | Rhino | Daylight and energy modeling | 3 | Medium |
| Eddy3D | Grasshopper | Real-time CFD for wind analysis | 3 | Small |
| Tool | Platform | Primary Use | Learning Curve (1-5) | Community Size |
|---|---|---|---|---|
| Karamba3D | Grasshopper | Interactive structural FEA for parametric models | 4 | Medium |
| Millipede | Grasshopper | Topology optimization | 3 | Small |
| Kangaroo | Grasshopper | Physics simulation, form-finding, dynamic relaxation | 3 | Large |
| Galapagos | Grasshopper | Evolutionary solver (single/dual objective) | 2 | Large (built-in) |
| Ameba | Grasshopper, Rhino | Topology optimization for architecture | 3 | Small |
| BESO | Various | Bi-directional evolutionary structural optimization | 4 | Small |
| Colibri | Grasshopper | Design space exploration and data capture | 2 | Medium |
| Opossum | Grasshopper | Model-based optimization (RBF surrogate) | 3 | Small |
| Tool | Platform | Primary Use | Learning Curve (1-5) | Community Size |
|---|---|---|---|---|
| HAL Robotics | Grasshopper | Industrial robot programming (ABB, KUKA, UR) | 4 | Medium |
| KUKA|prc | Grasshopper | KUKA robot programming and simulation | 4 | Medium |
| Robots | Grasshopper | Multi-brand robot programming | 3 | Small |
| Silkworm | Grasshopper | Custom G-code generation for 3D printing | 3 | Small |
| Taco | Grasshopper | IFC import/export for BIM interop | 2 | Small |
| Elefront | Grasshopper | Baking management, attribute handling | 2 | Medium |
| Pufferfish | Grasshopper | Tweens, morphing, blending geometry | 2 | Medium |
| Tool | Platform | Primary Use | Learning Curve (1-5) | Community Size |
|---|---|---|---|---|
| Speckle | Multi-platform | Open-source data exchange and collaboration | 2 | Large (growing) |
| Rhino.Inside | Revit, others | Embed Rhino/Grasshopper inside Revit and other apps | 3 | Medium |
| BHoM | Multi-platform | Buildings and Habitats object Model; open interop | 4 | Medium |
| IFC.js | Web | IFC parsing and visualization in browser | 3 | Medium |
| xBIM | .NET | IFC toolkit for BIM development | 4 | Medium |
| IfcOpenShell | Python | Open-source IFC geometry engine and parser | 3 | Medium |
| Tool | Platform | Primary Use | Learning Curve (1-5) | Community Size |
|---|---|---|---|---|
| LunchBox | Grasshopper | Paneling, data management, ML basics | 2 | Large |
| Elk | Grasshopper | OpenStreetMap data import, GIS mapping | 2 | Medium |
| Heron | Grasshopper | GIS data import (rasters, shapefiles) | 2 | Medium |
| TT Toolbox | Grasshopper | Data management, geometry utilities | 2 | Medium |
| Owl | Grasshopper | Machine learning integration (Accord.NET) | 4 | Small |
| Brain | Grasshopper | Neural network training inside Grasshopper | 3 | Small |
| Lark | Grasshopper | Spectral daylight analysis | 3 | Small |
| Decoding Spaces | Grasshopper | Urban analysis (isovist, visibility, network) | 3 | Small |
For in-depth explanations and mathematical foundations, see references/core-concepts.md.
| Concept | Definition | AEC Example |
|---|---|---|
| List | Ordered collection of items accessible by index | A list of floor-to-floor heights for a tower: {3.5, 3.2, 3.2, 3.0, 3.0, ...} |
| Data Tree | Hierarchical, nested list structure unique to Grasshopper | Building floors (branches) containing rooms (items per branch) |
| Dictionary | Key-value pairs for named data access | Room names mapped to areas: {"Office A": 45.2, "Meeting": 22.0} |
| Graph | Nodes and edges representing relationships | Spatial adjacency graph: nodes = rooms, edges = required adjacencies |
| Mesh | Vertices, edges, faces topology for surface representation | Building envelope represented as quad mesh for panelization |
| Concept | Definition | AEC Relevance |
|---|---|---|
| NURBS | Non-Uniform Rational B-Splines; smooth curves/surfaces defined by control points, knots, degree | Free-form facade geometry, complex roof surfaces, organic massing |
| Degree | Polynomial degree of a NURBS curve (1=linear, 2=arc-like, 3=smooth) | Controls curvature continuity at joints; degree 3 standard for smooth surfaces |
| Control Points | Points that influence (but don't lie on) a NURBS curve/surface | Adjusting control points reshapes geometry without breaking continuity |
| Knot Vector | Sequence controlling parameter distribution along a NURBS curve | Determines where control points have most influence; uniform vs. non-uniform |
| Boolean Operations | Union, difference, intersection of solid volumes | Combining building masses, cutting openings, creating floor plates from massing |
| Voronoi Diagram | Partition of space into regions closest to each seed point | Floor plan subdivision, facade paneling patterns, structural diagrid generation |
| Delaunay Triangulation | Triangulation maximizing minimum angle; dual of Voronoi | Terrain mesh generation, structural surface triangulation, point cloud meshing |
| Subdivision Surfaces | Iterative mesh refinement for smooth surfaces (Catmull-Clark, Loop) | Smooth facade panels from coarse control meshes; organic form generation |
| UV Space | 2-parameter coordinate system on a surface (0-1 range in each direction) | Mapping patterns, panels, or analysis results onto curved surfaces |
| Concept | Definition | AEC Relevance |
|---|---|---|
| Genetic Algorithm | Evolutionary search using selection, crossover, mutation on a population | Multi-objective building optimization (energy, daylight, cost) |
| Fitness Function | Quantitative measure of solution quality in optimization | Daylight autonomy percentage, structural weight, energy use intensity |
| Pareto Front | Set of non-dominated solutions in multi-objective optimization | Trade-off visualization between conflicting objectives (cost vs. performance) |
| Topology Optimization | Material distribution optimization within a design domain | Structural member layout, floor plate opening placement, facade density |
| Gradient Descent | Iterative optimization following the steepest descent of objective function | Fast convergence for smooth, single-objective problems with known gradients |
| Simulated Annealing | Probabilistic optimization with decreasing randomness over time | Escaping local optima in complex design spaces; layout optimization |
| Swarm Intelligence | Optimization inspired by collective behavior (PSO, ant colony) | Urban layout optimization, pedestrian flow simulation |
| Concept | Definition | AEC Relevance |
|---|---|---|
| Panelization | Decomposing a surface into manufacturable panels (planar, single-curved, doubly-curved) | Facade rationalization; minimizing unique panel types for cost reduction |
| Rationalization | Simplifying complex geometry for feasible fabrication | Converting free-form surfaces to planar quads or developable strips |
| Robotic Toolpath | Sequence of spatial positions and orientations for a robotic end-effector | Robotic hot-wire cutting, 3D printing, bricklaying, welding |
| G-code | Machine instruction language for CNC and 3D printing | Controlling 3-axis CNC mills, laser cutters, FDM printers |
| Nesting | Optimal arrangement of 2D parts on sheet material to minimize waste | CNC cutting of facade panels, plywood formwork, sheet metal parts |
| Kerf Bending | Cutting parallel slots to allow sheet material to bend | Making planar sheet material conform to curved formwork |
| Unrolling/Flattening | Mapping a 3D surface to a flat 2D pattern | Developable surfaces for metal cladding; fabric cutting patterns |
| Concept | Definition | AEC Relevance |
|---|---|---|
| IFC Schema | Industry Foundation Classes; open BIM data standard (ISO 16739) | Exchanging building models between Revit, ArchiCAD, Tekla, etc. |
| LOD/LOI | Level of Development / Level of Information for BIM elements | Defining how much geometric and data detail a BIM element carries at each project stage |
| Digital Twin | Real-time digital replica of a physical asset fed by sensor data | Building operations, predictive maintenance, energy management |
| gbXML | Green Building XML; schema for transferring building energy model data | Energy simulation model exchange between design and analysis tools |
| Speckle Stream | Version-controlled, real-time data channel for design collaboration | Live syncing geometry between Grasshopper, Revit, Unity, web dashboards |
Use this decision tree to determine which computational design paradigm and toolset best fits a given design problem.
START: What is the primary design challenge?
|
+-- [A] "I need to explore variations of a known design concept"
| |
| +-- Are the variables well-defined and bounded?
| +-- YES --> PARAMETRIC DESIGN
| | Tools: Grasshopper, Dynamo
| | Skills: parametric-modeling, surface-rationalization
| |
| +-- NO --> GENERATIVE DESIGN
| Tools: Grasshopper + Galapagos/Octopus, Dynamo + Refinery
| Skills: generative-design, optimization-solvers
|
+-- [B] "I need to generate designs from rules or procedures"
| |
| +-- Are rules geometric (shapes, patterns)?
| | +-- YES --> ALGORITHMIC DESIGN (Shape Grammars, L-Systems)
| | | Tools: Grasshopper, Python scripting, Processing
| | | Skills: algorithmic-patterns, form-generation
| | |
| | +-- NO (rules are spatial/programmatic) --> ALGORITHMIC DESIGN (Space Planning)
| | Tools: Grasshopper, custom Python, Dynamo
| | Skills: space-planning, graph-based-layout
| |
+-- [C] "I need to optimize for measurable performance"
| |
| +-- Which performance domain?
| +-- Structural --> PERFORMANCE-DRIVEN (Structural)
| | Tools: Karamba3D, Kangaroo, Millipede
| | Skills: structural-optimization, form-finding
| |
| +-- Environmental (energy, daylight, wind) --> PERFORMANCE-DRIVEN (Environmental)
| | Tools: Ladybug/Honeybee, ClimateStudio, Butterfly/Eddy3D
| | Skills: environmental-analysis, climate-responsive-design
| |
| +-- Multi-objective --> GENERATIVE + PERFORMANCE-DRIVEN
| Tools: Octopus, Opossum, Colibri + simulation tools
| Skills: multi-objective-optimization, design-space-exploration
|
+-- [D] "I need to incorporate real-world data into design"
| |
| +-- What kind of data?
| +-- GIS/Geospatial --> DATA-DRIVEN (GIS)
| | Tools: Elk, Heron, QGIS, ArcGIS
| | Skills: site-analysis, urban-data
| |
| +-- Sensor/IoT --> DATA-DRIVEN (Real-time)
| | Tools: Firefly, custom APIs, Speckle
| | Skills: responsive-systems, digital-twin
| |
| +-- Demographic/Programmatic --> DATA-DRIVEN (Programming)
| Tools: Excel/CSV + Grasshopper, Python + Pandas
| Skills: program-analysis, data-visualization
|
+-- [E] "I need to prepare design for manufacturing"
| |
| +-- What fabrication method?
| +-- CNC (subtractive) --> FABRICATION
| | Tools: RhinoCAM, Grasshopper toolpath plugins
| | Skills: cnc-fabrication, nesting-optimization
| |
| +-- 3D Printing (additive) --> FABRICATION
| | Tools: Silkworm, custom G-code, slicer integration
| | Skills: additive-manufacturing, toolpath-generation
| |
| +-- Robotic --> FABRICATION (Robotic)
| | Tools: HAL Robotics, KUKA|prc, Robots
| | Skills: robotic-fabrication, toolpath-planning
| |
| +-- Formwork/Mold --> FABRICATION
| Tools: Grasshopper + Unrolling, nesting plugins
| Skills: formwork-design, surface-development
|
+-- [F] "I need to exchange data between platforms"
|
+-- INTEROPERABILITY
Tools: Speckle, Rhino.Inside, BHoM, IfcOpenShell
Skills: bim-interop, data-exchange
These are the most common mistakes in computational design practice. Recognizing and avoiding them is as important as mastering the tools themselves.
Description: Creating a parametric model with dozens of sliders and parameters without a clear design intent or understanding of which parameters matter most. The result is an unmanageable definition where changing any slider produces unpredictable results.
Symptoms: 50+ sliders in a Grasshopper definition, no parameter hierarchy, parameters that interact chaotically, inability to explain what the model "does."
Remedy: Start with the minimum viable parameterization. Identify the 3-5 parameters that most affect design quality. Use sensitivity analysis to prune irrelevant parameters. Document the design intent each parameter serves.
Description: Running an evolutionary solver without understanding the fitness landscape, the search space topology, or why the solver converges (or fails to converge) to particular solutions. The designer trusts the output without critical evaluation.
Symptoms: Accepting the first Galapagos/Octopus result without interrogating it, unable to explain why the "optimal" solution looks the way it does, no visualization of the fitness landscape.
Remedy: Always visualize the design space (use Colibri/Design Explorer). Understand what your fitness function actually rewards. Run the optimizer multiple times from different starting points. Critically evaluate whether the "optimal" solution makes architectural sense.
Description: Generating complex geometry (doubly-curved surfaces, branching structures, cellular forms) without any consideration of how forces flow through the structure or how it will be supported.
Symptoms: Beautiful renders that cannot be built, structural engineers rejecting the geometry entirely, massive structural redundancy to make arbitrary forms work.
Remedy: Integrate structural feedback early (Karamba3D, Kangaroo). Use form-finding methods that inherently produce structurally efficient shapes. Collaborate with structural engineers from the beginning, not after form is "finalized."
Description: Designing geometry that is theoretically elegant but practically impossible or prohibitively expensive to fabricate. Every panel is unique, curvature exceeds material bending limits, assembly sequence is impossible.
Symptoms: Thousands of unique panels, no consideration of material sheet sizes, tolerances ignored, no unfolding/nesting strategy, "we'll figure out fabrication later."
Remedy: Establish fabrication constraints as inputs to the parametric model, not afterthoughts. Rationalize surfaces early. Minimize unique component count. Consult fabricators during design, not after.
Description: Grasshopper data tree structures between components don't match, causing either no output, incorrect output, or explosive combinatorial results. This is the single most common Grasshopper debugging issue.
Symptoms: Components produce unexpected numbers of outputs, geometry appears in wrong locations, Param Viewer shows mismatched tree structures, "null" items throughout trees.
Remedy: Always use Param Viewer to inspect tree structures. Understand Grasshopper's matching rules (longest list, shortest list, cross-reference). Use Graft, Flatten, Simplify, and Path Mapper deliberately. Consider restructuring the definition to maintain clean data tree alignment.
Description: Using different geometric resolutions for analysis and design — e.g., running energy simulation on a highly detailed architectural model, or performing structural analysis on geometry too coarse to capture critical features.
Symptoms: Simulations that take days instead of minutes, analysis results that don't correspond to the actual design, mesh-dependent results.
Remedy: Create purpose-specific geometric representations: a coarse massing model for energy, a refined mesh for structural analysis, a rationalized surface for fabrication. Establish clear LOD protocols for each analysis type.
Description: Optimizing details before the overall design concept is established. Spending weeks optimizing facade panel angles when the building massing hasn't been resolved.
Symptoms: Highly optimized subsystem designs that become irrelevant when the overall design changes, wasted computation time, losing the forest for the trees.
Remedy: Follow a staged optimization approach: massing first, then systems, then components. Each stage should be sufficiently resolved before optimizing the next level of detail. Accept that early-stage models will be approximate.
Description: Letting the capabilities and defaults of software tools dictate the design outcome. The design looks like "a Grasshopper project" rather than a response to site, program, and context.
Symptoms: Projects that look like Voronoi diagrams or attractor-field patterns because those are easy to generate, not because they serve a design purpose. Design intent is "I wanted to try this component."
Remedy: Start with the design question, not the tool. Define the problem, objectives, and constraints before opening Grasshopper. Use computational tools to explore and evaluate, not to generate the starting concept.
Description: Building an elaborate parametric model in one platform without considering how it will be exchanged with collaborators using different tools (structural engineer in SAP2000, contractor in Tekla, client in Revit).
Symptoms: Manual model rebuilding in every platform, data loss at every exchange, inconsistent models across disciplines, last-minute interoperability crises.
Remedy: Plan the data exchange workflow at project kickoff. Use open standards (IFC, gbXML) where possible. Adopt Speckle or similar platforms for live interop. Design the parametric model with exportability in mind (clean geometry, consistent naming).
Description: Building extremely complex logic — nested loops, recursive algorithms, database queries, file I/O — entirely in visual programming (Grasshopper/Dynamo) when text-based scripting would be far more readable, maintainable, and performant.
Symptoms: Grasshopper definitions with 500+ components that could be 100 lines of Python, spaghetti wires that no one can follow, extreme slowness from Grasshopper overhead on simple operations.
Remedy: Use GhPython/C# scripting components for complex logic. Move substantial algorithms into standalone Python libraries. Use visual scripting for geometry flow and high-level workflow orchestration; use code for data processing and algorithmic logic.
Description: Working on computational design files without version control, relying on "Save As" with date-stamped filenames, losing the ability to track changes, revert, or collaborate effectively.
Symptoms: Folders full of "definition_v3_final_FINAL_v2.gh", no ability to diff or merge, lost work after crashes, inability to collaborate on the same definition.
Remedy: Use Git for version control. Grasshopper XML format is somewhat diffable. Use Speckle for geometry versioning. Adopt naming conventions and folder structures. Consider text-based representations (Python scripts, Hops definitions) for complex logic.
Description: Creating parametric definitions that only the author can use. No documentation, no logical grouping, no named groups, no input/output clarity.
Symptoms: Colleagues cannot use the definition, parameters have no labels or bounds, the definition breaks when anyone else touches it, knowledge leaves when the author leaves.
Remedy: Group and color-code definition sections. Label all inputs with human-readable names and valid ranges. Use Metahopper for documentation. Create a "user interface" cluster with exposed parameters. Write a companion document explaining the definition's logic.
This section routes to the appropriate specialized skill based on the user's computational design context. When the foundational layer detects a specific domain need, it activates the relevant skill.
| User Context / Keywords | Recommended Skill | Description |
|---|---|---|
| Parametric modeling, Grasshopper definition, sliders, parameters | parametric-modeling | Core parametric modeling workflows and best practices |
| Generative design, evolutionary optimization, multi-objective | generative-design | Generative and evolutionary design strategies |
| Form-finding, minimal surfaces, hanging chain, Kangaroo | form-finding | Physics-based form-finding and dynamic relaxation |
| Structural analysis, FEA, Karamba, load paths | structural-computation | Computational structural analysis and optimization |
| Environmental analysis, energy, daylight, Ladybug, Honeybee | environmental-simulation | Environmental performance simulation workflows |
| Facade, panelization, rationalization, cladding | surface-rationalization | Surface panelization and fabrication rationalization |
| Robotic fabrication, CNC, 3D printing, toolpath | digital-fabrication | Digital fabrication and robotic manufacturing |
| Data exchange, IFC, Speckle, Rhino.Inside, BIM | interoperability | Cross-platform data exchange and BIM integration |
| Urban analysis, GIS, site data, morphology | urban-computation | Urban-scale computational analysis and generation |
| Python scripting, C#, code, algorithm | scripting-for-designers | Programming and scripting for computational designers |
| Machine learning, neural network, classification, prediction | ml-for-design | Machine learning applications in AEC design |
| Data visualization, dashboard, mapping | data-visualization | Design data visualization and communication |
| Topology optimization, material distribution | topology-optimization | Topology optimization methods and workflows |
| Mesh, subdivision, remeshing, geometry processing | geometry-processing | Computational geometry and mesh processing |
| Pattern, tessellation, tiling, ornament | algorithmic-patterns | Algorithmic pattern generation and tessellation |
| Responsive, adaptive, kinetic, smart materials | responsive-systems | Responsive and adaptive building systems |
| Workflow, pipeline, automation, batch processing | workflow-automation | Computational design workflow automation |
1. Parse user query for domain-specific keywords
2. Match against routing table (multiple matches possible)
3. If single match: activate that skill directly
4. If multiple matches: present top 3 candidates with brief descriptions
5. If no match: remain in cd-foundations and provide general guidance
6. Always keep cd-foundations active as the knowledge base layer
The following reference files provide deeper knowledge for each foundational topic:
| Reference File | Content | Lines |
|---|---|---|
references/pioneers-and-movements.md | Detailed biographies of 20+ computational design pioneers; 8 major movements with origins, tenets, projects, and current state | 400+ |
references/tools-ecosystem.md | Complete tool descriptions, capabilities, licensing, workflows, integration points, community resources, plugin ecosystems | 400+ |
references/core-concepts.md | Data structures, mathematical foundations, coordinate systems, tolerance, computational complexity, recursion/iteration patterns | 350+ |
references/learning-pathways.md | Beginner-to-expert learning roadmaps by tool, by domain; key books, courses, conferences, communities, portfolio guidance | 300+ |
This foundation layer remains active throughout all computational design interactions, providing paradigm context, tool awareness, and routing intelligence to specialized skills.
npx claudepluginhub amanbh997/claude-skills-for-computational-designersExplores architectural design philosophy, movements, critical theory, and precedent analysis to inform design reasoning.
Provides reference for parametric design methodology, data structures, constraint systems, Grasshopper/Dynamo patterns, and associative geometry in AEC computational design.
Guides each phase of the design lifecycle — from research and strategy through UI design, interaction design, prototyping, and handoff. Includes 63 specialized skills across 8 categories.