Fetches db-seed from jezweb/claude-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/db-seed
Restart Cursor to activate db-seed. Access via /db-seed in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
small (5-10 rows/table), medium (20-50), large (100+)
small
Domain context
"e-commerce store", "SaaS app", "blog", etc.
Infer from schema
Output format
TypeScript (Drizzle), raw SQL, or both
Match project's ORM
Purpose affects data quality:
dev: Varied data, some edge cases (empty fields, long strings, unicode)
demo: Polished data that looks good in screenshots and presentations
testing: Systematic data covering boundary conditions, duplicates, special characters
3. Plan Insert Order
Build a dependency graph from foreign keys. Insert parent tables before children.
Example order for a blog schema:
1. users (no dependencies)
2. categories (no dependencies)
3. posts (depends on users, categories)
4. comments (depends on users, posts)
5. tags (no dependencies)
6. post_tags (depends on posts, tags)
Circular dependencies: If table A references B and B references A, use nullable foreign keys and insert in two passes (insert with NULL, then UPDATE).
4. Generate Realistic Data
Do NOT use generic placeholders like "test123", "[email protected]", or "Lorem ipsum". Generate data that matches the domain.
Data Generation Patterns (no external libraries needed)
Names: Use a hardcoded list of common names. Mix genders and cultural backgrounds.
Emails: Derive from names — [email protected]. Use example.com domain (RFC 2606 reserved).
Dates: Generate within a realistic range. Use ISO 8601 format for D1/SQLite.
constrandomDate=(daysBack:number)=>{const d =newDate(); d.setDate(d.getDate()- Math.floor(Math.random()* daysBack));return d.toISOString();};
IDs: Use crypto.randomUUID() for UUIDs, or sequential integers if the schema uses auto-increment.
Deterministic seeding: For reproducible data, use a seeded PRNG:
functionseededRandom(seed:number){return()=>{ seed =(seed *16807)%2147483647;return(seed -1)/2147483646;};}const rand =seededRandom(42);// Same seed = same data every time
Prices/amounts: Use realistic ranges. (rand() * 900 + 100).toFixed(2) for $1-$10 range.
Descriptions/content: Write 3-5 realistic variations per content type and cycle through them. Don't generate AI-sounding prose — write like real user data.
5. Output Format
TypeScript (Drizzle ORM)
// scripts/seed.tsimport{ drizzle }from'drizzle-orm/d1';import*as schema from'../src/db/schema';exportasyncfunctionseed(db: ReturnType<typeof drizzle>){console.log('Seeding database...');// Clear existing data (reverse dependency order)await db.delete(schema.comments);await db.delete(schema.posts);await db.delete(schema.users);// Insert usersconst users =[{ id: crypto.randomUUID(), name:'Sarah Chen', email:'[email protected]',...},// ...];// D1 batch limit: 10 rows per INSERTfor(let i =0; i < users.length; i +=10){await db.insert(schema.users).values(users.slice(i, i +10));}// Insert posts (references users)const posts =[{ id: crypto.randomUUID(), userId: users[0].id, title:'...',...},// ...];for(let i =0; i < posts.length; i +=10){await db.insert(schema.posts).values(posts.slice(i, i +10));}console.log(`Seeded: ${users.length} users, ${posts.length} posts`);}
Run with: npx tsx scripts/seed.ts
For Cloudflare Workers, add a seed endpoint (remove before production):
app.post('/api/seed',async(c)=>{const db =drizzle(c.env.DB);awaitseed(db);return c.json({ ok:true});});
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
