phuryn/product-name
pm-marketing-growth/skills/product-name/SKILL.md
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills product-nameInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 21, 2026, 1:53 PM41.9s1 file scanned
SKILL.md
- name:
- product-name
- description:
- Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.
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:
- Name: The proposed product name
- Rationale: Explain why this name works—how it reflects the product's value, appeals to the target audience, and aligns with brand positioning
- Brand Fit: How the name supports the overall brand architecture and messaging strategy
- Memorability: Why the name is distinctive, easy to remember, and differentiating in the market
- 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
Related Skills
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
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.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
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.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026