Use when you need information on how to use the OpenAI API.
Use when writing or reviewing code in any project. Use when making naming decisions for variables, constants, functions, or classes. Use when a linter flags naming conventions and you need to decide whether to fix or suppress. Use when fixing TypeScript type errors, lint warnings about types, or running a linter.
Use when completing a coding task and deciding whether documentation needs updating. Use when code changes have been made and you need to check if README, changelog, guides, or other docs should reflect those changes. Use when a project's CLAUDE.md has a Documentation Sync section listing files and triggers. Use after completing any development work to update release notes and changelogs. Use when offering to cut a new version of a project.
Reserved namespace for the broker DM/inbox CLI's shared reference docs (`docs/critical-rules.md`, `docs/signals.md`, `docs/authority.md`, etc.). All broker workflows are slash commands — `/skill-cefailures:broker:setup`, `:mode`, `:send`, `:read`, `:doctor`. Do not auto-load this skill on mentions of broker, inbox, DM, identity, or collaboration.
Use when authoring or updating user-capability documentation (`capabilities.md` files) co-located with route folders, screen components, feature folders, or API endpoints. Use when planning, brainstorming, or specifying any user-facing feature change. Use when reviewing whether a `capabilities.md` is in sync with the code it describes.
Use when working with elkjs for automatic graph layout, configuring ELK layout algorithms, building the ELK JSON graph format, or troubleshooting elkjs layout issues in a JavaScript/TypeScript codebase.
Use when writing, reviewing, or building software involving IEEE style — covers editorial style, reference/citation formatting, mathematical notation, and TypeBox schema derivation for IEEE reference types.
Use when setting up Knex configuration, installing Knex/drivers, customizing connection behavior (pooling, dynamic connections, hooks), or interpreting Knex-generated SQL for queries and schema across different SQL dialects.