SaaS-blueprint

Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.

Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.

Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.

Creates an llms.txt file from scratch based on repository structure. Use when configuring LLM discovery files. For updating existing configurations, see update-llms.

Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.

Structured validation framework that scores product ideas. Use when evaluating problem severity, willingness-to-pay, or founder-market fit. For market intelligence, see market-research.

Deep web research skill using Firecrawl MCP. Use when estimating market size (TAM/SAM/SOM), analyzing trends, or scraping competitors. For competitor teardowns, see competitor-analysis.

Reference and learning guide for the Model Context Protocol (MCP). Use when implementing clients/servers or debugging connection issues. For server listings, see mcp-server-registry.

Guidance on using and integrating official reference servers. Use when building custom servers or deploying standard configurations. For server listings, see mcp-server-registry.

Instructions for discovery and usage of servers through the official MCP registry. Use when discovering new integrations. For building custom servers, see mcp-reference-servers.

Meta-skill that generates compliant PLAYBOOK.md files following the BRAINIAC template. Use when creating or editing modules in the command center. For general readme creation, see create-readme.

Updates the llms.txt file to reflect changes in documentation. Use when editing repository details or specifications. For creating from scratch, see create-llms.

Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the `changelog` skill calls for a release.

Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans ./ directory files and creates a README.md file for the project. Only used when creating a new repository. or when the README.md file is missing.