What problem does it solve? As a service grows, inconsistencies creep into API responses, design tokens, error codes, environment configs, and i18n keys, causing client parsing failures, UI drift, and missing translations. This Skill determines which parts of a service require strict consistency versus which can stay flexible, and produces an automated validation framework to enforce the rules. ## Core Features & Use Cases - Strict vs Flexible Classification: Categorizes service areas into must-enforce zones (API response shapes, design tokens, error codes, env config, DB migrations, i18n keys) and flexible zones (internal utilities, comments, test data, log messages). - Consistency Rules Manifest: Produces a consistency-rules.json file declaring enforcement method per area, such as json-schema for APIs, tokens.json for design tokens, enums for error codes, and zod-schema for environment config. - CI Validation Output: Generates automated validation scripts with clear violation error messages that run in CI pipelines. - Use Case: A growing web service starts seeing mismatched API response fields breaking the mobile client. Run this Skill to define a JSON schema per endpoint, wire validation into CI, and block merges that violate the contract. ## Quick Start Ask the assistant to analyze which parts of my service need strict consistency and generate a consistency-rules.json with CI validation for API schemas, design tokens, and env config.