AGENT SKILL

principle-exhaust-the-design-space

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

License 许可
MIT
最近更新
2026-11-01
Stars
★ 0
Forks
0

01 前言 Front Matter

name
principle-exhaust-the-design-space
description
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
disable-model-invocation
true

03 SKILL.md 正文

Exhaust the Design Space

When a novel interaction or architectural decision has no established precedent, explore several concrete alternatives before implementation. Building the wrong thing costs more than exploring three options.

The rule. When the right answer is not obvious, build 2-3 competing prototypes or sketches. Compare them side by side. Only then commit. Design it twice is this rule by another name. A second flavor of the first shape does not count.

When it applies:

  • Novel UI interactions (no prior art in the codebase)
  • Architectural choices with multiple viable approaches
  • Product design decisions where user experience depends on feel, not logic

When it doesn't:

  • Mechanical implementation where the pattern is established
  • Bug fixes or refactors with a clear target state
  • Changes where constraints dictate a single viable approach

04 同仓库更多 Skills

YunosukeYoshino
YunosukeYoshino/pstack-devin

pstack

poteto-mode for Devin: deliberate, verified, concise engineering mode that routes to the bundled pstack library (how, why, architect, swarm, arena, interrogate, tdd, unslop, principles, playbooks). Invoke explicitly via @skills:pstack or when the user asks for poteto / pstack mode.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

unslop

Cut AI tells from any writing. Must always apply.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 0
YunosukeYoshino
YunosukeYoshino/pstack-devin

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 0