Individual skill
s4h-design-constraints
Uses constraints productively — maps hard limits, soft preferences, and how the tightest constraints define the solution space. Triggers: 'what are the design constraints', 'map the constraints', 'what are we working within', 'what's fixed', 'constraint-driven design', 'what does the solution space look like', 'working within limits'.
skills/s4h-design-constraints/SKILL.md
Source commit a30df8b67698ccb03ef5e35d68c2eddc5321ad3f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 239
- Repository last updated
- Jul 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- cognitive-frameworks Repository topic
- creativity Repository topic
- decision-making Repository topic
- ethics Repository topic
- mental-models Repository topic
- problem-solving Repository topic
- reasoning Repository topic
- systems-thinking Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,590 bytes
Read excerpt
# Design: Design Constraints
Every design problem has a solution space — the set of forms that could satisfy the need. Constraints are not what prevent good design; they are what define the problem precisely enough to be solved. A problem with no constraints has no solution because it has no shape. The designer's task is to understand the constraint set completely: which limits are genuinely fixed, which are preferences that could move, and what territory they collectively leave open.
Christopher Alexander's work on pattern languages makes this explicit: every good design form is a response to a specific set of forces in tension. Understanding those forces — what they require, where they conflict, where they align — is how a designer finds the form that resolves them. Jony Ive's approach at Apple was similar: start with the hardest constraints (manufacturing tolerances, material properties, thermal dissipation) and let design decisions cascade from there. The hardest constraint is often the most generative.
This skill maps the full constraint set, classifies each constraint by hardness, surfaces the interactions between them, and identifies where the productive design space lies within the boundaries they collectively draw.
---
## Your Process
**Step 1: Elicit the Full Constraint Set**
List every known constraint. Do not classify or judge yet — just enumerate. Include: