Design Rationale
Checked<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
product-on-purpose
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned product-on-purpose/pm-skills at 1cef1a9eae.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1cef1a9eae
- Scanned
- 5 files, 663 lines
About this skill
What it does
This skill helps articulate the "why" behind design decisions for a product. It translates user needs, business goals, and strategic objectives into clear rationales that justify specific features or UI elements. The output provides a structured explanation of how a design choice aligns with broader product purpose and intended outcomes.
When to use it
- Justifying feature prioritization: Use this skill when needing to explain why one feature was chosen over another for inclusion in a release.
- Communicating design decisions to stakeholders: Clearly articulate the reasoning behind UI/UX choices to engineering, marketing, or leadership teams.
- Documenting product evolution: Create a record of design rationale as a product matures and requirements change.
- Onboarding new team members: Provide context for existing features by explaining their original purpose and justification.
Key capabilities
- Generates rationales linking design choices to user needs.
- Connects design decisions to business objectives.
- Provides structured explanations of product strategy alignment.
Example prompts
- "Explain the rationale behind implementing a dark mode option in our mobile app."
- "What's the reasoning for using a card-based layout on the homepage?"
- "Generate a design rationale for prioritizing user onboarding animations over detailed feature descriptions."
Tips & gotchas
The quality of the output depends heavily on providing sufficient context about the product, target users, and business goals. Without this information, the generated rationales may be generic or lack specific relevance.