Built as working context, not shelfware.
This resource is meant to be useful inside the tools where product work now happens: your codebase, your notes, and your AI-assisted workflow.
01
Paste the markdown into Claude, ChatGPT, Cursor, Codex, Gemini, or another AI agent as reusable project context.
02
Use it before a planning, implementation, review, or audit session so the agent has constraints, criteria, and working structure up front.
03
Adapt the sections to your product, team, or repo before asking the agent to execute against it.
Markdown previewpersonal-site-content-audit-template.md
# Personal Site Content Audit Template Use this to evaluate a portfolio or personal site from a recruiter, client, or hiring-manager perspective. ## 1. Positioning - Name: - Current role or target role: - Location and availability: - Target audience: - One-sentence positioning: - Three strongest proof points: - Work I want more of: - Work I want less of: ## 2. First Impression - [ ] The first viewport says who this person is. - [ ] The site makes location or work model clear if relevant. - [ ] The strongest capability is visible early. - [ ] The visual style supports the role being pursued. - [ ] The site feels current without relying on trend-only language. - [ ] There is an obvious next action. Notes: - ## 3. Credibility - [ ] Work history is accurate. - [ ] Role scope is specific. - [ ] Outcomes are concrete. - [ ] Tools and methods are explained with enough depth. - [ ] Case studies separate personal contribution from team contribution. - [ ] Claims are backed by examples, artifacts, or metrics. Evidence gaps: - ## 4. Content Coverage Score each area from 1 to 5. | Area | Score | Notes | | --- | --- | --- | | About | | | | Work | | | | Tools | | | | Writing | | | | Contact | | | | Resume/CV | | | | SEO metadata | | | ## 5. Recruiter Signals - [ ] Current title or target title is easy to infer. - [ ] Location is clear. - [ ] Time zone or remote preference is clear if useful. - [ ] Seniority level is supported by evidence. - [ ] Technical stack is explicit. - [ ] AI tooling is credible and practical, not just buzzwords. - [ ] Contact path is simple. - [ ] CV or LinkedIn is available. ## 6. Rewrite Queue | Page/Section | Problem | Proposed Change | Priority | | --- | --- | --- | --- | | | | | | | | | | | | | | | | ## 7. Final Pass - [ ] Remove outdated geography, roles, or company references. - [ ] Remove vague adjectives that are not proven. - [ ] Replace generic process language with concrete workflows. - [ ] Add missing screenshots or artifacts. - [ ] Check mobile layout. - [ ] Run build and link checks.