Memory #95 CURRENT
tribernachi-skills top-level layout is fixed Never add top-level directories to D:/GitHub/tribernachi-skills/. Only general/, publishers/, domains/, genres/, templates/, web/, web-uploads/ are allowed. Reference/tooling docs go elsewhere. The `tribernachi-skills` repo enforces a fixed top-level layout via its `CLAUDE.md`: > Top-level layout (`general/`, `publishers/`, `domains/`, `genres/`) is fixed. Add new files within these dirs only. `templates/`, `web/`, `web-uploads/` also exist as top-level dirs but are repo infrastructure, not extension points. **Why:** the repo is a *canonical skill source* with a four-layer composition contract (general → publisher → domain → genre). Adding ad-hoc top-level dirs (e.g. `reference/`) breaks the layered-loading model that other consumers rely on. Mark caught me adding `reference/` for a Claude tooling catalog on 2026-05-01 and we relocated it to `D:/GitHub/tribernachi/catalog/`. **How to apply:** - Skill files (composing publisher/domain/genre) → place under the matching top-level dir in `tribernachi-skills/`. - Reference / catalog / tooling docs that are *not* skills → place under `D:/GitHub/tribernachi/catalog/` (next to `TTF.CAT.DOCS-001`) or another project's `docs/` dir, never inside `tribernachi-skills/`. - If unsure whether something is a "skill," check whether it has a publisher × domain × genre identity. If not, it's not a skill. — [feedback_tribernachi_skills_layout.md]
| Composite | FCF1CC3AA7A79F125 |
| Project prime | 13 |
| Domain prime | 59 |
| Type prime | 61 |
| Importance | 1.000000 (CRITICAL) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.