proof-points
Extract proof points from portfolio case studies and generate punchy scripts with storyboards. Use when user wants to create impactful narratives about their work, develop case study content, write portfolio scripts, identify what makes their project valuable, or pair achievements with visuals. Triggers on requests like "help me explain this project," "what did I improve here," "create a script for this case study," or "extract the value from this work."
When & Why to Use This Skill
The Proof Points skill is designed to transform raw project data and case studies into compelling, high-impact narratives. By extracting specific, verifiable improvements and framing them as client-focused outcomes, it helps professionals generate structured scripts and visual storyboards. This tool is essential for anyone looking to communicate the value of their work through portfolios, video content, or professional presentations using a proven 'Problem-Solution-Impact' framework.
Use Cases
- Portfolio Development: Convert technical project notes into punchy, value-driven scripts that highlight specific achievements for personal websites or job applications.
- Short-Form Video Creation: Generate scripts and storyboard layouts for YouTube Shorts, TikTok, or LinkedIn videos to showcase design or development 'before and after' transformations.
- Client Case Studies: Extract key 'proof points' from complex projects to create professional documentation that focuses on business outcomes rather than just process.
- Visual Storytelling: Brainstorm the most effective visual evidence, such as diagrams or interaction recordings, to pair with project narratives for maximum credibility.
- Stakeholder Presentations: Translate technical fixes into clear, impactful stories that demonstrate ROI and project success to non-technical stakeholders.
| name | proof-points |
|---|---|
| description | Extract proof points from portfolio case studies and generate punchy scripts with storyboards. Use when user wants to create impactful narratives about their work, develop case study content, write portfolio scripts, identify what makes their project valuable, or pair achievements with visuals. Triggers on requests like "help me explain this project," "what did I improve here," "create a script for this case study," or "extract the value from this work." |
Proof Points
Extract specific, verifiable improvements from projects and assemble them into impactful narratives.
Workflow
1. Gather Input
Accept either:
- Visual evidence: Screenshots, flipbook demos, before/after comparisons
- Description: User explains what they did, the problem, the solution
If visual evidence provided, analyze it first. If description only, ask clarifying questions about specific improvements made.
2. Extract Draft Proof Points
Identify 2-5 proof points. Each proof point must be:
- Specific: "horizontal nav truncates on tablet" not "it wasn't responsive"
- Verifiable: Can be demonstrated with evidence
- Client-value-focused: Frame as business outcome, not just technical fix
Present draft proof points to user:
"Here's what I'm seeing as the key improvements. Did I get this right? What am I missing?"
3. Refine Collaboratively
Apply these principles when refining:
- Lead with problem, not process - Nobody cares about "conducted research" until they feel the pain
- Technical specifics = credibility - Concrete details beat vague claims
- Frame fixes as client outcomes - "Users couldn't add restaurants because the integration was broken" > "I fixed the script"
- Contrast creates impact - Before/after in the same breath
Ask about anything not visible in screenshots:
"Are there improvements that aren't immediately visible here?"
4. Brainstorm Visuals
For each proof point, propose the most impactful visual:
- Before/after comparison
- Screenshot of the specific problem
- Diagram showing the fix
- Demo/interaction recording
User will create/capture these later - just describe what would work best.
5. Assemble Output
Generate a Markdown file with:
## Script
[Hook - attention-grabber, 1-2 sentences]
[Problem - the pain point, what was broken]
[Proof Points - 2-4 specific improvements with contrast]
[Outcome - client value delivered]
## Storyboard
| Text | Image |
|------|-------|
| [Script segment] | [Description of ideal visual] |
| ... | ... |
Terminology
| Term | Meaning |
|---|---|
| Hook | Opening attention-grabber (first 1-3 seconds of video, or first sentence) |
| Proof points | Specific, verifiable improvements - the core deliverable |
| Outcome | Client value delivered - the "so what" |
Output Flexibility
The script works for multiple formats:
- YouTube Shorts (9:16 video with narration)
- Case study hero slideshow (16:9 or square)
- Written intro paragraph with supporting images
- Interactive comparison demos
The storyboard's "Image" column describes ideal visuals - user decides execution format.