kata-push-to-framework

Promote markdown artifacts into a framework repository with validated lang/clade/subclade/pilar layout.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines the repetitive work of taking newly written project documentation artifacts and promoting them into a shared framework structure, including ensuring required i18n language variants exist.

Core Features & Use Cases

  • Artifact promotion with structure validation: Scans .md files under a configured project artifacts root, validates expected lang/clade/subclade/pilar layout, and prepares exact destination paths in the framework.
  • Automated i18n completion: Copies missing language files by invoking translation from the default-language artifact, ensuring all required languages are present at the destination.
  • Local or remote publishing workflow: Supports local filesystem copying and GitHub-MCP-only remote synchronization that creates a branch, commits, and opens a PR in the framework repository.
  • Optional cleanup: Can remove promoted artifacts from the project after a successful local copy or remote PR creation.

Quick Start

Ask the AI to run kata-push-to-framework in local mode and promote all markdown artifacts found under the configured artifacts directory into the framework, generating any missing i18n translations for the required languages.

Frequently Asked Questions about kata-push-to-framework

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

FAQPage Schema
How do I promote markdown documentation into a framework repository?

Promoting markdown documentation into a framework repository involves validating a lang/clade/subclade/pilar directory layout and copying files to exact destination paths without content alteration. It supports local filesystem integration or remote synchronization via GitHub MCP tools.

What is the best way to automate i18n translation generation for markdown artifacts?

Automating i18n translation generation for markdown artifacts is handled by copying missing language files from the default-language artifact. This ensures all required language variants exist at the destination framework directory.

Does the artifact promotion workflow support remote GitHub pull requests?

Yes, the artifact promotion workflow supports remote GitHub pull requests using GitHub MCP tools. It creates a remote branch, commits the validated markdown files, and opens a PR directly in the framework repository.

How do I ensure my directory structure is valid before syncing markdown files to a framework?

To ensure your directory structure is valid before syncing markdown files to a framework, the skill scans .md files and validates the expected lang/clade/subclade/pilar layout. It reads .ahrena/.directives to prepare exact destination paths.

Can I automatically clean up project artifacts after a successful framework promotion?

Yes, you can automatically clean up project artifacts after a successful framework promotion. The skill optionally removes promoted markdown files from the source project following a successful local copy or remote PR creation.