Builds AI-native products using Dan Shipper's 5-product playbook and Brandon Chu's AI product frameworks. Use when implementing prompt engineering, creating AI-native UX, scaling AI products, or optimizing costs. Focuses on 2025+ best practices.
npx skills add https://github.com/menkesu/awesome-pm-skills --skill ai-startup-building
Claude uses this skill when:
Key Principles:
Modern Approach:
- Use structured outputs (JSON)
- Implement streaming
- Design for retry logic
- Plan for model switching
- Cache aggressively
Strategies:
// Modern AI product pattern (2025)
interface AIFeature {
// Streaming for responsiveness
async *stream(prompt: string): AsyncGenerator<string> {
const cached = await checkCache(prompt);
if (cached) return cached;
// Route to appropriate model
const model = this.selectModel(prompt);
for await (const chunk of model.stream(prompt)) {
yield chunk;
}
}
// Model selection (cost optimization)
selectModel(prompt: string): Model {
if (this.isSimple(prompt)) {
return this.smallModel; // Fast, cheap
} else {
return this.largeModel; // Smart, expensive
}
}
// Retry logic (reliability)
async withRetry<T>(fn: () => Promise<T>): Promise<T> {
for (let i = 0; i < 3; i++) {
try {
return await fn();
} catch (e) {
if (i === 2) throw e;
await sleep(Math.pow(2, i) * 1000);
}
}
}
}
# AI Cost Analysis: [Feature]
## Current Usage
- Daily requests: [X]
- Model: [GPT-4/Claude/etc.]
- Cost per 1K requests: [$X]
- Monthly cost: [$Y]
## Optimization Plan
### 1. Caching (Est. 80% hit rate)
- Before: [100]% paid calls
- After: [20]% paid calls
- Savings: [80]%
### 2. Model Routing
- Simple queries ([60]%): Small model
- Complex queries ([40]%): Large model
- Savings: [50]%
### 3. Batching
- Real-time: [X]% of requests
- Batchable: [Y]% of requests
- Savings: [Z]%
## Projected Cost
- Before optimization: [$X/month]
- After optimization: [$Y/month]
- Reduction: [Z]%
Build:
Optimize:
Scale:
Approach:
Key Insights:
Dan Shipper:
> "AI doesn't replace PMs. It makes small PM teams as powerful as large ones."
On Prompt Engineering:
> "The best prompts in 2025 are structured, explicit, and tested with evals."
Brandon Chu:
> "Build for the AI you'll have in 6 months, not the AI you have today."
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take menkesu/ai-startup-building 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.