vibe-coding-toolkit
A curated, battle-tested AI-coding toolkit: Claude Code plugins, subagent orchestration, quality gates, and ready-to-copy prompts, extracted from real production use.
- ai-agents
- ai-coding
- claude-code
- developer-tools
- llm-agents
- prompts
- Stars
- 1,167
- Forks
- 198
- + today
- +5
- Created
- 2mo
Ranking data as of October 15, 2026 (UTC).
Star History
Today, hour by hour
Overview
A curated, battle-tested AI-coding toolkit: Claude Code plugins, subagent orchestration, quality gates, and ready-to-copy prompts, extracted from real production use. It ranks #86 on GitTiger, gaining +5 stars on October 15, 2026 (UTC).
The project is written in JavaScript and has 198 forks. It was created 2mo ago.
What it is
Vibe Coding Toolkit is a JavaScript toolkit of Claude Code plugins, subagent orchestration, quality gates and ready-to-copy prompts. Its description says these were extracted from real production use.
Capabilities described
The README summary, written in Portuguese, outlines a five-step workflow: - Understand: inspect the product, stack, instructions, dependencies, integrations and current checks. - Decide: brainstorm and present improvements, risks, dependencies and completion criteria. - Configure: install, update, integrate or reuse applicable catalog components. - Improve: align docs and rules, and make code changes in small verifiable steps. - Verify: compare before and after, test available integrations, and record limits.
Getting started
The supplied data has no installation commands. See the README at https://github.com/soumatheusgomes/vibe-coding-toolkit.
Missing evidence
The supplied data does not list the catalog contents, individual plugins or the specific quality gates. License: MIT (license field).
git clone https://github.com/soumatheusgomes/vibe-coding-toolkit.git
cd vibe-coding-toolkit
# see README for setupFrequently Asked Questions
What is Vibe Coding Toolkit?
According to the description, a curated AI-coding toolkit with Claude Code plugins, subagent orchestration, quality gates and prompts.
What workflow does it describe?
The README summary describes five steps: understand, decide, configure, improve and verify.
What license does it use?
The license field is MIT.