agent-kit-source

Guides editing, building, and laying out the agent-kit rules package source.

1|Updated Jan 14, 2024
One-click install
npx skills add https://github.com/Eyhenij/rt-tools --skill agent-kit-source-eyhenij
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-kit-source
Source: https://github.com/Eyhenij/rt-tools/tree/main/.claude/skills/agent-kit-source
Command: npx skills add https://github.com/Eyhenij/rt-tools --skill agent-kit-source-eyhenij

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing the agent-kit rules package source is error-prone: edits only reach consumer trees through a build, stale build caches silently serve outdated resources, and guards refuse edits to laid-out copies or non-empty overrides. This Skill encodes the correct edit-build-layout order and the triage workflow for proposals arriving from consumer trees. ## Core Features & Use Cases - Edit-build-layout workflow: Enforces the single correct order (edit, build, lay out) via pnpm run agent-kit:sync and pnpm run agent-kit:check, including clean-build recovery from stale Nx caches. - Guard awareness: Explains the two refusal guards — one blocking edits of files carrying the layout header, one blocking writes over non-empty overrides — and how to resolve each. - Proposal triage: Covers sorting intake proposals from consumer trees using the /agent-kit-digest and /rules-review commands plus the cargo-triage rule. - Use Case: A maintainer edits a rule resource in the package source, hits a refusal from the layout-header guard, and uses this Skill to learn the edit belongs in the package source or an override, then rebuilds cleanly and lays out. ## Quick Start Ask the agent to edit a rule resource in the agent-kit package source and then run the sync command to build and lay it out.

Frequently Asked Questions about agent-kit-source

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

FAQPage Schema
How do I edit a rule in the agent-kit package source?

Edit the resource in the package source tree, then run pnpm run agent-kit:sync to rebuild the package and lay it out. Edits never reach consumer trees directly; the launch line reads only the built output, so the order is always edit, build, lay out.

Why does the agent-kit audit report a divergence after my edit?

The divergence usually comes from a stale build cache: the builder considers the input unchanged and serves yesterday's output. Remove the dist/agent-kit directory and rebuild with pnpm exec nx build @rt-tools/agent-kit --skip-nx-cache to fix it.

What is the difference between agent-kit:sync and agent-kit:check?

Both commands rebuild the package first. agent-kit:sync builds and lays out the resources into the tree, while agent-kit:check builds, writes nothing, and refuses with an error if it finds any divergence between source and layout.

Why was my edit to a laid-out file refused?

A guard refuses edits to files carrying the layout header because the next layout would overwrite the copy. It directs you to edit the package source instead, or create an override for tree-specific content; deleting the copy is allowed since layout restores it.

When should a resource stay tree-local instead of joining the package?

A resource stays tree-local when the consumer lacks what it speaks of or has nobody to call it. If either question answers no, it remains the tree's own resource with the same shape and law, enforced by a boundary check in the push gate.