catalog-authoringlisted

<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. --> # Catalog Authoring ## Scope Owns authoring the two projected catalog content types — **skills** and **fragments** — in their non-discoverable YAML source format, and projecting them to the files coding agents actually load. - A **fragment** is always-on guidance merged into the projected `CLAUDE.md`, `AGENTS.md`, and `copilot-instructions.md` (and, when scoped, into per-path rules/instructions files). Keep it terse; point at commands, do not restate mechanically-enforced rules. - A **skill** is an on-demand runbook projected to `SKILL.md` at the target skill roots and loaded only when its `description` trigger matches. ## The non-negotiable rule: sources are never named for discovery Coding agents auto-discover context by **filename/extension** — `SKILL.md`, `AGENTS.md`, `CLAUDE.md`, `*.instructions.md`, `*.mdc`, `GEMINI.md`. So catalog **sources** are authored as YAML (`skill.yaml`, `<id>.fragment.yaml`) and the discoverable `.md` is emitted only at the target roots by the projector. Never add a `SKILL.md` or `*.fragment.md` under `.basicly/core/`; the `catalog lint` gate rejects it. ## Author a skill 1. Scaffold: `basicly catalog new skill <slug>` writes `core/skills/<slug>/skill.yaml`. 2. Fill in `name` (must equal the slug), a strong one-line `description` (the discovery trigger — state *when* to use it), and the `instructions` body as a `|` literal block sca