orange-lab

Use when creating or editing TypeScript code in the orange-lab repo — stacks, components (`stacks/<module>/components/`, `components/`), or the `@orangelab/pulumi` library (`packages/pulumi/src/`). Covers code style, component patterns, Pulumi config conventions, and secrets handling. Not needed for markdown/documentation-only changes.

Use when the user asks to create, update, or revise documentation for an application component — typically a `<app>.md` file under `stacks/<module>/components/<app>/`. Trigger on phrases like "document `<app>`", "write `<app>`.md", "update `<app>` docs", "add docs for `<app>`", "backfill `<app>` links". The components folder is a Pulumi convention; users think of these as applications, so the skill is named accordingly.

Use when the user asks to create, update, or revise documentation for a stack module — typically the `README.md` at `stacks/<module>/README.md`. Trigger on phrases like "document `<module>` stack", "update `<module>` README", "write stack README", "add module docs". Distinct from `document-app` (per-component docs); a module README is the entry point that lists and links its components.

Use when the user asks to update, deploy, or apply changes to all Pulumi stacks (core and all stacks in the stacks/ folder). Trigger on phrases like "update all stacks", "deploy all stacks", "pulumi up all", or "apply all stacks".

Use ONLY when the user asks to create a new release, draft release, or release notes for the orange-lab project. Trigger on phrases like "create release", "draft release notes", or "release 0.6.0".