Built as working context, not shelfware.
This resource is meant to be useful inside the tools where product work now happens: your codebase, your notes, and your AI-assisted workflow.
01
Paste the markdown into Claude, ChatGPT, Cursor, Codex, Gemini, or another AI agent as reusable project context.
02
Use it before a planning, implementation, review, or audit session so the agent has constraints, criteria, and working structure up front.
03
Adapt the sections to your product, team, or repo before asking the agent to execute against it.
Markdown previewportfolio-case-study-proof-template.md
# Portfolio Case Study Proof Template Use this to turn product work into a case study that proves judgment instead of only taste. ## 1. Situation ```md Product: Team: Timeline: Role: Audience: Business context: User problem: ``` ## 2. Constraint Name what made the work hard: - Technical constraint: - Time constraint: - Research or data gap: - Design-system constraint: - Business pressure: - Existing user behavior: ## 3. Decisions | Decision | Alternatives | Why this path | Tradeoff | | --- | --- | --- | --- | | | | | | ## 4. Messy Middle Evidence Include at least three: - State map - Before/after flow - Decision log - Component or data constraint - Prototype screenshot - QA checklist - Rejected direction ## 5. Outcome ```md What changed: How we know: What is uncertain: What I would revisit: ``` ## 6. Hiring Signal The case study should make these visible: - Judgment under constraints. - Communication with engineering. - Taste in service of behavior. - Ability to simplify scope. - Reflection without fake certainty.