From f83b0add5890cfd04dcceaa4afda1611d2927ee3 Mon Sep 17 00:00:00 2001 From: Julian lechner Date: Thu, 1 Oct 2026 11:02:07 +0200 Subject: [PATCH] docs(skills): describe flat Claude skill layout Co-Authored-By: Claude Opus 5.5 --- docs/skills.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/skills.md b/docs/skills.md index b717d92..f95e152 100644 --- a/docs/skills.md +++ b/docs/skills.md @@ -20,7 +20,7 @@ Each skill defines a focused workflow with the investigation, decision points, a The single catalog in `shared/skills/` includes development skills and focused skills for writing, images, content and site structure, positioning, psychology, and conversion. Builds include every retained skill for both clients. Updating a managed installation backs up and removes unchanged setup-owned skills deleted from the catalog; local changes are backed up and retained. -Claude's generated package additionally has `skills/rules/`: one skill per focused rule file or directory in +Claude discovers only `skills//SKILL.md`, so its generated package flattens the categorized catalog to one directory per skill name, together with the skill's `references/`; the build fails on duplicate names or a `name` that differs from its directory. Claude's package additionally has a `rules-*` skill for each focused rule file or directory in `shared/rules/`. The rule-to-skill loading conditions live in `shared/global-instructions.md`, so full rule text loads only when Claude invokes a matching skill instead of sitting permanently in context. Codex reads the matching rule files directly. Both clients embed the general rules in their global instructions.