Why I Built a Claude Code Playbook for WordPress
How one public repo of rules, skills and commands keeps Claude Code consistent across every WordPress project I work on, and syncs to every machine on merge.
About me
I started in higher-ed marketing and kept coming back to WordPress because it gives people real ownership of their site. Today I build themes, plugins, and web apps for businesses and agencies — and write it all down for the next developer.
Story
I started on the web in higher-ed marketing — landing pages, content updates, and figuring out why a page that looked fine still wasn’t getting clicks. That taught me more about what people need than any course or tool.
WordPress is the tool I kept coming back to. Most shops need a site they can edit themselves: update hours, add a product, fix a typo, without waiting on a developer. That still matters to me.
These days I build WordPress themes and plugins for shops, tours, and inns, and publish the code on GitHub so other developers can read it.
Most of my earlier work lived inside employers, so the public repos are recent. The Power Platform work for enterprise clients is in the resume below; it has no public demo.
Full-Stack Web Developer with experience in WordPress and PowerPlatform.
Available
View GitHub profile → (opens in a new window)Now
A short list of where my time is going — open work, WordPress builds, and writing.
Nights and weekends belong to my family, not projects.
Last updated
How one public repo of rules, skills and commands keeps Claude Code consistent across every WordPress project I work on, and syncs to every machine on merge.
The website basics every new developer should learn and every business owner should understand: how a site works, who owns what, backups, and staging.
Install the WordPress MCP Adapter, expose an ability with mcp.public, and connect Claude Code or Cursor through an Application Password. Includes the default endpoint and the safety checks…
Services
WordPress is the specialty. Adjacent work — APIs, React, Power Platform, deploys — is in range because I am a self-taught problem solver with 17 years in-house.
New sites, sites that need a cleanup, and themes shops can edit themselves. Practical WordPress — not a pile of plugins they will never use.
Custom pieces when WordPress needs something it does not ship with. Small, documented, and written so the next developer is not stuck guessing.
React interfaces, PHP or Node services, authentication, databases, APIs, and deployment workflows built as one maintainable system.
Curious about a specific project type? Write a note.
Hire me
Available
I’m open to full-time roles, contract work, and freelance projects. I’m based in Gettysburg, PA, and happy to work remote.
If you’re hiring a full-stack developer, need an experienced WordPress specialist, want agency overflow support, or have a web project to discuss, send a short note about what you’re working on.
Written scope before I start. Custom quotes — no menu of add-ons.
Full-stack web development with deep WordPress and PHP experience. Open to on-site, hybrid, or remote.
Project-based work with a clear, written scope for shops and agencies.
A handful of silent-sub jobs. You keep the relationship. I build the WordPress platform, integration, or web application.
A few hours a week or a focused sprint. Flexible.
You don’t need a finished spec. A short description of the problem is enough. Here’s what helps:
That’s it. I’ll follow up with clarifying questions or an honest note if I’m not the right fit.
Use the contact form — a paragraph is plenty. I usually reply within one business day (ET).
Experience
Newest role first. I work with shops and agencies anywhere, and I’m open to full-time, contract, and agency overflow work.
Saliense
All Native Group · Federal Services Division
Knowledge Capital Associates — USMC Contractor
At a glance
The short version, if you are hiring. The resume above has the detail.
Employers on the record: Saliense, All Native Group, and Knowledge Capital Associates.
Power Apps, Power Automate, and InfoPath for enterprise clients — details in the resume. There is no public demo.
Hiring managers can ask for a private walkthrough of constrained employer work under NDA.
Process
Four steps. Written scope. You own everything at the end.
1–2 days
Tell me who the site is for, what is broken, and what a win looks like. A short note is enough.
2–4 days
I send a plain list of work, a rough timeline, and what is out of scope. You approve or push back.
1–2 weeks
I build on staged pages you can click. Every line ships after I have read and tested it.
Handoff
You own the domain, hosting, database, and code. I leave a short admin guide and stay reachable for questions.
Fit
A few honest checks before we spend time on a call.
Approach
Sage 11, Blade, Tailwind, Vite, and PHP 8.3 — shipped through GitHub. Here is how I run a WordPress build from the first note to a clean handoff.
Hosting, DNS, the database, and the Git repo sit in accounts under your name before we close. The Sage theme, plugins, and deploy notes go with the site — so another developer can pick up without guessing.
I build with Sage 11, Blade, Tailwind, and page fields shops edit in WordPress — not a page builder. If an owner cannot update hours or a product in a couple of minutes, the theme is not done.
Cursor, Claude, and ChatGPT help with scaffolding and first-pass PHP. I still read, test, and own every line that reaches production — Vite builds, PHP 8.3, and GitHub Actions included.
Custom work lives in focused PHP plugins or theme modules with standard WordPress hooks, PHPDoc, and a clean uninstall path. Kitchen-sink plugins stay off the site.
Blade stays thin; logic lives in App helpers with typed functions and explicit names. If another developer cannot follow a function in half a minute, I rewrite it before handoff.
Semantic HTML, keyboard paths, and solid contrast. Labels, errors, and handoff notes read like they were written for a busy shop owner — welcoming to developers, clear for everyone else.
Open source
Public repos from Gettysburg — Sage themes, WordPress plugins, and web apps shops and developers can fork. Stats and activity below pull live from the GitHub API.
Synced from the GitHub API 52 minutes ago
The repos pinned to my GitHub profile — the ones I point developers to first. Pin or unpin a repo on GitHub and this list follows within the hour.
Rules, skills, slash commands and a deploy kit that teach Claude Code how to build WordPress (Sage/Bedrock, Tailwind v4) and front-end projects — auto-synced to every machine.
Shell AI Agents Bedrock Claude Code Coding Standards Developer Tools
WalkRidge is a custom WordPress theme for walking and historical home tours. Clean performance, responsive layout, SEO-ready structure, and easy content management.
PHP WordPress WordPress Theme Gutenberg
Acreline is a WordPress theme for farms, land, and historic homes — searchable listings, agents, and showing requests. Customizer identity, eight color styles, Sage 11. Demo and support by Matt Hummel.
PHP WordPress WordPress Theme Roots Io Sage Gutenberg
Lightweight, server-rendered Table of Contents block for Gutenberg. TOCguide builds an accessible, SEO-friendly outline from your headings — numbered or bulleted, zero setup. Independent plugin. GPLv2+.
PHP Block Editor Gutenberg Gutenberg Block
Sage 11 WordPress theme for matthummel.com — Blade, Tailwind v4, Vite. Portfolio and services for a Gettysburg developer.
PHP Bedrock Roots Io Sage Theme Roots Sage
Fresh commits on public GitHub repos — a quick read on what I am shipping this week.
Primary language of each public repo, counted live. Small static sites pull HTML up; the themes and plugins are PHP.
Stack
WordPress, Sage, Tailwind, and the rest of the stack behind shipped repos. Not an exhaustive list — just what shows up in public GitHub.
Questions
If yours is not here, ask.
The domain, hosting, database, and code are yours. After handoff I have no access unless you invite me. Another developer can pick up where I left off.
Development. I can work from your design or a clear reference. For original design work I will refer someone rather than half-guess it.
A simple site is often two to three weeks. Custom fields or booking can take four to eight. I give a realistic estimate during scoping.
Yes. Pages use standard WordPress fields. I document anything unusual in plain English before handoff.
Yes. I can stay in the background on agency work. Rate is project-based. Write and tell me what you need.
No. I have about 17 years of in-house employer web work. Most of that cannot be shown. Public GitHub is the trail I started in 2025.
WordPress is the specialty. Adjacent work — APIs, React, Power Platform, deploys — is in range because I am a self-taught problem solver with 17 years in-house.
Online
Most of my WordPress code and writing shows up here and on GitHub. RSS is the calmest way to follow along.
Get in touch
Got a question about a post, a project, or a role? Send it over. I usually reply within one business day (ET).
Remote · within one business day (ET)