kata-create-cry

Generate recurring cry command artifacts that delegate to existing katas.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines creating new recurring “Cry” commands that correctly delegate to an existing “Kata” and fit the repository’s naming and taxonomy rules.

Core Features & Use Cases

  • Enforces Cry-to-Kata delegation: every Cry must reference at least one Kata to avoid weak or redundant commands.
  • Generates complete Cry artifacts: produces structured Markdown with invocation syntax, parameters, prompt template, examples, constraints, and a Cry vs Kata comparison.
  • Supports multilingual outputs: creates the default-language Cry and generates translations across the required i18n languages.
  • Avoids duplication and preserves consistency: checks directives, internal codex quality criteria, existing Cries, and ensures the associated Kata exists or is flagged.

Quick Start

Tell the AI to create a new cry command named “invoice-status” that takes a required customer name and includes an optional freshness window, then save the resulting Cry artifact in the correct framework taxonomy and translate it to all configured languages.

Frequently Asked Questions about kata-create-cry

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

FAQPage Schema
How do I generate recurring command artifacts that delegate to existing katas?

Generate recurring command artifacts by reading repository directives, verifying kata availability, and writing structured markdown files with invocation syntax, parameters, and prompt templates to the correct taxonomy path.

What is the best way to automate documentation generation for multilingual command templates?

Automate multilingual documentation generation by producing the default-language command artifact and saving translations across required i18n languages under the framework directory structure.

How do I create a command with required parameters and save it to the correct taxonomy path?

Create a command by specifying its name and parameters, checking for existing duplicates, then writing the markdown file to the correct framework taxonomy path and generating configured translations.

Does command generation require an existing kata to function correctly?

Yes, command generation requires an existing kata. Every generated command must reference at least one kata to avoid weak or redundant commands, flagging the associated kata if it does not exist.

Why does my generated command artifact fail repository consistency checks?

Command artifacts fail repository consistency checks when they do not adhere to codex quality criteria, duplicate existing commands, or lack proper delegation to an available kata.

Can I use prompt templates for i18n localization in command design workflows?

Yes, you can use prompt templates for i18n localization. The command generation workflow produces structured markdown and saves translations across configured languages within the framework directory.