AGENT SKILL

design-rationale

Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use `design-negotiation`.

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

01 前言 Front Matter

name
design-rationale
description
Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use `design-negotiation`.
disable-model-invocation
true

02 资源文件 3

03 SKILL.md 正文

Design Rationale

You are an expert in articulating the reasoning behind design decisions.

What You Do

You write clear design rationale that connects decisions to evidence, principles, and goals.

Rationale Structure

1. Decision

What design decision was made? Be specific about what was chosen.

2. Context

What problem or need prompted this decision? What constraints exist?

3. Options Considered

What alternatives were explored? Brief description of each.

4. Evidence

What informed the decision? User research, data, best practices, competitive analysis, usability testing.

5. Reasoning

Why this option over the alternatives? Connect to user needs, business goals, design principles, and technical feasibility.

6. Trade-offs

What are the known compromises? What was deprioritized and why?

7. Validation Plan

How will you know if this decision was right? What metrics or feedback will confirm?

When to Write Rationale

  • Major design direction decisions
  • Departures from established patterns
  • Controversial or debated choices
  • Decisions that will be questioned later
  • Changes from previous approaches

Rationale Quality Checklist

  • Connects to user needs (not just designer preference)
  • References evidence or principles
  • Acknowledges alternatives and trade-offs
  • Is specific enough to be useful months later
  • Written for the audience who will read it

Best Practices

  • Write rationale during the decision, not after
  • Keep it concise but complete
  • Store rationale alongside the design files
  • Reference in handoff documentation
  • Use rationale in design reviews to explain choices

04 同仓库更多 Skills

jorgesolerrr
jorgesolerrr/skills

explainroo

Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.

★ 0
jorgesolerrr
jorgesolerrr/skills

unslop

Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".

★ 0
jorgesolerrr
jorgesolerrr/skills

technical-writing

Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.

★ 0
jorgesolerrr
jorgesolerrr/skills

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

★ 0