Use when recording architectural or implementation decisions in a module/package/area agent/decisions.md file. Use when user mentions record decision, boundary decision, why we chose, decision log, or remember this decision.

Use when running a governed editorial assignment desk from Readian recommendations through candidate selection and source-backed story packs.

Enable feature flag mode - all code changes will be guarded by feature flags for safe rollback. Use when implementing new features that need gradual rollout, A/B testing, or safe rollback capability. Applies the Legacy pattern for large changes, factory/DI switching for medium changes, and simple conditionals for small changes. Use when user mentions feature flag, feature toggle, gradual rollout, safe rollback, or guard with flag.

Use when conducting a thorough Android/KMP PR code review. Preserve mobile review depth by running the appropriate Kotlin baseline review layer first, then add Android/KMP-specific specialists such as UI and UX/accessibility. Produces a structured review with risk register and prioritized action items. Use when user mentions Android review, KMP review, mobile review, or asks to review Android/KMP changes.

Use when reviewing UX correctness and accessibility risks, delegating UI-framework-heavy checks to bill-kmp-code-review-ui. Use when user mentions UX review, accessibility, content description, screen reader, or localization review.

Use when reviewing Kotlin backend/server API boundaries including request validation, serialization, HTTP or RPC contracts, status-code mapping, and backward compatibility. Use when user mentions API contract, request validation, response serialization, status codes, or backward compatibility in Kotlin backend.

Use when reviewing architecture, boundaries, DI scopes, and source-of-truth consistency in Kotlin code. Use when user mentions Kotlin architecture, DI scope, module boundaries, or dependency direction in Kotlin code.

Use when reviewing lifecycle, coroutine, threading, and logic correctness risks in Kotlin code. Use when user mentions coroutine leak, race condition, dispatcher misuse, lifecycle-unsafe collection, or threading bug in Kotlin code.

Use when removing an existing skill or platform skill set and cleaning up agent installs, manifests, and supporting links.

Use when reviewing unit tests in a file, current changes, or a commit to flag low-value, tautological, or coverage-only tests that do not validate real behavior. Use when user mentions check test quality, review tests, tautological tests, weak tests, or coverage-padding.

Fixture quality-check content.