case-study-design-decisions
Skill1 starsChanged 4 months agoMITView on GitHub
Explain and defend pivotal design decisions in a case study using stakeholder context, user and business evidence, alternatives, constraints, trade-offs, consequences, limitations, and follow-up. Use when a portfolio draft shows screens without rationale, lists activities instead of decisions, needs executive credibility, must explain rejected options, or must communicate complex enterprise, platform, system, or AI-agent design choices.
In this repository11 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Remove aesthetic rationale that does not affect use, comprehension, trust, or performance.
- Distinctive: line 31
Do not hide uncertainty or pretend consensus existed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Case Study Design Decisions
Make the decision legible to a skeptical non-designer. Read references/decide-record.md.
Workflow
- Identify the reader’s influence, priorities, vocabulary, and likely objection.
- Select only decisions that changed user outcomes, system behavior, risk, cost, or delivery.
- Complete a DECIDE record for each pivotal decision.
- Connect design evidence, business consequences, technical constraints, and limitations.
- Represent rejected alternatives fairly.
- State what agreement enabled and what happened next.
- Remove aesthetic rationale that does not affect use, comprehension, trust, or performance.
Communication pattern
For each decision:
- set context before showing the artifact;
- name the problem and tension;
- explain the choice in the reader’s language;
- ground the rationale in users, business, research, and constraints;
- acknowledge limitations without weakening the argument;
- show the decision or learning that followed.
Do not hide uncertainty or pretend consensus existed. Distinguish the design recommendation from the final organizational decision.
Output
Return a decision shortlist, completed DECIDE records, likely stakeholder questions, and recommended captions or callouts for the associated visuals.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

