kata-make-sync-cursor

Regenerate the .cursor directory from Ahrena sources via make or Python sync-cursor.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates drift and stale AI prompt artifacts by letting you regenerate the project’s .cursor/ content from the source of truth in .ahrena/framework and .ahrena/artifacts.

Core Features & Use Cases

  • Deterministic regeneration: Ensures .cursor/ is rebuilt using the Makefile target sync-cursor or the equivalent .ahrena/update.py sync-cursor workflow.
  • Environment validation: Confirms required Ahrena files/directives exist (or instructs you to install/bootstrapping first) so regeneration runs in the expected context.
  • Terminal-aware execution: Selects the right terminal behavior based on .ahrena/.directives (or OS inference) to avoid inconsistent command execution.

Use case: after updating Ahrena inputs (framework/artifacts) you need your editor/runtime prompt setup to match the latest project state without manually copying files.

Quick Start

Run the sync-cursor target for this repository from the project root so .cursor/ is regenerated from .ahrena/framework and .ahrena/artifacts, using make sync-cursor when available or python .ahrena/update.py --target . --sync-cursor otherwise.

Frequently Asked Questions about kata-make-sync-cursor

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

FAQPage Schema
How do I regenerate .cursor prompt files to prevent editor configuration drift?

To regenerate .cursor prompts and prevent configuration drift, run the sync-cursor target from the project root, which rebuilds the .cursor directory from Ahrena framework and artifact sources.

What is the best way to keep .cursor directory files in sync after framework updates?

Keeping .cursor directory files in sync after framework updates requires executing the sync-cursor target, which deterministically rebuilds editor prompts using the Makefile target or the equivalent update.py sync-cursor workflow.

Do I need Ahrena files to run the sync-cursor workflow?

Yes, running the sync-cursor workflow requires Ahrena files and directives to exist in the repository, as the environment validation confirms these sources are present before regenerating the .cursor directory.

How does the sync-cursor execution path detect terminal directives?

The sync-cursor execution path detects terminal directives by reading .ahrena/.directives, selecting the correct command execution behavior between make sync-cursor or python .ahrena/update.py to avoid inconsistent terminal execution.

Why does my .cursor directory contain outdated prompt artifacts after updating Ahrena inputs?

Outdated prompt artifacts in the .cursor directory appear after updating Ahrena inputs because the directory must be rebuilt from .ahrena/framework and .ahrena/artifacts using the sync-cursor target to match the latest project state.

Can I use make sync-cursor instead of python .ahrena/update.py to rebuild editor prompts?

Yes, you can use make sync-cursor to rebuild editor prompts, as the workflow selects the make-driven execution path when available or falls back to python .ahrena/update.py with the sync-cursor flag otherwise.