Skip to main content
ZICQ

Skills ZICQ category:Documents develop-design-rationale

Develop Design Rationale

Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.

685 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied

When to use it

- When making significant UX decisions that affect user experience

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Design Rationale; When to Use; When NOT to Use; Instructions; Output Format; Quality Checklist. It includes spec-recommended sections: input/output examples.

File analysis

File analysis: besides SKILL.md, the body references references/TEMPLATE.md, references/EXAMPLE.md. Those resources load on demand.

Design RationaleWhen to UseWhen NOT to UseInstructionsOutput FormatQuality ChecklistExamples

· License:Apache-2.0

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
develop-design-rationale
description
Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference.
License
Apache-2.0
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 2
  • references/TEMPLATE.md
  • references/EXAMPLE.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "develop-design-rationale" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-6c070c270879a0c2-Develop-Design-Rationale.html
Save it as .cursor/skills/develop-design-rationale/SKILL.md or .claude/skills/develop-design-rationale/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/product-on-purpose/pm-skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/product-on-purpose/pm-skills' --list

npx skills add 'https://github.com/product-on-purpose/pm-skills' --skill 'develop-design-rationale'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout
--- name: develop-design-rationale description: Documents the reasoning behind design decisions including alternatives considered, trade-offs evaluated, and principles applied. Use when making significant UX decisions, aligning with stakeholders on design direction, or preserving design context for future reference. license: Apache-2.0 metadata: phase: develop version: "2.1.0" updated: 2026-06-10 category: specification frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose --- # Design Rationale A design rationale document captures the "why" behind design decisions.the context, constraints, alternatives considered, and reasoning that led to a particular solution. While designs themselves show what was built, rationale documents preserve institutional knowledge about why it was built that way. ## When to Use - When making significant UX decisions that affect user experience - Before design reviews to prepare stakeholder discussions - When multiple valid approaches exist and the choice needs justification - To onboard new team members to existing design decisions - When revisiting past decisions to understand original reasoning - During design system evolution to document pattern choices ## When NOT to Use - The decision is architectural or a technology selection -> use `develop-adr` (Nygard format) - You need stakeholder alignment on the overall solution direction -> use `develop-solution-brief` - You are documenting exploration findings rather than a decision -> use `develop-spike-summary` - The decision is trivially reversible and low-stakes: a rationale document adds ceremony; record the reasoning in the PR or ticket instead ## Instructions When asked to document design rationale, follow these steps: 1. **State the Decision** Begin with a clear, one-sentence summary of what design decision was made. This becomes the title and reference point for the document. 2. **Describe the Context** Explain the situation that prompted this decision. What problem were you solving? What constraints existed? What user needs informed the direction? Include relevant research findings. 3. **List Options Considered** Document at least 2-3 alternatives that were evaluated. For each option, describe what it would look like and its key characteristics. Be fair to all options.avoid strawmen. 4. **Define Evaluation Criteria** Specify how options were assessed: usability heuristics, technical feasibility, brand alignment, user research findings, business requirements, or design principles. 5. **Explain the Reasoning** Walk through why the chosen option best meets the criteria. Be explicit about trade-offs.what you gained and what you sacrificed. Acknowledge where the decision is reversible vs. irreversible. 6. **Document Trade-offs Accepted** Every design decision involves trade-offs. Name what you gave up and why it was acceptable. This honesty helps future teams understand constraints. 7. **Note Follow-up Considerations** Capture anything that needs attention later: metrics to watch, conditions that might warrant revisiting the decision, or related decisions to make. ## Output Format Use the template in `references/TEMPLATE.md` to structure the output. A complete rationale fills every template section: Decision Summary; Context; Options Considered; Evaluation; Decision Rationale; Trade-offs Accepted; Reversibility; Follow-up Considerations; Supporting Materials; and Decision History. ## Quality Checklist Before finalizing, verify: - [ ] Decision is clearly stated in one sentence - [ ] Context explains the "why now" and constraints - [ ] Multiple alternatives are documented fairly - [ ] Evaluation criteria are explicit - [ ] Reasoning addresses why chosen option beats alternatives - [ ] Trade-offs are honestly acknowledged - [ ] A reader who inherits this design can reconstruct why the chosen option won without asking anyone ## Examples See `references/EXAMPLE.md` for a completed example.

Related skills

Documents

Ontology

Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, …

Documents

Nano Pdf

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Documents

Word / DOCX

Create, inspect, and edit Microsoft Word documents and DOCX files with reliable styles, numbering, tracked changes, tables, sections, and co…

Documents

Api Gateway

Call third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when…