agentic-kit
A Claude Code plugin marketplace of four small plugins (core, writing, dnd, coding) that stay inert outside the projects they are meant for.
- Status
- Preparing for public release
- First commit
- Latest commit
- Claude Code plugins
- TypeScript
- Hooks
- Subagents
- Markdown skills
The problem
I use Claude Code for code, for fiction and for running D&D campaigns, and each of those wants different context and different guard rails. Putting everything in one global config makes every session noisier, and it lets behaviour meant for one kind of project leak into another.
Key design decisions
Small plugins that stay quiet. There are four, installable independently from one marketplace:
core: two skills.teachruns a probe, plan, teach session;visualizeadds one diagram, delegating authoring and rendering to a subagent that looks at the rendered image first.coding: a status line (branch, worktree marker, dirty-file count) and a toast when a test, lint, typecheck or build command fails.dnd: inside a campaign folder it loads the campaign README and latest session notes and adds/recap,/npcand/prep. Its prompt keeps DM-only material out of anything meant for players.writing: a scene pane, proposals, authorship levels and a researcher subagent, for writing-studio projects.
The coding, dnd and writing plugins detect their project type and do nothing elsewhere, so installing all of them costs nothing in unrelated repos.
The writer stays in control. The writing plugin refuses agent edits to scenes, notes, the ledger and project config, and every accepted proposal is a git commit with provenance trailers. Because it commits on its own, that behaviour is called out at the top of its README with the opt-out. The guard is exact for write tools but best-effort for shell commands, and the README says so rather than calling it a security boundary.
Stack
Claude Code plugin manifests, hooks and skills, with TypeScript for the hook modules.
Outcome and what I would change
The current repo history is two commits, both dated 2026-10-21, so there is no long track record to cite. The marketplace is being prepared for a public release, and the writing plugin is only useful to someone who also has the writing-studio CLI. I would split that dependency out sooner. The coding plugin’s agents pane also needs an agents CLI that is not part of the repo; it reports an error without it, which I documented but would rather not need to.