Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By walis85300
DynamoDB single-table design pipeline: access patterns → table design → query interfaces. Three-step guided workflow for designing and documenting DynamoDB schemas.
npx claudepluginhub walis85300/marketplace --plugin dynamo-expertInteractive skill for eliciting, formalizing, and persisting DynamoDB access patterns. Use when the user wants to start designing a DynamoDB table, define entities, or document how their application will read and write data. This is Step 1 of a 3-step pipeline: access patterns -> table design -> query interfaces. The output is a structured .md file that feeds into the dynamodb-table-design skill.
Generates language-agnostic repository interfaces (method signatures, input/output types, and entity models) from a DynamoDB table design document. Use when the user has a table design .md file (from dynamodb-table-design skill) and wants to generate the code skeleton for their data access layer. This is Step 3 of a 3-step pipeline: access patterns -> table design -> query interfaces.
Orchestrator for the DynamoDB single-table design pipeline. Use when the user wants to design a DynamoDB table end-to-end or is unsure which step to start with. Routes to the appropriate specialized skill: dynamodb-access-patterns, dynamodb-table-design, or dynamodb-query-interfaces.
Designs a DynamoDB single-table structure from a documented set of access patterns. Use when the user has an access patterns .md file (from dynamodb-access-patterns skill) and wants to design partition keys, sort keys, GSIs, composite keys, and map every access pattern to a concrete DynamoDB query operation. This is Step 2 of a 3-step pipeline: access patterns -> table design -> query interfaces.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Database plugin for nosql-data-modeler
Database schema design and ERD generation
Schema design, query optimization, migrations, indexing, transactions, data integrity, and connection pooling.
Use this agent when you need to optimize database performance for B2B applications at enterprise scale. This agent specializes in multi-tenant database optimization, query performance tuning, indexing strategies, connection pooling, and database scaling for SaaS platforms. Handles PostgreSQL, MySQL, MongoDB, and cloud database optimizations. Examples:
Expert database guidance for the AWS database portfolio. Design schemas, execute queries, handle migrations, and choose the right database for your workload.
Database architecture and SQL optimization with PostgreSQL expertise
Documentation generation agents and skills for code explanation and API docs
Code review skills and agents for catching bugs, security issues, and style problems
Git workflow automation with conventional commits, branch naming, and pre-commit hooks
A demo marketplace showcasing Claude Code plugin capabilities including skills, agents, commands, hooks, and MCP servers.
This repository serves as a Claude Code plugin marketplace — a catalog that distributes plugins to Claude Code users via /plugin marketplace add. It demonstrates the full spectrum of Claude Code's extensibility features through three example plugins.
# Add the marketplace (from within Claude Code)
/plugin marketplace add https://github.com/your-org/marketplace
# Install a specific plugin
/plugin install code-review@demo-marketplace
# Test a single plugin locally
claude --plugin-dir ./plugins/code-review
# Test multiple plugins
claude --plugin-dir ./plugins/code-review --plugin-dir ./plugins/git-toolkit
# Load the entire marketplace locally (from within Claude Code)
/plugin marketplace add ./
/plugin install code-review@demo-marketplace
Code review skills and agents for catching bugs, security issues, and style problems.
Features:
review - Automatic code review on file changessecurity-reviewer - Specialized security analysis/code-review:quick-review - On-demand code reviewsTags: review, security, quality
Git workflow automation with conventional commits, branch naming, and pre-commit hooks.
Features:
conventional-commit - Enforces conventional commit standards/git-toolkit:smart-commit [type|scope] - Intelligent commit creation/git-toolkit:branch - Smart branch managementTags: git, commits, automation
Documentation generation agents and skills for code explanation and API docs.
Features:
explain-code - Contextual code explanationsdoc-writer - Comprehensive documentation specialist/doc-generator:api-docs - Generate API documentation/doc-generator:readme - Create project README filesTags: docs, documentation, explanation
AI-powered development tools with 29 agents, 22 commands, 19 skills, and 1 MCP server.
External Plugin: Sourced from EveryInc/compound-engineering-plugin
Tags: ai-powered, compound-engineering, workflow-automation
marketplace/
├── .claude-plugin/
│ └── marketplace.json # Marketplace catalog (root manifest)
├── plugins/
│ ├── code-review/ # Code review plugin
│ │ ├── .claude-plugin/plugin.json
│ │ ├── skills/review/SKILL.md
│ │ ├── agents/security-reviewer.md
│ │ └── commands/quick-review.md
│ ├── git-toolkit/ # Git workflow plugin
│ │ ├── .claude-plugin/plugin.json
│ │ ├── skills/conventional-commit/SKILL.md
│ │ ├── commands/smart-commit.md
│ │ ├── commands/branch.md
│ │ └── hooks/hooks.json
│ └── doc-generator/ # Documentation plugin
│ ├── .claude-plugin/plugin.json
│ ├── skills/explain-code/SKILL.md
│ ├── agents/doc-writer.md
│ ├── commands/api-docs.md
│ └── commands/readme.md
└── CLAUDE.md # Development guidelines
skills/*/SKILL.md) - Auto-invoked by Claude based on task contextcommands/*.md) - User-invoked via slash commands (/plugin:command)agents/*.md) - Specialized Claude personas for complex taskshooks/hooks.json) - Event handlers for git operations and file changesEach plugin follows this structure:
plugin-name/
├── .claude-plugin/plugin.json # Plugin manifest (name, version, description)
├── skills/ # Auto-invoked capabilities
│ └── skill-name/SKILL.md
├── commands/ # User-invoked slash commands
│ └── command-name.md
├── agents/ # Specialized Claude personas
│ └── agent-name.md
├── hooks/ # Event handlers
│ └── hooks.json
└── scripts/ # Shell scripts for hooks
Create plugin manifest:
mkdir -p plugins/my-plugin/.claude-plugin
# Edit plugins/my-plugin/.claude-plugin/plugin.json
Add capabilities:
mkdir -p plugins/my-plugin/{skills,commands,agents}
# Create your .md files following the examples