Loading...
Loading...
Found 2,893 Skills
Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.
Use when revising existing wiki pages because knowledge has changed, a new piece of information updates or contradicts existing content, or the user wants to directly edit wiki content with LLM assistance.
Runbook Generator
Prepare code for a pull request by orchestrating sync, format, lint, test, review, and doc updates. Use when user says 'create a PR', 'prepare pull request', 'get ready for PR', 'validate my changes', 'prepare for review', 'pre-merge checks', or 'is this ready to merge'. Do NOT use for only running tests, only reviewing (use review-diff), only syncing with main (use merge-main), or actually opening the PR on GitHub — this skill stops at "ready."
Design complete API contracts in OpenAPI 3.0/3.1 YAML with endpoints, schemas, security, pagination, error handling, and RFC 7807 problem details. Use when asking to design an API, create an OpenAPI spec, define API endpoints, write API contracts, or generate a Swagger specification.
Novel Research Skill. Used for searching and organizing writing materials, genre references, real-world research, professional details, historical and geographical information, technical data, case inspirations, visual references, and market observations; stored in research.yaml, records, or notes. Activated when users request information searching, material collection, latest updates, research verification, background authenticity, modifying research notes, or saving sources.
Patterns and conventions for creating a good PR
Add an implementation requirement to the ***implementation reqs*** section of a ***plain spec file. Use when the user wants to add non-functional requirements like technology choices, architectural constraints, coding standards, data formats, error handling strategies, or any HOW-to-build guidance to a .plain file.
agent-team: Cancel a non-terminal task with a reason.
bklit-ui monorepo contributors only — ship a chart or component from playground prototype to production in packages/ui with docs and registry.
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Vendor-neutral skill to draft a blameless incident postmortem from structured incident inputs (timeline, impact, contributing factors) and produce an actionable report.