admin-ui-changes
Provides a guided process for modifying WordPress admin interfaces and associated logic.
Install
mkdir -p .claude/skills/admin-ui-changes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12829" && unzip -o skill.zip -d .claude/skills/admin-ui-changes && rm skill.zipInstalls to .claude/skills/admin-ui-changes
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when changing WordPress admin pages, menus, templates, and admin JS/CSS.Key capabilities
- →Verify route/menu source in `AIPS_Admin_Menu::add_menu_pages()`
- →Identify controllers providing data to templates
- →Separate business logic into service/controller classes
- →Escape all output for security
- →Verify nonce/capability for state-changing actions
- →Place admin interactions in `ai-post-scheduler/assets/js/`
How it works
The skill outlines a workflow for mapping page ownership, separating concerns, implementing security measures, updating assets, and validating changes for WordPress admin UI modifications.
Inputs & outputs
When to use admin-ui-changes
- →Create new admin menu
- →Update admin CSS/JS
- →Modify admin page templates
About this skill
Admin UI Changes Skill
Use this skill when changing WordPress admin pages, menus, templates, and admin JS/CSS.
Scope
- Admin menus/routes and admin-facing rendering.
ai-post-scheduler/templates/admin/,ai-post-scheduler/assets/js/,ai-post-scheduler/assets/css/, and admin controllers.
Required workflow
- Map page ownership
- Verify route/menu source in
AIPS_Admin_Menu::add_menu_pages(). - Identify the controller that provides data to the template.
- Verify route/menu source in
- Separate concerns
- Put business logic in
ai-post-scheduler/includes/service/controller classes. - Keep templates in
ai-post-scheduler/templates/admin/primarily for rendering.
- Put business logic in
- Security + hygiene
- Escape all output (
esc_html,esc_attr,esc_url,wp_kses_post). - Verify nonce/capability for state-changing actions.
- Escape all output (
- Asset updates
- Place admin interactions in
ai-post-scheduler/assets/js/. - Keep styles in
ai-post-scheduler/assets/css/and reuse existing classes when possible.
- Place admin interactions in
- Validation
- Exercise affected admin pages.
- Run relevant PHPUnit tests for touched controllers/services.
Guardrails
- Do not register menu pages in
AIPS_Settings; useAIPS_Admin_Menu. - Avoid render-time controller reinstantiation patterns.
- Follow plugin style conventions (tabs,
array()).
Useful files
ai-post-scheduler/includes/class-aips-admin-menu.phpai-post-scheduler/includes/class-aips-admin-assets.phpai-post-scheduler/templates/admin/ai-post-scheduler/assets/js/ai-post-scheduler/assets/css/
When not to use it
- →When registering menu pages in `AIPS_Settings`
- →When using render-time controller reinstantiation patterns
- →When not adhering to plugin style conventions
Limitations
- →Admin menus/routes and admin-facing rendering are within scope
- →Templates are primarily for rendering
- →Requires adherence to plugin style conventions
How it compares
This skill provides a structured workflow for modifying WordPress admin UI, ensuring adherence to security and architectural best practices, unlike direct, unguided modifications.
Compared to similar skills
admin-ui-changes side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| admin-ui-changes (this skill) | 0 | 2mo | No flags | Intermediate |
| fullstack-guardian | 1 | 3mo | No flags | Advanced |
| tauri-syntax-permissions | 0 | 4mo | No flags | Intermediate |
| tauri | 0 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
fullstack-guardian
Jeffallan
Use when implementing features across frontend and backend, building APIs with UI, or creating end-to-end data flows. Invoke for feature implementation, API development, UI building, cross-stack work.
tauri-syntax-permissions
OpenAEC-Foundation
>
tauri
BiFangKNT
构建、调试与发布 Tauri v2 应用的工程化工作流。覆盖项目初始化(create-tauri-app)、前端与 Rust 命令通信(`#[tauri::command]` + `invoke`)、状态管理、Capabilities 权限建模、插件接入、跨平台构建与问题排查。当用户需求涉及“创建 Tauri 项目”“把 Web 前端接到 Rust 后端”“最小权限配置(fs/http/shell)”“接入 Tauri 官方插件”“执行 tauri dev/build”“排查 Tauri 构建或运行错误”时使用此 skill。
wordpress-pro
trongquach
Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching a
electron-development
wegonbeok45
Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.
xss-testing
Ed1s0nZ
XSS跨站脚本攻击测试的专业技能