djzeneyer

Review WordPress plugin PHP code for djzeneyer.com. Use when asked to review PRs, diffs, files or snippets touching plugins/, WordPress PHP, hooks, REST routes, settings, admin screens, SQL, sanitization, escaping, capabilities, nonces, PHPCS/WPCS, PHPStan or plugin security.

Secure backend coding for djzeneyer.com, especially WordPress/PHP plugins, REST APIs, auth boundaries, sanitization, escaping, SQL safety, CSP/CORS and public/private data classification.

Use when a WordPress task is ambiguous and you need to route it to the correct workflow/skill: wp-headless, wp-plugin-development, wp-rest-api, wp-performance, wp-wpcli-and-ops, backend-security-coder, codeql-security, auth-implementation-patterns, or frontend skills.

Use when developing WordPress plugins for djzeneyer.com: architecture, hooks, activation/deactivation/uninstall, admin UI, REST integration, settings, cache/transients, security, schema and release packaging.

Cria novos temas sazonais ou de marca para o djzeneyer e os injeta na arquitetura de CSS variables. Use quando o usuário pedir para gerar um novo tema (ex: Halloween, Natal, Verão).

Identidade de marca, tom de voz e diretrizes de copy para Zen Eyer. Usar sempre que criar posts de redes sociais, textos de site, e-mails de newsletter, títulos de músicas, descrições de eventos, bios para imprensa ou qualquer conteúdo público em nome de Zen Eyer ou da Tribo Zen.

Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.

Master skill para navegação no ecossistema Zen Eyer. Ensina o agente a ler a arquitetura de camadas (.context, .agents, .human), respeitar a hierarquia de contexto e preservar a politica publica de IA do site. Use no inicio de tarefas amplas, revisoes de PR, mudancas de contexto ou alteracoes de SEO/IA.

Diagnose SEO, GEO, AEO, crawlability, indexation, machine-readable resources and organic visibility issues for djzeneyer.com. Audit only; do not implement fixes unless requested.

Build and audit Zen Eyer authority signals across E-E-A-T, entity identity, external citations, Knowledge Panel, Wikidata/MusicBrainz/platforms, Zoukology, press/media and topical Brazilian Zouk authority.

Practical clean code and refactoring guidance for djzeneyer.com. Use for code review/refactor quality while respecting project architecture, tests, i18n, SEO/AI surfaces and public/private data boundaries.

CodeQL security patterns for djzeneyer.com. Read before changing HTML sanitization, Markdown generation, React escaping, PHP output escaping, SQL, debug scripts or GitHub security alerts.

React performance and client-side best practices for djzeneyer.com. This project uses Vite 8 + React Router 7, not Next.js/SSR/Server Components. Use for memoization, bundle size, re-renders and client-side data fetching.

React composition, hooks, component boundaries and state patterns for the djzeneyer.com React SPA. Use for component design, not for Next.js, Server Components, SSR or data-fetching architecture decisions.

Design, validate and optimize schema.org JSON-LD for djzeneyer.com, including Person/MusicGroup entity graph, MusicEvent, Article, FAQ, Product, WebSite and AI/search discovery surfaces.

Tailwind CSS v4 patterns for djzeneyer.com: CSS-first theme, responsive layouts, design tokens, reusable components and performance-safe class usage.

TypeScript type safety for djzeneyer.com: React 19, Vite 8, API contracts, schemas, React Query data, route types and safe public/private boundaries. Use for complex types and contracts, not routine UI copy.

Optimize djzeneyer.com web performance across Core Web Vitals, Vite bundles, prerender output, images, caching, runtime React cost and WordPress/API TTFB. Use for performance audits and implementation planning.

Use only when the task explicitly involves WordPress Interactivity API, @wordpress/interactivity, data-wp-* directives, block/template reactivity, or admin/plugin UI that must run inside WordPress rather than the React SPA.

Use when a WordPress/plugin/REST endpoint is slow or cache-heavy in djzeneyer.com: TTFB, admin, REST, WP-Cron, DB queries, autoloaded options, transients, APCu, LiteSpeed, Cloudflare and remote HTTP calls.

Use for deterministic inspection of the djzeneyer.com WordPress/React repo: theme, custom plugins, tooling, tests, PHP/Node version hints and structure changes that should update context files.

Use when creating/updating WordPress REST API routes for djzeneyer.com, debugging auth/permissions, exposing public artist/AI resources, validating schemas, or changing response shape/pagination/cache.

Use when working with WP-CLI or WordPress operations for djzeneyer.com: safe search-replace, DB export/import, plugin/theme management, cron, cache/rewrite flushing, LiteSpeed/Cloudflare-aware ops and automation.

Authentication and authorization patterns for djzeneyer.com, especially ZenEyer Auth, JWT, Google OAuth, WordPress REST permissions, route guards and user/session privacy.

Write clear, credible, conversion-focused copy for landing pages, emails and public pages. In this project, apply `zen-content-voice` first and never fabricate claims.

Consolidates and updates project AI context files after a significant work session. Equivalent to Claude Code's /dream, but aligned to this repository's current context architecture: AI_CONTEXT_INDEX.md, AGENTS.md, .agents/, .context/, .human/ and LEARNINGS.md. Use after meaningful code changes, bug fixes, architectural decisions, SEO/AI discovery changes, or when context files feel stale.

Optimiza titles, descriptions, canonical/OG/Twitter metadata and URL suggestions for djzeneyer.com public pages, using HeadlessSEO/Zen SEO Lite patterns and project voice. Use after content intent is clear, not as a standalone SEO audit.

Create, adapt or analyze social content for Zen Eyer, especially Instagram, TikTok, YouTube Shorts and Zouk community channels. Use `zen-content-voice` first.

Expert in headless/decoupled WordPress architectures. Use for WordPress REST + React SPA integration, JWT auth, CORS, prerender/SSG, cache strategy, and public AI/search resources. For this project, do not default to Next.js, ISR, WPGraphQL, or SSR.

Use when configuring, running, or fixing PHPStan/static analysis for djzeneyer.com WordPress plugins: phpstan.neon, baselines, stubs, WordPress-specific typing and third-party plugin classes.