KhaledSaeed18/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 /.claude/skills/ /.)
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):
bash
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 |