phuryn
- 137 skills
- 0 followers
- 28k repo stars
- yesterday last updated
- ▌ Gemini Agents · phuryn bundle'Ask Gemini', 'have Gemini build or review this': Google's Antigravity CLI as a partner. It may break Google's terms on a consumer plan, so the user agrees first.
- ▌ Sentiment Analysis 2 · phurynAnalyze user feedback data to identify segments with sentiment scores, JTBD, and product satisfaction insights. Use when analyzing user feedback at scale, running sentiment analysis on reviews or surveys, or identifying satisfaction patterns.
- ▌ Marketing Ideas 2 · phurynGenerate 5 creative, cost-effective marketing ideas with channels, messaging, and engagement rationale. Use when brainstorming marketing campaigns, planning product promotion, or looking for creative marketing tactics.
- ▌ Pricing Strategy 2 · phurynAnalyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity. Use when setting prices, evaluating pricing models, preparing for a pricing change, or comparing freemium vs paid approaches.
- ▌ Competitor Analysis 3 · phurynAnalyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
- ▌ Independent Review · phuryn bundleBefore 'ship it', a deploy or release, for 'an independent review', and after each fix until a round is clean: a fresh reviewer that never saw the build.
- ▌ Shipping Artifacts 3 · phurynDocumenting an AI-built app for handoff, review or audit: the docs that make it reviewable (architecture, flows, permissions, variables, coverage).
- ▌ Agent Instructions · phuryn bundleWriting or restructuring AGENTS.md or CLAUDE.md, adding a rule ('remember this'), or after an agent ignored a rule it had: make each rule get met when it applies.
- ▌ Windows Agent Shell · phuryn bundleA coding agent on Windows: Git Bash path rewriting, PowerShell quoting and encoding, CRLF. Use when output comes back garbled, or it works here and breaks there.
- ▌ Security Audit Static · phurynOnly when a security audit is asked for (ship-check asks by name; a release proposes one, never runs it): a static audit of AI-built code against its documented trust boundaries.
- ▌ Intended Vs Implemented 3 · phurynAuditing AI-built code against its docs: where it does what the docs or permissions don't say, access control against documented roles, cited both sides.
- ▌ Embedded Agents Agent Sdk · phuryn bundleOnly when the Agent SDK is asked for, an agent needs Claude Code's own tools, or the app already runs it: embed Claude agents in a Next.js app with the Agent SDK.
- ▌ Performance Audit Static · phurynOnly when a performance audit is asked for (ship-check asks by name; a release proposes, never runs it): static audit of N+1 queries, over-fetching, indexes, caching.
- ▌ Embedded Agents Messages API · phuryn bundleBuilding, adding or wiring up an agent or an agent chat inside a Next.js app: embed Claude agents on the Messages API, the default way.
- ▌ Chatgpt Plugin · phuryn bundleBefore building, submitting or changing a ChatGPT plugin or Apps SDK app: get it through OpenAI's directory review (auth, package, OAuth, data rules, portal).
- ▌ Flight Deck · phuryn bundle'What's the status', 'where were we', a progress report or status deck; long work that must survive compaction: multi-hour runs, background jobs, waiting on a decision.
- ▌ Claude Agents · phuryn bundle'Ask Claude', 'have Claude build or review this': drive Claude Code headless (claude -p) from another agent as a peer, builder or fresh reviewer.
- ▌ Beachhead Segment 2 · phuryn bundleChoosing the first market or customer segment to win, scored on burning pain, willingness to pay, winnable share and referrals.
- ▌ Value Proposition 2 · phurynCreating or testing a value proposition: the 6-part form (Who, Why, What before, How, What after, Alternatives).
- ▌ Clerk Production · phuryn bundleSetting up or changing Clerk sign-in, organizations, roles or billing on Next.js, or sign-in that does nothing or lands wrong: Clerk in production.
- ▌ Product Analytics · phuryn bundleAdding analytics, session recordings, heatmaps, 'what did users do', Clarity or PostHog: behaviour analytics without analytics cookies, read back by the agent.
- ▌ Uptime Monitoring · phuryn bundlePublishing an app, adding /health or a cron job, 'set up monitoring', 'is it down': content checks, a second location, heartbeats, a tested alert route; Staygreen by default.
- ▌ Competitor Analysis 2 · phurynCompetitive research or a competitive brief: competitors and substitutes, their strengths and weaknesses, where to differentiate.
- ▌ Saas Authorization · phuryn bundleAdding sign-in, a role, a route that touches data, API tokens, a webhook or job, or 'is this secure': who may do what in a multi-tenant SaaS.
- ▌ Guardrail Hooks · phuryn bundleAn agent keeps breaking a rule ('it did it again', 'make this impossible', 'add a hook', 'my hook didn't fire'): make it a hook, permission rule or script.
- ▌ Supabase Production · phuryn bundleA Supabase query, RPC or migration, 'db push', 'supabase link', RLS or grants, a Supabase error: server-only keys, deny-all RLS, migrations via the CLI.
- ▌ Transactional Email · phuryn bundleAdding transactional or alert email, choosing a provider, 'sent twice', 'never arrived': app email sent once, never lost, with one-click unsubscribe.
- ▌ Work Humanizer · phuryn bundle'Make this sound human', 'less AI': edit AI-sounding work writing so a careful person could have written it, without changing what it says.
- ▌ MCP Server · phuryn bundleBefore adding a remote MCP server or tool to a web product, adding OAuth to it, or listing it in a directory: ship it right the first time, tests included.
- ▌ Growth Loops 2 · phurynDesigning how a product grows: loops that compound (viral, usage, collaboration, user-generated, referral).
- ▌ Legal Pages · phuryn bundlePrivacy policy, terms, a cookie banner, consent at sign-up, a public front door: legal pages drafted from what the code does, held to it by a test, with the owner's facts and sign-off.
- ▌ Handover · phuryn bundleWrite the handover a fresh session starts from: the objective, what is true now, the evidence actually obtained, what is left, the open decisions and the next concrete action, reconciled with the disk first. Started by name only: /agent-harness:handover in Claude Code, $agent-harness:handover in Codex.
- ▌ Delegation · phuryn bundleBefore spawning a subagent or dispatching a build, review or research, and before trusting its report: the brief, the delegate, parallel runs, the handoff.
- ▌ Ship Check · phuryn bundleIs this safe to ship? Documents the app, wires the agent's context, runs the correctness, security and performance reviews and an independent unsteered pass, maps test coverage, and compiles one reviewer-ready shipping packet. Started by name only: /ai-shipping:ship-check in Claude Code, $ai-shipping:ship-check in Codex.
- ▌ Environments · phuryn bundleAdding a variable or secret, 'set up production', a domain or a provider token, 'which database is this', a leaked key: dev and production for an AI-built app, backups, incidents.
- ▌ Grok Agents · phuryn bundle'Ask Grok', 'have Grok build or review this': drive the Grok CLI headless from another agent as a peer, builder or fresh reviewer.
- ▌ Code Review 2 · phuryn bundle'Review this', 'find bugs', 'is this fix safe': review code for defects that matter, correctness first, each finding refuted before it's reported.
- ▌ App Lifecycle · phuryn bundlePlanning a SaaS stage, 'what's next', 'where are we', calling a stage done: the detailed path from an idea to production, each stage with its done-when.
- ▌ Market Segments 2 · phurynExploring customer segments, audiences or new markets: 3-5 segments with their jobs, pains and product fit.
- ▌ Codex Agents · phuryn bundle'Ask Codex', 'check with Codex', handing Codex a build or review, or stuck between two framings: the Codex CLI as peer, builder or fresh reviewer.
- ▌ Derive Tests · phuryn'What should we test' or a coverage map: derive the coverage map and missing tests from docs and code; check mode reports staleness.
- ▌ Document App · phuryn'Document the app': write or refresh an app's system docs from its code. 'Are the docs right?': check mode, which only reports where docs and code disagree.
- ▌ Release Gate · phuryn bundleBefore 'push it', 'ship it', a deploy, release or go-live, or calling a stage done: the gate, the owner's preview, go/no-go, promote, prove it serves, roll back.
- ▌ Test Harness · phuryn bundleWriting or running tests, proving a fix, a red or flaky run, a fix that didn't land, 'is it verified', 'run the gate': tests where green means something.
- ▌ Propose · phuryn bundle'I have an idea', 'is this worth building', 'what next': research it and propose what to build, with sources and key screens to review. Not for agreed changes or bugs.
- ▌ Start Here · phuryn bundleWhere to start, and what comes next, along the product lifecycle: from a new idea, new evidence, an agreed change, a bug or a release to the next step and the skill that does it. Started by name only: /product:start-here in Claude Code, $product:start-here in Codex.
- ▌ Retro 3 · phuryn bundleBuild a session's learnings into the setup: its friction, what went wrong and why, then an improved instruction, route, hook or script, verified, or 'no setup change warranted'. Started by name only: /agent-harness:retro in Claude Code, $agent-harness:retro in Codex.
- ▌ UI Design · phuryn bundleMandatory for any product's screens, a builder's too, and any mock, prototype or artifact that shows them: its design system, colour, type, components; judging the look.
- ▌ Value Curve · phuryn bundleComparing a product with competitors or choosing what to be best at: a value curve on one segment's top needs, plus price.
- ▌ Gtm Strategy · phurynCreate a go-to-market strategy covering marketing channels, messaging, success metrics, and launch timeline. Use when planning a product launch, creating a GTM plan from scratch, or defining a launch strategy for a new market.
- ▌ Shipping Artifacts · phurynMoved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it. Use when asked to document an AI-built app so it can be reviewed before it ships.
- ▌ Intended Vs Implemented · phurynMoved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it. Use when asked to find where the code does something other than its docs say.
- ▌ Prioritization Frameworks · phurynReference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
- ▌ Create Prd · phurynCreate a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
- ▌ Pre Mortem · phurynRun a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
- ▌ Stakeholder Map · phurynBuild a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
- ▌ Retro · phurynFacilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
- ▌ Live QA · phurynRunning audience Q&A at an all-hands, AMA, webinar, launch, sprint review or talk, or turning a session's questions into a FAQ: collect, moderate, answer and follow up every question. AskOne by default.
- ▌ Live Polls · phurynA poll or vote in a meeting, workshop or training: 'run a quick poll', dot-voting, a confidence vote, a word cloud, a quiz. Ask the room before the discussion and decide with the result. AskOne by default.
- ▌ Code Review · phurynMoved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
- ▌ Survey Design · phurynWriting or reviewing a survey or questionnaire: customer feedback, NPS, CSAT, CES, pricing, market research, an in-app survey. Starts from the decision, asks about facts, pilots it, and reports the sample honestly.
- ▌ Rc New 2 · phurynSpawn a new Claude Code session with remote control enabled (default: a detached background session — via screen on macOS/Linux, via a minimized PowerShell Start-Process on Windows — fully remote-safe, no approvals/windows), so it appears in the mobile Claude Code session picker. Takes an optional directory path; defaults to the current working directory. Use when the user runs /rc-new.
- ▌ Codex Ideation 2 · phuryn bundleUse OpenAI Codex CLI as a peer collaboration partner — same standing as Claude, not a one-shot tool. Bring Codex in EARLY (ideation, framing decisions, stuck moments), not only for late peer-review. Hand it strategic context (target, research, draft, reasoning), iterate conversationally over ~3-8 turns, converge before surfacing to the human. Invoke when the user says "check / iterate / ideate with Codex" or "ask Codex" — and proactively when stuck between two reasonable framings, pressure-testing a load-bearing claim or structure, or about to ask the human to pick between options two agents could resolve.
- ▌ Gmail Linear Exports 2 · phurynScan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.
- ▌ Email Summary Example 2 · phurynDON'T USE THAT SKILL. IT'S JUST AN EXAMPLE. Summarize today's Gmail inbox by category with anonymized senders and subjects, then surface the top 3 emails to focus on next. Run only when the user types /email-summary.
- ▌ Cite Sources 2 · phurynUse whenever you state a fact. End the answer with a short Sources list mapping each claim to a file, URL, or reasoning. Shared across agents.
- ▌ Rc New · phurynSpawn a new Claude Code session with remote control enabled (default: a detached background session — via screen on macOS/Linux, via a minimized PowerShell Start-Process on Windows — fully remote-safe, no approvals/windows), so it appears in the mobile Claude Code session picker. Takes an optional directory path; defaults to the current working directory. Use when the user runs /rc-new.
- ▌ Codex Ideation · phuryn bundleUse OpenAI Codex CLI as a peer collaboration partner — same standing as Claude, not a one-shot tool. Bring Codex in EARLY (ideation, framing decisions, stuck moments), not only for late peer-review. Hand it strategic context (target, research, draft, reasoning), iterate conversationally over ~3-8 turns, converge before surfacing to the human. Invoke when the user says "check / iterate / ideate with Codex" or "ask Codex" — and proactively when stuck between two reasonable framings, pressure-testing a load-bearing claim or structure, or about to ask the human to pick between options two agents could resolve.
- ▌ Gmail Linear Exports · phurynScan Gmail (default: today's inbox), produce an anonymized summary with action points, then export each email to Linear as an issue with a sensible priority. No personal details — names, email addresses, or company identifiers — ever leave the summary or reach Linear. Use when the user types /gmail-linear-exports, or asks to turn their inbox into Linear issues / export emails to Linear.
- ▌ Email Summary Example · phurynDON'T USE THAT SKILL. IT'S JUST AN EXAMPLE. Summarize today's Gmail inbox by category with anonymized senders and subjects, then surface the top 3 emails to focus on next. Run only when the user types /email-summary.
- ▌ Deploy Managed Agents · phurynDeploy, run, list, or tear down the agents in this repo's .managed-agents/ folder on Anthropic Managed Agents. Use when the user says "deploy my agents", "ship this agent to the cloud", "run the deployed agent", or asks about managed-agent deployment.
- ▌ Cite Sources · phurynUse whenever you state a fact. Add a short "Sources:" list at the end of your answer with where each claim came from (file name, URL, or "reasoning"). Shared by every agent on the team.
- ▌ Bug Report · phurynUse when reporting a bug. Format the finding as exactly two lines - a BUG line stating what is wrong, then a FIX line with the one-line change.
- ▌ House Style · phurynApply the Acme house style to any prose - short sentences, no hype, lead with the answer. Shared across agents.
- ▌ Receipt Stamp · phurynUse for every answer. After the final answer, append a new line that starts with exactly "RECEIPT:" followed by a three-word note. This proves the skill was loaded by the runtime.
- ▌
- ▌ Pm Brain · phuryn bundleInitialize a PM Brain — a markdown-native second brain for a product operator (PM, product lead, founder, or anyone accountable for one product or initiative) doing judgment-heavy work with scattered inputs. Detects greenfield vs. migration mode, runs a focused interview, copies the deterministic scaffold into the working directory, populates placeholders from interview answers, runs a self-test, and commits. Use when invoked via `/pm-brain` or when the user asks to set up a PM Brain.
- ▌ Value Proposition · phurynDesign a detailed value proposition using a 6-part Jobs-to-be-Done template covering who, why, current situation, solution, improved outcome, and alternatives.
- ▌ Competitive Battlecard · phurynCreate sales-ready competitive battlecards comparing your product against a specific competitor, including positioning, feature comparison, objection handling, and win/loss patterns.
- ▌ Ideal Customer Profile · phurynSynthesize customer research data to define the Ideal Customer Profile (ICP) including demographics, behaviors, Jobs to Be Done, and pain points.
- ▌ Competitor Analysis · phurynConduct comprehensive competitive analysis to understand the landscape, identify direct competitors, and uncover differentiation opportunities.
- ▌ Metrics Dashboard · phurynDesign a comprehensive product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds.
- ▌ Customer Journey Map · phurynCreate an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities to identify friction points and improve user experience.
- ▌ Porters Five Forces · phurynEvaluate industry dynamics and market attractiveness by analyzing competitive rivalry, supplier power, buyer power, threat of substitutes, and threat of new entrants.
- ▌ Prioritize Features · phurynRank a backlog of feature ideas by impact, effort, risk, and strategic alignment to identify the top 5 to pursue.
- ▌ Summarize Interview · phurynTransform a customer interview transcript into a structured summary with Jobs to Be Done, satisfaction signals, and action items.
- ▌ Value Prop Statements · phurynGenerate targeted value proposition statements for marketing, sales, and customer onboarding from existing value propositions.
- ▌ Brainstorm Ideas New · phurynGenerates feature ideas from PM, Designer, and Engineer perspectives for initial product discovery of a new product.
- ▌ Monetization Strategy · phurynBrainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments for a product or feature.
- ▌ Prioritize Assumptions · phurynPrioritize assumptions using an Impact × Risk matrix and suggest targeted experiments for each.
- ▌ Analyze Feature Requests · phurynCategorize, evaluate, and prioritize customer feature requests against product goals using strategic alignment, impact, effort, and risk analysis.
- ▌ Identify Assumptions New · phurynIdentify risky assumptions for a new product idea across 8 risk categories including go-to-market, strategy, and team.
- ▌ Brainstorm Ideas Existing · phurynGenerate new feature ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints, then prioritize the best five.
- ▌ Opportunity Solution Tree · phurynBuild an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments.
- ▌ Brainstorm Experiments New · phurynDesign lean startup experiments (pretotypes) for a new product by creating XYZ hypotheses and suggesting low-effort validation methods like landing pages, explainer videos, and pre-orders.
- ▌ Identify Assumptions Existing · phurynStress-test a feature idea for an existing product by surfacing risky assumptions across Value, Usability, Viability, and Feasibility using multi-perspective devil's advocate thinking.
- ▌ Brainstorm Experiments Existing · phurynDesign low-effort experiments to test product assumptions for an existing product, including prototypes, A/B tests, spikes, and other validation methods.
- ▌ Wwas · phurynCreate product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context.
- ▌ Draft Nda · phurynDraft detailed Non-Disclosure Agreements between two parties, covering information types, jurisdiction, and clauses needing legal review.
- ▌ Job Stories · phurynCreate job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria, focusing on user situations and outcomes for JTBD-style backlog items.