Communitygithub.com

qike7777/skill-library

Build a stunning personal portfolio website with a distinctive visual identity. Integrates the ui-ux-design-pro design database (67+ styles, 161 palettes, 57 font pairings) for bold, memorable aesthetics. Covers personal branding, project showcase layout, responsive HTML/CSS, interactive effects (hover/filter/lightbox), and Vercel deployment. Designed for designers, developers, freelancers, and creative professionals. Triggers: - "portfolio" - "personal portfolio" - "build a portfolio" - "portfolio website" - "showcase my work" - "personal website" - "作品集" - "个人网站" - "个人作品集

skill-library 是什么?

skill-library is a Claude Code agent skill that build a stunning personal portfolio website with a distinctive visual identity. Integrates the ui-ux-design-pro design database (67+ styles, 161 palettes, 57 font pairings) for bold, memorable aesthetics. Covers personal branding, project showcase layout, responsive HTML/CSS, interactive effects (hover/filter/lightbox), and Vercel deployment. Designed for designers, developers, freelancers, and creative professionals. Triggers: - "portfolio" - "personal portfolio" - "build a portfolio" - "portfolio website" - "showcase my work" - "personal website" - "作品集" - "个人网站" - "个人作品集.

兼容平台✓Claude Code~Codex CLI✓Cursor
npx skills add https://github.com/qike7777/skill-library/tree/HEAD/skills/3-websites-and-apps/portfolio

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

预览

来自技能 README

skill-library preview

文档

SKILL.md — Portfolio Builder

Build a personal portfolio that makes people remember you. Backed by 67+ UI styles, 161 color palettes, 57 font pairings, and portfolio-specific patterns. Pipeline: understand → brand identity → content → build → deploy.


Overview

A portfolio has one job: make someone want to work with you. Everything — design, copy, project selection, interactions — serves that goal.

Pipeline (5 Phases):

Phase 0 — Understand    →  Who are you? What do you do? Who's looking at this?
Phase 1 — Design        →  Visual identity: style, palette, fonts — the "feel" of your work
Phase 2 — Content       →  Bio, project descriptions, skills, contact
Phase 3 — Build         →  HTML/CSS + interactive project grid + animations
Phase 4 — Deliver       →  Live preview → Vercel deploy

Portfolio Types

TypeAudienceFocus
DesignerClients, hiring managersVisual work, case studies, process
DeveloperRecruiters, clients, collaboratorsProjects, tech stack, GitHub
Creative (photographer/illustrator/etc.)Clients, galleriesFull-bleed imagery, minimal text
FreelancerPotential clientsServices, past work, contact/CTA
Student / Career ChangerRecruiters, hiring managersProjects, skills, story arc

Tech Stack

Default: HTML + CSS + Vanilla JS — same as Landing Page. No framework needed.

  • Fastest to build and deploy
  • Zero dependencies, maximum control over animations
  • Vercel deploys as static files instantly

File Structure

portfolio/
├── index.html          # Main page (single-page or anchor-nav)
├── styles.css          # Design tokens → reset → layout → components → sections → animations
├── main.js             # Filter, lightbox, scroll effects, mobile nav
├── assets/
│   ├── images/         # Project screenshots, avatar, OG image
│   └── fonts/          # Self-hosted fonts (optional)
└── README.md

Phase 0 — Understand

0.1 Key Questions

QuestionWhy It Matters
What do you do?Designer / developer / photographer / freelancer / student / hybrid
Who will visit this?Recruiters, clients, collaborators, gallery curators
What's the #1 goal?Get hired / get freelance clients / get into a program / just have a presence
How many projects to show?3–6 is ideal; quality over quantity
Do you have a brand already?Existing colors, fonts, logo — or starting fresh
Tone?Minimal, bold, dark, playful, editorial, technical, luxury
Any reference portfolios?Sites you love or want to differentiate from

0.2 Portfolio Archetype Mapping

ArchetypeKey SectionsVisual Priority
DesignerHero + Selected Work (case studies) + About + Skills + ContactCase study detail, process shots
DeveloperHero + Projects (live links + GitHub) + Skills/Stack + About + ContactCode snippets, live demos, GitHub stats
CreativeFull-bleed Hero + Gallery/Grid + About + ContactImagery dominates, minimal UI chrome
FreelancerHero + Services + Work + Testimonials + ContactCTA prominence, trust signals
StudentHero + Projects + Skills + About + ContactStory arc — growth and potential

Phase 1 — Design Research

1.1 The Design Database

# Style search
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --domain style --max-results 5

# Color palette
python3 src/ui-ux-pro-max/scripts/search.py "<mood/industry>" --domain color --max-results 5

# Typography
python3 src/ui-ux-pro-max/scripts/search.py "<style/mood>" --domain typography --max-results 3

# Portfolio-specific patterns
python3 src/ui-ux-pro-max/scripts/search.py "portfolio" --domain landing --max-results 5

# Product-type rules for personal sites
python3 src/ui-ux-pro-max/scripts/search.py "portfolio personal site" --domain product

# Full design system
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --design-system -p "Portfolio"

# Stack-specific snippets
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --stack html

1.2 Portfolio-Specific Aesthetic Principles

A portfolio IS the design work. If it looks generic, the viewer assumes the work is generic.

❌ Generic (avoid)✅ Distinctive (aim for)
White background, Inter font, grey textA palette that expresses personality
"Hi, I'm [Name]. I'm a designer." heroAn opening line that creates intrigue
3-column card grid with identical paddingA layout that reflects the work's character
Hover: opacity 0.8Hover: reveals project info with personality
Footer: "© 2024 Name. All rights reserved."Footer that's an extension of the brand

1.3 Color Strategy for Portfolios

Unlike landing pages (accent = CTA), portfolio colors express personality:

PersonaPalette Direction
Minimalist designerNear-white + 1 strong accent, generous whitespace
Bold creativeDark bg + vivid accent, high contrast
Technical developerDark/terminal aesthetic OR clean light with code-inspired accents
Warm freelancerEarthy tones, approachable, human-feeling
Luxury/premiumDeep neutrals + gold/champagne, refined typography

1.4 Design Brief for Portfolios

## Portfolio Design Brief: <Name>

### Identity
- **Who:** <name + role>
- **Archetype:** <designer / developer / creative / freelancer / student>
- **Portfolio goal:** <get hired / get clients / just have a presence>
- **Target viewer:** <recruiters / clients / collaborators>

### Personality (pick 3 adjectives)
- <e.g., precise, warm, bold>

### Style Direction
- **Primary style:** <from search — e.g., "Dark Editorial", "Soft Minimalism">
- **One-word aesthetic:** <e.g., "focused", "expressive", "technical">
- **Why this style fits the work:** <one sentence>

### Color Palette
- **Background:** <hex> — <name>
- **Background secondary:** <hex> — for cards/panels
- **Text primary:** <hex>
- **Text muted:** <hex>
- **Accent:** <hex> — used sparingly, maximum impact
- **Border/divider:** <hex>

### Typography
- **Heading font:** <name> + weight + Google Fonts URL
- **Body font:** <name> + Google Fonts URL
- **Heading style note:** <e.g., "tight tracking, large scale contrast">

### Layout Pattern
- **Grid:** <e.g., asymmetric 2-col, masonry, full-bleed row>
- **Project card style:** <e.g., image-first with hover overlay, minimal text card>
- **Section transitions:** <e.g., full-width dividers, staggered entry, none>

### Interactions
- **Project card hover:** <e.g., scale + overlay with title/tags>
- **Scroll animations:** <e.g., stagger fade-up on work grid>
- **Cursor:** <default / custom dot / none>

1.5 Quality Criteria

  • Archetype identified, primary goal clear
  • 3+ style options searched before deciding
  • Palette expresses personality (not just "clean" defaults)
  • Font pairing has contrast — one display, one body
  • Layout pattern matches work type (photography ≠ code projects)
  • User approved Design Brief

Phase 2 — Content

2.1 Hero Copy

The hero opening line is the most important text on the page. It must answer: who are you, what do you do, and why does it matter — with personality.

Formula options:

FormulaExample
Role + differentiator"Product designer who obsesses over the 0.1-second moments"
Outcome-first"I make complex software feel simple"
Bold statement"Good design is invisible. Great design is inevitable."
Playful/direct"I build things for the web. Currently open to work."
Name + descriptor"Hi, I'm Maya — I design for humans, not screens"

Avoid:

  • "I'm a passionate designer with 5 years of experience"
  • "Welcome to my portfolio"
  • Generic adjectives: creative, innovative, dedicated, passionate

2.2 Project Descriptions

Each project entry needs:

### <Project Name>
**Role:** <your role — e.g., "Lead Designer", "Solo Developer">
**Type:** <e.g., "Mobile App", "Brand Identity", "Web App">
**Tags:** [<tech/skill tags>]

**The challenge:** <1-2 sentences — what problem needed solving>
**What I did:** <2-3 sentences — your specific contribution and decisions>
**The outcome:** <1 sentence with a result if possible — "Reduced onboarding time by 40%">

[Live →](<url>)  [Case Study →](<url>)  [GitHub →](<url>)

Rules:

  • Lead with the PROBLEM, not the technology
  • Your ROLE must be specific — "designer" is not a role, "designed the onboarding flow" is
  • If you have metrics, use them. If not, describe the qualitative outcome
  • 3–6 projects max — curate ruthlessly

2.3 About Section

Structure:

  1. Who you are — current state (role, location, what you're focused on)
  2. How you got here — brief arc (not a resume, a story)
  3. What you care about — the "why" behind the work
  4. What you're looking for — open to work / specific types of projects / collaborations

Length: 80–150 words. Not a bio, not a CV. A person.

2.4 Skills / Stack Section

For designers:

Design: Figma, Prototyping, Design Systems, Typography, Motion
Research: User Interviews, Usability Testing, Competitive Analysis

For developers:

Frontend: React, TypeScript, Next.js, CSS/Tailwind
Backend: Node.js, PostgreSQL, REST/GraphQL
Tools: Git, Docker, Vercel, Figma

Display as tag clouds, icon grids, or grouped lists — never just a plain bullet list.

2.5 Contact Section

Keep it dead simple:

  • Email (the most important thing — make it clickable with mailto:)
  • 2–3 social links (GitHub, LinkedIn, Twitter/X, Dribbble — pick what's relevant)
  • Optional: a short "currently available for..." line
  • Optional: a simple contact form (Formspree)

No contact forms with 6 fields. No "let's grab coffee" filler.

2.6 Quality Criteria

  • Hero opening line has personality (not generic)
  • Each project leads with the problem, not the tech
  • Roles are specific, not just job titles
  • About section reads like a person wrote it
  • 3–6 projects, curated for quality
  • Contact section has a mailto link as the primary action

Phase 3 — Build

3.1 HTML Structure

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title><Name> — <Role></title>
  <meta name="description" content="<150-char personal description>">

  <!-- Google Fonts -->
  <link rel="preconnect" href="https://fonts.googleapis.com">
  <link href="https://fonts.googleapis.com/css2?family=<HeadingFont>:wght@400;600;700&family=<BodyFont>:wght@400;500&display=swap" rel="stylesheet">

  <!-- OG Tags -->
  <meta property="og:title" content="<Name> — <Role>">
  <meta property="og:description" content="<description>">
  <meta property="og:image" content="<og-image.jpg>">
  <meta name="twitter:card" content="summary_large_image">

  <link rel="stylesheet" href="styles.css">
</head>
<body>
  <nav class="nav" id="nav">...</nav>

  <main>
    <section class="hero" id="home">...</section>
    <section class="work" id="work">...</section>
    <section class="about" id="about">...</section>
    <section class="skills" id="skills">...</section>  <!-- optional -->
    <section class="contact" id="contact">...</section>
  </main>

  <footer class="footer">...</footer>

  <div class="project-modal" id="modal" aria-hidden="true">...</div>  <!-- optional lightbox -->

  <script src="main.js"></script>
</body>
</html>

3.2 CSS Architecture

/* ── 1. Google Fonts ── */
/* ── 2. CSS Variables ── */
:root {
  /* Colors from Design Brief */
  --color-bg: <hex>;
  --color-bg-secondary: <hex>;
  --color-text: <hex>;
  --color-text-muted: <hex>;
  --color-accent: <hex>;
  --color-border: <hex>;

  /* Typography */
  --font-heading: '<HeadingFont>', serif;
  --font-body: '<BodyFont>', sans-serif;

  /* Type scale */
  --text-hero: clamp(3rem, 8vw, 7rem);
  --text-h2: clamp(1.75rem, 4vw, 2.75rem);
  --text-h3: clamp(1.125rem, 2vw, 1.5rem);
  --text-body: 1.0625rem;
  --text-sm: 0.875rem;

  /* Spacing */
  --section-padding: clamp(5rem, 12vw, 10rem);
  --container-width: 1200px;
  --gap: 1.5rem;
  --radius: 8px;
  --radius-lg: 16px;

  /* Transitions */
  --transition: 0.3s ease;
  --transition-slow: 0.6s ease;
}

/* ── 3. Reset + Base ── */
/* ── 4. Layout (.container, .section, .grid-2, .grid-3) ── */
/* ── 5. Nav (fixed, scroll-aware bg change) ── */
/* ── 6. Hero ── */
/* ── 7. Work / Project Grid ── */
/* ── 8. Project Card + Hover ── */
/* ── 9. About ── */
/* ── 10. Skills ── */
/* ── 11. Contact ── */
/* ── 12. Footer ── */
/* ── 13. Modal / Lightbox (if used) ── */
/* ── 14. Scroll animations ── */
/* ── 15. Responsive ── */

3.3 Project Grid

<!-- Work section with optional filter -->
<section class="work" id="work">
  <div class="container">
    <div class="work__header">
      <h2 class="work__title">Selected Work</h2>
      <!-- Optional filter tabs -->
      <div class="work__filters" role="tablist">
        <button class="filter-btn active" data-filter="all">All</button>
        <button class="filter-btn" data-filter="design">Design</button>
        <button class="filter-btn" data-filter="dev">Development</button>
      </div>
    </div>

    <div class="work__grid" id="work-grid">
      <!-- Project Card -->
      <article class="project-card" data-category="design" data-index="0">
        <div class="project-card__image">
          <img src="assets/images/project-1.jpg" alt="<Project Name> — <brief description>" loading="lazy">
          <div class="project-card__overlay">
            <span class="project-card__type"><Type></span>
            <h3 class="project-card__title"><Project Name></h3>
            <div class="project-card__links">
              <a href="..." class="project-card__link">View Project →</a>
            </div>
          </div>
        </div>
      </article>
      <!-- Repeat for each project -->
    </div>
  </div>
</section>

3.4 Interactive Effects

Project Card Hover:

.project-card__image {
  position: relative;
  overflow: hidden;
}

.project-card__image img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  transition: transform var(--transition-slow);
}

.project-card:hover .project-card__image img {
  transform: scale(1.05);
}

.project-card__overlay {
  position: absolute;
  inset: 0;
  background: linear-gradient(to top, rgba(0,0,0,0.8) 0%, transparent 60%);
  opacity: 0;
  transition: opacity var(--transition);
  display: flex;
  flex-direction: column;
  justify-content: flex-end;
  padding: var(--gap);
  color: #fff;
}

.project-card:hover .project-card__overlay {
  opacity: 1;
}

Filter Functionality (JS):

const filterButtons = document.querySelectorAll('.filter-btn');
const projectCards = document.querySelectorAll('.project-card');

filterButtons.forEach(button => {
  button.addEventListener('click', () => {
    const filter = button.dataset.filter;
    
    // Update active button
    filterButtons.forEach(btn => btn.classList.remove('active'));
    button.classList.add('active');

    // Filter projects
    projectCards.forEach(card => {
      if (filter === 'all' || card.dataset.category === filter) {
        card.style.display = 'block';
      } else {
        card.style.display = 'none';
      }
    });
  });
});

Lightbox Modal (JS):

const modal = document.getElementById('modal');
const modalImage = modal.querySelector('.modal__image');
const modalClose = modal.querySelector('.modal__close');

projectCards.forEach(card => {
  card.addEventListener('click', () => {
    const img = card.querySelector('.project-card__image img');
    modalImage.src = img.src.replace('-thumb', '-full'); // assumes naming convention
    modal.setAttribute('aria-hidden', 'false');
  });
});

modalClose.addEventListener('click', () => modal.setAttribute('aria-hidden', 'true'));
modal.addEventListener('click', (e) => {
  if (e.target === modal) modal.setAttribute('aria-hidden', 'true');
});

Scroll Animations (JS):

const observer = new IntersectionObserver((entries) => {
  entries.forEach(entry => {
    if (entry.isIntersecting) {
      entry.target.classList.add('revealed');
    }
  });
}, { threshold: 0.1 });

document.querySelectorAll('.project-card, .about__content, .skill-tag').forEach(el => {
  el.classList.add('hidden');
  observer.observe(el);
});
.hidden {
  opacity: 0;
  transform: translateY(2rem);
  transition: opacity 0.6s ease, transform 0.6s ease;
}

.revealed {
  opacity: 1;
  transform: translateY(0);
}

3.5 Mobile Navigation

<nav class="nav" id="nav">
  <button class="nav__toggle" aria-label="Toggle navigation">☰</button>
  <ul class="nav__links">
    <li><a href="#home">Home</a></li>
    <li><a href="#work">Work</a></li>
    <li><a href="#about">About</a></li>
    <li><a href="#skills">Skills</a></li>
    <li><a href="#contact">Contact</a></li>
  </ul>
</nav>
const navToggle = document.querySelector('.nav__toggle');
const navLinks = document.querySelector('.nav__links');

navToggle.addEventListener('click', () => {
  navLinks.classList.toggle('open');
  navToggle.setAttribute('aria-expanded', navLinks.classList.contains('open'));
});

// Close nav on link click (mobile)
navLinks.querySelectorAll('a').forEach(link => {
  link.addEventListener('click', () => navLinks.classList.remove('open'));
});
@media (max-width: 768px) {
  .nav__toggle {
    display: block;
    background: none;
    border: none;
    font-size: 1.5rem;
    cursor: pointer;
  }

  .nav__links {
    display: none;
    position: absolute;
    top: 100%;
    left: 0;
    width: 100%;
    background: var(--color-bg);
    flex-direction: column;
    padding: var(--gap);
    box-shadow: 0 4px 12px rgba(0,0,0,0.1);
  }

  .nav__links.open {
    display: flex;
  }
}

3.6 Quality Criteria

  • HTML is semantic and accessible (nav landmarks, alt attributes, ARIA labels)
  • CSS uses named tokens from design brief
  • Project grid has hover effect with overlay
  • Filter functionality works (if more than one category)
  • Lightbox works with keyboard accessibility (Escape to close)
  • Scroll-triggered entrance animations are implemented
  • Responsive design works on mobile, tablet, desktop
  • Navigation collapses to hamburger on mobile
  • All images have descriptive alt text
  • OG meta tags are populated

Phase 4 — Deliver

4.1 Live Preview

# Serve locally for testing
npx serve portfolio &

# Open in browser
open http://localhost:3000

4.2 Deploy to Vercel

cd portfolio

# Install Vercel CLI (if not installed)
npm i -g vercel

# Deploy
vercel --prod

Configure vercel.json if needed:

{
  "version": 2,
  "builds": [{"src": "**/*", "use": "@vercel/static"}],
  "routes": [{"src": "/(.*)", "dest": "/index.html"}]
}

4.3 Quality Checklist (Final)

  • All links work (internal anchors, external, social)
  • Images load correctly (no broken links)
  • Contact email is clickable (mailto:)
  • OG preview renders correctly (test with opengraph.xyz)
  • Page loads fast (lighthouse target: 90+ performance)
  • Responsive in portrait/landscape on mobile
  • Tab through the page works (accessibility)
  • No console errors
  • User reviews and approves before go-live
  • Custom domain set up if applicable

Portfolio Output Checklist

Phase 0 — Understand

  • Archetype, audience, and primary goal identified

Phase 1 — Design Research

  • Design Brief completed and approved
  • Palette, fonts, layout, interactions specified

Phase 2 — Content

  • Hero line written
  • Each project has Problem → Action → Outcome
  • About section written (80–150 words, personal tone)
  • Skills/stack listed appropriately
  • Contact section with mailto

Phase 3 — Build

  • HTML, CSS, and JS files created
  • All interactive features implemented
  • Responsive design complete

Phase 4 — Deliver

  • Live preview verified
  • Deployed to Vercel (or alternative)
  • Final quality checklist passed

Design Database Commands (Quick Reference)

# Style search
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --domain style --max-results 5

# Color palette
python3 src/ui-ux-pro-max/scripts/search.py "<mood/industry>" --domain color --max-results 5

# Typography
python3 src/ui-ux-pro-max/scripts/search.py "<style/mood>" --domain typography --max-results 3

# Portfolio-specific patterns
python3 src/ui-ux-pro-max/scripts/search.py "portfolio" --domain landing --max-results 5

# Product-type rules for personal sites
python3 src/ui-ux-pro-max/scripts/search.py "portfolio personal site" --domain product

# Full design system
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --design-system -p "Portfolio"

# Stack-specific snippets
python3 src/ui-ux-pro-max/scripts/search.py "<query>" --stack html

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

相关技能