メニュー
Frame web development through user outcomes and design thinking principles. Use when defining features, prioritizing backlogs, translating stakeholder needs into buildable specifications, or when technical implementation needs grounding in user value.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create, update, close, and report on Jira tickets. Reads JIRA_URL and JIRA_TOKEN from environment variables or .env file. Provides comprehensive guidance for Jira ticket lifecycle management, API integration, and automation workflows.
AI-powered clarity engine for job seekers and founders. Not a resume fixer — a thinking partner. Helps you find your north star sentence: who you are, what you do, and why it matters to someone else. Produces one core version and targeted variations for different audiences. Use before interviews, investor conversations, networking events, or any moment where you need to introduce yourself under pressure.
Review code for bugs, security issues, and improvements. Use when the user asks to: (1) review code or a diff, (2) check code quality, (3) find bugs or issues, (4) audit for security problems. Trigger on phrases like 'review this', 'check my code', 'any issues with this', 'code review'.
Full-lifecycle career advisor — self-discovery through career growth. Use when the user wants to: (1) discover identity, values, ikigai, or skills inventory, (2) define dream job or analyze career gaps, (3) close gaps via learning, certifications, portfolio, or personal branding, (4) build narrative hats or role-specific positioning, (5) search for jobs, generate resumes, or prepare for interviews, (6) onboard into a new role, track achievements, or generate self-reviews, (7) backfill past roles, run weekly recall, or check career readiness. Proactively nudges users to document achievements NOW — not when they need a resume. Consolidates the former career-resume, career-tracker, portfolio-strategy, and github-profile skills.
Synthesizes professional accomplishments into high-converting landing page content. Triggers when a user wants to build a landing page, launch a consulting service, productize their career expertise, create a service page, or monetize their skills. Also triggers on: "freelance", "consulting offer", "offer page", "service offering", "turn my experience into a business". Uses career-advisor data as the foundation.
Query Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers. Use when user mentions NotebookLM, shares a notebooklm.google.com URL, asks to query their notebooks/docs, or says "ask my NotebookLM", "check my docs", "query my notebook". Provides browser automation, notebook library management, and persistent auth. Drastically reduced hallucinations through document-only responses from Gemini.
| name | pm-design-thinking |
| description | Frame web development through user outcomes and design thinking principles. Use when defining features, prioritizing backlogs, translating stakeholder needs into buildable specifications, or when technical implementation needs grounding in user value. |
Users don't want features. They want outcomes. Build backward from the transformation.
"Before building: Who is frustrated? What are they trying to accomplish?
What's blocking them? What does success look like in their words?"
"After understanding: What's the smallest thing we can build to test
if we understood the problem correctly?"
| PM Artifact | Agent-Ready Specification |
|---|---|
| "As a user, I want to filter products" | "Build product filtering: by category (multi-select), price range (slider), and availability. Show result count updating in real-time. Empty states show 'No matches' with clear-filters option" |
| "Improve checkout conversion" | "Reduce checkout to single page. Show running total. Validate fields on blur, not submit. Guest checkout default, account creation optional post-purchase" |
Structure prompts around JTBD:
"When [situation], I want to [motivation], so I can [outcome]"
→ "When a user lands on the dashboard Monday morning, they want to see
what needs attention first, so they can prioritize without clicking
around. Build a 'needs attention' widget showing: overdue tasks,
unread messages, approaching deadlines—sorted by urgency."
Before prompting, filter through:
"Build a clickable prototype (React) of the new onboarding flow.
Hardcode the data. Focus on interaction patterns, not backend.
I need to test this with users tomorrow."
| PM Theater | Real PM Thinking |
|---|---|
| "Add a dashboard" | "Help users answer: Am I on track today?" |
| "We need analytics" | "We need to know if users find value before day 7" |
| "Make it intuitive" | "New users complete core action in <2 minutes without help text" |
"Before building, generate 3 different approaches to solving [user problem]. For each, state: the assumption it tests, the simplest possible implementation, and how we'd know it worked."
The agent becomes a product thinking partner, not just a feature factory.
| Skill | When to use it |
|---|---|
idea-validation | Before feature definition — validate that the problem is worth solving |
product | After feature definition — write PRDs, prioritize roadmaps, manage scope |