メニュー
Rewrite project markdown into stronger hiring-manager case studies with clear summary, highlights, problem, approach, outcome, skills, tools, and tags. Use when editing src/content/projects/*.md.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Safely edit Astro content collections, markdown frontmatter, portfolio-config.json, and project data without breaking schema validation or build output.
Check portfolio edits for invented metrics, unsupported claims, inflated ownership, inconsistent scale numbers, and stale dates. Use before committing content changes.
Review portfolio content for senior TPM, product operations, game production, live operations, and community platform leadership positioning. Use when editing README, homepage, About, Career, Now, Contact, or top-level portfolio messaging.
Edit portfolio content so recruiters and hiring managers can understand the strongest proof within 30 seconds. Use for top-level pages, README, summaries, card summaries, and project highlights.
Map portfolio projects to specific job targets and recommend featured ordering, project emphasis, and language changes for applications.
Build, run, and drive the TRiley-Nexus Astro portfolio site. Use when asked to start the site, take a screenshot of any page, smoke-test all routes, build for production, or verify a UI change.
| name | case-study-rewrite |
| description | Rewrite project markdown into stronger hiring-manager case studies with clear summary, highlights, problem, approach, outcome, skills, tools, and tags. Use when editing src/content/projects/*.md. |
| paths | ["src/content/projects/*.md"] |
Improve project markdown so each project reads like a concise portfolio case study.
For each project, strengthen these fields:
summary: 1–2 sentences. Lead with what was delivered, for whom, and why it mattered.cardSummary: 1 recruiter-scan-friendly sentence.highlights: maximum 3 bullets. Use the strongest proof points.problem: what was broken, slow, risky, expensive, unclear, or difficult.approach: what Riley changed, built, coordinated, or operationalized.outcome: what improved. Put verified metrics first.skills: portable skills, not internal-only labels.tools: specific tools and platforms.tags: 4–6 concise tags.Use this internal structure:
Condense that structure into the existing frontmatter fields unless the site clearly renders markdown body content well.
Treat these as high-priority case studies:
Use active voice. Lead with outcomes. Be specific about scope. Preserve verified numbers. Do not invent numbers. Do not overstate sole ownership. Prefer "led," "owned," "coordinated," "built," "standardized," "translated," and "operationalized" only when supported by the existing content.