skene-cookbook: Cursor rule for Cursor

Cursor Rules for skene-cookbook

Project Context

Repository: skene-cookbook - 764 AI skill library with 36 skill chain recipes Package: @skene/skills-directory v0.2.0 License: MIT Purpose: Pre-built AI skill chains for PLG, sales, customer success, security, and more

Architecture Patterns

Skill Structure (Non-Negotiable)

Every skill MUST follow this exact structure:

skills-library/{domain}/{skill-name}/
├── skill.json          # Metadata (name, description, category, risk_level)
├── instructions.md     # AI agent execution instructions
└── tests/              # Optional: skill-specific tests

Do NOT:

• Create skills outside skills-library/executable/ or skills-library/reference/
• Modify existing skill structure without updating registry
• Add skills without skill.json and instructions.md

Registry Auto-Generation

The registry/ directory is AUTO-GENERATED from skills-library/:

• Never manually edit files in registry/
• Always run npm run verify:metrics after skill changes
• Registry regeneration syncs badges and counts across README.md, METRICS.md, docs/directory.md

Risk Level Classification

Skills are classified by risk level (defined in skill.json):

• Low - Read-only operations, no external dependencies
• Medium - Write operations, requires configuration
• High - External API calls, requires credentials
• Critical - System-level operations, requires manual review

Rule: When creating a skill that makes external API calls, uses credentials, or modifies data, always set risk_level: "High" or "Critical".

Naming Conventions

Skill IDs

• Format: {domain}_{action}_{target} (e.g., sales_analyze_pipeline)
• Use snake_case, all lowercase
• Be descriptive but concise (3-5 words max)

File Naming

• Skill directories: kebab-case (e.g., analyze-customer-health/)
• Python files: snake_case (e.g., analyze_skills.py)
• JavaScript files: kebab-case (e.g., skills-directory.js)
• Documentation: SCREAMING_SNAKE_CASE for top-level (e.g., AGENTS.md), kebab-case for nested