Interactive Portfolio workflow skill. Use this skill when the user needs Expert in building portfolios that actually land jobs and clients - and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills/skills/interactive-portfolio from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses EXTERNAL_SOURCE.json plus ORIGIN.md as the provenance anchor for review.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Capabilities, Patterns, Portfolio Architecture, Project Showcase, Developer Portfolio, Portfolio Interactivity.
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
| Situation | Start here | Why it matters |
|---|---|---|
| First-time use | EXTERNAL_SOURCE.json | Confirms repository, branch, commit, and imported path before touching the copied workflow |
| Provenance review | ORIGIN.md | Gives reviewers a plain-language audit trail for the imported source |
| Workflow execution | SKILL.md | Starts with the smallest copied file that materially changes execution |
| Supporting context | SKILL.md | Adds the next most relevant copied source file without loading the entire package |
| Handoff decision | ## Related Skills | Helps the operator switch to a stronger native skill when the task drifts |
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Use @interactive-portfolio-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Review @interactive-portfolio-v2 against EXTERNAL_SOURCE.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Use @interactive-portfolio-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Review @interactive-portfolio-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/interactive-portfolio, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open EXTERNAL_SOURCE.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
@hugging-face-vision-trainer-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.@humanize-chinese-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.@hybrid-cloud-architect-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.@hybrid-cloud-networking-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
| Resource family | What it gives the reviewer | Example path |
|---|---|---|
references | copied reference notes, guides, or background material from upstream | references/n/a |
examples | worked examples or reusable prompts copied from upstream | examples/n/a |
scripts | upstream helper scripts that change execution or validation | scripts/n/a |
agents | routing or delegation notes that are genuinely part of the imported package | agents/n/a |
assets | supporting assets or schemas copied from the source package | assets/n/a |
Structure that works for portfolios
When to use: When planning portfolio structure
In 30 seconds, visitors should know:
| Section | Purpose | Priority |
|---|---|---|
| Hero | Hook + identity | Critical |
| Work/Projects | Prove skills | Critical |
| About | Personality + story | Important |
| Contact | Convert interest | Critical |
| Testimonials | Social proof | Nice to have |
| Blog/Writing | Thought leadership | Optional |
Option 1: Single page scroll
- Best for: Designers, creatives
- Works well with animations
- Mobile friendly
Option 2: Multi-page
- Best for: Lots of projects
- Individual case study pages
- Better for SEO
Option 3: Hybrid
- Main sections on one page
- Detailed case studies separate
- Best of both worlds
[Your name]
[What you do in one line]
[One line that differentiates you]
[CTA: View Work / Contact]
How to present work effectively
When to use: When building project sections
| Element | Purpose |
|---|---|
| Thumbnail | Visual hook |
| Title | What it is |
| One-liner | What you did |
| Tech/tags | Quick scan |
| Results | Proof of impact |
1. Hero image/video
2. Project overview (2-3 sentences)
3. The challenge
4. Your role
5. Process highlights
6. Key decisions
7. Results/impact
8. Learnings (optional)
9. Links (live, GitHub, etc.)
| Instead of | Write |
|---|---|
| "Built a website" | "Increased conversions 40%" |
| "Designed UI" | "Reduced user drop-off 25%" |
| "Developed features" | "Shipped to 50K users" |
What works for dev portfolios
When to use: When building developer portfolio
| Include | Avoid |
|---|---|
| Real problems solved | Tutorial clones |
| Side projects with users | Incomplete projects |
| Open source contributions | "Coming soon" |
| Technical challenges | Basic CRUD apps |
// Show code snippets that demonstrate:
- Clean architecture decisions
- Performance optimizations
- Clever solutions
- Testing approach
Adding memorable interactive elements
When to use: When wanting to stand out
| Level | Example | Risk |
|---|---|---|
| Subtle | Hover effects, smooth scroll | Low |
| Medium | Scroll animations, transitions | Medium |
| High | 3D, games, custom cursors | High |
- Terminal-style interface (for devs)
- OS desktop metaphor
- Game-like navigation
- Interactive timeline
- 3D workspace scene
- Generative art background
Severity: MEDIUM
Situation: Spent 6 months on portfolio, have 2 projects to show
Symptoms:
Why this breaks: Procrastination disguised as work. Portfolio IS a project, but not THE project. Diminishing returns on polish. Ship it and iterate.
Recommended fix:
| Element | MVP Version |
|---|---|
| Hero | Name + title + one line |
| Projects | 3-4 best pieces |
| About | 2-3 paragraphs |
| Contact | Email + LinkedIn |
Week 1: Design and structure
Week 2: Build core pages
Week 3: Add 3-4 projects
Week 4: Polish and launch
Severity: HIGH
Situation: Recruiters check on phone, everything breaks
Symptoms:
Why this breaks: Built desktop-first. Didn't test on real devices. Complex interactions don't translate. Forgot about thumb zones.
Recommended fix:
[ ] iPhone Safari
[ ] Android Chrome
[ ] Tablet sizes
[ ] Slow 3G simulation
[ ] Real device (not just DevTools)
/* Complex hover → simple tap */
@media (hover: none) {
.hover-effect {
/* Show content directly */
}
}
Severity: MEDIUM
Situation: Great portfolio, zero contacts
Symptoms:
Why this breaks: No clear CTA. Contact buried at bottom. Multiple competing actions. Assuming visitors will figure it out.
Recommended fix:
| Goal | CTA |
|---|---|
| Get hired | "Let's work together" |
| Freelance | "Start a project" |
| Network | "Say hello" |
| Specific role | "Hire me for [X]" |
Hero section: Main CTA
After projects: Secondary CTA
Footer: Final CTA
Floating: Optional persistent CTA
Severity: MEDIUM
Situation: Best work is 3 years old, newer work not shown
Symptoms:
Why this breaks: Haven't updated in years. Newer work is "not ready." Scared to remove old favorites. Portfolio drift.
Recommended fix:
| Action | Frequency |
|---|---|
| Add new project | When completed |
| Remove old project | Yearly review |
| Update copy | Every 6 months |
| Tech refresh | Every 1-2 years |
Keep if:
Remove if:
Severity: HIGH
Message: No clear way for visitors to contact you.
Fix action: Add prominent contact CTA in hero and after projects section
Severity: HIGH
Message: Portfolio may not be mobile-responsive.
Fix action: Add <meta name='viewport' content='width=device-width, initial-scale=1'>
Severity: MEDIUM
Message: Portfolio images may be slowing down load time.
Fix action: Use WebP, implement lazy loading, add srcset for responsive images
Severity: MEDIUM
Message: Projects should have live links or source code.
Fix action: Add live demo URLs and GitHub links where possible
Severity: LOW
Message: Projects don't show impact or results.
Fix action: Add metrics, outcomes, or testimonials to project descriptions
Skills: interactive-portfolio, frontend, scroll-experience
Workflow:
1. Plan portfolio structure
2. Select 3-5 best projects
3. Design hero and project sections
4. Add subtle scroll animations
5. Implement and optimize
6. Launch and share
Skills: interactive-portfolio, 3d-web-experience, scroll-experience, branding
Workflow:
1. Define personal brand
2. Design unique experience
3. Build interactive elements
4. Showcase work creatively
5. Ensure mobile works
6. Launch