agentsclimarketplace
Sign in

Create rule

Skill mgiovani/cc-arsenal/skills/create-rule

Create a new memory/instruction rule for whatever AI coding tool a project actually uses, a CLAUDE.md entry or .claude/rules/*.md file for Claude Code, an AGENTS.md entry for Codex/Cursor/Copilot/Gemini-CLI-style tools, or a .cursor/rules/*.mdc file for Cursor. Use when the user runs /create-rule or asks to add a project rule, user/personal rule, coding standard, style guide entry, or workflow instruction to memory, AGENTS.md, or CLAUDE.md. Not for creating skills or slash commands (use create-skill). Not for discovering or installing existing third-party skills (use find-skills).From its SKILL.md

Install
npx -y skills add mgiovani/cc-arsenal --skill create-rule

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.5 KB, as published. Nobody here has run it

Create Rule

Generate a new memory rule (a project instruction, coding standard, or workflow guideline) in whatever format the project's AI tooling actually reads.

This creates memory rules, not skills or commands (use create-skill) and not a search for existing skills to install (use find-skills).

Anti-hallucination guidelines

  • Verify existing patterns first: check the actual codebase, don't assume conventions.
  • Base rules on real code found in the project, not invented standards.
  • If no convention exists, ask the user rather than making one up.
  • Check existing CLAUDE.md / AGENTS.md / .claude/rules/*.md / .cursor/rules/*.mdc for conflicts before adding a new rule.
  • Only use paths frontmatter on .claude/rules/*.md (Claude Code) or globs on .cursor/rules/*.mdc (Cursor), never on CLAUDE.md or AGENTS.md, which have no frontmatter.

Steps

  1. Parse arguments: rule name from $1 (or the first word of the arguments), description from the rest: ask the user if either is missing.
  2. Detect the tool convention by checking what's already in the repo:
    • CLAUDE.md or .claude/rules/*.md present → Claude Code.
    • AGENTS.md present (with no Claude-specific files) → Codex/Cursor/Copilot/Gemini-CLI-style tool. This repo's own AGENTS.md + CLAUDE.md pair is a live example of the pattern.
    • .cursor/rules/*.mdc present → Cursor's native format.
    • More than one convention present → ask which the user wants updated (or write to more than one, if the user says so).
    • None present → ask the user which tool/format they use before writing anything.
  3. Decide type and scope for the detected tool (details and templates in the reference):
    • Claude Code: modular .claude/rules/<name>.md for a focused single topic vs. a CLAUDE.md entry for a short cross-cutting instruction; project (.claude/rules/, git-shared) vs. user (~/.claude/rules/, personal): ask if unclear from context; path-specific rules need paths frontmatter.
    • AGENTS.md-style tools: append a new section to the single root AGENTS.md, this format has no per-topic file split or frontmatter.
    • Cursor: .cursor/rules/<name>.mdc with description/globs/alwaysApply frontmatter; scope by directory nesting for path-specific rules.
  4. Write the rule, following the matching template in references/rule-examples.md: imperative language, specific expectations, one topic per file, code examples where useful.

Examples

  • /create-rule api-errors "Standard error handling for API routes" in a Claude Code repo → writes .claude/rules/api-errors.md with paths: src/api/**/*.ts frontmatter and concrete guidelines.
  • /create-rule formatting "2-space indentation, single quotes" in a Claude Code repo, no path scope needed → writes .claude/rules/formatting.md with no frontmatter.
  • /create-rule --user preferences "Prefer functional patterns, async/await over raw promises" → writes ~/.claude/rules/preferences.md (personal, not git-shared).
  • /create-rule testing "Use table-driven tests and no test interdependence" in a repo with only AGENTS.md → appends a ## Testing section to AGENTS.md instead of creating a new file.
  • /create-rule react-components "Function components only, props typed with interfaces" in a Cursor repo → writes .cursor/rules/react-components.mdc with globs: ["**/*.tsx"] frontmatter.

What ships with it: 4 files

13.3 KB alongside SKILL.md

evals/

references/

Gives 0 of the 12 instructions most memory context skills give

Counted across 754 of the 1,056 authors here whose files we hold, read 2026-09-06

  • Preserve existing content structurein 15 of 754, across 9 files
  • Front-load the leading wordin 14 of 754, across 10 files
  • Update existing entries instead of duplicatingin 14 of 754, across 7 files
  • Keep CLAUDE.md under one hundred linesin 14 of 754, across 12 files
  • Read CLAUDE.md at the project rootin 14 of 754
  • Keep each meaning in a single source of truthin 12 of 754, across 8 files
  • Redact sensitive information before committingin 11 of 754, across 4 files
  • Scan for all CLAUDE.md filesin 11 of 754, across 7 files
  • Use frontmatter for metadata on filesin 10 of 754, across 3 files
  • Repeat user interactions 10 timesin 10 of 754, across 4 files
  • Write the CLAUDE.md file into the target folderin 10 of 754, across 8 files
  • Use memlab to process snapshotsin 9 of 754, across 3 files

Said here and by no other author read

  • Verify existing patterns first.
  • Base rules on real code.
  • Ask the user if no convention exists.
  • Use correct frontmatter per tool.
  • Parse arguments for rule name and description.
  • Detect the tool convention.

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,474. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.