Menu
Publish a completed Persona portfolio safely through Vercel or GitHub Pages.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
AI assistant framework for building unique, authentic portfolio websites from scratch. Guides agents through research, design, and implementation phases.
Reference guide for portfolio color palettes. Includes quick vibe lookup, full palettes, and application guidelines using the 60-30-10 rule.
Generate authentic, compelling copy for portfolios. Covers tone calibration, taglines, bios, project descriptions, and avoiding assumptions.
Create unique visual designs by synthesizing from inspirations and preferences. Covers typography, color, layout, spacing, and animation philosophy.
Reference for selecting distinctive typography. Includes font recommendations by vibe, category, archetype, and pairing guidelines for Next.js projects.
Gather information about users from materials, profile config, GitHub, and web search to inform portfolio content and design decisions.
| name | deploy |
| description | Publish a completed Persona portfolio safely through Vercel or GitHub Pages. |
Use this only after the portfolio is complete. Never publish the untouched Persona starter page.
git remote -v. Do not publish to JacbK/Persona.npm run check and fix every failure.rg -n "TODO|Lorem ipsum|Your Name" src public
git status --short
profile.yaml, resumes, and uploaded materials are safe to make public.Offer:
Publishing changes external state, so wait for the user's choice.
The simplest path is Vercel's Git integration:
https://vercel.com/new.For CLI deployment, use the user's installed and authenticated Vercel CLI. Do not request, print, or store a token in project files.
vercel
vercel --prod
The included .github/workflows/deploy-vercel.yml is manual. It requires VERCEL_TOKEN, VERCEL_ORG_ID, and VERCEL_PROJECT_ID repository secrets.
GitHub Pages needs a static export. Persona's manual workflow handles this in a disposable CI checkout:
The workflow removes the local-only config UI and APIs only from its temporary build workspace. Do not delete working source files just to deploy.
Use the host's current official Next.js adapter or documentation. Do not guess output directories; Next.js server and static-export deployments use different outputs.
origin points to the Persona template repository.profile.yaml, source files, shell history, or agent configuration committed to Git.