By tstapler
Stapler-Driven Development (SDD) workflow. Enforces spec-before-code with 7 numbered phase commands. Run /sdd:status to find your current phase.
npx claudepluginhub tstapler/dotfiles --plugin sddPhase 1 — Interview to capture requirements. Outputs: project_plans/<project>/requirements.md
Phase 2 — Parallel research across 4 dimensions. Outputs: project_plans/<project>/research/*.md
Phase 3 — Architecture + task breakdown. Outputs: project_plans/<project>/implementation/plan.md
Phase 4 — Map test coverage to requirements before writing a line of code. Outputs: project_plans/<project>/implementation/validation.md
Phase 5 — Execute plan via subagent dispatcher. START IN A FRESH SESSION.
Phase 6 — Code review + test coverage hard gate before shipping.
Phase 7 — Prepare and open the PR.
Capture an architecture decision record
Maintenance shortcut — pick highest priority bug, find root cause, fix, verify
Full SDD workflow — ideate → research → plan → validate → implement → verify → ship. Planning runs in subagents; no fresh session required.
One-shot workflow for simple tasks and bug fixes that fit in a single context window. Skips artifacts and fresh-session requirements.
Show current SDD phase and the next command to run
Execute an implementation plan by dispatching fresh subagents per task with dual-review (spec compliance + code quality). Use when running sdd:5-implement or executing any multi-task implementation plan.
Enforce Red-Green-Refactor TDD cycle. Use when implementing any new class or method — write the failing test first, then make it pass. Never write production code before a failing test exists.
These are the configuration for various machines I own. I make every attempt to do things in a cross platform manner when possible.
My primary machines run Manjaro Linux, and Ubuntu Linux. Typically, my Work computers are Macs. There are some bits to make the original Windows Subsystem for Linux work because I used Windows briefly at Work.
I install my dotfiles to a new machine by using this script. It clones this repo, and symlinks my dotfiles to my home directory using cfgcaddy a tool I wrote.
You can use alternatives such as GNU Stow or yadm which have more users and likely less bugs 😉.
The key idea is that you should keep your dotfiles in a git repo in somewhere like $HOME/dotfiles and then symlink them to your $HOME directory for them to be read by other tools.
Once you have that system setup, you can copy pieces of my configuration piecemeal. I don't recommend copying everything directly. This repo has grown pretty organically over the years so it contains a lot of configuration you may not
I a pretty comprehensive ZSH configuration
I use zplug as my package manager, you can find the packages in .zplug_packages.zsh. It is responsible for installing zsh packages as well as a few binaries.
The directory .shell contains several scripts that are sourced in the .zshrc, their names should be fairly self explanatory.
I'm a heavy Vim user, so I have configuration for Intellij's vim plugin as well as actual Vim split across a few different files
I am a polyglot when it comes to programming languages so I use asdf to manage installing different languages and versions across my machines in a consistant way.
.tool-versions sets the global language version used across the system.
I have some configuration for installing each of the language specific plugins in the file .shell/languages.sh.
Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, Hermes, and 17+ AI coding assistants. Now with Arabic, German, Spanish, and Chinese (Simplified & Traditional) support.
Modifies files
Hook triggers on file write and edit operations
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Team-oriented workflow plugin with role agents, 27 specialist agents, ECC-inspired commands, layered rules, and hooks skeleton.
Complete developer toolkit for Claude Code
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, rules, and legacy command shims evolved over 10+ months of intensive daily use
Meta-prompting and spec-driven development system for Claude Code. Productivity framework for structured AI-assisted development.