Best Codex skills for WordPress: a reviewed starter set

WordPress work crosses content, blocks, themes, plugins, PHP, styles, JavaScript, caching, and browser behavior. The collection helps keep those responsibilities visible. It is designed for an existing site where content, URLs, and editor ownership need to survive the change.

The set contains four complementary skills: project brief, rendered layout review, block compatibility review, and accessibility evidence review. Use only the skills needed for the current task.

Use the project-brief skill when the request names a goal but leaves the visible result unclear. It turns words such as cleaner or more modern into page locations, expected behavior, preservation constraints, and observable checks.

A brief is especially useful before a shared template change. It identifies which routes need direct testing and which existing content must remain editable.

Use the layout review for hierarchy, reading width, card density, responsive behavior, and interaction states. It asks which layer owns a defect before proposing a fix and requires a second shared view to be checked after a common CSS or template change.

Use the compatibility skill when a saved block looks different in the editor and frontend, a plugin update changes markup, or a theme override makes a block hard to edit. The expected output identifies the registered block, saved attributes, rendered markup, owning stylesheet, and the smallest compatible correction.

Use the accessibility skill for keyboard reachability, focus visibility, landmark and heading structure, labels, alternative text decisions, zoom and narrow-layout checks. It records automated and manual evidence separately and avoids claiming conformance from a single scanner.

These packages are selected because their scopes complement one another and their files pass the AboutCodex package checks. Package structure does not establish that a workflow fits every theme, builder, or plugin stack. Review each skill, adapt it to the site, and record the client and cases you actually tested.

• Browse the WordPress collection
• Codex for WordPress
• Read the WordPress plugin case study

AboutCodex does not rank these skills by download requests. The current starter label reflects editorial fit, inspectable instructions, limitations, and structural checks. Future workflow-tested labels should include the tested site, task, date, observations, and failures.

Begin with the project brief when the request is subjective or spans several WordPress surfaces. It turns phrases such as “make this page better” into a page list, intended reader action, constraints, and observable checks. Move to the layout review after the intended behavior is clear. Add block compatibility when saved markup, third-party blocks, or the editor can be affected. Add the accessibility review for headings, controls, forms, focus behavior, and reading order.

The skills can be used separately, but the sequence matters on a complex change. A visual correction can hide a block ownership problem, and a front-end screenshot cannot prove that the editor remains usable. Preserve the theme and plugin boundaries already present in the project, test one shared view after changing a shared selector, and keep screenshots or measured observations with the handoff.

• Download WordPress skills
• Read the WordPress workflow case study

Evaluate each skill on a small representative task before trusting it on a broad redesign. Give it a real page, a stated viewport, and one clear defect. A strong result identifies the owning layer, proposes a focused correction, and records what was rendered or parsed. A weak result repeats generic design advice, replaces editable blocks with opaque markup, or treats a single desktop screenshot as responsive evidence.

Keep the package review label honest. AboutCodex checks that each ZIP has valid frontmatter, the expected folder, and inspectable files. That establishes package structure. Workflow-tested status should require repeated tasks, recorded inputs, concrete outputs, and a review date. Readers should be able to understand that difference before downloading.