Skip to content
Back to search

portfolio-case-study

MarketplaceWorks with Claude CodeGitHub

Claude Code skill: learn your portfolio's house style once, then turn any finished design project into a ready-to-post case study.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/apratimpanwar--portfolio-case-study/badge.svg)](/listings/apratimpanwar--portfolio-case-study)

HTML

<a href="/listings/apratimpanwar--portfolio-case-study"><img src="/api/listings/apratimpanwar--portfolio-case-study/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code:

/plugin marketplace add ApratimPanwar/portfolio-case-study
/plugin install portfolio-case-study@portfolio-case-study

Or copy `skills/portfolio-case-study/` into `~/.claude/skills/`.

Requirements: - Python 3 with Pillow and pypdf: `pip install pillow pypdf` - For Illustrator files: [poppler](https://poppler.freedesktop.org/) (`pdftoppm`) or `pip install pymupdf`. Optional: Adobe Illustrator, for artboard names, fonts and link checks (Windows script included; macOS command documented) - For Framer: Node 22+, then `npm install` in `skills/portfolio-case-study/scripts/framer/` - For Figma: the [Figma MCP server](https://help.figma.com/hc/en-us/articles/32132100833559) connected in Claude Code - For Cargo/browser-assisted deploys: [Claude in Chrome](https://claude.com/chrome)

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "portfolio-case-study",
  3. "owner": {
  4. "name": "Apratim Panwar",
  5. "url": "https://github.com/ApratimPanwar"
  6. },
  7. "plugins": [
  8. {
  9. "name": "portfolio-case-study",
  10. "source": "./",
  11. "description": "Find unpublished design projects, write them up in your house style, and deploy them to your site."
  12. }
  13. ]
  14. }
README.md · README · 132 lines
  1. # portfolio-case-study
  2. A [Claude Code](https://claude.com/claude-code) skill that finds the design
  3. projects you never published, writes them up in your portfolio's own house style,
  4. and puts them on your site.
  5. There's always one project that never makes it onto the portfolio. It's finished,
  6. shipped, paid for, and it sits in a folder. This skill writes down your case-study
  7. format once, so every new write-up starts where the last one ended, and gets it
  8. the rest of the way onto the site.
  9. ## How it works
  10. ```
  11. DISCOVER folders + Figma -> candidate projects (you pick)
  12. LEARN your existing portfolio -> house-rules.md (once)
  13. BUILD project + house rules -> case.json + images (per project)
  14. DEPLOY case.json -> your site (draft -> preview -> you say go)
  15. ```
  16. **DISCOVER** scans your folders for things that look like projects: images,
  17. source files (`.psd`, `.ai`, `.indd`, `.sketch`…), process PDFs, and Figma links
  18. mentioned in notes. It ranks them and you pick one. With a Figma token it can also
  19. list your team's Figma files.
  20. **LEARN** reads your live portfolio and records the rules it actually follows:
  21. structure, word counts, image grid, title pattern and voice, with real quotes as
  22. do/don't examples. It shows you the inconsistencies it found, so you decide what's
  23. a rule and what's a mistake. It also records where case studies live on your
  24. platform (CMS collection, repo folder, block markup).
  25. **BUILD** takes the project folder, Figma links and your rough notes. If the
  26. finished artwork lives in Illustrator files, it pulls every artboard out as an
  27. image (sized for the web whether it's a 70mm label or a 700mm poster), along with
  28. the text, print sizes and, with Illustrator installed, artboard names, fonts and
  29. linked-file status. A raw
  30. voice-note transcript is ideal: who the client was, what they asked for, what
  31. changed and why. It writes the case study in your voice, orders the images for the
  32. story, and makes web-ready copies (downscaled, GPS/EXIF stripped). The result is a
  33. platform-neutral `case.json`. It doesn't make up metrics, quotes or results.
  34. **DEPLOY** sends `case.json` to your site:
  35. | Platform | How | What's automated |
  36. |---|---|---|
  37. | Custom / static / Claude-built site (Astro, Next, Hugo, 11ty, Jekyll, HTML) | edits your repo, builds, previews, pushes | everything; you approve the push |
  38. | Framer | [Framer Server API](https://www.framer.com/developers/server-api-introduction) script | images, CMS item, preview; you approve production |
  39. | Webflow | Webflow Data API v2 | staged CMS item; you approve publishing |
  40. | Cargo | drives the editor in your signed-in Chrome | uploads + layout; you press Publish |
  41. | Squarespace, Wix, Notion, Behance… | paste-ready content + image order | the writing |
  42. Nothing goes live without your explicit yes. Every route goes draft → preview →
  43. your approval → live.
  44. When you correct something, it offers to write the correction into
  45. `house-rules.md`, so the fix sticks for every future case study.
  46. ## Install
  47. In Claude Code:
  48. ```
  49. /plugin marketplace add ApratimPanwar/portfolio-case-study
  50. /plugin install portfolio-case-study@portfolio-case-study
  51. ```
  52. Or copy `skills/portfolio-case-study/` into `~/.claude/skills/`.
  53. Requirements:
  54. - Python 3 with Pillow and pypdf: `pip install pillow pypdf`
  55. - For Illustrator files: [poppler](https://poppler.freedesktop.org/) (`pdftoppm`) or `pip install pymupdf`.
  56. Optional: Adobe Illustrator, for artboard names, fonts and link checks (Windows script included; macOS command documented)
  57. - For Framer: Node 22+, then `npm install` in `skills/portfolio-case-study/scripts/framer/`
  58. - For Figma: the [Figma MCP server](https://help.figma.com/hc/en-us/articles/32132100833559) connected in Claude Code
  59. - For Cargo/browser-assisted deploys: [Claude in Chrome](https://claude.com/chrome)
  60. ## Use
  61. ```
  62. Find projects on my Desktop I haven't put on my portfolio
  63. ```
  64. ```
  65. Learn the house style from https://your-portfolio.com
  66. ```
  67. ```
  68. Make a case study from ~/Projects/acme-rebrand, Figma: <url>.
  69. Notes: <paste your voice-note transcript>
  70. ```
  71. ```
  72. Deploy it to my Framer site
  73. ```
  74. ## Keys and tokens
  75. Set these in your own environment. The skill never asks for them in chat and
  76. never writes them to files.
  77. | Variable | For | Where to get it |
  78. |---|---|---|
  79. | `FRAMER_API_KEY` | Framer deploys | Framer → Site Settings → General → API keys |
  80. | `WEBFLOW_TOKEN` | Webflow deploys | Webflow → Site settings → Apps & integrations → API access (CMS read/write) |
  81. | `FIGMA_TOKEN` | listing Figma files (optional) | Figma → Settings → Security → Personal access tokens (`projects:read`) |
  82. ## Scripts
  83. All in `skills/portfolio-case-study/scripts/`. They work on their own too.
  84. | Script | Does |
  85. |---|---|
  86. | `find_projects.py [roots]` | rank folders that look like design projects; collect Figma links in them |
  87. | `figma_list.py <team_id>` | list Figma files in a team (needs `FIGMA_TOKEN`) |
  88. | `extract_ai.py <file.ai or folder> <out>` | artboards to PNG, print sizes, text; flags files that need Illustrator |
  89. | `illustrator/run_illustrator.ps1` | drive Illustrator: artboard names, layers, fonts, spot colours, broken links, exports |
  90. | `collect_assets.py <folders...>` | inventory images, flag oversized files, propose a grid |
  91. | `prepare_images.py <assets.json> <out>` | downscale, strip EXIF/GPS, number in display order |
  92. | `framer/deploy.mjs <case.json>` | dry run → draft → preview → production, one flag per stage |
  93. ## Figma access
  94. The connected Figma account must be able to open the file. A share link that
  95. opens in your browser can still be refused to the API. If so, set link sharing to
  96. "Anyone with the link · can view", or export the frames into the project folder.
  97. ## Credit
  98. Inspired by [@0xCharlota's thread](https://x.com/0xCharlota/status/2105590462622871841)
  99. on turning a case-study format into a reusable Framer Skill. This takes the same
  100. idea across platforms for Claude Code.
  101. ## License
  102. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.