brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
development-workflow
Use when starting work on features, bugs, or significant changes requiring multiple commits and coordination of design, implementation, testing, and documentation
go-style-guide
Google Go Style Guide for writing clear, idiomatic, and maintainable Go code. Use this skill when writing, reviewing, or refactoring Go code to ensure adherence to Google's best practices. Triggers on tasks involving Go packages, functions, error handling, naming, or performance optimization.
issue-management
Use when tasked with working on an issue from an issues/ directory, especially when asked to "work on an issue", "work on the next issue", or "continue working"
product-vision-document
Use when creating product vision documents, product strategy docs, or communicating product ideas to non-technical stakeholders like investors, executives, or cross-functional teams
technical-design-document
Use when designing complex technical features requiring cross-team coordination, system architecture decisions, data model changes, API definitions, or when stakeholders need comprehensive technical documentation before implementation
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
ticket-breakdown
Use when asked to break down a ticket or feature specification into smaller implementable issues for independent completion by agents
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment