By tarqd
Personal toolkit for using Claude as a coding agent: design → bootstrap → plan → drive pipeline with structured handoff reports, ADR management, and an ADR-edit advisory hook
Manage the project's Architecture Decision Records — propose new ADRs, supersede or deprecate existing ones, flip status (accept / reject), and audit the ADR set for drift. Use when the user says "write an ADR", "propose an ADR for X", "supersede ADR-N", "deprecate ADR-N", "accept ADR-N", "audit ADRs", "check the ADR set", or when a non-trivial architectural decision needs to be recorded. Detects project convention (filename pattern, header style, section template, index format) from existing ADRs before making changes — never invents a format.
Bootstrap a local project onto GitHub for agent-driven development. Use when a project has files locally but no git history, no remote, or no initial commit and is about to start phase-1 implementation. Writes a project-appropriate .gitignore, decides the .claude/ versioning policy, stages files explicitly, creates the initial commit, creates the GitHub repo, verifies the push, and hands off to /track-plan.
Turn a design discussion into the project's bootstrap document set — DESIGN doc, Architecture Decision Records (ADRs), and a phased implementation plan — or evolve an existing one. Auto-detects whether the repo is fresh (bootstrap) or has prior design artifacts (evolve); asks the user when state is ambiguous. Use when the user explicitly asks to write up a design, turn a discussion into ADRs, add or supersede ADRs from a conversation, propose changes to an existing design doc, add a new phase to the plan, or scaffold ADRs and phase docs in a fresh repo.
Drive a GitHub tracking issue one step toward completion. Inspects PR and issue state, picks the next actionable sub-issue respecting dependencies and dedup signals, implements one slice, opens a PR, then exits with a structured report (carry-over / follow-up / retrospective). Use when the user wants to advance a tracking issue by one slice — typically paired with /track-plan, and often re-invoked by an external orchestrator (e.g. /goal) for autonomous progress. Idempotent: GitHub state is the only source of truth between runs.
Scaffold a GitHub tracking issue with sub-issues from a design doc, ADR, or implementation plan. Use when the user has a spec with multiple slices / phases / migration steps that should land as separate PRs. Confirms the slice breakdown with the user before creating issues. Pairs with /track-drive for execution.
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A personal collection of Claude Code plugins by Chris Tarquini.
| Plugin | Description |
|---|---|
| kickstart | Skills for creating and using kickstart templates |
| rust | Explore Rust documentation and create skills for crates |
| just | Write justfiles and use the just command runner |
| plugin-development | Toolkit for creating Claude Code plugins |
# Add the marketplace
/plugin marketplace add tarqd/skills
# Install a plugin
/plugin install kickstart@tarq
Or install from a local clone:
git clone https://github.com/tarqd/skills.git
cd skills
# Add local marketplace
claude plugin marketplace add ./
# skills will be available via /plugin command
# Install dependencies (macOS)
just setup
just new-plugin
This prompts for plugin details, creates the structure, and registers it in marketplace.json.
just add-skill rust # Add a skill to the rust plugin
just add-agent rust # Add an agent
just add-hook rust # Add a hook
# Or run interactively
just add-skill
just # Show all recipes
| Recipe | Description |
|---|---|
just setup | Install dependencies via Homebrew |
just new-plugin | Create a new plugin and register in marketplace |
just add-skill [plugin] | Add a skill to a plugin |
just add-agent [plugin] | Add an agent to a plugin |
just add-hook [plugin] | Add a hook to a plugin |
just validate | Run all validations |
just ci | CI entrypoint |
--plugin-dirThe fastest way to test a plugin during development is using the --plugin-dir flag:
# Test a plugin directly without installing
claude --plugin-dir ./plugins/my-plugin
# Test multiple plugins
claude --plugin-dir ./plugins/kickstart --plugin-dir ./plugins/rust
This loads the plugin directly from the directory, so changes take effect immediately on the next session.
Alternatively, add the marketplace locally for a more production-like setup:
# Clone and enter the repo
git clone https://github.com/tarqd/skills.git
cd skills
# Add as local marketplace
/plugin marketplace add ./
# Install a plugin you're working on
/plugin install my-plugin@tarq
# After making changes, reinstall to pick them up
/plugin uninstall my-plugin@tarq
/plugin install my-plugin@tarq
just validate # Run all validations
just validate-schemas # Validate JSON schemas
just validate-templates # Validate kickstart templates
The templates can be used standalone to scaffold Claude Code plugins anywhere.
# macOS
brew install kickstart
# Or see https://github.com/Keats/kickstart
| Template | Description |
|---|---|
claude-plugin | Full plugin with empty component directories |
claude-skill | Skill with SKILL.md, reference.md, examples.md |
claude-agent | Standalone agent file |
claude-hook | Hook configuration with shell script |
# Clone the templates
git clone https://github.com/tarqd/skills.git
cd skills
# Create a new plugin anywhere
kickstart templates/claude-plugin -o ~/my-projects/
# Add a skill to any plugin
kickstart templates/claude-skill -o ~/my-projects/my-plugin/skills/
# Add an agent
kickstart templates/claude-agent -o ~/my-projects/my-plugin/agents/
# Add hooks
kickstart templates/claude-hook -o ~/my-projects/my-plugin/hooks/
Each template prompts for configuration interactively. Use --no-input to accept defaults:
kickstart skills/templates/claude-plugin -o ./ --no-input
├── .claude-plugin/
│ └── marketplace.json # Marketplace configuration
├── plugins/ # Plugins
│ ├── kickstart/
│ ├── rust/
│ ├── just/
│ └── plugin-development/
├── templates/ # Kickstart templates
│ ├── claude-plugin/
│ ├── claude-skill/
│ ├── claude-agent/
│ └── claude-hook/
├── ci/ # Validation scripts
├── schemas/ # JSON schemas
└── Justfile # Task runner
MIT
npx claudepluginhub tarqd/skills --plugin agentic-devSkills for building, validating, and bundling MCP desktop extensions (.mcpb) using @anthropic-ai/mcpb
Skills for using and creating kickstart project templates - a powerful scaffolding tool
Skill for developing MCP servers in Swift using the official swift-sdk
test
Link checking with lychee - CLI usage, configuration, and GitHub Actions workflows
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex and antigravity CLIs when installed) to get diverse perspectives on coding problems
Permanent coding companion for Claude Code — survives any update. MCP-based terminal pet with ASCII art, stats, reactions, and personality.