wp-theme
Skill4 starsChanged 3 days agoMITView on GitHub
Architect, scaffold, and extend enterprise-grade WordPress classic themes. Use when creating a new theme, adding page sections, building templates, wiring enqueues, or integrating front-end libraries (Vite, Tailwind v4, GSAP, Lenis, Tempus, Three.js, swup). Covers style.css header, template hierarchy, functions.php boot chain, manifest-driven enqueue, and the front-end component pattern.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- wpgaurav/WordPress-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- wpgaurav/WordPress-skills★ 19same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- diagnosing-bugsSkill
- domain-modelingSkill
- fixSkill
- frontend-designSkill
- grill-meSkill
- grill-with-docsSkill
- gsap-coreSkill
- gsap-performanceSkill
- gsap-pluginsSkill
- gsap-scrolltriggerSkill
- gsap-timelineSkill
- gsap-utilsSkill
- handoffSkill
- landing-page-conversion-auditSkill
- refactorSkill
- researchSkill
- reviewSkill
- share-learningSkill
- tddSkill
- threejs-animationSkill
- threejs-fundamentalsSkill
- threejs-geometrySkill
- threejs-interactionSkill
- threejs-lightingSkill
- threejs-loadersSkill
- threejs-materialsSkill
- threejs-postprocessingSkill
- threejs-shadersSkill
- threejs-texturesSkill
- to-specSkill
- to-ticketsSkill
- verifySkill
- wp-accessibilitySkill
- wp-accessibility-standardsSkill
- wp-css-standardsSkill
- wp-github-actions-standardsSkill
- wp-html-standardsSkill
- wp-i18nSkill
- wp-js-standardsSkill
- wp-performanceSkill
- wp-php-standardsSkill
- wp-pluginSkill
- wp-security-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 98
Run the canonical 4-step chain — build → format:all:check → phpcs → phpstan, in order, stopping at the first red (see …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
WordPress Classic Theme — Enterprise Architecture
Classic themes (not block themes) that survive Theme Review. Load
docs/wordpress-theme-architecture.md and docs/frontend-stack.md for full references.
Standards questions route to the standards skills: wp-php-standards,
wp-js-standards, wp-css-standards, wp-html-standards (and
wp-accessibility-standards for conformance). Deep GSAP API details come from the
vendored gsap-* skills (official greensock/gsap-skills) on GSAP-specific requests;
their guidance is generic — the house integration rules in docs/frontend-stack.md
(Lenis, Tempus, reduced-motion, manifest enqueue) override it.
Canonical structure
theme-slug/
├── style.css # theme header ONLY (no styles — Vite handles CSS)
├── functions.php # boot loader (load-order sensitive)
├── index.php / front-page.php / page.php / single.php / archive.php / 404.php ...
├── template-parts/ # content-{x}.php parts via get_template_part()
├── configure/ # boot modules (utilities, configure, js-css, acf)
├── acf-json/ # ACF field group sync (save + load paths)
├── src/ # Vite source (scripts/components/*.js, styles/main.css)
├── dist/ # Vite build output (gitignored)
├── languages/ # load_theme_textdomain path
├── vendor/ # composer dev tooling (phpcs, pint) — never runtime deps
├── package.json / vite.config.mjs / composer.json / phpcs.xml
└── .husky/pre-commit # build + format:all:check + phpcs + phpstan gatestyle.css header (required fields)
Theme Name, Theme URI, Author, Description, Version (X.X.X), Requires at least, Tested up to, Requires PHP, License, License URI, Text Domain (slug with dashes), Tags, Domain Path.
functions.php boot chain (order matters)
configure/utilities.php— Vite manifest reader (snoozle_get_vite_manifest()pattern, static-cached), nav class filtersconfigure/configure.php—after_setup_theme: menus, thumbnails, title-tag, html5, textdomain, cleanup (remove emoji/embed/global styles, unused image sizes)configure/js-css.php— manifest-driven enqueue onwp_enqueue_scriptsconfigure/acf.php—acf-json/save/load paths +SS_THEME_DIR_PATHconstant
Each file: if ( ! defined( 'ABSPATH' ) ) { exit; } guard; snoozle_-style prefixes;
function_exists guards where required.
Enqueue (manifest-driven, Vite)
vite.config.mjs:basedefaults to/wp-content/themes/{slug}/dist/(override withVITE_BASEfor subdirectory installs),build.manifest: true, entrysrc/scripts/main.js, code-splitting viarolldownOptions- PHP reads the manifest, enqueues the hashed entry with
['strategy' => 'defer'], rewrites tag totype="module"viascript_loader_tag - Dynamic chunks (
qrcode-*, three-*) load via runtimeimport()— never enqueue them - Fonts/CSS preloaded in
header.phpfrom manifest paths - Dev:
npm run dev(Vite server) +npm run start(build --watch); PHP changes need a browser reload
Front-end component pattern (JS)
New component in src/scripts/components/{name}.js:
export function initComponent() { // guard: element exists?
if ( ! document.querySelector( '.selector' ) ) return;
const prefersReduced = window.matchMedia( '(prefers-reduced-motion: reduce)' ).matches;
if ( prefersReduced ) return;
const ctx = gsap.context( () => { /* anims */ } );
const unsub = Tempus.add( ( { time, deltaTime } ) => { /* loop */ } );
return () => { // cleanup returned for teardown
ctx.revert();
unsub();
};
}Register in src/scripts/main.js (init on DOMContentLoaded, collect cleanups).
Heavy work (Three.js, QR): dynamic import() + IntersectionObserver.
Stack defaults (do not invent alternatives)
- Tailwind v4 CSS-first:
@themetokens +@font-faceinsrc/styles/main.css,@sourcefor PHP template dirs if auto-detection misses them; no tailwind.config.js - Lenis:
autoRaf: false, driven by Tempus{ order: -1 };data-lenis-preventfor nested scrollables; reduced-motion gate - GSAP:
gsap.context()+ revert,matchMediafor reduced-motion,ScrollTrigger.refresh()after fonts/images - swup (optional): re-init + destroy all libs on
content:replace
Verification chain
Run the canonical 4-step chain — build → format:all:check → phpcs → phpstan, in
order, stopping at the first red (see docs/verification-chain.md).
Scaffolding
Greenfield themes → scaffolder agent (templates/theme/). New sections → the
build-section flow inside this skill: read one existing section first, match the house
pattern, ACF fields via get_field(), escape at output, verify chain.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

