Create a personal site
Produce a working site that explains who the person is, shows relevant work, and gives visitors a useful next step.
Choose the content and platform
- Infer the audience and purpose from the request. Ask for missing facts that affect the result, such as a short bio, selected work, or a public contact link; continue layout work while waiting.
- Honor the chosen platform and host. If Sites is available and the user has no platform preference, use its current skill and tools. Otherwise, a small static HTML/CSS site is a useful starting point. Preserve any supplied codebase and its conventions.
- Use only supplied personal facts and public links. Do not invent achievements, employers, credentials, testimonials, or contact information. Keep any draft examples visibly labeled and replace or remove them before publishing.
Use the example assets
The paths below are relative to this skill directory:
- Starter page and stylesheet: a responsive, dependency-free fictional portfolio. Copy both into the working project before adapting them. The HTML works directly; it does not read the JSON file.
- Portfolio content: fictional biography and projects matching the starter.
- Researcher content: an alternate fictional content shape with research interests and writing. Use it as an input example, not verified publication data.
Replace the example banner, name, bio, titles, descriptions, metadata, and links as a coherent set. Select sections the user can fill; remove irrelevant cards and empty sections. Adapt the visual design to the request instead of forcing the example layout.
Build and verify
- Use semantic sections, readable typography, responsive spacing, visible keyboard focus, meaningful link text, and text alternatives for informative images. Keep the primary action easy to find. Respect reduced-motion preferences if adding animation.
- Preview at a narrow phone width and a wide desktop width. Check navigation, primary actions, horizontal overflow, and local asset paths. Run existing build or validation commands when applicable. Report any preview or tooling limitation accurately.
- Before publishing, remove fictional content and unresolved links, and follow the selected host's available workflow within the user's authorization. Verify the live URL when deployed.
- Deliver a preview or working files, describe remaining content gaps, and give the shortest useful instructions for editing the site later. Claim a live site only after deployment succeeds.