From example-skills
Curate and present creative/technical work for maximum impact. Structure case studies, craft project narratives, optimize for different audiences (hiring managers, clients, collaborators). Supports portfolio websites, PDF decks, and presentation formats. Triggers on portfolio review, case study writing, project showcase, or work presentation requests.
npx claudepluginhub organvm-iv-taxis/a-i--skills --plugin document-skillsThis skill uses the workspace's default tool permissions.
Transform scattered work into compelling professional narrative.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Transform scattered work into compelling professional narrative.
A portfolio isn't a list of projects—it's a story about who you are and what you can do for the person viewing it.
Before curating, identify the viewer:
| Audience | Primary Interest | Time Available | Decision Criteria |
|---|---|---|---|
| Hiring Manager | Can you do the job? | 30-90 seconds initial | Relevant skills, growth |
| Technical Lead | How do you think? | 2-5 minutes deep dive | Problem-solving, code quality |
| Client | Can you solve my problem? | 1-2 minutes | Similar work, results |
| Collaborator | Would I enjoy working with you? | Variable | Process, communication |
| Academic | What's your contribution? | Thorough review | Rigor, originality |
[Hero: Your positioning statement]
[Featured Work: 3-4 best pieces]
[Brief About]
[Contact/CTA]
Positioning Statement Formula:
I'm a [role] who [unique approach/specialty].
I help [audience] achieve [outcome] through [method].
The 3-5-7 Rule:
Selection Criteria:
| Criterion | Weight | Question |
|---|---|---|
| Relevance | 30% | Does it match target opportunity? |
| Impact | 25% | Can I quantify results? |
| Craft | 20% | Does it showcase my best work? |
| Recency | 15% | Is it current enough? |
| Story | 10% | Is there a compelling narrative? |
## [Project Name]
**Role**: [Your specific role]
**Timeline**: [Duration]
**Team**: [Size/composition]
[One compelling image]
[2-3 sentence summary: Problem → Solution → Result]
**Key Outcome**: [Single quantified result]
# [Project Name]
## Overview
[Elevator pitch: What is it? Who's it for? Why does it matter?]
## The Challenge
[Problem statement with context and stakes]
## My Role
[Specific responsibilities and contributions]
## Process
[Key phases with visuals]
1. Discovery/Research
2. Ideation/Strategy
3. Execution/Implementation
4. Iteration/Refinement
## Solution
[What was built/created with visuals]
## Results
[Quantified outcomes]
- [Metric]: [Before] → [After]
- [Metric]: [Improvement]
## Reflection
[What I learned, what I'd do differently]
See references/case-study-template.md
Status Quo → Disruption → Struggle → Insight → Resolution → New Normal
[User] was struggling with [problem]
We discovered [insight]
So we built [solution]
Which resulted in [impact]
We started by [research/discovery]
Which revealed [key insight]
Leading us to [design decision]
Through [iteration], we arrived at [solution]
Given [constraints: time/budget/tech]
We had to [creative approach]
Which taught us [lesson]
And delivered [outcome despite constraints]
| Type | Purpose | Specs |
|---|---|---|
| Hero | First impression | 16:9 or 4:3, high-res |
| Process | Show thinking | Annotated, clear |
| Detail | Craft quality | Cropped, focused |
| Before/After | Show impact | Side-by-side |
| Context | Real-world use | In-situ photos |
When to use:
Keep under 60 seconds for portfolio context.
❌ "E-commerce Website Redesign" ✅ "Increasing Conversion 40% Through Checkout Simplification"
❌ "I designed the UI and implemented the frontend" ✅ "Led design and development of checkout flow that reduced cart abandonment from 68% to 41%"
| Weak | Strong |
|---|---|
| Improved performance | Reduced load time from 4.2s to 0.8s |
| Increased engagement | Grew DAU 3x over 6 months |
| Better user experience | NPS improved from 32 to 67 |
See references/website-structure.md
See references/pdf-portfolio.md
See references/deck-structure.md
references/case-study-template.md - Full case study formatreferences/website-structure.md - Portfolio website architecturereferences/pdf-portfolio.md - PDF portfolio best practicesreferences/deck-structure.md - Presentation deck format