Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Design case study writer

    2

    Transform design project notes into evidence-based UX case studies focused on decisions and outcomes.

    $7.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    Design case study writer

    Design case study writer

    Example session with this skill installed

    Write a UX case study for a fintech app redesign. I led the mobile checkout flow. We improved task completion from 40% to 85% in testing. Constraints: 3-week sprint, legacy API limits.

    • Read your context and instructions
    • Compiled the design case study
    • Generated the UI component

    Processed the fintech redesign notes. The narrative focuses on the tension between legacy API latency and the need for a high-speed checkout experience.

    Project Card

    50% increase in task completion | Lead Product Designer | 1 PM, 2 Engineers | 3 Weeks | iOS/Android | Shipped

    Executive Summary

    Mobile checkout completion was stalled at 40% due to legacy API latency causing user drop-off. As Lead Designer, I audited the checkout flow and implemented an optimistic UI pattern to mask backend delays. Evaluative testing showed completion rates rose to 85%. This project demonstrates the ability to deliver high-performance UX within strict technical and time constraints.

    Full Narrative

    Context and stakes

    The existing checkout required four distinct API calls before confirming a purchase. Users frequently abandoned the app during the 5-second "Processing" state, leading to a 40% completion rate.

    My role and constraints

    I led the end-to-end redesign of the mobile flow. We were restricted to a 3-week sprint and could not refactor the legacy backend, forcing a frontend-only solution to a performance problem.

    Decisions and tradeoffs

    We faced a choice: show a detailed loading state or use optimistic UI. While optimistic UI risks showing success before the server confirms, I chose to implement it for the "Add to Cart" and "Address Selection" steps to build momentum. I countered the risk by keeping the final "Place Order" button behind a high-contrast validation state.

    Outcomes

    • Evaluative Result: Prototype task completion increased from 40% to 85% in a 10-participant study.
    • Operational Result: Reduced perceived latency by 3.2 seconds.
    • Implementation: Successfully shipped to production within the 3-week window.

    Visual Plan

    PlacementArtifactClaim ProvedCaption
    HeroBefore/After FlowStreamlined stepsReducing the checkout journey from 5 screens to 3.
    Mid-sectionAPI Latency DiagramTechnical constraintMapping the 5-second delay that caused user drop-off.
    DetailOptimistic UI StatesDesign solutionUsing skeleton screens to maintain user momentum during API calls.

    Next steps

    1. Review the Visual Plan to ensure you have screenshots of the optimistic UI states.
    2. Verify the 85% completion metric against your final research report.
    3. Prepare the 30-second "elevator pitch" for recruiters based on the Executive Summary.

    design-case-study-writer.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Convert messy project notes into a structured portfolio narrative.Extract individual contributions from team-based product launches.Audit portfolio claims to ensure they are backed by specific evidence.Prepare a high-impact 5-minute case study walkthrough for interviews.

    About this skill

    Hiring managers and design leads are tired of seeing the same generic process diaries. Most UX case studies focus on tools and frameworks rather than decisions and outcomes. This skill helps you audit your project evidence, extract the narrative spine, and write a high-impact case study that proves your specific contribution to a product's success.

    What it does

    • Audit evidence by mapping claims to specific artifacts, sources, and roles to ensure credibility.
    • Identify tension to move beyond linear "process" and highlight real constraints, conflicts, and technical limits.
    • Differentiate ownership by clearly separating individual contributions from team efforts and stakeholder decisions.
    • Select proof by identifying which visuals (flows, wireframes, data) actually support a specific claim.
    • Structure narratives across different formats, from executive summaries to detailed interview decks.

    How it works

    1. Provide project materials such as rough notes, research findings, Figma links, or role descriptions.
    2. Review the evidence ledger generated to confirm which claims are supported and where gaps exist.
    3. Select a narrative spine based on the identified tension and pivotal decision.
    4. Generate the final case study including a project card, executive summary, narrative, and visual plan.

    Frameworks & tools

    This skill is framework-agnostic but follows industry standards for UX, UI, and Product Design portfolios. It works with inputs from Figma, Jira, research repositories, and raw project documentation.

    Why this beats prompting it yourself

    Generic prompts often lead to "marketing fluff" and inflated claims like "best-in-class experience." This skill enforces a strict evidence-to-claim mapping that prevents hallucinated metrics and ensures your individual craft is visible to recruiters.

    Use cases

    • Portfolio building for designers needing to turn messy project notes into a structured web page.
    • Interview preparation by creating a 5-minute verbal walkthrough focused on trade-offs.
    • Seniority leveling by shifting the narrative from "doing tasks" to "making strategic decisions."
    • Confidentiality handling by transforming sensitive data into honest, directional signals.

    Known limitations

    This skill will not invent research, metrics, or quotes. It requires the user to provide baseline evidence to function effectively.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 2 days ago

    • Passed all security checks, Safe to install

    Listed2 days ago

    What's inside

    Frequently Asked Questions