dotclaude

My personal collection of Claude Code extensions, distributed as a shadcn GitHub registry.

Items install into the current project under .claude/, so run the install command from your project root. (shadcn writes into the project you run it in; its ~ means "project root", not your home directory, so a skill lands in <project>/.claude/skills/<name>/.)

Most items are for software work. The thesis plugin is the exception: a full research lifecycle for a master's thesis or paper (research question, literature search, paper notes, verified citations, synthesis, methodology, statistics, writing, LaTeX and Word toolchains, an examiner-style reviewer, and progress tracking), built for computer-science students and usable by anyone who writes with a bibliography.

Skills, agents, commands, and hooks

If you are new to Claude Code extensions, here is what each kind is and when you would reach for it. They differ mainly in who or what sets them off.

• Skill. A reusable procedure Claude loads on its own when your request matches what the skill is for. You do not have to ask for it by name. Reach for a skill when you keep repeating the same multi-step task and want Claude to just know how to do it well (for example, writing a good commit or scanning for leaked secrets).
• Agent. A specialist Claude can hand a whole side task to, working in its own separate context and handing back just the result. Reach for an agent when a job would otherwise flood the main conversation with noise, like deep web research or a focused code review.
• Command. A shortcut you trigger yourself by typing /name. Reach for a command when you want to kick something off deliberately, on your timing, rather than leaving it to Claude to decide.
• Hook. A script that runs automatically on an event in Claude Code, such as before a tool runs or when a session ends. Reach for a hook when you want something to happen every single time, with no model judgment involved, like logging or a safety check.

The table under What installs where shows where each one lands on disk and what triggers it.

Install

There are two ways to get these items: plugins (bundles, managed by Claude Code, hooks pre-wired), or the shadcn CLI (one item at a time, copied into your project).

As Claude Code plugins (recommended)

Add the marketplace once, then install any bundle:

/plugin marketplace add KhaledSaeed18/dotclaude
/plugin install security@dotclaude

A good starter set is engineering + git + security-hooks: the daily workflow skills, the branch lifecycle, and the deterministic guardrails. From a terminal you can install all three in one line (the CLI takes one plugin per call):

for p in engineering git security-hooks; do claude plugin install "$p@dotclaude"; done

Prefer browsing? After adding the marketplace, open /plugin and pick from the Discover tab: no typing needed.

Plugins update with the repo (/plugin marketplace update dotclaude), namespace their commands (/security:security-audit), and (unlike the shadcn route) hook plugins activate immediately, with no manual settings.json editing.

Plugin	What you get	Install
engineering	Engineering workflow skills, review agents, and a /feature pipeline: orientation, planning, test-driven development, systematic debugging, refactoring, error handling, observability, containers, CI pipelines, dependency upgrades, migration planning, incident postmortems, code review, completion verification, and performance work. (22 skills, 7 agents, 2 commands)	/plugin install engineering@dotclaude
docs	Documentation that stays true to the code: architecture decision records with an /adr command, READMEs verified against the repository, developer guides in the four documentation types, and OpenAPI specifications kept in sync in CI. (4 skills, 1 command)	/plugin install docs@dotclaude
pr-toolkit	Pull-request review as a set of specialists: a read-only code explorer, a behaviour-preserving simplifier, hunters for silent failures and test gaps, a type-design reviewer, and a /review-pr command that runs them in parallel and merges one ranked review. (5 agents, 1 command)	/plugin install pr-toolkit@dotclaude
security	Security review toolkit: OWASP-aligned code review, dependency and secret auditing skills, a security-auditor agent, and a full-codebase /security-audit command. (3 skills, 1 agent, 1 command)	/plugin install security@dotclaude
security-hooks	Deterministic guardrails, active immediately after install: a compound-command deny list, sensitive-file protection, and prompt-injection screening. (3 hooks)	/plugin install security-hooks@dotclaude
git	Version-control skills for the whole branch lifecycle: committing, worktrees, merge conflicts, undo/recovery, PR descriptions, changelogs, releases, and branch cleanup. (9 skills, 3 commands)	/plugin install git@dotclaude
productivity	Session and personal productivity: collaborative brainstorming, plan stress-testing, session handoffs, meeting notes, a decision log, learning plans, a /prime command that loads project context, and a /weekly-review that assembles the week from evidence. (8 skills, 3 commands)	/plugin install productivity@dotclaude
testing	Testing toolkit: browser-based end-to-end verification with Playwright and a /write-tests command that generates a suite matching project conventions. (2 skills, 1 command)	/plugin install testing@dotclaude
research	Investigation toolkit: a deep-research subagent for multi-source work with citations, plus name-clearing skills for software projects (registries, app stores) and for businesses (social handles, storefronts, company registers). (2 skills, 1 agent)	/plugin install research@dotclaude
thesis	The research lifecycle for a master's thesis or paper: research question and proposal, multi-source literature search, structured paper notes, a verified BibTeX bibliography, citation verification with a hook that catches invented keys as they are written, argument-first literature synthesis, research design and design science, statistics planning and reporting, PRISMA systematic reviews, citation-graph expansion, reproducible experiments and benchmark reporting, section-by-section academic writing, LaTeX and Word toolchains, publication figures, an examiner-style reviewer and a paper critic, proofreading, supervisor updates, a research log, and progress tracking. (21 skills, 2 agents, 3 commands, 1 hook)	/plugin install thesis@dotclaude
writing	Prose for a human reader: strip machine-writing tells from any text, draft emails that get answered, and outline talks and defences slide by slide. (3 skills)	/plugin install writing@dotclaude
workflow-hooks	Session workflow guardrails, active on install: a session-start situation report, a stop gate that runs the tests before Claude finishes, type errors fed back after each edit, git footgun protection, a branch-first nudge, and a subagent audit log. (6 hooks)	/plugin install workflow-hooks@dotclaude
format-on-edit	Automation hook that runs the project's own formatter (Biome, Prettier, gofmt, rustfmt, or ruff) on every file Claude edits, so changes land already formatted. (1 hook)	/plugin install format-on-edit@dotclaude
notify	Desktop notifications for Claude Code: surfaces permission requests and attention prompts as native macOS/Linux notifications so long sessions can run in the background. (1 hook)	/plugin install notify@dotclaude
precompact-saver	Context-preservation hook that snapshots the full session transcript before every compaction, keeping the newest ten snapshots per project. (1 hook)	/plugin install precompact-saver@dotclaude
tool-call-logger	Observability hook that appends one sanitized JSON line per tool call to a local log, with secret redaction and payload truncation. (1 hook)	/plugin install tool-call-logger@dotclaude

The four create-* authoring skills are intentionally not in any plugin; they exist to author items for this repository and install via shadcn only.

With the shadcn CLI (single items)

Install any single item with the shadcn CLI:

npx shadcn@latest add KhaledSaeed18/dotclaude/<item>

For example, run this from your project root and the handoff skill lands in .claude/skills/handoff/:

npx shadcn@latest add KhaledSaeed18/dotclaude/handoff

What installs where

Each item installs under .claude/, by type:

Type	Installs to	Triggered by
Skills	.claude/skills/<name>/	Claude, automatically, when the description matches the task
Agents	.claude/agents/<name>.md	Claude delegating to the subagent, or you invoking it