Individual skill
form-follows-function-success-criteria
Use this skill when the team is in a form-vs-function debate and needs to step back to define what "success" actually means for the design. Trigger when stakeholders disagree about visual treatment, when a design feels off and no one can articulate why, or when reviewing a design against an unclear brief. Sub-aspect of `form-follows-function`; read that first.
plugins/HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/form-follows-function-success-criteria/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,532
- 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
- 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 · 4,765 bytesreferences/criteria-frameworks.mddoc · 1,694 bytes
Read excerpt
# Defining success criteria explicitly
The book's reframe of form-follows-function: instead of asking "what should be omitted?", ask "what's critical to this design's success?". Then weigh form and function against those criteria. The discipline is making success criteria explicit rather than assuming.
## Common implicit success criteria
Without explicit criteria, teams default to assumed criteria — often without alignment:
- Designer assumes: visual elegance.
- Engineer assumes: implementation simplicity.
- Product manager assumes: feature completeness.
- Marketing assumes: brand differentiation.
- Stakeholder assumes: stakeholder approval.
