Ask questions about design, architecture, or how code fits together
Create session handoff document for transferring work to another session
Generate or update project documentation
Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.
Add, fix, or update logging in project code
Uses power tools
Uses Bash, Write, or Edit tools
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.
Stop vibe-coding. Ship with structure.
Plugins that make Claude Code follow a real development process.
No frameworks. No dependencies. No bloat. Just markdown files that work.
You: "Build me an auth system"
Claude: *writes 500 lines*
Claude: "Done! Here's your auth system."
You: *tests it*
You: "This doesn't actually validate tokens."
Claude: "Oh right, let me fix that..."
Claude: *writes 200 more lines that break something else*
LLMs skip steps. They write code that looks right but doesn't work. They forget what they were doing between sessions.
Every AI coding tool adds more features, more complexity, more noise. This goes the other way: simple markdown files that enforce discipline.
Most AI tools just generate. This one asks.
┌─────────────────────────────────────────────────────────────────────────┐
│ │
│ TYPICAL AI THIS WORKFLOW │
│ │
│ You: "Build auth" You: "Build auth" │
│ │ │ │
│ ▼ ▼ │
│ AI: *generates 500 lines* AI: "JWT or session-based? │
│ │ What's the token lifetime? │
│ ▼ Refresh token strategy?" │
│ You: "This is wrong" │ │
│ │ ▼ │
│ ▼ You: *answers* │
│ AI: *generates 300 more* │ │
│ │ ▼ │
│ ▼ AI: *builds exactly that* │
│ You: "Still wrong" │ │
│ │ ▼ │
│ ▼ AI: "I built X, Y, Z. │
│ *repeat until frustrated* Is that what you meant?" │
│ │ │
│ ▼ │
│ You: "Yes" or "No, actually..." │
│ │ │
│ ▼ │
│ *catches drift before it compounds*│
│ │
└─────────────────────────────────────────────────────────────────────────┘
Questions appear at every phase:
LLMs are confident. Confident and wrong. Questions force verification before the wrong code compounds into a mess.
┌────────────────────────────────────────────────────────────────────┐
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ PLAN │───▶│ BUILD │───▶│ VERIFY │───▶│ AUDIT │ │
│ └─────────┘ └─────────┘ └─────────┘ └─────────┘ │
│ │ │ │
│ │ ┌─────────┐ │ │
│ └─────────────▶│ FIX │◀───────────────────┘ │
│ └─────────┘ │
│ │
└────────────────────────────────────────────────────────────────────┘
Plan before you code. Track deviations. Audit for fake code. Fix systematically.
git clone https://github.com/jsai/claude-tooling.git
cd claude-tooling && ./install.sh
npx claudepluginhub jsai23/claude-tooling --plugin utilObsidian vault management: PARA filing, semantic search, backlinks, tags, inbox processing
Agent loop management: launch, author session prompts, observe running loops
Document-driven development workflow: plan → build → verify → garden
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
External tools integration skills for CLI utilities, APIs, and third-party services
You work with me (Claude) - I guide your workflow and suggest next actions.
PROJECT.md-first autonomous development with hybrid auto-fix documentation. 8-agent pipeline, auto-orchestration, docs auto-update on commit (true vibe coding). Knowledge base system with 90% faster repeat research. Strict mode enforces SDLC best practices automatically. Works for ANY Python/JavaScript/TypeScript/Go project.
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation