Skip to content

docs: move still-true rules from retired agent memory #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
schuettc merged 1 commit into from
Oct 5, 2026
Merged

docs: move still-true rules from retired agent memory #61

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# claude-code-plugins

## Plugin authoring

Plugins are skills-only: no `commands/` directory and no `commands` key. Name invocable actions `<domain>-<verb>` with `user-invocable: true`; give ambient advisory skills a descriptive name with no prefix. Name a plugin `<domain>-<category-noun>`. Per-project disable goes through `enabledPlugins`; setup skills offer `/plugin disable` and never self-mutate. Mirror `feature-workflow` when adding a plugin. How plugins compose is in [ADOPTION.md](ADOPTION.md).

## Publishing npm packages

Packages published through npm OIDC trusted publishing must set `repository.url` (plus `repository.directory` in a monorepo) to the building repo, or the registry rejects provenance with a 422. Publish a prerelease to the `dev` tag first; promoting to `latest` is a deliberate step (tag a clean version, see `.github/workflows/publish-ghost-mcp-dev.yml`). Never reuse a version after a failed publish. Test an npm `bin` entry point by spawning it through a symlink, the way npm installs it.
Loading