agentsclimarketplace
Sign in

Case study design decisions

Skill jpoindexter/design-case-study-skills/skills/case-study-design-decisions

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.From its SKILL.md

Install
npx -y skills add jpoindexter/design-case-study-skills --skill case-study-design-decisions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 245 tokens by cl100k_base, as published. Nobody here has run it

Case Study Design Decisions

Make the decision legible to a skeptical non-designer. Read references/decide-record.md.

Workflow

  1. Identify the reader’s influence, priorities, vocabulary, and likely objection.
  2. Select only decisions that changed user outcomes, system behavior, risk, cost, or delivery.
  3. Complete a DECIDE record for each pivotal decision.
  4. Connect design evidence, business consequences, technical constraints, and limitations.
  5. Represent rejected alternatives fairly.
  6. State what agreement enabled and what happened next.
  7. 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.

What ships with it: 2 files

3.9 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.