claude-code-artifacts-public CLAUDE.md

CLAUDE.md

Guidance for Claude Code when working in this repository.

This repository is a public library of reusable Claude Code artifacts. Each artifact type lives under its own <type>/library/ directory (skills/library/, hooks/library/, rules/library/, agents/library/, slash-commands/library/) or, for environments, under environments/library/ and environments/templates/. Every type also carries a short README describing its own layout, conventions, and installation.

README maintenance

The root README.md is a catalog organized by artifact category, not a description of the directory tree. It deliberately has no "repository structure" section: a reader should meet the actual, useful artifacts first, then learn how to consume them.

Category order

Present categories in this fixed order, skipping any that are currently empty:

1. Environments
2. Skills
3. Rules
4. Hooks
5. Agents
6. Slash commands

The order is fixed even as categories come and go; when a category gains its first artifact it takes its slot in this sequence, and the categories that remain are shown in this same relative order.

A category appears only when it has content

A category earns its own ## section in the root README only when the repository actually contains at least one standalone artifact of that type under the type's library/ directory. A type whose library/ holds no standalone artifacts yet — only its own README.md or files that serve another artifact — is omitted from the root catalog until its first standalone artifact lands. The goal is that every section a reader sees points at something real they can use, never at an empty placeholder.

Only standalone artifacts are cataloged

The catalog describes only standalone entities: artifacts that deliver value installed on their own. The repository holds many files, and not every file warrants a description. A file that works only as part of a larger artifact — a shared helper module several hooks load, a hook's companion configuration, or an environment configuration's bundled skill, hooks, and runtime files — never gets its own ### subsection: it is described (and linked) inside the entry of the artifact it serves, or, for a cross-cutting helper, mentioned in its category's prose. The test is whether a reader could install the file alone and get value from it; if it only makes sense wired into something larger, it belongs inside that larger artifact's entry.