Menu

Individual skill

principle-exhaust-the-design-space

Use for a UI, architecture, or product choice the codebase has never faced, or one decided by how it feels in use. Build two or three rival throwaway prototypes and pick based on comparing them side by side.

plugins/requie/endostack/skills/principle-exhaust-the-design-space/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
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,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Exhaust the design space

When the codebase offers no existing pattern for a choice, make two or three rival prototypes and compare them directly before committing. Your first design is a single sample from the options, and it cannot be judged without others next to it.

## When it applies

A novel UI interaction or architectural choice with nothing similar already in the code, and product decisions where the right answer depends on how something feels to use more than on a logical argument. An example: choosing how an agent asks the user to approve a risky tool call (inline prompt, batched review queue, or a policy file the user edits once).

Skip it when the codebase already has an established pattern for the decision, or when one logical argument settles it.

## What to do

1. Name the open decision and the dimensions that matter (friction, error rate, latency, how much the user must read).
2. Build two or three cheap, throwaway prototypes that take genuinely different approaches. Three color variants of one layout count as one approach.