Update a personal site
Make the requested change in the user's existing site and keep its content, stack, hosting, and design conventions consistent.
Locate the source and make the edit
- Inspect the supplied source, repository, or connected site. A public URL helps understand the page, but editing requires its source or an authorized site tool. If access is missing, draft the replacement content or patch while asking for the editable source.
- Identify the relevant page, component, data file, and styles. Reuse established components. Keep changes focused; expand them only when necessary to complete the requested behavior.
- Preserve verified facts and links. Use the user's new information for added projects or biography edits. Ask about consequential missing facts instead of borrowing the fictional examples as personal data.
- For a project entry, obtain a title, brief description, the person's role, and an optional public link. Omit unavailable fields instead of inventing them. Follow the site's existing field names rather than introducing a new schema.
Example assets
These paths are relative to this skill directory:
- Portfolio example shows a concise bio and project entries.
- Researcher example shows a research-focused alternative.
- Starter page and styles provide layout examples when the user requests a redesign. They are optional references; preserve the existing source for ordinary edits.
Check and deliver
- Run the site's existing checks when available. Preview affected pages at phone and desktop widths; check the edited links, keyboard focus, navigation, and overflow.
- Review the diff for accidental changes to unrelated pages, public contact details, or metadata.
- Publish only within the request's existing authorization and use the chosen host's workflow. Check the deployed page when applicable.
- Describe the concrete change, how it was verified, and where the user can preview or edit it. Distinguish a prepared change from a deployed one.