consistency-guard

Generates a JSON-schema-based framework that enforces consistency across APIs, design tokens, and configs.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill consistency-guard-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consistency-guard
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/consistency-guard
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill consistency-guard-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about consistency-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce API response consistency across a service?

Define a JSON Schema per API response and validate payloads against it in CI. This Skill generates a consistency-rules.json that maps api_responses to a json-schema method with a schemas directory, so contract violations fail the build before deployment.

What parts of a codebase need strict consistency vs flexibility?

Strict consistency is required for API response shapes, design tokens, error codes, environment config, DB migrations, and i18n keys because breakage propagates to clients and users. Internal utility signatures, comments, test data, and log message text can stay flexible.

How do I keep design tokens consistent between design and code?

Maintain a single tokens.json source of truth and run a transformation pipeline that generates platform-specific outputs. The consistency framework marks design_tokens as enforced via tokens.json so drift between design handoff and UI code is caught automatically.

Can I validate environment variables at application startup?

Yes, use a schema validation library such as zod to check env config on boot, as declared in the env_config rule. This prevents environment-specific behavior differences from surfacing only at runtime in production.

When should consistency rules not be enforced?

Avoid enforcing consistency on internal refactoring surfaces like utility function signatures, comment formats, and test fixtures, where rigidity slows development. Over-enforcement reduces developer autonomy without improving correctness.