kilo-rule-editor

Create, update, and migrate Kilo custom rules across kilo.jsonc and .kilo/rules.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/cc01cc/cmtx-project --skill kilo-rule-editor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kilo-rule-editor
Source: https://github.com/cc01cc/cmtx-project/tree/main/.github/skills/kilo-rule-editor
Command: npx skills add https://github.com/cc01cc/cmtx-project --skill kilo-rule-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create, update, and refactor Kilo custom rules via kilo.jsonc and .kilo/rules. Use when the user asks to configure rules, define global rules, manage rule precedence, migrate legacy .kilocoderules files, troubleshoot rule behavior, or improve rule clarity and enforceability.

Core Features & Use Cases

  • Create & refactor rules: structure Kilo rules in kilo.jsonc and .kilo/rules for project and global scopes.
  • Migrate legacy rules: move from .kilocoderules to the modern layout with optional folder-based organization.
  • Enforce precedence & validation: resolve conflicts and ensure rules load in the intended order.
  • Documentation-aware workflow: fetch live Kilo docs before creating or updating rules to stay in sync.

Quick Start

Fetch the latest official Kilo documentation and begin by outlining your target scope, then generate or migrate rule files in kilo.jsonc or .kilo/rules to align with the current guidance.

Frequently Asked Questions about kilo-rule-editor

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

FAQPage Schema
How do I migrate legacy .kilocoderules files to the modern Kilo layout?

Migrate .kilocoderules files by moving them into kilo.jsonc or .kilo/rules with optional folder-based organization. This updates your configuration to the modern layout while preserving existing rule definitions.

How do I manage rule precedence between kilo.jsonc and .kilo/rules?

Rule precedence is managed by resolving conflicts between kilo.jsonc and .kilo/rules to ensure rules load in the intended order. Validation checks locations, scope, and syntax before applying changes.

What is the best way to create custom Kilo rules for global and per-project scopes?

Creating custom Kilo rules involves structuring definitions in kilo.jsonc and .kilo/rules for project and global scopes. The workflow fetches live Kilo documentation first to ensure rules align with current standards.

Can I use JSONC for Kilo rules configuration and validation?

Yes, kilo.jsonc is the standard format for Kilo configuration. The system validates JSONC syntax, checks locations and scope, and enforces rule authoring standards before applying any updates.

Why are my Kilo custom rules not loading in the correct order?

Kilo rules may not load correctly due to precedence conflicts between kilo.jsonc and .kilo/rules. Validation resolves these conflicts and ensures syntax and location checks pass before applying changes.

Do I need to fetch official documentation before updating Kilo rules?

Fetching live Kilo documentation before creating or updating rules is required to stay in sync with current guidance. This documentation-aware workflow ensures your rule authoring standards are up to date.