A local plugin marketplace for Claude Code providing development workflows and document processing.
Extends Claude Code with:
Configure environment variable (add to your shell profile: ~/.zshrc, ~/.bashrc, etc.):
export CT_PLUGINS_DIR=~/.claude/plugins/marketplaces/codethread-plugins/plugins
After adding, reload your shell: source ~/.zshrc (or restart your terminal)
# Add marketplace
/plugin marketplace add [email protected]:codethread/claude-code-plugins.git
# Install plugins
/plugin install claude-code-knowledge@codethread-plugins
/plugin install doc-writer@codethread-plugins
/plugin install langs@codethread-plugins
/plugin install workflow@codethread-plugins
/plugin install bdfl@codethread-plugins
/plugin install karen@codethread-plugins
Then run claude --init (or claude --init-only) in any project to install dependencies and build plugins. Each plugin's Setup hook handles its own initialization automatically.
After installation, plugins provide slash commands, agents, and skills. See individual plugin READMEs for usage:
plugins/claude-code-knowledge/README.md - Claude Code docs and skill creationplugins/doc-writer/README.md - Documentation writing guidanceplugins/langs/README.md - Language-specific patternsplugins/workflow/README.md - Development workflowplugins/bdfl/README.md - Opinionated project bootstrapping and migrationplugins/karen/README.md - Scope gatekeeper agentFor detailed information, ask Claude:
What can the langs plugin do?
How do I create a new plugin?
Show me the plugin directory structure
Claude will reference CLAUDE.md files for comprehensive architecture details.
Project-level slash commands for maintaining this repository:
/release - Prepare plugin releases with version bumps, changelog updates, and git tags
.env, node_modules, hidden files)type(plugin1,plugin2): description<plugin-name>-v<version>git show first)Plugins provide automatic suggestions via hooks using structured XML tags. All plugin suggestions follow the pattern <plugin-PLUGINNAME-suggestion>, allowing you to control Claude's attention to these recommendations in your project's CLAUDE.md.
Example 1: Emphasize all plugin suggestions
# CLAUDE.md
ALWAYS follow `<plugin-*-suggestion>` tags closely. These provide
context-specific recommendations from installed plugins.
Example 2: Emphasize specific plugins
# CLAUDE.md
- ALWAYS follow `<plugin-langs-suggestion>` when test files are detected
- Consider `<plugin-claude-code-knowledge-suggestion>` for Claude Code questions
Example 3: Ignore specific suggestions
# CLAUDE.md
Follow all `<plugin-*-suggestion>` tags except `<plugin-langs-suggestion>`
(I prefer to manage test files manually).
The XML tag format ensures Claude treats these suggestions as structured prompts rather than visual formatting, improving reliability with Anthropic models.
Skill creation scripts sourced from Anthropic's skills repository.
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.
npx claudepluginhub codethread/claude-code-plugins --plugin bdflPhase-based development workflow: What, How, Build. Structured planning with research, learning tests, and prototyping before implementation.
Pithos hooks for Claude Code. Tracks runs/tasks/artifacts for spawner-launched sessions.
Scope gatekeeper agent that pushes back on unnecessary features and complexity. Delegate to Karen before implementing new features to challenge necessity, detect optimistic bias, and insist on the simplest solution.
Push notifications for Claude Code via cc-notify server (Stop, PermissionRequest, activity tracking)
No description provided.
Scaffold new projects and add features with best-practice templates
Universal Claude Code workflow with specialized agents, skills, hooks, and output styles for any software project. Includes orchestrator, code-reviewer, debugger, docs-writer, security-auditor, refactorer, and test-architect agents.
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
Reorganizes project structure by cleaning root clutter, creating logical folder hierarchies, and moving files to optimal locations. Tracks dependencies and fixes broken imports/paths. Use PROACTIVELY when project structure becomes unwieldy or needs architectural cleanup.
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions. For example: user: 'I need to add a user authentication system to my app' -> assistant: 'I'll use the code-architect agent to design the architecture and folder structure for your authentication system' -> <uses agent>. Another example: user: 'How should I organize my e-commerce product catalog feature?' -> assistant: 'Let me use the code-architect agent to design a scalable structure for your product catalog' -> <uses agent>.
better-chatbot project conventions and standards. Use for contributing code, following three-tier tool system (MCP/Workflow/Default), or encountering server action validators, repository patterns, component design errors.