Miao Portfolio Workflow
mengzheng001-prog/miao-portfolio-workflow
Do currículo em PDF ao portfólio online mantido — automático
Ver no GitHubSkill Claude para manter portfólio pessoal deployed no Vercel. Automatiza o ciclo completo: parsear PDF de currículo, preencher template, fazer deploy inicial, sincronizar edições e gerenciar domínio customizado via APIs (GitHub, Vercel, registradores DNS).
Instalação
npx convez-ai mengzheng001-prog/miao-portfolio-workflow1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerar portfólio pessoal a partir de PDF de currículo sem escrever código
- Editar e sincronizar mudanças no portfólio direto via Claude
- Fazer deploy automático em Vercel e gerenciar domínio customizado
- Adaptar templates pré-prontos a layouts e frameworks diferentes
Veredito

Excelente para profissionais que querem portfólio online sem overhead técnico. O design modular (6 fases independentes) funciona bem, e a auto-detecção de setup é prática. Limitação: templates em HTML vanilla; projectos Next.js/SvelteKit precisam adaptação manual.
README
A tradução para o português deste README ainda está na fila.
miao-portfolio-workflow
v0.3 — full lifecycle Claude skill: from a resume PDF to a deployed-and-maintained personal portfolio site on Vercel.
Target user: 求职者 / 自由职业者 / 想做个人作品集的人。即使你不会前端,给 Claude 一份简历 PDF,它能帮你一路做到「线上能访问 + 长期维护」。
What this skill does
6 phases covering the full lifecycle:
| Phase | Goal |
|---|---|
| 1. PDF 解析 | Parse resume PDF → structured resume.json(按 resume.schema.json 契约) |
| 2. 选模板 | Default: pull from miao-portfolio-templates. Custom external templates also supported |
| 3. 填充模板 | Replace {{占位符}} + 重写示范 section → 完整 portfolio/ |
| 4. 首次部署 | gh repo create + Vercel Import → live at xxx.vercel.app |
| 5. 长期维护 | Edit source → sync → commit + push via proxy → verify auto-build |
| 6. 域名绑定 | Vercel REST API + 多家 DNS 注册商(阿里云 / 腾讯云 / Cloudflare / Namecheap / GoDaddy / Spaceship) |
Each phase is independently entered—if you already have a portfolio repo and just want to add a project card, skill goes directly to Phase 5.
Install
# Clone into Claude's skills directory
git clone https://github.com/mengzheng001-prog/miao-portfolio-workflow.git \
~/.claude/skills/miao-portfolio-workflow
Or for project-scoped use:
git clone https://github.com/mengzheng001-prog/miao-portfolio-workflow.git \
<your-project>/.claude/skills/miao-portfolio-workflow
Restart Claude. The skill auto-loads from the skills directory.
When it triggers
This skill activates when you ask Claude to do any of:
- "在我的主页加一张项目卡 / 改副标题 / 换图标"
- "把工作经历调到核心项目前面"
- "给其他项目区加左右滑动按钮"
- "section 配色重新设计一下,深浅交替"
- "我买了个新域名 XXX,绑到 Vercel"
- "main.js / index.html 改完后怎么推上线"
Claude will read SKILL.md and walk through the 5-step workflow.
Generalizable to different project setups
v0.2 update: SKILL.md now starts with a Step 0 — Project Discovery phase that auto-detects:
- Source directory location (
personal-main//src//site//public// ...) - Deploy mode (same repo vs separate deploy repo)
- CSS class naming (
bento-card/card/ Tailwind utilities / ...) - Section IDs (
#projects/#experience/ your own naming) - Network proxy needs (mainland China / WSL / VPN setups)
- DNS registrar (Aliyun / Tencent DNSPod / Cloudflare / Namecheap / GoDaddy)
So even if your project uses a different layout / CSS framework / DNS provider, the skill will adapt. The HTML snippets in examples/ are reference points — Claude reads them, then applies your project's actual conventions.
Tested compatibility:
| Setup | Status |
|---|---|
| AI Studio / Vercel template (vanilla HTML) | ✅ Tested |
| Vite + vanilla HTML | ✅ Compatible |
| Tailwind utility-class projects | 🟡 Templates need light adapt |
| Next.js / SvelteKit | 🟡 Workflow applies, HTML templates don't |
| Webflow / Framer export | 🟡 Workflow applies, no HTML edits |
What's in this repo
miao-portfolio-workflow/
├── SKILL.md # Main skill spec (Claude reads this)
├── README.md # This file
└── examples/
├── 01-add-personal-project-card.html # HTML snippet for new project card
└── 02-add-horizontal-nav-buttons.md # frame + buttons + JS pattern
Why this exists
When you build a portfolio with AI tools (Anthropic AI Studio, Vercel v0, Lovable), the typical setup is:
- AI generates source files in one directory
- You "deploy" by either uploading a zip to Vercel or pushing to a separate GitHub repo Vercel watches
The catch: future edits split into "where you change code" vs "where Vercel reads code". Newcomers often only change source files and wonder why production doesn't update.
This skill encodes the round-trip workflow so Claude does it right every time — no more "I changed the file but it's not live".
License
MIT — feel free to fork and adapt.
Credits
Distilled from a real-world session maintaining a personal portfolio for an AI Product Manager job search, including project card additions, section reordering, dark/light background rebalancing, horizontal scroll nav, and custom domain binding via Aliyun DNS.