kata-create-lexis

Draft unbreakable Lexis laws with codex-lexis quality criteria and translations.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-create-lexis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-create-lexis
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-create-lexis
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-create-lexis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you define new Lexis (unbreakable laws) in a consistent taxonomy so they are clear, testable, and never admit exceptions.

Core Features & Use Cases

  • Directive-driven structure: Builds each Lexis using repository directives (default language, mandatory i18n languages, naming/prefixes, and addressing pattern).
  • Codex-based law quality: Forces you to follow codex-lexis criteria (clarity, imperatives like MUST/MUST NOT, unambiguity, testability, necessity, and immutability).
  • Taxonomy-safe writing: Prevents duplication or contradiction by checking existing Lexis and saving to the correct framework/{lang}/{clade}/{subclade}/lexis/ path in kebab-case.
  • Always-valid automated checks: Requires an explicit automated validation tool, timing, and metric so the Lexis can be verified.
  • Multilingual propagation: Creates translations for all mandatory language.i18n values using the kata-translate workflow (or direct translation guidance when qualified).

Quick Start

Ask the AI to draft a new Lexis named "avoid-duplicate-reads" for the correct framework clade/subclade, using templates and codex quality rules, and to generate validated translations for all required languages.

Frequently Asked Questions about kata-create-lexis

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

FAQPage Schema
How do I author a new policy rule so it has no exceptions and is testable?▼

Authoring an unbreakable Lexis requires drafting a clear imperative law using MUST or MUST NOT statements, ensuring it includes purpose, coverage, violation consequences, concrete examples, and automated validation metrics.

How do I prevent duplication when adding a new rule to a taxonomy?▼

To prevent duplication in a taxonomy, check existing Lexis entries before saving the new rule to the correct framework clade and subclade path in kebab-case, ensuring no contradictions with current directives.

What is required to fully validate a new compliance directive?▼

Validating a compliance directive requires specifying an automated validation tool, timing, and metric so the Lexis can be continuously verified, alongside meeting codex-lexis criteria for clarity, testability, and immutability.

How do I create multilingual translations for a new knowledge base law?▼

Creating multilingual translations for a knowledge base law involves generating translations for all mandatory language.i18n values using the kata-translate workflow, ensuring the taxonomy-driven Lexis remains aligned across languages.

Does policy authoring for a knowledge base support multilingual i18n requirements?▼

Yes, policy authoring supports multilingual i18n requirements by producing validated translations for all mandatory language.i18n values, ensuring the unbreakable Lexis is correctly propagated across different languages.

When should I not use a strict imperative format for taxonomy authoring?▼

You should not use a strict imperative format for taxonomy authoring if the rule inherently requires exceptions, as unbreakable Lexis demands immutability, unambiguity, and absolute necessity without admitting exceptions.