What problem does it solve? Writing a portfolio case study about employer or client work is risky and time-consuming: claims lack evidence, numbers lack methods, and screenshots can leak confidential data. This Skill runs a structured nine-phase workflow that turns a repository into a publishable, evidence-backed case study while enforcing confidentiality clearance at every step. ## Core Features & Use Cases - Evidence-first workflow: Mines git history, PRs, migrations, and code structure into a claim-by-claim evidence ledger before any prose is written, then interviews the user only for what the repo cannot answer. - Measurement and research phases: Benchmarks before-and-after states with git worktrees, Lighthouse, autocannon, and EXPLAIN ANALYZE, then anchors numbers against public baselines like Core Web Vitals thresholds. - Confidentiality gating and safe visuals: Assigns a disclosure tier, maintains a never-publish list, captures screenshots and short recordings against seeded synthetic data via a Playwright script, and runs a redaction and secret-scan QA pass. - Use Case: An engineer wants to publish a portfolio write-up of a dashboard performance project. The Skill clears what may be disclosed, proves the p95 improvement with measured benchmarks, captures redacted screenshots, drafts the case study, and packages a project.json and excerpt for the portfolio site. ## Quick Start Ask the assistant to write a portfolio case study for this repository using the case-study skill, starting with the clearance questions.
