A production-analysis workflow for turning a web project into case-study images and videos. A case study explains how a design or project was made, using the project's own rendered scenes and assets.

Capture web pages, create scene and layer breakdowns, and produce applicable clips, images, Blender turntables, and other presentation material.

It replaces a single showreel with separate material for chapters, transitions, layers, and assets. The workflow adapts to the technologies and files the project actually contains.

case-study — Skill for Claude Code by darkroomengineering/cc-settings

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add darkroomengineering/cc-settings --skill case-study

Clone the repo

git clone --depth 1 https://github.com/darkroomengineering/cc-settings

Made for: Claude Code.

Or install darkroom, the plugin that ships this one along with the rest of its 24 skills, 11 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/case-study/github.svg)](https://agentmods.dev/skills/darkroomengineering/cc-settings/case-study)

Your own site

<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/case-study"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/case-study/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/darkroomengineering/cc-settings/case-study"><img src="https://agentmods.dev/badge/skills/darkroomengineering/cc-settings/case-study.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 224 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,750 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00224	$0.05750
Opus 5.5	$0.00090	$0.02300
Sonnet 5.5	$0.00045	$0.01150
Haiku 4.5	$0.00022	$0.00575

Measured 6d ago against content hash 53672044adc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

case-study scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

The scan reads SKILL.md. This mod also ships 40 executable files (examples/play-template.js, examples/recipe-template.js, examples/transition-anatomy.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/case-study/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Case study from a project

The goal is raw material a designer can build a case study from: many separate, clean, 16:9 videos and images that show how the work is made, not one showreel. Everything comes from the project itself: the live site rendered by its own code, its own GLB models and bakes, its own stems and SVGs. Nothing is invented, and each item says how it was made.

Fit the pipeline to the project

Every project is different; run the phases that apply and say which you skipped and why.

Project	Works as is	Adapt
three.js based (vanilla, React Three Fiber, Threlte, TresJS)	everything	nothing
Other WebGL engines (Babylon, PixiJS, OGL, Spline, Unity WebGL)	film, clips, holds, clicks, DOM-mode layers, sound, image assets, board	no scene hooks: reach the engine's own globals in `page.evaluate` for 3D layers; Blender only if model files exist
DOM / GSAP / Lottie / video sites	film (the clock also steps CSS animations and video), DOM-mode layers via `css()`, clicks, sound, assets, board	skip Blender, solo and instances
Multi-page sites	everything, per page	`boot.js` each URL; "chapters" become pages or sections
No sound / no Theatre keyframes	—	skip phase 6, or place stems by section from the code's triggers
Games and app-like flows (keyboard play, timers, forms)	layers, sound, assets, tokens, board	boot with `TIMERS=1` and a network guard; the film is a scripted playthrough (`examples/play-template.js`), cut by its logged events; 2D sprite games skip Blender and rebuild the level from their atlases instead

What the user expects (learned the hard way)

16:9, 1920×1080 masters for everything, including stills, grids and Blender renders. Re-render instead of cropping.
A list of separate videos and images, never just one film. Cut long captures into per-chapter and per-transition clips, plus stills.
Every chapter gets the same depth. Each one is decomposed layer by layer and gets a 3D turntable. Don't stop at the most obvious scene.
Every sound and every image asset as its own file, including small UI glyphs such as a navigation rail's icons.
Colours and typography are part of every case study: palette, themes, each typeface, the type scale, and what the live site really uses.
Masters go to the studio Drive, one folder per project, and the board links to that folder (phase 10).
The repo stays clean. No commits. Revert lockfile or config churn caused by installs and dev servers.
Captures never write to the client's production. No score rows, no leads, no analytics hits, no anonymous sign-ins: block or fake those requests in the capture browser (BLOCK / FAKE_OK, phase 2) before the first take, and never submit a real form.
The board is something to play with, not only to watch. The user asked for more interactivity and immersion: give each chapter a playable piece rebuilt from the project's own assets and logic (state buttons for a character, the level itself, its mini-games, a music machine, layer toggles, a camera pull-back slider). See "Playable pieces" in references/board.md.
Show progress with contact sheets, and look at every capture (Read the image) before using it.

Read the full file on GitHub · 207 lines

Files

What ships with it

46 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago Changed · +64 lines · +30 tokens per session 53672044adc5
7d ago First seen · 143 lines · 194 tokens per session scan A fd540dbe94ea

Subscribe to this mod's changes

case-study is a skill published in the GitHub repository darkroomengineering/cc-settings (52 stars, last pushed today), licensed MIT. It adds 224 tokens to every session and 5,750 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-23.

Claude Code Creative and media Design and UX agents ai darkroom-engineering developer-tools dotfiles

logo-design

Professional logo and brand-mark design, from brief to production files. Guides discovery and the design brief, concept generation, choosing a mark type (wordmark, monogram, letterform, pictorial, abstract, emblem, mascot, combination), building clean geometric SVG logos, optical refinement, colour and typography…

jjmartres/ai-coding-agents · 213 tokens

mermaid-diagrams

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes…

jjmartres/ai-coding-agents · 138 tokens

case-study