Individual skill
form-follows-function-as-axiom
Use this skill when applying the descriptive form-follows-function interpretation — functional clarity as a source of aesthetic quality. Trigger when designing tools, dashboards, or instrumental surfaces where every element should earn its presence. Sub-aspect of `form-follows-function`; read that first.
plugins/HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/form-follows-function-as-axiom/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 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)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering 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 · 3,077 bytesSKILL.mdcore · 3,077 bytesreferences/descriptive-cases.mddoc · 1,880 bytes
Read excerpt
# Form follows function as descriptive axiom
The descriptive interpretation: beautiful design tends to result from purity of function. Every visible element has a purpose; nothing decorative without function. The result tends to be coherent, timeless, and pleasing without being explicitly "designed for beauty."
## When the descriptive interpretation applies cleanly
- **Industrial tools** (Leatherman, Dyson, Snap-on) — function-derived form is what users want.
- **Information design** (Tufte-style charts, transit maps) — every mark earns its place.
- **Working software UI** (IDEs, dashboards, admin panels) — clarity dominates.
- **Type design** (Helvetica, Inter, IBM Plex) — function (legibility) drives the form.
- **Architecture for utility** (warehouses, factories, infrastructure) — pure function reads as visually honest.
In these contexts, the rule "strip what doesn't serve function" usually improves the result.
