Product Development Skill for Claude
End-to-end product development for iOS/macOS apps. Covers market research, competitive analysis, PRD generation, architecture specs, UX design, implementation guides, testing, and App Store release. Use for product planning, validation, or generating specification documents.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/rshankras/claude-code-apple-skills --skill product-developmentThe instruction itself
10 sections, as written by the authorProduct Development Expert
Comprehensive product development guidance for iOS/macOS apps. This skill orchestrates the entire product lifecycle from idea validation to App Store release.
When This Skill Activates
Use this skill when the user:
- Has an app idea and wants to validate it
- Needs market research or competitive analysis
- Wants to generate product specifications
- Needs architecture or UX design documents
- Is preparing for App Store submission
- Wants to plan beta testing or TestFlight strategy
- Needs localization strategy or market expansion planning
- Wants end-to-end product planning
Available Modules
Read relevant module files based on the user's needs:
Phase 0: Idea Discovery
idea-generator/
Brainstorm and rank app ideas via 5 lenses.
- Developer profile elicitation (skills, interests, constraints)
- Five brainstorming lenses (skills, problem-first, technology-first, market gap, trend-based)
- Feasibility filtering and scoring
- Ranked shortlist of 3-5 ideas with
next_stepcommands
app-namer/
Turn a chosen idea into validated, App-Store-ready name candidates.
- Branded vs. descriptive vs. hybrid archetypes, paired with a subtitle
- App Store display rules (30-char limit, Home-Screen truncation, name/subtitle interplay)
- Validation gauntlet: App Store Connect name, trademark knockout, domain/.app, social handle, linguistic safety
- Ranked shortlist with scores and a "reserve now" action; feeds
app-store/keyword-optimizer
Discovery & Validation
product-agent/
AI-powered product discovery and validation.
- Idea validation and assessment
- MVP scoping
- Market opportunity analysis
market-research/
Deep market analysis.
- Market sizing (TAM/SAM/SOM)
- Growth trends and maturity
- Entry barriers and distribution channels
- Revenue potential
competitive-analysis/
Competitor deep dive.
- Feature comparison matrices
- Pricing analysis
- Strengths/weaknesses
- Differentiation opportunities
Specification Generation
prd-generator/
Product Requirements Document.
- Features and user stories
- Acceptance criteria
- Success metrics
architecture-spec/
Technical architecture.
- Architecture pattern selection
- Tech stack decisions
- Data models
- App structure
ux-spec/
UI/UX specifications.
- Wireframes and user flows
- Design system definition
- Interaction patterns
implementation-guide/
Development roadmap.
- Step-by-step instructions
- Pseudo-code examples
- Implementation priorities
test-spec/
QA and testing strategy.
- Unit test coverage
- UI testing plan
- Accessibility testing
- Beta testing strategy
release-spec/
App Store preparation.
- Submission guide
- Asset requirements
- Privacy compliance
- Marketing strategy
Pre-Launch
beta-testing/
TestFlight beta program strategy and feedback collection.
- Internal vs. external testing cohort management
- Beta tester recruitment and incentive strategies
- Feedback collection methodology (in-app, surveys, interviews)
- Signal vs. noise framework for interpreting feedback
- Go/no-go launch decision framework
localization-strategy/
Market prioritization and localization planning.
- Language tier recommendations by app category
- Minimum viable localization levels (metadata-only to full)
- Translation workflow with Xcode String Catalogs
- Cultural adaptation beyond translation
- Localized ASO strategy
Orchestration
implementation-spec/
Master orchestrator.
- Generates complete specification package
- Coordinates all role-based agents
- End-to-end spec generation
WORKFLOW.md
Product development workflow guide.
How to Use
- Identify where user is in product lifecycle
- Read relevant module SKILL.md for detailed process
- Generate requested specifications
- Save outputs to appropriate files
Example Workflows
User doesn't have an idea yet:
- Use
idea-generator/to brainstorm and rank ideas - Pick top idea from shortlist
- Run
product-agent/to validate the idea - Run
app-namer/to name it and reserve the App Store name - Continue with market research and specs
User has new app idea:
- Use
product-agent/for initial validation - Run
market-research/for market sizing - Run
competitive-analysis/for competitor insights - Generate PRD with
prd-generator/
User wants full spec package:
- Use
implementation-spec/orchestrator - It coordinates all spec generators
- Produces complete documentation set
Other skills for the same job
different authors, same section of the catalogue
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
Prepares and structurally reviews readiness evidence for ISO management-system and laboratory-competence standards - ISO 13485 medical device QMS, ISO 14971 device risk management, ISO/IEC 17025 testing and calibration laboratories, and ISO 15189 medical laboratories. Use when organizing declared scope, controlled documents, risk-management files, scope of accreditation, traceability, CAPA, external-provider controls, or bounded local evidence manifests, and when separating ISO certification from laboratory accreditation, FDA QMSR inspection, CLIA certification, MDSAP, and EU MDR/IVDR evidence boundaries. Not for legal applicability, compliance, certification, or accreditation decisions; contains no clause text.
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers closed-form power for t-tests, ANOVA, proportions, correlations, chi-square, and regression, plus simulation-based (Monte Carlo) power for designs with no formula — logistic/Poisson regression, mixed models, cluster-randomized trials, survival, and interactions. Use this skill even when the request only mentions an effect size, alpha, or "80% power" without saying "power analysis" explicitly. For laying out the study (randomization, blocking, factorial/DOE, crossover, sequential designs) use experimental-design; for analyzing data already collected and reporting it use statistical-analysis.
Universal QA checklist for generated scientific plots: overlapping labels, clipped text, missing axes/legends, overcrowded data, and cross-journal resolution/format guidance.
Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation.
Run PinchBench benchmarks to evaluate OpenClaw agent performance across real-world tasks. Use when testing model capabilities, comparing models, submitting benchmark results to the leaderboard, or checking how well your OpenClaw setup handles calendar, email, research, coding, and multi-step workflows.
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
Verify PowerToys behavior end-to-end with the winapp CLI across two scenarios: (A) a module's release checklist against the installed build; (B) PR validation — derive each PR's checklist from its description + diff, then drive it against the installed build (a merged/shipped PR, or a whole release/hotfix set) or by building + sideloading the module when the PR isn't in the build yet (unmerged or not-yet-released). Drive each item via UIA invoke / Named Events / settings.json edits / clipboard / GPO / SendInput, and emit a structured PASS / FAIL / BLOCKED verdict per item with evidence (FAIL distinguishes product defects from stale/ambiguous checklist items). Use when asked to verify a module checklist, validate a PR, sign off a release/hotfix's PRs, or QA installed/sideloaded PowerToys bits. Combines generic winapp ui mechanics (references/winapp-ui-testing.md) with PT-specific recipes, per-scenario playbooks (references/scenarios/), and the helper .ps1 files shipped with this skill.
How to use it
Take rshankras/product-development from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.