[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78AVARK9227GQADRKWYFWR9":3,"skill-same:01M78AVARK9227GQADRKWYFWR9":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M78AVARK9227GQADRKWYFWR9","portfolio-website-design",null,"Build professional portfolio websites — dark or light theme, glassmorphism cards, founder\u002Fengineer positioning — with full deployment (Vercel \u002F GitHub Pages).","abdullibrahim733-pixel\u002FEagle","abdullibrahim733-pixel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F230504522?v=4","01M787SK0DQR0H1K326DJT6EBK","ibrahim abdull","01M787SK1HWS9V959THKZM6N70",0,"MIT","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: portfolio-website-design\ndescription: Build professional portfolio websites — dark or light theme, glassmorphism cards, founder\u002Fengineer positioning — with full deployment (Vercel \u002F GitHub Pages).\nversion: 1.2.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [design, html, css, portfolio, glassmorphism, ux, ui, vercel, deployment]\n    related_skills: [static-site-deployment, claude-design, popular-web-designs]\n---\n\n# Portfolio Website Design\n\nBuild a complete, deployable portfolio site that positions the user professionally. Supports dark and light themes with glassmorphism cards, responsive layout, and a clear information hierarchy.\n\n## When To Use\n\nUse this skill when the user requests:\n- A complete portfolio or personal website\n- A developer \u002F engineer \u002F founder landing page\n- Professional online presence with project showcase\n- Any request to \"prepare my portfolio\"\n\n## Key Features\n\n1. **Glassmorphism Design**:\n   - Semi-transparent card backgrounds with backdrop blur\n   - Works on both dark and light themes (different CSS variables per theme)\n   - Subtle borders for depth without overwhelming content\n   - Ensure proper contrast — text must be readable on blurred backgrounds\n\n2. **Color Palette (choose one)**:\n   - **Dark Tech** (default for engineers\u002FAI\u002Frobotics founders): `bg: #0a0a0f`, accents: Emerald `#10b981` + Amber `#f59e0b`\n   - **Light Professional** (default for consultants\u002Fdesigners): white bg, Olive `#3D9970` + Light Green `#A8E6CF` accents\n   - Always pick the palette that matches the user's brand and industry — ask if uncertain\n\n3. **Responsive Layout**:\n   - Mobile-first approach with CSS Grid + Flexbox\n   - Media queries for all screen sizes\n   - Hamburger menu on mobile\n\n4. **Complete Sections**:\n   - Hero with headline + CTA\n   - About \u002F personal story\n   - Expertise \u002F services \u002F skills (3-column cards)\n   - Ventures \u002F Companies \u002F Projects (for founders with multiple ventures)\n   - Research or technical depth section (for engineers)\n   - Philosophy \u002F operating principles (optional, adds personality)\n   - Contact with email + social links\n   - Footer\n\n## Honesty Audit: Claims → Receipts\n\nBefore building or rebuilding a portfolio, audit every claim against the user's actual artifacts (disk, repos, deployed projects). A portfolio's job is to show what has been DONE, not what is INTENDED. Every public claim must survive an interview. This is a core user preference (Truth Over Ego) — a claim with no receipt is a liability, not a feature.\n\n### When to run this\n- Responding to critique like \"your site overclaims\" or \"you've shipped nothing\"\n- Rebranding (company name change, identity shift)\n- Before applying to programs \u002F accelerators \u002F scholarships where claims get checked\n\n### Workflow\n1. **Locate the source, not just the live URL** — find the local project dir (e.g. `~\u002FProjects\u002Fportfolio-website\u002F`). Curl the live site to see served HTML, but audit the source files for edits.\n2. **Map the claim surface** — title\u002Fmeta, nav CTAs, hero, about, projects (often a JS data file like `js\u002Fprojects.js`), research (often `js\u002Fresearch.js`), contact, footer, console easter egg (`js\u002Fmain.js`).\n3. **Verify every claim against disk** — check `~\u002FProjects\u002F` for real artifacts (code, PDFs, STLs, protos, market reports). A venture with no on-disk artifact gets removed or relabeled \"planned\u002Fconcept\". Count real things: `find \u003Cproject> -type f | wc -l`, prototype dirs, build outputs.\n4. **Fix dead links to real artifacts** — if an artifact exists but the site links elsewhere (e.g. paper PDF present, button points at a GitHub profile), point the button at the real file.\n5. **Label research honestly** — \"proof-of-concept \u002F educational pipeline\", NOT \"drug discovery\" for a 2-qubit VQE toy model. Mark planned items \"Roadmap — not yet run\". The page can stay up; the framing must be true.\n6. **Brand coherence** — title, meta, footer, console log, and JS data (`lab:` fields) must all name the SAME single company. Flag mismatches (site says UMG Africa, research data says Version Extreme Cooperation) and email-domain lag after a rebrand — change with user confirmation, don't silently pick.\n7. **Receipts over aspirational metrics** — replace counters like \"5 Active Ventures\" \u002F \"∞ First Principles\" with verifiable numbers: \"1 Company \u002F 52 Prototypes Built \u002F 4 R&D Programs\". Every number must be countable from disk.\n8. **Truthful role titles** — \"Form 5 student and founder\", never \"engineer\" before credentials exist. Navbar \"Open to opportunities\" instead of \"Available for projects\" when nothing is shipped.\n9. **Deploy + verify** — `vercel deploy --prod --yes`, then curl the LIVE aliased URL: grep for expected new strings, `grep -c` removed strings (must be 0), new asset paths return 200 (see static-site-deployment).\n\n### Pitfalls\n- **JS countup counters render \"0\" in raw HTML \u002F static screenshots.** A critic can screenshot \"0 Active Ventures\" while the page animates to the real value. Audit the `data-target` attribute, not the rendered text; when responding to such a critique, check the JS before accepting the claim.\n- **Hidden-but-present images** — a real `\u003Cimg src=\"assets\u002Fimages\u002Fprofile.jpg\" style=\"display:none\">` next to a \"Your photo here\" placeholder. Enable it (drop the inline style) instead of leaving the placeholder.\n- **JS data files are part of the claim surface** — editing index.html alone leaves `js\u002Fprojects.js` \u002F `js\u002Fresearch.js` \u002F the console easter egg contradicting the new identity. Grep the whole source dir for stale brand strings before deploying.\n\n## Workflow\n\n### Phase 0: Research (DO FIRST — most important step)\nBefore writing any code, research the user's background:\n1. **Obsidian vault** — search for `about me.md`, company notes, project descriptions\n2. **GitHub repos** — check for existing projects, READMEs, portfolio content\n3. **Previous conversations** (session_search) — look for personal details, preferences, past portfolio discussions\n4. **Extract structured info**: name, age, location, title, companies\u002Fproducts with descriptions, expertise areas, research domains, philosophy\n5. Identify the **core narrative** — is this a founder, an engineer, a researcher, or all three? The hero headline and about section must tell one coherent story.\n\n### Phase 1: Planning\n- Define site structure based on extracted content\n- Choose dark or light theme based on user's industry (dark for tech\u002FAI\u002Fengineering, light for design\u002Fconsulting)\n- Map each Obsidian note section to a page\u002Fsection\n- Decide on a hero headline that captures the user's unique angle\n\n### Phase 2: Design System\n- Establish color palette (CSS custom properties)\n- Define typography hierarchy (Inter for body, JetBrains Mono \u002F Fira Code for tech elements)\n- Create glassmorphism component styles (dark glass `rgba(255,255,255,0.03)` for dark themes, light glass `rgba(255,255,255,0.85)` for light themes)\n- Plan responsive breakpoints\n\n### Phase 3: Implementation\n- Create directory structure: `index.html`, `css\u002Fstyles.css`, `js\u002Fmain.js`\n- Write semantic HTML with sections matching extracted content\n- Implement CSS with full glassmorphism, gradients, and animations\n- Add JavaScript for: scroll effects, mobile menu, smooth anchor nav, parallax, scroll-triggered reveals\n- Use Font Awesome CDN for icons\n\n### Phase 4: Favicon & Brand Assets\nGenerate a complete favicon set before deployment — every portfolio needs a proper icon, not a default browser favicon.\n\n**Required files** (all in project root):\n| File | Size | Purpose |\n|------|------|---------|\n| `favicon.svg` | Scalable | Modern browsers (crisp at any size, supports gradients) |\n| `favicon-32x32.png` | 32×32 | Standard browser tab |\n| `favicon-16x16.png` | 16×16 | Bookmarks bar, tiny contexts |\n| `favicon-48x48.png` | 48×48 | Windows pinned tabs |\n| `apple-touch-icon.png` | 180×180 | iOS home screen |\n| `favicon.ico` | Multi-size | Legacy browser fallback (16+32+48+256) |\n\n**Generation approach** — Use Python\u002FPillow for PNGs\u002FICO, hand-write the SVG:\n```python\nfrom PIL import Image, ImageDraw\n\ndef create_favicon(size):\n    img = Image.new('RGBA', (size, size), (0, 0, 0, 0))\n    draw = ImageDraw.Draw(img)\n    s = size \u002F 256.0  # scale factor\n    # Dark rounded-square background\n    draw.rounded_rectangle([0, 0, size-1, size-1], radius=int(40*s), fill=(18, 18, 24, 255))\n    # Brand mark (letter, shape, or symbol) in accent color\n    # ... draw your design ...\n    return img\n\n# Generate all sizes\nfor name, sz in [('favicon-16x16.png',16), ('favicon-32x32.png',32),\n                  ('favicon-48x48.png',48), ('apple-touch-icon.png',180)]:\n    create_favicon(sz).save(name)\n\n# ICO with multiple sizes\ncreate_favicon(256).save('favicon.ico', format='ICO', sizes=[(16,16),(32,32),(48,48),(256,256)])\n```\n\n**SVG favicon** — write by hand (Pillow can't produce SVG). Use `\u003ClinearGradient>` for polish, keep geometry simple so it reads at 16×16.\n\n**HTML `\u003Clink>` tags** — add to `\u003Chead>` after `\u003Ctitle>`:\n```html\n\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" sizes=\"32x32\" href=\"\u002Ffavicon-32x32.png\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" sizes=\"16x16\" href=\"\u002Ffavicon-16x16.png\" \u002F>\n\u003Clink rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"\u002Fapple-touch-icon.png\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fx-icon\" href=\"\u002Ffavicon.ico\" \u002F>\n```\nBrowsers pick the best format from this list — SVG gets priority on modern browsers, ICO is the legacy fallback.\n\n**Design guidelines:**\n- Use the site's accent color for the brand mark (emerald for dark tech, olive for light)\n- Dark background (`#121218`) works universally — the mark pops against it\n- Keep geometry bold and simple — fine detail vanishes at 16×16\n- A small accent dot or secondary element adds character without clutter\n- Match the favicon style to the site's overall design language\n\n**Verification:** After deploy, curl the favicon URL directly to confirm HTTP 200:\n```bash\ncurl -sL -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fyour-site.vercel.app\u002Ffavicon.svg\n```\n\n> **Reference:** See `references\u002Ffavicon-generation-workflow.md` for the full script and SVG template used on Ibrahim's portfolio.\n\n### Phase 4b: Profile Image Swap\nWhen the site has a placeholder `\u003Cdiv>` instead of a real photo (common in scaffolded portfolios):\n\n1. **Check the HTML** — look for commented-out `\u003Cimg>` tags near a placeholder div (e.g. `\u003C!-- \u003Cimg src=\"...\" class=\"profile-img\" ... -->` alongside a `div.image-placeholder` with an icon and \"Your photo here\" text)\n2. **Check the JS** — there's usually toggle logic (`getElementById('profileImg')` \u002F `getElementById('profilePlaceholder')`) that shows the image and hides the placeholder on load. This is already wired — just uncomment the `\u003Cimg>`.\n3. **Uncomment the `\u003Cimg>` tag** and update `src` and `alt` text.\n4. **Place the image file** at the path referenced in `src` (e.g. `assets\u002Fimages\u002Fprofile.jpg`).\n5. **Crop tall photos** — if the source photo is a tall portrait (e.g. 597×1280), center-crop to 4:5 ratio focusing on the face\u002Fupper body before saving. The CSS `object-fit: cover` handles the final display, but a extreme aspect ratio wastes most of the image.\n6. **Optimize** — resize to max 800px wide, JPEG quality 90%. Profile images should be under 100KB.\n7. **Verify** — deploy, curl the image URL for HTTP 200, then visually confirm it renders in the hero section.\n\n```python\nfrom PIL import Image\nimg = Image.open('source_photo.jpg')\nw, h = img.size\n# Center-crop to 4:5\ncrop_h = int(w \u002F (4\u002F5))\nimg_cropped = img.crop((0, 0, w, crop_h))\n# Resize for web\nimg_final = img_cropped.resize((400, 500), Image.LANCZOS)\nimg_final.save('assets\u002Fimages\u002Fprofile.jpg', 'JPEG', quality=90)\n```\n\n### Phase 5: Deployment Config\n- Create `vercel.json` with cleanUrls, security headers, and cache headers for static assets\n- Verify Vercel CLI is logged in (`vercel whoami`)\n- Deploy with `vercel deploy --prod --yes`\n\n### Phase 6: Verification\n- Check live URL returns HTTP 200 on all paths\n- Verify favicon files serve correctly (curl each one)\n- Verify CSS, JS, and icon CDN resources load\n- Confirm responsive layout at 1440px, 768px, 375px\n- Test smooth scrolling and mobile menu interaction\n- Verify all sections render with correct content\n\n## HTML Structure\n\n```\nportfolio-website\u002F\n├── index.html          ← Single-page scroll site\n├── vercel.json         ← Vercel deployment config\n├── favicon.svg         ← SVG favicon (scalable, modern browsers)\n├── favicon-*.png       ← PNG favicons (16, 32, 48px)\n├── favicon.ico         ← Legacy ICO (multi-size)\n├── apple-touch-icon.png ← iOS home screen (180×180)\n├── css\u002F\n│   └── styles.css      ← All styles (no separate theme files)\n├── js\u002F\n│   └── main.js         ← Interactivity + animations\n└── assets\u002F\n    └── images\u002F         ← Optional project images, profile pic\n```\n\nKeep it single-page scroll for portfolios under 8 sections. Multi-page only if the user explicitly requests it.\n\n## CSS Guidelines\n\n### Dark Glass (default for tech portfolios):\n```css\n.glass-card {\n  background: rgba(255, 255, 255, 0.03);\n  border: 1px solid rgba(255, 255, 255, 0.06);\n  backdrop-filter: blur(12px);\n  -webkit-backdrop-filter: blur(12px);\n  transition: all 0.3s ease;\n}\n.glass-card:hover {\n  background: rgba(255, 255, 255, 0.05);\n  border-color: rgba(255, 255, 255, 0.1);\n}\n```\n\n### Light Glass (alternate for light themes):\n```css\n.glass-card {\n  background: rgba(255, 255, 255, 0.85);\n  border: 1px solid rgba(255, 255, 255, 0.18);\n  box-shadow: 0 8px 32px rgba(31, 38, 135, 0.15);\n  backdrop-filter: blur(10px);\n}\n```\n\n### Dark Theme Color Variables:\n```css\n:root {\n  --bg-primary: #0a0a0f;\n  --bg-card: rgba(255, 255, 255, 0.03);\n  --border-glass: rgba(255, 255, 255, 0.06);\n  --text-primary: rgba(255, 255, 255, 0.9);\n  --text-secondary: rgba(255, 255, 255, 0.4);\n  --accent-primary: #10b981;   \u002F* emerald *\u002F\n  --accent-secondary: #f59e0b; \u002F* amber *\u002F\n  --glass-bg: rgba(255, 255, 255, 0.03);\n}\n```\n\n### Scroll-Triggered Reveal (adds polish):\n```css\n.reveal {\n  opacity: 0;\n  transform: translateY(24px);\n  transition: opacity 0.7s cubic-bezier(0.16, 1, 0.3, 1),\n              transform 0.7s cubic-bezier(0.16, 1, 0.3, 1);\n}\n.reveal.visible {\n  opacity: 1;\n  transform: translateY(0);\n}\n```\n\n## JavaScript Functionality\n\n1. **Navbar** — `navbar-scrolled` class on scroll > 60px for backdrop blur\n2. **Mobile Menu** — hamburger toggle with close-on-link-click\n3. **Smooth Scroll** — all `href=\"#section\"` links with 80px navbar offset\n4. **Reveal Animations** — IntersectionObserver on `.glass-card` and headings\n5. **Parallax Glow** — optional: hero background orbs track mouse position\n6. **Console Easter Egg** — subtle branded message in devtools\n\n## Verification (Final Checklist)\n\nBefore declaring done:\n1. All files created with correct structure\n2. HTML is valid and semantic\n3. Glassmorphism renders properly (not just code — check visually)\n4. Text contrast is sufficient on glass cards\n5. Mobile menu opens and closes\n6. Smooth scroll works to every section\n7. Vercel deployment returns HTTP 200 on all routes\n8. CSS\u002FJS have immutable cache headers in vercel.json\n9. Content matches what was extracted from the user's vault — no hallucinated projects\n\n## Pitfalls\n\n- **Don't preselect colors.** The Olive\u002FLightGreen\u002FAmber palette from v1.0 is one option among many. Dark emerald\u002Famber is more appropriate for tech founders. Always match the palette to the user's industry.\n- **Don't skip research.** Building a portfolio without first reading the user's vault\u002Frepos produces generic output that misses their actual narrative.\n- **Glassmorphism overuse** hurts readability — use it on section cards, not on every element.\n- **Dark glass with white text** needs careful contrast. Use `rgba(255,255,255,0.9)` for headings, `rgba(255,255,255,0.4)` for body — never pure black or pure white.\n- **Template-first thinking.** The old SKILL.md referenced templates that didn't exist. For single-page portfolios, build from scratch — it's faster and more flexible than editing a generic template.\n- **Deploy is part of the deliverable.** Don't stop at file creation. The user experiences the site at a URL, not in a directory tree.\n- **Mobile-first is not optional.** Test at 375px before delivering. Glassmorphism effects degrade on low-end mobile browsers — `backdrop-filter` may not be supported.\n- **Company tags.** For founder portfolios with multiple ventures, add status badges (✅ Live, 🟡 Beta, 🔧 Build, 🥦 Research, 🔬 Concept) to each venture card — this shows maturity at a glance.\n- **Don't ship with a default favicon.** A ⚡ emoji or browser-default icon looks unfinished. Generate a proper favicon set (SVG + PNG + ICO) using the Phase 4 workflow. It takes 5 minutes and elevates perceived quality immediately.\n- **Research sections need data-driven content.** When building a research\u002Fshowcase section (e.g. quantum computing, drug discovery), pull real data from authoritative sources (PDB, PubChem, arXiv) and render it in structured tables\u002Fcards — not generic placeholder text. Use JavaScript to render data from a `researchData` object so the HTML stays clean and the data is easy to update. Example: protein targets with PDB IDs, drug candidates with molecular formulas and binding energies, method descriptions with equations.\n- **Validate scientific claims against system capabilities.** Before publishing performance claims (e.g. \"screens 10,000 compounds\"), verify the math: qubits → database size (2^n), Grover iterations → actual queries. A 10-qubit system screens 1024 candidates in ~25 queries, not 10,000. If PDB API calls fail or return empty, fall back to known literature data and note the source. Always cross-check PDB IDs exist at rcsb.org before publishing them.\n- **Vercel may not serve separate JS\u002FCSS files.** When new `.js` or `.css` files return 404 despite correct paths, inline them into `index.html` using `\u003Cstyle>` and `\u003Cscript>` tags. This is reliable because the single HTML file always deploys. Apply this proactively when adding significant new sections (research, blog, etc.) to avoid deployment surprises.\n\n## Related\n\nSee `references\u002Fportfolio-design-session.md` for the original Ibrahim build pattern (dark theme, glassmorphism, Vercel deploy) and `references\u002Fportfolio-honesty-rebuild-2026-08.md` for the claims→receipts rebuild (UMG Africa → Version Extreme Cooperation, Jenga\u002FHydrolith removed, quantum relabeled, verified live deploy).","# Portfolio Website Design\n\nBuild a complete, deployable portfolio site that positions the user professionally. Supports dark and light themes with glassmorphism cards, responsive layout, and a clear information hierarchy.\n\n## When To Use\n\nUse this skill when the user requests:\n- A complete portfolio or personal website\n- A developer \u002F engineer \u002F founder landing page\n- Professional online presence with project showcase\n- Any request to \"prepare my portfolio\"\n\n## Key Features\n\n1. **Glassmorphism Design**:\n   - Semi-transparent card backgrounds with backdrop blur\n   - Works on both dark and light themes (different CSS variables per theme)\n   - Subtle borders for depth without overwhelming content\n   - Ensure proper contrast — text must be readable on blurred backgrounds\n\n2. **Color Palette (choose one)**:\n   - **Dark Tech** (default for engineers\u002FAI\u002Frobotics founders): `bg: #0a0a0f`, accents: Emerald `#10b981` + Amber `#f59e0b`\n   - **Light Professional** (default for consultants\u002Fdesigners): white bg, Olive `#3D9970` + Light Green `#A8E6CF` accents\n   - Always pick the palette that matches the user's brand and industry — ask if uncertain\n\n3. **Responsive Layout**:\n   - Mobile-first approach with CSS Grid + Flexbox\n   - Media queries for all screen sizes\n   - Hamburger menu on mobile\n\n4. **Complete Sections**:\n   - Hero with headline + CTA\n   - About \u002F personal story\n   - Expertise \u002F services \u002F skills (3-column cards)\n   - Ventures \u002F Companies \u002F Projects (for founders with multiple ventures)\n   - Research or technical depth section (for engineers)\n   - Philosophy \u002F operating principles (optional, adds personality)\n   - Contact with email + social links\n   - Footer\n\n## Honesty Audit: Claims → Receipts\n\nBefore building or rebuilding a portfolio, audit every claim against the user's actual artifacts (disk, repos, deployed projects). A portfolio's job is to show what has been DONE, not what is INTENDED. Every public claim must survive an interview. This is a core user preference (Truth Over Ego) — a claim with no receipt is a liability, not a feature.\n\n### When to run this\n- Responding to critique like \"your site overclaims\" or \"you've shipped nothing\"\n- Rebranding (company name change, identity shift)\n- Before applying to programs \u002F accelerators \u002F scholarships where claims get checked\n\n### Workflow\n1. **Locate the source, not just the live URL** — find the local project dir (e.g. `~\u002FProjects\u002Fportfolio-website\u002F`). Curl the live site to see served HTML, but audit the source files for edits.\n2. **Map the claim surface** — title\u002Fmeta, nav CTAs, hero, about, projects (often a JS data file like `js\u002Fprojects.js`), research (often `js\u002Fresearch.js`), contact, footer, console easter egg (`js\u002Fmain.js`).\n3. **Verify every claim against disk** — check `~\u002FProjects\u002F` for real artifacts (code, PDFs, STLs, protos, market reports). A venture with no on-disk artifact gets removed or relabeled \"planned\u002Fconcept\". Count real things: `find \u003Cproject> -type f | wc -l`, prototype dirs, build outputs.\n4. **Fix dead links to real artifacts** — if an artifact exists but the site links elsewhere (e.g. paper PDF present, button points at a GitHub profile), point the button at the real file.\n5. **Label research honestly** — \"proof-of-concept \u002F educational pipeline\", NOT \"drug discovery\" for a 2-qubit VQE toy model. Mark planned items \"Roadmap — not yet run\". The page can stay up; the framing must be true.\n6. **Brand coherence** — title, meta, footer, console log, and JS data (`lab:` fields) must all name the SAME single company. Flag mismatches (site says UMG Africa, research data says Version Extreme Cooperation) and email-domain lag after a rebrand — change with user confirmation, don't silently pick.\n7. **Receipts over aspirational metrics** — replace counters like \"5 Active Ventures\" \u002F \"∞ First Principles\" with verifiable numbers: \"1 Company \u002F 52 Prototypes Built \u002F 4 R&D Programs\". Every number must be countable from disk.\n8. **Truthful role titles** — \"Form 5 student and founder\", never \"engineer\" before credentials exist. Navbar \"Open to opportunities\" instead of \"Available for projects\" when nothing is shipped.\n9. **Deploy + verify** — `vercel deploy --prod --yes`, then curl the LIVE aliased URL: grep for expected new strings, `grep -c` removed strings (must be 0), new asset paths return 200 (see static-site-deployment).\n\n### Pitfalls\n- **JS countup counters render \"0\" in raw HTML \u002F static screenshots.** A critic can screenshot \"0 Active Ventures\" while the page animates to the real value. Audit the `data-target` attribute, not the rendered text; when responding to such a critique, check the JS before accepting the claim.\n- **Hidden-but-present images** — a real `\u003Cimg src=\"assets\u002Fimages\u002Fprofile.jpg\" style=\"display:none\">` next to a \"Your photo here\" placeholder. Enable it (drop the inline style) instead of leaving the placeholder.\n- **JS data files are part of the claim surface** — editing index.html alone leaves `js\u002Fprojects.js` \u002F `js\u002Fresearch.js` \u002F the console easter egg contradicting the new identity. Grep the whole source dir for stale brand strings before deploying.\n\n## Workflow\n\n### Phase 0: Research (DO FIRST — most important step)\nBefore writing any code, research the user's background:\n1. **Obsidian vault** — search for `about me.md`, company notes, project descriptions\n2. **GitHub repos** — check for existing projects, READMEs, portfolio content\n3. **Previous conversations** (session_search) — look for personal details, preferences, past portfolio discussions\n4. **Extract structured info**: name, age, location, title, companies\u002Fproducts with descriptions, expertise areas, research domains, philosophy\n5. Identify the **core narrative** — is this a founder, an engineer, a researcher, or all three? The hero headline and about section must tell one coherent story.\n\n### Phase 1: Planning\n- Define site structure based on extracted content\n- Choose dark or light theme based on user's industry (dark for tech\u002FAI\u002Fengineering, light for design\u002Fconsulting)\n- Map each Obsidian note section to a page\u002Fsection\n- Decide on a hero headline that captures the user's unique angle\n\n### Phase 2: Design System\n- Establish color palette (CSS custom properties)\n- Define typography hierarchy (Inter for body, JetBrains Mono \u002F Fira Code for tech elements)\n- Create glassmorphism component styles (dark glass `rgba(255,255,255,0.03)` for dark themes, light glass `rgba(255,255,255,0.85)` for light themes)\n- Plan responsive breakpoints\n\n### Phase 3: Implementation\n- Create directory structure: `index.html`, `css\u002Fstyles.css`, `js\u002Fmain.js`\n- Write semantic HTML with sections matching extracted content\n- Implement CSS with full glassmorphism, gradients, and animations\n- Add JavaScript for: scroll effects, mobile menu, smooth anchor nav, parallax, scroll-triggered reveals\n- Use Font Awesome CDN for icons\n\n### Phase 4: Favicon & Brand Assets\nGenerate a complete favicon set before deployment — every portfolio needs a proper icon, not a default browser favicon.\n\n**Required files** (all in project root):\n| File | Size | Purpose |\n|------|------|---------|\n| `favicon.svg` | Scalable | Modern browsers (crisp at any size, supports gradients) |\n| `favicon-32x32.png` | 32×32 | Standard browser tab |\n| `favicon-16x16.png` | 16×16 | Bookmarks bar, tiny contexts |\n| `favicon-48x48.png` | 48×48 | Windows pinned tabs |\n| `apple-touch-icon.png` | 180×180 | iOS home screen |\n| `favicon.ico` | Multi-size | Legacy browser fallback (16+32+48+256) |\n\n**Generation approach** — Use Python\u002FPillow for PNGs\u002FICO, hand-write the SVG:\n```python\nfrom PIL import Image, ImageDraw\n\ndef create_favicon(size):\n    img = Image.new('RGBA', (size, size), (0, 0, 0, 0))\n    draw = ImageDraw.Draw(img)\n    s = size \u002F 256.0  # scale factor\n    # Dark rounded-square background\n    draw.rounded_rectangle([0, 0, size-1, size-1], radius=int(40*s), fill=(18, 18, 24, 255))\n    # Brand mark (letter, shape, or symbol) in accent color\n    # ... draw your design ...\n    return img\n\n# Generate all sizes\nfor name, sz in [('favicon-16x16.png',16), ('favicon-32x32.png',32),\n                  ('favicon-48x48.png',48), ('apple-touch-icon.png',180)]:\n    create_favicon(sz).save(name)\n\n# ICO with multiple sizes\ncreate_favicon(256).save('favicon.ico', format='ICO', sizes=[(16,16),(32,32),(48,48),(256,256)])\n```\n\n**SVG favicon** — write by hand (Pillow can't produce SVG). Use `\u003ClinearGradient>` for polish, keep geometry simple so it reads at 16×16.\n\n**HTML `\u003Clink>` tags** — add to `\u003Chead>` after `\u003Ctitle>`:\n```html\n\u003Clink rel=\"icon\" type=\"image\u002Fsvg+xml\" href=\"\u002Ffavicon.svg\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" sizes=\"32x32\" href=\"\u002Ffavicon-32x32.png\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fpng\" sizes=\"16x16\" href=\"\u002Ffavicon-16x16.png\" \u002F>\n\u003Clink rel=\"apple-touch-icon\" sizes=\"180x180\" href=\"\u002Fapple-touch-icon.png\" \u002F>\n\u003Clink rel=\"icon\" type=\"image\u002Fx-icon\" href=\"\u002Ffavicon.ico\" \u002F>\n```\nBrowsers pick the best format from this list — SVG gets priority on modern browsers, ICO is the legacy fallback.\n\n**Design guidelines:**\n- Use the site's accent color for the brand mark (emerald for dark tech, olive for light)\n- Dark background (`#121218`) works universally — the mark pops against it\n- Keep geometry bold and simple — fine detail vanishes at 16×16\n- A small accent dot or secondary element adds character without clutter\n- Match the favicon style to the site's overall design language\n\n**Verification:** After deploy, curl the favicon URL directly to confirm HTTP 200:\n```bash\ncurl -sL -o \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fyour-site.vercel.app\u002Ffavicon.svg\n```\n\n> **Reference:** See `references\u002Ffavicon-generation-workflow.md` for the full script and SVG template used on Ibrahim's portfolio.\n\n### Phase 4b: Profile Image Swap\nWhen the site has a placeholder `\u003Cdiv>` instead of a real photo (common in scaffolded portfolios):\n\n1. **Check the HTML** — look for commented-out `\u003Cimg>` tags near a placeholder div (e.g. `\u003C!-- \u003Cimg src=\"...\" class=\"profile-img\" ... -->` alongside a `div.image-placeholder` with an icon and \"Your photo here\" text)\n2. **Check the JS** — there's usually toggle logic (`getElementById('profileImg')` \u002F `getElementById('profilePlaceholder')`) that shows the image and hides the placeholder on load. This is already wired — just uncomment the `\u003Cimg>`.\n3. **Uncomment the `\u003Cimg>` tag** and update `src` and `alt` text.\n4. **Place the image file** at the path referenced in `src` (e.g. `assets\u002Fimages\u002Fprofile.jpg`).\n5. **Crop tall photos** — if the source photo is a tall portrait (e.g. 597×1280), center-crop to 4:5 ratio focusing on the face\u002Fupper body before saving. The CSS `object-fit: cover` handles the final display, but a extreme aspect ratio wastes most of the image.\n6. **Optimize** — resize to max 800px wide, JPEG quality 90%. Profile images should be under 100KB.\n7. **Verify** — deploy, curl the image URL for HTTP 200, then visually confirm it renders in the hero section.\n\n```python\nfrom PIL import Image\nimg = Image.open('source_photo.jpg')\nw, h = img.size\n# Center-crop to 4:5\ncrop_h = int(w \u002F (4\u002F5))\nimg_cropped = img.crop((0, 0, w, crop_h))\n# Resize for web\nimg_final = img_cropped.resize((400, 500), Image.LANCZOS)\nimg_final.save('assets\u002Fimages\u002Fprofile.jpg', 'JPEG', quality=90)\n```\n\n### Phase 5: Deployment Config\n- Create `vercel.json` with cleanUrls, security headers, and cache headers for static assets\n- Verify Vercel CLI is logged in (`vercel whoami`)\n- Deploy with `vercel deploy --prod --yes`\n\n### Phase 6: Verification\n- Check live URL returns HTTP 200 on all paths\n- Verify favicon files serve correctly (curl each one)\n- Verify CSS, JS, and icon CDN resources load\n- Confirm responsive layout at 1440px, 768px, 375px\n- Test smooth scrolling and mobile menu interaction\n- Verify all sections render with correct content\n\n## HTML Structure\n\n```\nportfolio-website\u002F\n├── index.html          ← Single-page scroll site\n├── vercel.json         ← Vercel deployment config\n├── favicon.svg         ← SVG favicon (scalable, modern browsers)\n├── favicon-*.png       ← PNG favicons (16, 32, 48px)\n├── favicon.ico         ← Legacy ICO (multi-size)\n├── apple-touch-icon.png ← iOS home screen (180×180)\n├── css\u002F\n│   └── styles.css      ← All styles (no separate theme files)\n├── js\u002F\n│   └── main.js         ← Interactivity + animations\n└── assets\u002F\n    └── images\u002F         ← Optional project images, profile pic\n```\n\nKeep it single-page scroll for portfolios under 8 sections. Multi-page only if the user explicitly requests it.\n\n## CSS Guidelines\n\n### Dark Glass (default for tech portfolios):\n```css\n.glass-card {\n  background: rgba(255, 255, 255, 0.03);\n  border: 1px solid rgba(255, 255, 255, 0.06);\n  backdrop-filter: blur(12px);\n  -webkit-backdrop-filter: blur(12px);\n  transition: all 0.3s ease;\n}\n.glass-card:hover {\n  background: rgba(255, 255, 255, 0.05);\n  border-color: rgba(255, 255, 255, 0.1);\n}\n```\n\n### Light Glass (alternate for light themes):\n```css\n.glass-card {\n  background: rgba(255, 255, 255, 0.85);\n  border: 1px solid rgba(255, 255, 255, 0.18);\n  box-shadow: 0 8px 32px rgba(31, 38, 135, 0.15);\n  backdrop-filter: blur(10px);\n}\n```\n\n### Dark Theme Color Variables:\n```css\n:root {\n  --bg-primary: #0a0a0f;\n  --bg-card: rgba(255, 255, 255, 0.03);\n  --border-glass: rgba(255, 255, 255, 0.06);\n  --text-primary: rgba(255, 255, 255, 0.9);\n  --text-secondary: rgba(255, 255, 255, 0.4);\n  --accent-primary: #10b981;   \u002F* emerald *\u002F\n  --accent-secondary: #f59e0b; \u002F* amber *\u002F\n  --glass-bg: rgba(255, 255, 255, 0.03);\n}\n```\n\n### Scroll-Triggered Reveal (adds polish):\n```css\n.reveal {\n  opacity: 0;\n  transform: translateY(24px);\n  transition: opacity 0.7s cubic-bezier(0.16, 1, 0.3, 1),\n              transform 0.7s cubic-bezier(0.16, 1, 0.3, 1);\n}\n.reveal.visible {\n  opacity: 1;\n  transform: translateY(0);\n}\n```\n\n## JavaScript Functionality\n\n1. **Navbar** — `navbar-scrolled` class on scroll > 60px for backdrop blur\n2. **Mobile Menu** — hamburger toggle with close-on-link-click\n3. **Smooth Scroll** — all `href=\"#section\"` links with 80px navbar offset\n4. **Reveal Animations** — IntersectionObserver on `.glass-card` and headings\n5. **Parallax Glow** — optional: hero background orbs track mouse position\n6. **Console Easter Egg** — subtle branded message in devtools\n\n## Verification (Final Checklist)\n\nBefore declaring done:\n1. All files created with correct structure\n2. HTML is valid and semantic\n3. Glassmorphism renders properly (not just code — check visually)\n4. Text contrast is sufficient on glass cards\n5. Mobile menu opens and closes\n6. Smooth scroll works to every section\n7. Vercel deployment returns HTTP 200 on all routes\n8. CSS\u002FJS have immutable cache headers in vercel.json\n9. Content matches what was extracted from the user's vault — no hallucinated projects\n\n## Pitfalls\n\n- **Don't preselect colors.** The Olive\u002FLightGreen\u002FAmber palette from v1.0 is one option among many. Dark emerald\u002Famber is more appropriate for tech founders. Always match the palette to the user's industry.\n- **Don't skip research.** Building a portfolio without first reading the user's vault\u002Frepos produces generic output that misses their actual narrative.\n- **Glassmorphism overuse** hurts readability — use it on section cards, not on every element.\n- **Dark glass with white text** needs careful contrast. Use `rgba(255,255,255,0.9)` for headings, `rgba(255,255,255,0.4)` for body — never pure black or pure white.\n- **Template-first thinking.** The old SKILL.md referenced templates that didn't exist. For single-page portfolios, build from scratch — it's faster and more flexible than editing a generic template.\n- **Deploy is part of the deliverable.** Don't stop at file creation. The user experiences the site at a URL, not in a directory tree.\n- **Mobile-first is not optional.** Test at 375px before delivering. Glassmorphism effects degrade on low-end mobile browsers — `backdrop-filter` may not be supported.\n- **Company tags.** For founder portfolios with multiple ventures, add status badges (✅ Live, 🟡 Beta, 🔧 Build, 🥦 Research, 🔬 Concept) to each venture card — this shows maturity at a glance.\n- **Don't ship with a default favicon.** A ⚡ emoji or browser-default icon looks unfinished. Generate a proper favicon set (SVG + PNG + ICO) using the Phase 4 workflow. It takes 5 minutes and elevates perceived quality immediately.\n- **Research sections need data-driven content.** When building a research\u002Fshowcase section (e.g. quantum computing, drug discovery), pull real data from authoritative sources (PDB, PubChem, arXiv) and render it in structured tables\u002Fcards — not generic placeholder text. Use JavaScript to render data from a `researchData` object so the HTML stays clean and the data is easy to update. Example: protein targets with PDB IDs, drug candidates with molecular formulas and binding energies, method descriptions with equations.\n- **Validate scientific claims against system capabilities.** Before publishing performance claims (e.g. \"screens 10,000 compounds\"), verify the math: qubits → database size (2^n), Grover iterations → actual queries. A 10-qubit system screens 1024 candidates in ~25 queries, not 10,000. If PDB API calls fail or return empty, fall back to known literature data and note the source. Always cross-check PDB IDs exist at rcsb.org before publishing them.\n- **Vercel may not serve separate JS\u002FCSS files.** When new `.js` or `.css` files return 404 despite correct paths, inline them into `index.html` using `\u003Cstyle>` and `\u003Cscript>` tags. This is reliable because the single HTML file always deploys. Apply this proactively when adding significant new sections (research, blog, etc.) to avoid deployment surprises.\n\n## Related\n\nSee `references\u002Fportfolio-design-session.md` for the original Ibrahim build pattern (dark theme, glassmorphism, Vercel deploy) and `references\u002Fportfolio-honesty-rebuild-2026-08.md` for the claims→receipts rebuild (UMG Africa → Version Extreme Cooperation, Jenga\u002FHydrolith removed, quantum relabeled, verified live deploy).",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":42,"description":7},"Hermes Agent","1.2.0",{"hermes":27},{"tags":28,"related_skills":38},[29,30,31,32,33,34,35,36,37],"design","html","css","portfolio","glassmorphism","ux","ui","vercel","deployment",[39,40,41],"static-site-deployment","claude-design","popular-web-designs",[43,44,45],"linux","macos","windows","main","1f420fcb3f20524e8a830b9d010e0c0ee312d437","hermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel","I am a developer at UMG Africa and i have 2 years of software development also i engage with embedded softwares i am good in rust, cpp, python and kotlin","2026-08-16 18:04:02",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add abdullibrahim733-pixel\u002FEagle --skill portfolio-website-design",{"tool":59,"command":60},"bunx","bunx skills add abdullibrahim733-pixel\u002FEagle --skill portfolio-website-design",{"tool":62,"command":63},"pnpm","pnpm dlx skills add abdullibrahim733-pixel\u002FEagle --skill portfolio-website-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002FSKILL.md",true,[67,73,77,81,85,89,95],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ffavicon-generation-workflow.md","REFERENCE","参考文档",4934,"https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002Freferences\u002Ffavicon-generation-workflow.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fportfolio-design-session.md",5490,"https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002Freferences\u002Fportfolio-design-session.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fportfolio-honesty-rebuild-2026-08.md",3086,"https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002Freferences\u002Fportfolio-honesty-rebuild-2026-08.md",{"path":82,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fscientific-data-api-patterns.md",2424,"https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002Freferences\u002Fscientific-data-api-patterns.md",{"path":86,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":87,"sourceHtmlUrl":88},"templates\u002Findex.html",4858,"https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002Ftemplates\u002Findex.html",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"templates\u002Fmain.js","SCRIPT","脚本",970,"https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002Ftemplates\u002Fmain.js",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"templates\u002Fstyles.css","OTHER","其他",3870,"https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fcreative\u002Fportfolio-website-design\u002Ftemplates\u002Fstyles.css",[102,109,116,123,130,137],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M78BBHAQCSZNG7HYMB97YG3Y","web-ui-verification","Verify web UIs via headless Chrome CDP, no vision needed.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fweb-ui-verification\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M78BB60RHXBY2QV4TA9S917B","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M78BB16QRJZA9P3TXN5SHCQH","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M78BAY69B9JP3SK2NAF3EH2D","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M78BAVDMEBYN49PRDQ8QXTBJ","simplify-code","Parallel 4-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M78BAE09PQ5RV5MSJN1S788A","scroll-driven-3d-websites","Scroll-scrubbed 3D promo sites (Three.js + GSAP).","https:\u002F\u002Fgithub.com\u002Fabdullibrahim733-pixel\u002FEagle\u002Fblob\u002Fmain\u002Fhermes-backup\u002Fskills\u002Fsoftware-development\u002Fscroll-driven-3d-websites\u002FSKILL.md",[],[]]