菜单
Audit every App Router page.tsx for missing or weak SEO metadata, OG/Twitter tags, canonical URLs, and JSON-LD structured data, per docs/PRODUCT.md §9's SEO requirements. Use after adding or changing a route, or when asked to check SEO health.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a portfolio case-study JSON file (title, description, client, category, role, stack, timeframe, sections of Problem/Approach/Challenges/Impact/Learnings) from a real feature/project/PR in any repo — company or personal. Use this whenever the user asks to "turn this into a case study," "write up this project for my portfolio," "generate case-study.json for X," "document this feature as a case study," or points at a folder/PR/commit range and asks for a portfolio write-up. Fully self-contained — bundles its own schema and reference example, so it works in any repo regardless of whether that repo has its own case-study schema files. Investigates the target code/history thoroughly before writing anything, and never invents facts, metrics, or quotes it can't source — always asks the user instead of guessing when something can't be determined from the evidence.
Enforce this portfolio's copy rules and verified facts before writing or editing any user-facing copy (hero text, section copy, case studies, project descriptions, resume-derived content). Claude applies it automatically before writing portfolio copy; the owner can also run /content-update directly to spot-check existing copy.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Scaffold a new App Router route or a new section within an existing route, following this repo's real structure and conventions (route sections vs. route-local components, global @ aliases, FullWidthWrapper/Section reuse, nav wiring). Use when the user asks to add a new page/route (e.g. "add the /work page") or a new section to an existing route (e.g. "add a testimonials section to the homepage").
Build the project and report First Load JS per route to catch bundle-size regressions. Run before declaring any task done if bundle size is relevant (new dependency, new route, large component added), per AGENTS.md golden rule 7 (Core Web Vitals as a feature).
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
| name | seo-audit |
| description | Audit every App Router page.tsx for missing or weak SEO metadata, OG/Twitter tags, canonical URLs, and JSON-LD structured data, per docs/PRODUCT.md §9's SEO requirements. Use after adding or changing a route, or when asked to check SEO health. |
Use src/app/page.tsx (the homepage) and src/app/layout.tsx as the reference baseline — they
already implement this correctly. An audit finding is "missing X" only if a route falls short
of what the homepage already does, not a hypothetical ideal.
For every page.tsx under src/app/, check:
Metadata object with at minimum title and description. Prefer
route-level overrides of the root template (src/app/layout.tsx sets a title template:
"%s — Gobind Singh") rather than duplicating the full title.alternates.canonical set, using SITE_URL from @lib/site-config
(don't hardcode the domain).openGraph block (title, description, url, images) using the shared
OG_IMAGE from @lib/site-config unless the route needs a distinct image.twitter block, card: "summary_large_image" to match the existing
pattern in layout.tsx/page.tsx.JsonLd component
(@components/json-ld), not a hand-written <script> tag. Check against
docs/PRODUCT.md §9 for what's expected per page type: Person/WebSite (home/about),
BreadcrumbList (nested pages), Article/BlogPosting (blog posts), CreativeWork
(case studies, optional).<h1> per page, logical heading order after it
(<h2> for section titles, etc. — most routes render Section's (or RailSection's)
title as an <h2>).next/image usage has a descriptive alt; no meaningful image ships
with an empty or placeholder alt.aria-label where the visible text is just an icon/arrow.Also check project-wide (not per-page):
src/app/sitemap.ts includes every real route (cross-check against what's actually built,
not just what's planned in docs/PRODUCT.md).src/app/robots.ts isn't accidentally disallowing a route that should be indexed.src/lib/site-config is the single source for SITE_URL/SITE_NAME/SITE_DESCRIPTION/
OG_IMAGE — flag any route that hardcodes these instead of importing them.Report format: one line per route, pass/fail per check above, with the specific gap named (not just "SEO incomplete"). If a route is fully compliant, say so briefly rather than omitting it.