docs: describe shared rule manifest

README.md

@@ -267,7 +267,7 @@ workspace-scoped and use automatic review for eligible escalation requests. Ever
 
 Claude Code receives the equivalent global instructions, agents, hooks, and `settings.json`. General rules are embedded
 once in `CLAUDE.md` (and in Codex's `AGENTS.md`); every technology- or
-situation-specific rule (`adapters/claude/rule-skills.tsv`) is generated as a skill under `skills/rules/` instead, so
+situation-specific rule (`adapters/rule-skills.tsv`) is generated as a skill under `skills/rules/` instead, so
 only its name and description are permanently visible and the full rule text loads only when Claude invokes it. Its
 generated settings use the supported automatic permission mode where available.
 
@@ -296,7 +296,7 @@ turning yellow at 60% and red at 85%; its status-line input does not expose the
 ### Add a rule
 
 Create a focused Markdown file in `shared/rules/`. For a rule that applies only to a language, framework, tool, or
-change area, add one row to `adapters/claude/rule-skills.tsv`. The build uses that manifest to generate both Claude's
+change area, add one row to `adapters/rule-skills.tsv`. The build uses that manifest to generate both Claude's
 rule skill and Codex's rule-loading condition. Put always-applicable guidance in `general.md`, which the build embeds
 for both clients; a new rule file is not automatically embedded.
 

docs/configuration.md

@@ -2,7 +2,7 @@
 
 Codex receives a generated global `AGENTS.md`, agent TOML files, skills, rule files, and a `config.toml` adapter. It keeps workspace sandboxing, automatic approval review, `agents.enabled = true`, `agents.max_concurrent_threads_per_session = 5`, and `agents.max_depth = 1`. Claude Code receives a generated global `CLAUDE.md`, agent Markdown files, skills, and `settings.json` with `auto` permissions, explicit `Agent` permission, and five-operation concurrency. Installation resolves user paths at runtime; the repository contains no machine-specific paths.
 
-Both clients embed `shared/rules/general.md` in their global instructions. Codex loads applicable focused rules from `rules/`; Claude generates them as skills from `adapters/claude/rule-skills.tsv`. Angular, WPF, and UI/UX rules have small entry points with references loaded by topic. `security.md` is the baseline for programming tasks; focused security rules cover authentication, web, API, data, files, network, cryptography, and supply-chain work.
+Both clients embed `shared/rules/general.md` in their global instructions. Codex loads applicable focused rules from `rules/`; Claude generates them as skills from the shared `adapters/rule-skills.tsv` manifest. Angular, WPF, and UI/UX rules have small entry points with references loaded by topic. `security.md` is the baseline for programming tasks; focused security rules cover authentication, web, API, data, files, network, cryptography, and supply-chain work.
 
 The Codex adapter sets `agents.max_depth = 1` and does not enable `features.multi_agent_v2`. Shared instructions also prohibit subagents from creating further subagents. Agent roles are optional, not stages that every task must run.
 

docs/skills.md

@@ -15,7 +15,7 @@ The current structure is organized by purpose:
 The files intentionally define only a small baseline. Detailed personal workflows and standards can be added later without changing the structure.
 
 Claude's generated package additionally has `skills/rules/`: one skill per technology- or situation-specific rule in
-`shared/rules/` (driven by `adapters/claude/rule-skills.tsv`), so the full rule text loads only when Claude invokes the
+`shared/rules/` (driven by the shared `adapters/rule-skills.tsv` manifest), so the full rule text loads only when Claude invokes the
 matching skill instead of sitting permanently in context. This category does not exist for Codex, which keeps loading
 applicable focused rules as plain files instead. Both clients embed the general rules in their global instructions.
 Split Angular, WPF, and UI/UX rules load supporting references only for the topic being worked on. See [Configuration](configuration.md).