By pbdeuchler
Enforce house style best practices across code architecture, PostgreSQL database design, property-based and unit testing, defense-in-depth validation, and technical writing during code writing, refactoring, and review workflows in TypeScript, Go, Python, Rust, JavaScript.
npx claudepluginhub pbdeuchler/llm-plugins --plugin house-styleALWAYS use this skill when writing or refactoring code. Includes context-dependent sub-skills to empower different coding styles across languages and runtimes.
Use when invalid data causes failures deep in execution - validates at every layer data passes through to make bugs structurally impossible rather than temporarily fixed
Use when writing database access code, creating schemas, or managing transactions with PostgreSQL - enforces transaction safety with TX_ naming, read-write separation, type safety for UUIDs/JSONB, and snake_case conventions to prevent data corruption and type errors
Use when writing or refactoring code, before creating files - enforces separation of pure business logic (Functional Core) from side effects (Imperative Shell) using FCIS pattern with mandatory file classification
Use when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testing
Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticity
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Claude Code plugins for design, implementation, and development workflows. Largely stolen from ed3d-plugins, ToB, davebcn87 and ever so slightly modified.
Autonomous experiment loop that optimizes any measurable target. Point it at a metric and it iteratively tries ideas, benchmarks them, keeps improvements, and discards regressions -- logging everything to a structured JSONL file. Runs indefinitely or until a time/iteration limit. Each experiment executes in an isolated subagent to keep the main context clean.
/autoresearch:start [duration-minutes]
Multi-perspective engineering review of any codebase -- or a scoped subset -- from a single command. A Haiku-powered scout maps the structure, then an Opus-powered panel of staff engineers reviews sampled files across seven dimensions (correctness, consistency, simplicity, design principles, idiomatic usage, security, test quality) and returns severity-classified findings with holistic remediation prose. For large codebases, files are partitioned by module and reviewed in parallel.
/blank-slate-review:start [scope]
Tightly scoped implementation planning with a panel of specialist engineer subagents. Creates plans of 5 steps or fewer, each roughly one story point, ready to hand off to an implementer. Five specialist agents (systems performance, distributed systems, security, infra ops, product lead) evaluate approaches from their domain at specific process steps.
/quick-plan:start [basic prompt]
Executes an implementation plan end-to-end in a single session: creates a branch, implements each step with TDD, runs per-step code review (fixing all severity levels), performs a holistic final review via a multi-persona staff engineer panel (with optional dueling-model review via Codex), and opens a PR. Rejects plans too large or vague to complete in 5 steps at a high quality bar.
/one-shot:start <absolute-plan-file-path> [seed-commitish]
Opinionated development guides covering coding patterns, testing strategies, database access, and technical writing. Skills activate automatically when relevant -- functional core / imperative shell, defense in depth, property-based testing, PostgreSQL conventions, and more.
/plugin install house-style@llm-plugins
Reference skills for developer tools: ast-grep for structural code search and transformation, and qmd for searching markdown knowledge bases. Loaded automatically when relevant tool usage is detected.
/plugin install tooling@llm-plugins
/plugin marketplace add https://github.com/pbdeuchler/llm-plugins.git
All plugins are available from the llm-plugins marketplace:
/plugin install autoresearch@llm-plugins
/plugin install blank-slate-review@llm-plugins
/plugin install house-style@llm-plugins
/plugin install one-shot@llm-plugins
/plugin install quick-plan@llm-plugins
/plugin install tooling@llm-plugins
Skills and commands to perform one shot prompting in a standardized workflow
Ed's stylistic particulars for writing code and English.
23 agent skills for systematic software development. Covers design, planning, TDD, code review, debugging, quality gates, and adversarial testing. Every skill is eval-tested with measured A/B deltas using Anthropic's skill evaluation framework.
Prompt engineering techniques for accurate, grounded Claude responses — anti-hallucination workflow with citation-backed analysis
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.
Share bugs, ideas, or general feedback.
No description provided.
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 claim