Skip to main content

portfolio-page

Build the one-page site that goes at the top of the resume. The person's real work with live links, deployed by the end of the sitting. Use when they say "make my portfolio", "I need a personal site", or their resume lists projects with nowhere to see them.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
portfolio-page
category
resume
description
Build the one-page site that goes at the top of the resume. The person's real work with live links, deployed by the end of the sitting. Use when they say "make my portfolio", "I need a personal site", or their resume lists projects with nowhere to see them.
# portfolio-page Build the page a stranger lands on after reading this person's resume. One page, their name on it, their actual work on it, every project clickable. The bar: live at a real URL by the end of the sitting, with nothing on it they cannot demo. ## Ground rules - Only work that exists goes on the page. A project earns a spot by having something to click: a live site, a repo with real commits, a video, a photo of the physical thing. No "coming soon" cards. - Two or three real projects beat six thin ones. If they have zero, say so and point at https://sphinxstack.com/skills/ — build one first, then this page takes twenty minutes. - Their choices, typed by you: which projects lead, what each blurb says, what the page feels like. Explain each move in a one-liner as you make it. - Static HTML/CSS they can read. No framework, no template soup. ## Session shape 1. Inventory: list everything they have made — repos, deployed sites, school projects, physical builds, designs. For each, find the link or artifact that proves it. Keep what proves; park the rest. 2. Blurbs: for each project, two sentences in their words — what it is and what they did — plus the link. Verify every link loads before it goes on the page. 3. Build: name, one line about who they are, contact (GitHub, and email only if they are comfortable publishing it), then the projects. Mobile-readable, fast, no photo required. 4. Deploy: GitHub Pages under their username, so the URL is theirs. Hand off to build-website or ship-on-github if those skills are present — this page is the simplest case of both. 5. Close the loop: put the URL on their resume header and their GitHub profile. Open it on their phone together. ## Done - Live URL with their name, short bio, and 2+ projects - Every project links to something a stranger can open right now - Works on a phone; every link tested - URL added to the resume and anywhere else they list themselves When they ship the next project, adding it here is a two-line edit they watched you make — they can do it themselves.
View on GitHub