Skills wordpress-theme-development

📦

wordpress-theme-development

Name: wordpress-theme-development
Author: sickn33

Content revision r2 Safe 🌐 Network access

Build Modern WordPress Themes

Building a complete WordPress theme requires coordinated templates, functions, block support, styling, and testing. This skill provides a phased workflow with practical examples and checklists.

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "wordpress-theme-development" from https://skillstore.io/skills/sickn33-wordpress-theme-development.md and its manifest at https://skillstore.io/api/skills/sickn33-wordpress-theme-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-wordpress-theme-development.md Signed manifest GET /api/skills/sickn33-wordpress-theme-development/manifest Signed lockfile GET /api/skills/sickn33-wordpress-theme-development/lockfile

Test it

Using "wordpress-theme-development". Plan a portfolio theme with projects, services, and a mobile navigation overlay.

Expected outcome:

Theme structure covering shared templates, project archives, service pages, patterns, assets, and translations.
Project content model with categories, sanitized client metadata, REST visibility, and archive behavior.
Responsive navigation plan with keyboard controls, accessible labels, and viewport testing.

Using "wordpress-theme-development". Review an existing theme before adding block editor support.

Expected outcome:

Compatibility assessment for templates, editor styles, theme settings, and registered supports.
Prioritized migration plan for theme.json, patterns, reusable styles, and editor testing.
Validation checklist covering content preservation, accessibility, responsive layouts, browsers, and performance.

Using "wordpress-theme-development". Define testing for a WordPress 7.0 theme upgrade.

Expected outcome:

A focused test matrix covering templates, editor behavior, navigation overlays, patterns, custom content, accessibility, responsive breakpoints, browsers, and performance.

Security Audit

Safe

v5 • 9/7/2026 Open versioned report

All five static findings are false positives in documentation examples. The URLs are metadata or schema references, and the responsive grid text performs no reconnaissance.

Files scanned

521

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (4)

references/detailed-guide.md:60 references/detailed-guide.md:62 references/detailed-guide.md:68 references/detailed-guide.md:117

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-wordpress-theme-development/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-wordpress-theme-development/security.svg)](https://skillstore.io/skills/sickn33-wordpress-theme-development?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-wordpress-theme-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-wordpress-theme-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-wordpress-theme-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). wordpress-theme-development security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-wordpress-theme-development/audits/5

BibTeX citation

@techreport{sickn33-sickn33-wordpress-theme-development-2026,
  author = {sickn33},
  title = {wordpress-theme-development security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-wordpress-theme-development/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wordpress-theme-development security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-09-07"
url: "https://skillstore.io/skills/sickn33-wordpress-theme-development/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-wordpress-theme-development:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Create a First Custom Theme

Follow a phased structure for templates, functions, styles, and block editor support.

Convert a Design System

Map an existing interface into responsive templates, theme settings, reusable patterns, and navigation.

Modernize an Existing Theme

Plan block editor support, custom post types, WordPress 7.0 features, and focused compatibility tests.

Try These Prompts

Plan a Starter Theme

Plan a WordPress theme for [site type]. List required files, template responsibilities, theme supports, menus, assets, and a practical implementation order.

Convert a Responsive Design

Convert this design specification into a WordPress theme plan: [design details]. Map layouts to templates, components, patterns, theme.json settings, and responsive breakpoints.

Add Structured Content

Design a custom post type for [content]. Include taxonomy, supported fields, sanitized REST-visible metadata, archive templates, editor behavior, and migration considerations.

Audit and Modernize a Theme

Review this theme architecture: [details]. Identify template, block editor, accessibility, performance, and WordPress 7.0 gaps. Prioritize changes and define verification steps.

Best Practices

Confirm the target WordPress and PHP versions before selecting APIs or features.
Sanitize stored metadata, escape rendered output, and use WordPress registration APIs.
Test templates, editor behavior, accessibility, responsiveness, browsers, and performance before release.

Avoid

Do not copy example identifiers, URLs, colors, or dimensions into production without review.
Do not place plugin-level business logic in a theme when content must survive theme changes.
Do not claim WordPress version compatibility without testing against that exact release.

Frequently Asked Questions

Does this skill generate a complete installable theme?

It provides a development workflow, examples, and checklists. A complete theme still requires project-specific implementation and validation.

Does it support block themes?

It covers theme.json, block patterns, block registration, templates, and editor behavior. Adapt the workflow to classic, hybrid, or block architecture.

Can it help create custom post types?

Yes. It covers registration, taxonomies, metadata, REST visibility, archive templates, and sanitization considerations.

Is the WordPress 7.0 guidance guaranteed current?

No. Verify version-specific APIs and behavior against official documentation and the exact installed release.

Does it replace security and accessibility review?

No. Use dedicated reviews and automated tests before deploying generated theme code.

What project details should I provide?

Provide the site type, content model, design system, target versions, required plugins, accessibility goals, performance targets, and deployment constraints.