/cd-foundations

title: Computational Design Foundations
description: Auto-activating foundation layer providing computational design paradigms, key pioneers, tools landscape, core concepts, and skill routing for all AEC computational design tasks
version: 1.0.0
tags: [computational-design, parametric, generative, algorithmic, AEC, foundation]
auto_activate: true
user_invocable: false

Computational Design Foundations

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.

---

1. Computational Design Paradigm Overview

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.

1.1 Parametric Design

**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:**

• Associative relationships between geometry elements (change one parameter, downstream geometry updates)
• Design intent is encoded as a graph of operations, not a static drawing
• Enables rapid iteration and variant generation from a single model definition
• Parameters can be numeric (dimensions), geometric (reference curves), or categorical (material type)

**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.

1.2 Generative Design

**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:**

• Goal-oriented: the designer specifies objectives (minimize material, maximize daylight, optimize circulation)
• Produces many candidate solutions rather than a single output
• Requires a fitness function or multi-objective evaluation framework
• Often employs evolutionary algorithms, agent-based systems, or stochastic search
• The designer's role shifts from form-maker to problem-framer and solution-curator

**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.

1.3 Algorithmic Design

**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:**

• Procedural logic: if/then branching, iteration, recursion
• Deterministic or stochastic depending on algorithm type
• Can encode complex rules (zoning regulations, structural grammars, spatial syntax rules)
• Bridges the gap between design logic and code
• Enables rule-based generation (shape grammars, L-systems, cellular automata)

**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.

1.4 Data-Driven Design

**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:**

• Real-world data as design input (GIS layers, weather files, pedestrian counts, census data)
• Requires data acquisition, cleaning, transformation, and mapping to design parameters
• Enables evidence-based design decisions
• Often combined with parametric or generative workflows
• Visualization and analytics are integral to the design process

**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.

1.5 Performance-Driven Design

**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:**

• Simulation-in-the-loop: design decisions are evaluated against performance models at every iteration
• Requires validated simulation engines (EnergyPlus, Radiance, FEA solvers)
• Multi-physics coupling: thermal, structural, lighting, acoustic, aerodynamic
• Performance targets as hard constraints or optimization objectives
• Demands understanding of both design and engineering domains

**When to Use:** When building performance is a primary driver — e.g., net-zero energy targets, structural weight minimization, acoustic optimization for concert halls, dayli