Claude
Cursor
Skill
config-placement
Where to put a new instruction in AI-assistant configuration (always-loaded root file, path-scoped rule, directory-level context file, skill, agent) and how to review a rule or skill. Load when adding or reviewing a rule, skill, agent or context file.
Virus-scanned
Reviewed automatically before listing.
Download
goldziher-ai-rulez-internal_builtins_universal_ai-governance_skills_config-placement-ca967ad.zip · 0 KB
Install
skills CLI
npx skills add https://github.com/Goldziher/ai-rulez/tree/main/internal/builtins/universal/ai-governance/skills/config-placement
Claude Code
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install goldziher-ai-rulez@llmmart
Git
git clone https://github.com/Goldziher/ai-rulez.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole goldziher/ai-rulez collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Placement order
- Always needed and short: the root context file.
- Tied to files, stable and under about 50 lines: a path-scoped rule in the deepest directory that covers all its globs.
- Knowledge about one directory: that directory's context file.
- A procedure or reference: a skill next to its code.
- Isolation or restricted tools: an agent.
Rules of thumb
- One home per fact. Link to it, do not copy it.
- A rule covers one topic and is imperative and checkable.
- Check that every glob matches a tracked file and that every path, command and flag the text names exists.
- Reviewers that run in CI often do not read path-scoped rules, so repeat a review-critical convention as a short block in the context file of its area.
- Never put secrets or customer data in any of these files.
Files (ai-rulez)
-
SKILL.md 1.1 KB
--- name: config-placement description: "Where to put a new instruction in AI-assistant configuration (always-loaded root file, path-scoped rule, directory-level context file, skill, agent) and how to review a rule or skill. Load when adding or reviewing a rule, skill, agent or context file." --- ## Placement order - Always needed and short: the root context file. - Tied to files, stable and under about 50 lines: a path-scoped rule in the deepest directory that covers all its globs. - Knowledge about one directory: that directory's context file. - A procedure or reference: a skill next to its code. - Isolation or restricted tools: an agent. ## Rules of thumb - One home per fact. Link to it, do not copy it. - A rule covers one topic and is imperative and checkable. - Check that every glob matches a tracked file and that every path, command and flag the text names exists. - Reviewers that run in CI often do not read path-scoped rules, so repeat a review-critical convention as a short block in the context file of its area. - Never put secrets or customer data in any of these files.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.