agentleFS
Sign inStart free
0mlkrizzz655335v0mlkrizzz655335v/claude-skills-zh/skills/ecosystem/create-rule/SKILL.md

create-rule

Skill2 starsChanged 5 months agoMITView on GitHub

创建持久化项目规则。写 AGENTS.md 等项目级长期指导。

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create or update persistent instructions in the format the user's actual agent or editor reads.

    line 9
  2. Distinctive:

    After writing, verify syntax where applicable, intended directory scope, and the content diff.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create Persistent Guidance

Create or update persistent instructions in the format the user's actual agent or editor reads. Honor an explicitly named file such as AGENTS.md or an existing .cursor/rules/*.mdc rule; do not silently switch formats.

For Codex project guidance, inspect applicable AGENTS.md files and use the appropriate repository or nested directory scope. For personal guidance, resolve the active Codex configuration root and instruction mechanism from the current runtime/documentation. Do not create a user-level policy from an ordinary one-off task.

For an editor that supports .cursor/rules/*.mdc, read rule format. Use that schema only for the matching runtime. Existing files and authoritative product documentation determine discovery and precedence.

Infer purpose, scope, and file patterns from the request and repository. Ask only when a meaningful ambiguity remains. Preserve unrelated instructions, user-provided exact wording, and supported metadata. Keep the rule focused on useful project facts and decisions; do not add generic workflow, mandatory examples, or arbitrary line limits.

After writing, verify syntax where applicable, intended directory scope, and the content diff. Distinguish a saved rule from a confirmed runtime reload.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free