Architect & Designer Thinking Frameworks
Material-first design frameworks from the architects and designers who defined built space — distilled into .md skill files.
The designers in this collection share a refusal to treat aesthetics as a layer added at the end. Frank Lloyd Wright's organic architecture started from site rather than program. Dieter Rams's Ten Principles of Good Design — including 'as little design as possible' — became the operating manual at Apple under Jony Ive's leadership. Le Corbusier's modular thinking propagated through twentieth-century urbanism, for better and worse. Charles and Ray Eames treated chair design, exhibition design, and educational film as one continuous practice. Tadao Ando works almost exclusively in concrete because the constraint produces buildings the constraint couldn't predict. This collection captures their documented frameworks as .md skill files for Claude, ChatGPT, and any LLM. Use them when designing a physical product, a built environment, a digital interface, or any system where the form has to do part of the functional work.
How architect & designers think
- Form follows function — the shape of a thing earns its place by what it does, not by what it references
- As little design as possible — every element must justify its presence; the bias should be toward removal
- Material integrity — the material the thing is made of should show through; faking one material with another is design failure
- Site-first design — the surrounding context determines the building or product, not an imported aesthetic
- Iterative prototyping — the working drawing is the conversation; treat models as drafts you'll throw away
Frameworks in this category
Frank Lloyd Wright
Organic Architecture & Site-First Design
Le Corbusier
Machine for Living & Modular Thinking
Dieter Rams
Ten Principles of Good Design
Jony Ive
Reduction, Material Integrity & Detail
Charles & Ray Eames
Iterative Prototyping & Cross-Disciplinary Play
Frank Gehry
Sculptural Ambition & Digital Fabrication
Tadao Ando
Concrete, Light & Meditative Space
Buckminster Fuller
Systems Thinking & Doing More With Less
When to use these frameworks
- Designing a physical product where every component competes for budget and weight
- Designing a digital interface where the question is what to leave out, not what to add
- Reviewing a built or digital design for the elements that don't earn their place
- Choosing materials, finishes, or component vendors where the choice will read for decades
- Working with a constraint (budget, site, brief) that initially feels like a problem rather than the design
Start here
Dieter Rams
Ten Principles of Good Design
Adjacent thinking
Frequently asked questions
Which design framework is best for someone working in digital product design?
Dieter Rams's Ten Principles. They were written for industrial products in the 1970s and translate so directly to digital interfaces that they read as if written for software — 'good design is honest', 'good design is unobtrusive', 'good design is as little design as possible'. The Eames iterative-prototyping practice is the second-most useful framework for anyone who works in build-test cycles.
Are these useful for non-design work — strategy, writing, software architecture?
Yes. Form-follows-function and as-little-design-as-possible both translate directly to writing — most prose problems are subtraction problems. Site-first design is a useful framing for software architecture: build for the actual deployment context, not an imagined ideal. The material-integrity framework applies to almost any work where the question is whether you're being honest about what something is rather than dressing it up.
Can these replace formal design education or working under a senior designer?
No. Design is a craft learned through critique on actual work, ideally from someone with significantly more experience than you. These frameworks describe how successful designers thought about their work and provide useful vocabulary for discussion, but no document replaces the in-room critique that builds judgement. Use them alongside, not instead of, real design feedback.
Why include both architects and product designers in one category?
Because the working frameworks travel across scale more than the specialised vocabularies suggest. Frank Lloyd Wright designing a house and Dieter Rams designing a calculator were solving variations of the same problem — how to make form do the functional work without retreating into ornament. Cross-scale grouping helps surface the patterns that hold across the architect/product-designer divide.
Save when you build a bundle.
Mix and match across categories. 4 for $14.99 (save 25%) or 10 for $29.99 (save 40%).
Browse all 459 frameworks →