agentleFS
art2urlart2url/career-agent-skills/skills/portfolio-case-study/SKILL.md

portfolio-case-study

Skill9 starsChanged 7 months agoMITView on GitHub

Write portfolio case studies that win interviews — structure project narratives with before/after results, and build ATS-safe creative resumes for design and technical roles

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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
  1. Distinctive:

    Use when the user wants to create case studies, build a portfolio, or design a creative resume that balances visual appeal with ATS …

    line 10
  2. Distinctive:

    Must-have: before/after comparisons, key deliverable screenshots, results chart.

    line 36
  3. Distinctive:

    Always: blur sensitive data, add captions, size for mobile.

    line 37
  4. Distinctive:

    Must still be scannable in 6 seconds

    line 52
  5. Distinctive:

    Never sacrifice content quality for visual design

    line 114

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Portfolio Case Study

Trigger

Use when the user wants to create case studies, build a portfolio, or design a creative resume that balances visual appeal with ATS compatibility.

Keywords: "case study", "portfolio case study", "portfolio", "write case study", "creative resume", "designer resume", "UX portfolio", "product design portfolio", "project writeup", "portfolio piece", "case study template", "design resume", "project showcase", "work samples", "portfolio website content", "how to write a case study"

Part 1: Case Studies

Structure

  1. Overview — project name, your role, team, timeline, one-sentence impact
  2. Problem — business context, user pain points, constraints, success metric
  3. Process — research, options considered, key decisions and rationale
  4. Solution — what you built/delivered, key features, how it solved the problem
  5. Results — quantified outcomes (before/after table), business impact
  6. Learnings — what worked, what you'd do differently

Target: 3-5 minute read.

Depth by Role

  • Product Manager: strategy, prioritization, stakeholder alignment, metrics
  • UX/Product Designer: user research, design iterations, usability testing
  • Software Engineer: architecture decisions, trade-offs, system design
  • Marketing: channel strategy, targeting, creative, attribution

Visual Elements

Must-have: before/after comparisons, key deliverable screenshots, results chart. Always: blur sensitive data, add captions, size for mobile.

Part 2: Creative Resume Strategy

Two-Version Approach

ATS version (online applications):

  • Single column, standard fonts, no graphics
  • Show creativity through: clean typography hierarchy, strategic white space, strong writing
  • Safe touches: subtle color in headers, hyperlinks to portfolio, clean dividers

Designed version (portfolio, networking, direct outreach):

  • Your resume IS a design sample
  • Consistent with portfolio site visual identity
  • 2-3 colors max, 2 font families, clear hierarchy
  • Must still be scannable in 6 seconds

Field-Specific

  • Graphic designers: Typography and layout precision demonstrate skill
  • UX designers: Information architecture and scanability show thinking
  • Writers: Impeccable copy with zero errors is the portfolio
  • Marketing: On-brand identity and strategic content choices

Portfolio Integration

Link resume to specific case studies:

- Redesigned checkout flow, reducing abandonment by 35%
  Case study: yourname.com/checkout

Output Format

For Case Studies:

## Case Study: [Project Name]

**Quick Facts:** Role | Company | Timeline | Team | Impact

### Problem
[Context + challenges]

### Process
[Research → Decisions → Rationale]

### Solution
[What you delivered]

### Results
| Metric | Before | After | Change |
|---|---|---|---|

### Learnings
[What worked + what you'd change]

For Creative Resumes:

## Creative Resume Strategy

### ATS Version
[Content and format guidance]

### Designed Version
[Typography, colors, layout specs]

### Portfolio Integration
[How to connect resume to portfolio]

Rules

  • Case studies show HOW and WHY, not just WHAT
  • Your contributions must be clearly distinguishable from the team's
  • Results need numbers — if you can't measure impact, measure activity
  • Creative resumes must pass the 6-second scan test
  • Never sacrifice content quality for visual design

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.