kata-create-kata

Generate standardized Kata Markdown artifacts with taxonomy paths and translations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error-prone process of writing a new repeatable “Kata” procedure by standardizing structure, taxonomy placement, and language translations so teams can scale contributions safely.

Core Features & Use Cases

  • Creates Katas from a template: Produces a complete Markdown artifact using the kata sample as the baseline structure.
  • Enforces quality and constraints: Uses internal directives and codex checks to ensure atomic workflow steps, required sections, and a final validation checklist.
  • Applies consistent taxonomy paths: Saves the Kata into the correct framework/{lang}/{clade}/{subclade}/katas/ location using the kata- prefix and kebab-case naming.
  • Generates translations for all required languages: Produces the default-language Kata and then translates it into each mandatory language in language.i18n.

Quick Start

Ask the AI to create a new Kata named "process-payment" following the kata-create-kata workflow, using the repository directives, the kata-sample template, and generating translations for all languages in language.i18n.

Frequently Asked Questions about kata-create-kata

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

FAQPage Schema
How do I generate a new procedural Markdown document with i18n translations?▼

To generate a new procedural Markdown document with i18n translations, use a template-based generation process that creates a default-language artifact and then produces equivalent files for all configured language.i18n entries.

What is the correct taxonomy path for saving standardized procedure entries?▼

The correct taxonomy path for saving standardized procedure entries is framework/{lang}/{clade}/{subclade}/katas/, enforcing a kata- prefix and kebab-case naming for consistent repository organization.

How do I ensure atomic workflow steps and required sections when authoring procedures?▼

To ensure atomic workflow steps and required sections when authoring procedures, apply internal repository directives and codex quality criteria that validate the Markdown structure against a baseline template.

Can I use this template-based generation to scale team contributions safely?▼

Yes, template-based generation scales team contributions safely by standardizing structure, taxonomy placement, and language translations, which eliminates manual errors in procedural authoring.

Do I need to read repository directives before creating a new Kata procedure?▼

Yes, you need to read repository directives from .ahrena/.directives, codex-katas, and templates/kata-sample.md before creating a new Kata procedure to ensure compliance with enforced constraints.