kata-create-codex

Generate structured Codex reference manuals with taxonomy and i18n compliance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of creating consistent, reusable reference manuals (“Codex” artifacts) by turning existing directives, templates, and quality criteria into a structured, maintainable documentation file.

Core Features & Use Cases

  • Guided Codex authoring: Produces a Codex with required sections (overview, context, principles, patterns, decisions, constraints, glossary, references) based on a codex sample template.
  • Taxonomy-safe placement: Ensures the artifact is saved into the correct clade/subclade codex path using the prescribed naming and kebab-case conventions.
  • Multi-language rollout: Creates translations for all required languages via the specified translation workflow to keep documentation coverage aligned.
  • Quality and duplication guardrails: Requires consulting codex directives and existing codex artifacts to avoid overlap and enforce update-trigger inclusion.

Quick Start

Ask an AI to create a new Codex for your domain by reading .ahrena/.directives, checking codex-codex and existing codex files, using templates/codex-sample.md as the base, saving it under the correct framework taxonomy path, and translating it into all languages listed in language.i18n.

Frequently Asked Questions about kata-create-codex

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

FAQPage Schema
How do I generate reference manuals across multiple languages from existing directives?

To generate reference manuals across multiple languages, this Skill reads your existing directives and templates to produce a structured Codex artifact, then applies a specified translation workflow to create equivalents for all required i18n languages.

What is the best way to ensure my documentation follows the correct taxonomy and naming conventions?

To ensure documentation follows the correct taxonomy and naming conventions, this Skill enforces prefix and kebab-case rules, saving your generated Codex artifact directly into the correct clade or subclade path within your framework.

How do I structure a Codex reference manual to avoid content duplication?

To structure a Codex reference manual and avoid content duplication, this Skill consults existing codex directives and artifacts to enforce quality guardrails, validating scope, glossary, and duplication constraints before finalizing the output.

Can I use a template-driven approach to create framework documentation with required sections?

Yes, you can use a template-driven approach to create framework documentation; this Skill uses a codex sample template to produce required sections including overview, context, principles, patterns, decisions, constraints, glossary, and references.

Do I need specific directory configurations to create and save Codex artifacts?

Yes, you need specific directory configurations to create and save Codex artifacts, as the Skill reads directives from a hidden configuration directory and saves the output Markdown structure under a prescribed framework taxonomy path.

Why does my generated documentation need an update trigger?

Your generated documentation needs an update trigger because quality guardrails require its inclusion to maintain ongoing consistency, define when the manual should be revised, and validate scope against existing artifacts.