product-name
This Claude Code skill generates five distinct product names with detailed rationale, brand alignment analysis, and trademark considerations. Use it when launching a new product, rebranding an existing offering, or exploring naming options that strengthen market positioning and resonate with your target audience before final selection and registration.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/product-name && cp -r /tmp/product-name/pm-marketing-growth/skills/product-name ~/.claude/skills/product-nameSKILL.md
# Product Name Brainstorm unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring name options that strengthen your brand positioning. ## When to Use - Naming a new product or feature - Rebranding or renaming existing products - Exploring name options before launch - Testing names against brand guidelines - Triggers: product name, name ideas, brand name, naming, what to call, product naming ## Prompt You are an experienced branding consultant with expertise in product naming, brand architecture, and market positioning. Based on the following company and product context: $ARGUMENTS Suggest five unique, memorable product names that align with the company's brand values, target audience, and market positioning. For each name suggestion, provide: 1. **Name**: The proposed product name 2. **Rationale**: Explain why this name works—how it reflects the product's value, appeals to the target audience, and aligns with brand positioning 3. **Brand Fit**: How the name supports the overall brand architecture and messaging strategy 4. **Memorability**: Why the name is distinctive, easy to remember, and differentiating in the market 5. **Domain & Trademark Considerations**: Brief note on availability and potential trademark/domain concerns Prioritize names that are: - Easy to pronounce and spell - Distinctive and differentiated from competitors - Aligned with brand tone and positioning - Relevant to the product's core value and use case - Available for trademark and domain registration ## Tips for Best Results - Share your brand guidelines and tone of voice - Specify target audience and their preferences - Mention competitor names and what you want to differentiate from - Include any naming conventions or patterns used by your company - Share the product's core value proposition and key features - Mention geographic markets or languages to consider
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.