Skip to content
Back to skills

Rules Manager

ASecurity

Create, edit, and maintain AGENTS.md and .agents/rules/. Use when adding, modifying, restructuring, or optimizing project rules, conventions, or constraints.

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 5, 2026
devops

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add twikus/claude-configuration --skill rules-manager --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rules Manager?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Rules Manager
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/twikus-rules-manager/badge)](https://www.skillsdirectory.com/skills/twikus-rules-manager)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: rules-manager
description: Create, edit, and maintain AGENTS.md and .agents/rules/. Use when adding, modifying, restructuring, or optimizing project rules, conventions, or constraints.
argument-hint: "[init | add <rule-name> | edit | optimize | task description]"
disable-model-invocation: true
user-invocable: true
---

Manage the two-tier rule system: the always-loaded index plus modular files. Every modular file must be linked from the index or agents will not find it.

Open [agents-vs-claude.md](references/agents-vs-claude.md) before choosing `AGENTS.md` + `.agents/rules/` versus `CLAUDE.md` + `.claude/rules/`, path-scoped `paths:` frontmatter, or dual-format setup. Run the same workflows against the chosen pair. Open [examples.md](references/examples.md) before writing a new rule file or index skeleton.

Never overwrite existing files without asking. Never write a rule file without confirming its content. Default new rules to a modular file (20–60 lines); put 1–2 line constraints in Universal Rules. When the user names index content (stack, commands, universal rules), edit that file in place. Write specific prohibitions. Do not add generic best practices, linter-enforced rules, or facts the agent can read from the code.

`init`: read package manifests; if the index or rules directory exists, ask before writing; create a <40-line index with an empty Rules section and the rules directory.

`add <name>`: slugify the name; `init` if no index; ask what it enforces and when it applies; write the modular file; add one index bullet whose path matches the file.

`edit`: change only the named index section; keep every modular-file link intact.

`optimize`: inventory index vs files (flag orphans and broken links); strip linter-enforced, generic, verbose, and code-derivable rules; compress to bullets; show the diff and wait. Targets: index <80 lines, each rule <60.

A free-form request is `add` with a derived name. Ask 1–2 scope questions if the rule is unclear.

Files in this skill

  • SKILL.md7.9 KB
  • agents/openai.yaml341 B
  • assets/codex-icon.svg577 B
  • references/agents-vs-claude.md2.3 KB
  • references/examples.md3.1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…