What problem does it solve? Adding license-based feature gating to an application requires knowing the correct SDK assertion types, feature kinds, and enforcement patterns, and guessing these leads to broken access checks or silently swallowed entitlement errors. This Skill guides the implementation of Monaiq feature gates, access checks, rate-limit assertions, and consumption recording using authoritative tool guidance instead of reverse-engineering SDK internals. ## Core Features & Use Cases - Feature-Type-Aware Implementation: Distinguishes Access features (binary allowed/denied gates) from RateLimit features (retrieve, record consumption, assert) and applies the correct assertion pattern for each. - Checkpointed Workflow: Enforces hard checkpoints before business-logic edits, validates builds across allowed, denied, expired, and over-limit paths, and records progress in a journal. - Locked Feature Experience Contract: Keeps premium capabilities visible with distinct locked, expired, over-limit, and misconfigured states, each with appropriate user recovery actions. - Use Case: A developer wants to gate a premium export feature behind a license check in a React app. The Skill discovers the feature in the catalog, fetches platform API guidance, plans the gate, obtains checkpoint approval, implements the check, and verifies the build. ## Quick Start Ask the assistant to add a license feature gate for a specific feature key in your SDK-integrated .NET or React application.
