Communitygithub.com

个人网站生成器 — 简历 + 链接 → 可部署个人站

把简历、社交媒体、作品集和日常产出做成可直接部署的静态个人网站:先访谈核实证据,再按「网站目标 × 内容深度」定信息层级,从 6 套视觉风格里选(或从参考站提取),生成后浏览器验收,经授权才部署。

个人网站生成器 — 简历 + 链接 → 可部署个人站 是什么?

Personal Website 配方第 1 步(合成):spacezephyr-personal-site-builder。内容→结构→视觉→代码,不编造经历、默认保护隐私;产出纯静态 HTML/CSS/JS,可上 Cloudflare Pages / Vercel / GitHub Pages。下一步交给 About 页叙事与 link-in-bio 链接中枢。

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add SpaceZephyr/personal-site-builder

在你喜欢的 AI 中提问

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

文档

Personal Website Builder

Transform "a resume + a bunch of links + scattered outputs" into an information-structured, visually styled static website that can be deployed directly.

Output: A set of pure static HTML/CSS/JS (no build, no framework, single-file CSS), deployable directly to Cloudflare Pages / Vercel / GitHub Pages.

Core Principles

  • Order is not reversible: Content → Structure → Visual → Code. Do not start with templates or ask about colors and fonts.
  • Distinguish four types of information: Facts confirmed by the user / Original source summaries / AI-drafted copy / Inferences pending confirmation. Do not fabricate experiences, numbers, clients, reviews, identities, or partnerships.
  • Privacy protection by default: Public phone numbers, addresses, private emails, and client materials must be individually confirmed before disclosure.
  • Don't create empty sections to fill templates: If information is insufficient, reduce content depth or list missing items; do not use placeholder case studies.
  • Offer options with recommendations: For every decision point, provide 2–3 substantially different options with a clear recommendation; do not dump all choices on the user.
  • Deployment is an external release action: Execute only with explicit user authorization.

Workflow

① Define Scope → ② Collect Materials → ③ Define Information Hierarchy → ④ Define Visual Style → ⑤ Generate → ⑥ Verify → ⑦ Deploy After Authorization

① Define Scope

First, determine whether it's new creation or modifying an existing site.

  • Existing project: Read directory structure, existing pages, content sources, build commands, deployment config, and git status first. Follow existing tech stack and design constraints; do not start from scratch.
  • New: Default to a lightweight responsive static site; introduce a framework or backend only if CMS, login, or dynamic data is genuinely needed.

Then ask only one direction-defining question:

"Who is this site mainly for? What action do you want them to take after viewing?"

Do not ask about colors, fonts, or animations at this step.

② Collect Materials

Read references/intake.md (contains minimum startup materials, progressive questioning order, content entity fields, evidence grading, privacy rules, list of crawlable sources).

Key points:

  • First response should be lightweight. The user has already stated what they have; the first reply should only ask them to send those materials. After reading the first batch, ask the next question. Only ask one question at a time that most impacts the next step; do not dump a dozen form fields at once.
  • Read what can be read first; don't ask. Resume (Read / docx / pdf skill), GitHub, blog, WeChat articles (WebFetch), platforms requiring login (claude-in-chrome). Stop immediately when encountering login walls, CAPTCHAs, or anti-scraping; instead ask the user to provide export files, text, link lists, or screenshots.
  • Numbers over adjectives, and use only verifiable metrics. "10 products, 50,000 users, nearly 200 skills" is far better than "extensive experience"; do not supplement unverifiable estimates.
  • Duplicate content across platforms is merged into one content entity, retaining multiple source links; in case of conflicting information, keep both versions for the user to confirm.

After collection, output a Materials Confirmation Checklist (Existing / Pending / Missing / Suggested Additions). Proceed to the next step only after user confirmation.

③ Define Information Hierarchy

Read references/architectures.md. Use the Dual-Axis decision:

Axis 1 – Site Goal (select one primary goal, at most one secondary goal)

User's main materials arePrimary Goal
Work experience, skills, education, aiming to submit resumesJob-seeking conversion
Projects / Design / Photography / Video, rich visual assetsPortfolio showcase
A life story + interests + values, few finished productsPersonal introduction
Long-term written articles / books read / paths traveled, archivingLong-term record
Seeking consulting, commissions, coaching, commercial ordersClient acquisition
WeChat Official Account / X / Xiaohongshu / Podcast, fans and content assetsCreator homepage
Launched products or open-source projects, wanting people to use/buyIndie developer

Axis 2 – Content Depth (determined by the quantity of materials, not by wish)

  • L1 Business Card Level — Single page, only needs identity / positioning / primary action / 3 representative links. Suitable when materials are scarce or quick launch is needed.
  • L2 Proof Level — Homepage + detailed project/experience pages. Requires personal contribution, process, results, and media assets.
  • L3 Content System Level — Homepage + details + categorized index + archives + continuous update mechanism. Requires a stable content source and willingness to update.

If materials don't support L2, go with L1 first; if there's no ability for continuous updates, don't choose L3.

Output 2–3 genuinely different options (differences must come from visitor tasks, not just renaming sections) using the template in architectures.md. For each option, specify: Who it suits / First-screen promise / Primary action / Navigation / Homepage order / Which existing materials are used / What else is needed / Key trade-offs. Clearly recommend one. Proceed to visual after user confirmation.

④ Define Visual Style

First ask: "Do you have any websites or designs you like? If so, send me the links or screenshots." Having reference examples is far more accurate than asking users to choose from adjectives.

Three paths, chosen based on what the user has:

  1. User provides reference URLs / screenshots / design specifications → Read references/style-extraction.md. Preferably open the reference site using claude-in-chrome and run the script inside to sample real computed styles (font stack, color values, border-radius, shadows, container widths), sampling both light and dark themes. If the site can't be opened or requires login, fall back to screenshot analysis. Extract the feel, do not clone the entire site; do not take logos, copy, illustrations, or unique layouts.
  2. User mentions a brand name ("Make it look like Notion" or "Apple style") → Invoke the brand-design-md skill to fetch DESIGN.md, mapping to site.css :root variables.
  3. User has no reference → Read references/visual-styles.md. Choose 2–3 directions from 6 built-in styles with recommendation reasons, each with ready-to-paste CSS variable values.

When the user provides multiple reference sites, first ask: "Which one's feel do you want most? What specifically do you like about the others?" — Most people like A's typography + B's color scheme; directly making an intersection results in a mishmash.

When the user mentions WordPress / Framer / Webflow / Notion, borrow their information organization and feel; do not pretend to generate a theme or project for that platform.

Regardless of the path taken, only modify :root variables at the end; do not rewrite the component parts of site.css. Write code only after selection.

⑤ Generate the Site

Start by copying assets/starter/:

  • site.css — CSS variables + typography baseline + card/list components, light/dark themes. Changing style = modifying :root variables; do not rewrite the entire file.
  • nav.js — Single file injected fixed top bar (dark mode toggle + scroll-away behavior), configure SITE_NAME / LINKS / THEME_KEY in the top config section. The 760px in its inline CSS must match --max in site.css.
  • index.html — Homepage skeleton, sections added/removed per the chosen plan.

Must meet:

  • First screen displays the person's real name or common moniker + positioning + one primary action; only one primary action, at most one secondary action.
  • Navigation reflects the confirmed information architecture; do not copy platform template sections; 4–6 items.
  • Works prioritize problem / my role / approach / result, not just thumbnails.
  • Social links explain what you can see on this platform, not just a row of icons.
  • Each page is a standalone xxx/index.html, sharing /site.css and /nav.js; do not use CDN, frameworks, or build steps.
  • <title>, <meta name="description">, favicon, and share image are complete; external links use target="_blank" rel="noreferrer".
  • Smooth browsing on both desktop and mobile; main flow operable by keyboard; complete semantic structure and alt text; supports prefers-reduced-motion.
  • Images use real works/people/screenshots; if images are missing, first request assets; any generated images must be labeled as generated.
  • Do not use phrases like "This is my personal website" or "Below are my works" as part of the design.

Chinese typography: line-height ≥ 1.7, paragraph spacing ≥ 18px, font stack must include PingFang SC. When stronger frontend design capability is needed, invoke the frontend-design skill.

⑥ Verification

Read references/delivery-checklist.md and go through each item. At minimum, verify:

  • Homepage, navigation, detail pages, external links, primary action
  • Five width breakpoints: 360 / 390 / 768 / 1280 / 1440
  • Longest name and title do not overflow; empty content, image load failures, and broken external links are handled gracefully
  • Console has no errors affecting usage; no unexpected horizontal scrolling or layout overlaps
  • Both light and dark themes are readable (contrast ratio ≥ 4.5:1)
  • No remaining TODO placeholders, fabricated numbers, or test links within the site
  • Public information matches the user-confirmed checklist

Use python3 -m http.server for local preview, or use claude-in-chrome to take screenshots, and ask the user to confirm before publishing.

⑦ Deploy After Authorization

First explain where it will be published, whether it's public, which repository/account will be used, and which domain names or environment variables will be modified. Get explicit authorization before execution.

  • Existing projects: Continue with the current deployment method; for new static sites, prioritize Cloudflare Pages / Vercel / GitHub Pages (leave build command blank, set output directory to the site root).
  • Build → Publish → Visit the production URL to verify key content. Preview success does not equal custom domain activation.
  • Do not bundle secrets, original resumes, or platform-exported data into the site.

Final Delivery Notes

Concisely list: Selected goal and content depth / Implemented pages and key content / Access URL / Verification results / Content not yet public or pending additions. Do not use lengthy retellings to conceal incomplete code, verification, or deployment.

What Not to Do

  • ❌ Cramming all content onto the homepage — The first screen should clearly say "Who you are + what you can do + how to find you" within 3 seconds; everything else is secondary
  • ❌ Vague phrases like "Passionate about technology, pursuing excellence" — Replace with verifiable facts and numbers
  • ❌ Fabricating experiences, projects, numbers, or client testimonials that the user hasn't provided
  • ❌ Dumping a dozen questions at once, or skipping material confirmation and solution confirmation to write code directly
  • ❌ Forcing L3 when materials are insufficient, using empty blogs and placeholder case studies to pad content
  • ❌ Complex animations, gradient stacks, different fonts for each section — The credibility of a personal website comes from restraint
  • ❌ Cloning an entire reference site and just changing the name — Extract the feel of colors/typography/spacing, not logos, copy, illustrations, or unique layouts
  • ❌ Pushing / deploying / publishing contact information without authorization

相关技能