Diegopherlt Dotclaudefiles
diegopherlt-dotclaudefiles is a Claude Code plugin marketplace for the Build phase that restores a 3-plugin backup with 9-phase planning, TDD enforcement, and quality gates.
Restore a strict 9-phase, TDD-enforced Claude Code setup with quality gates, parallel agents, and packaged skills from a dotfiles-style backup repo.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install diegopherlt-dotclaudefiles@DieGopherLT/dotclaudefilesBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:DieGopherLT/dotclaudefiles") and the paste-ready config with skillselion.get_install_config("plugin:DieGopherLT/dotclaudefiles").
What it does
diegopherlt-dotclaudefiles is a backup repository of DieGopherLT’s Claude Code configurations, exposed as a marketplace with three plugins rather than raw folders only. The keyword set describes a disciplined solo-builder ritual: a nine-phase plan before coding, strict test-driven development with red-green-refactor enforcement, quality and feature gates, semantic analysis, auditing, and parallel agent specialization. That pattern is journey-wide in practice—you invoke planning discipline before scope commits, during implementation, and again before merge—even though Skillselion shelves it under Build agent-tooling as the first place builders install such a bundle. Multilanguage and daily-development hooks suggest it targets serious shipping habits, not casual chat prompts. Community discovery metadata shows a small star footprint, so fork and trim gates to match your risk tolerance. Ideal if you want an opinionated safety rail around Claude Code; poor fit if you prefer lightweight, interruptible pair programming without enforced TDD or phased plans.
Highlights
- 3-plugin marketplace backup of personal Claude Code dotclaudefiles
- 9-phase planning workflow with explicit implementation and quality gates
- Strict test-driven development with red-green-refactor enforcement keywords
- Semantic analysis, auditing, and smart parallelization for agent runs
- Multilanguage development configs packaged as installable plugins and skills
Why builders use it
Without backed-up Claude Code configs, strict planning and TDD enforcement drift away and every new repo starts with a weaker agent workflow.
Installing the marketplace reapplies packaged plugins, skills, and gates so Claude Code follows the maintainer’s nine-phase, test-driven delivery ritual.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is diegopherlt-dotclaudefiles for?
It is for developers who already treat Claude Code as a structured delivery tool and want the author’s gated, TDD-first configuration restored quickly.
When should I use diegopherlt-dotclaudefiles?
Use it at project kickoff and whenever you reset a machine—before creative implementation—so nine-phase planning and test enforcement are active from the first commit.
How do I add diegopherlt-dotclaudefiles to my agent?
Register github.com/DieGopherLT/dotclaudefiles as your Claude Code marketplace, install all three plugins, then align your local skills and commands with the bundled layout.
Comments
Share how you use diegopherlt-dotclaudefiles, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.