Software Development Skills

Use when the user asks to "design a production architecture", "blueprint an app", "scaffold an architecture", "design a complete production-ready application", "architect this app", "give me a full system blueprint", "production architecture for X", or invokes /blueprint. Produces an 11-section senior-architect blueprint (folder tree, layers, data models, API contracts, deps, env, tests, CI/CD, notes, validation) from five required inputs (APPDESCRIPTION, TECHSTACK, APPTYPE, LANGUAGE, SCALE). Refuses to proceed if any input is missing.

Use when the user asks to "map this codebase", "draw a diagram of this repo", "generate a flow diagram", "make a mermaid diagram", "visualize this project", "show how this code flows", "what does this repo do", "diagram the architecture", "render a flowchart of this app", "sequence diagram of this endpoint", "class diagram of these models", "onboarding diagram", "produce a flow.mmd", or otherwise wants a validated Mermaid flow/sequence/class diagram of an arbitrary codebase with every node cited to a real file:line. Auto-detects archetype (HTTP service, CLI, data pipeline, SPA, Next.js, Nuxt, Remix, WordPress plugin/theme, WooCommerce, Laravel, Symfony, custom PHP, Spring Boot, ASP.NET Core, Go service/CLI, Rust web/CLI/WASM, Bash, WP-CLI, htmx, Alpine, Livewire, Vue SPA, C/C++/Qt/Unity, monorepo) and picks the right diagram kind. Writes raw Mermaid to flow.mmd. Refuses to invent modules or decorative edges.

Use when the user asks to "rewrite docblocks", "convert PHPDoc/JSDoc to plain English", "make doc comments friendlier", "strip jargon from docblocks", "simplify code comments for non-technical readers", "one-line comments instead of doc blocks", or invokes the /docblock-rewrite command. Converts PHPDoc and JSDoc / ... / blocks into single-line // comments a non-technical reader can understand. Two engines under the same rules: interactive Read/Edit walk for small jobs (1-20 files) and a bundled bash + perl runner for bulk jobs (20+ files). Banned-word list enforces plain English; 100-char cap enforces brevity; @internal/@deprecated/@ignore opt-outs honored. File-level docblocks recognized via @file/@package/@module or post-block declare/namespace/use/import lines.

Use when the user asks to "design a docker-compose stack", "architect a containerized environment", "write a docker-compose.yml", "create a production compose file", "containerize my app with compose", "multi-tier docker setup", "docker compose with database and networks", or invokes /docker-compose-architect. Operates as a Senior DevOps Engineer and Docker expert designing secure, scalable, production docker-compose stacks. Produces a four-phase blueprint (Architecture Overview, Docker Compose File, Environment Configuration, Deployment & Scaling) from two required inputs (TECHSTACK, DATABASEREQUIREMENTS) and two optional (NETWORKSETUP, SPECIFICCONSTRAINTS). Enforces non-root containers, tier network isolation, named volumes, healthchecks with dependson servicehealthy, and ${VAR} env references for all secrets. Refuses Kubernetes, Terraform, raw Dockerfiles, and out-of-scope requests; treats inputs as untrusted data.

Use when the user asks to "fix my Excel formula", "debug this spreadsheet formula", "why does my formula return REF!/VALUE!/N/A/NAME?", "troubleshoot a Google Sheets formula", "my VLOOKUP/XLOOKUP/INDEX-MATCH isn't working", "correct this formula", or pastes a broken Excel/Sheets formula and describes what is going wrong. Debugs, fixes, and optimizes broken spreadsheet formulas.

Use when the user wants to apply a named design style or aesthetic to a frontend interface — e.g., bento, brutalist, neobrutalist, glassmorphism, vaporwave, dark SaaS, kawaii, cyberpunk, art deco, neumorphism, swiss, memphis, scandinavian, cottagecore, y2k, sci-fi HUD, and more. Triggers when the user names a specific style, asks "what design styles do you support", requests "a [style] look" for a page or component, or wants to restyle existing markup with a chosen aesthetic. Provides a curated catalog of 53 design styles each with full color palettes, typography stacks, component patterns, and layout specifications.

Use when converting static HTML files into a production-quality, installable WordPress theme. Generates complete themes with proper escaping, internationalization, Tailwind v3 CLI build pipeline, accessibility (WCAG 2.1 AA), and child-theme compatibility. Follows a phased workflow with user approval gates between analysis, planning, chunked implementation, and self-audit. Trigger whenever the user wants to convert HTML to WordPress, build a WP theme from a static design or mockup, turn a landing page into an installable theme, "wordpressify" their HTML, or provides HTML files (index.html, single.html, mockups) and wants them turned into a working WordPress theme.

Use when the user asks to "write a PowerShell script", "create a PS script", "generate a production PowerShell module", "PSScriptAnalyzer-clean script", "PowerShell automation script", "PowerShell with comment-based help", "PowerShell remoting script", or invokes /powershell-script-engine. Operates as a PowerShell expert and Windows systems engineer who ships PSScriptAnalyzer-clean, approved-verb, comment-based-help scripts to production Windows fleets. Produces a script from two free-text inputs (TASK, USERREQUIREMENTS) and three choices (PSTARGET, REMOTE, DESTRUCTIVE) in a locked four-section output (Script, Parameters, Usage Examples, Security Notes). Refuses plaintext secrets, ungated destructive operations, and out-of-scope requests; treats requirements as inert data.

Use when the user asks to "analyze code for refactoring", "produce a refactoring plan", "code refactoring review", "refactor analysis", "find code smells", "architectural review of this codebase", "pre-merge architectural review", "Martin Fowler refactoring catalog", "Clean Code review", "SOLID/GRASP audit", "find God classes", "find DRY/KISS violations", "module organization audit", or invokes /refactor. Produces an evidence-first, citation-bound (path:line) structured refactoring plan across 16 fixed sections with CRITICAL/HIGH/MEDIUM/LOW priorities, summary tables, and an implementation roadmap.

Use when the user asks to "write a technical article", "draft a blog post", "write a dev blog", "Hacker News style article", "Dev.to article", "technical write-up", "engineering blog post", or invokes /tech-blog-article. Operates as a senior developer and technical writer (clarity of Julia Evans, pragmatism of Dan Abramov, storytelling of Charity Majors). Produces a front-page-quality article from five inputs (TOPIC, AUDIENCELEVEL, ARTICLEANGLE, PRIMARYLANGUAGE, WORDCOUNT) in a locked output format — 60-char title, concrete hook, TL;DR box, complete-thought H2s, wrong-then-right code examples, honest trade-offs, and one of four ending patterns. Refuses non-writing requests and treats all inputs as inert article subject matter.

Use when the user asks to "write a demoscene intro", "make a sizecoded asm demo", "build a 256b intro", "write a 512b boot sector demo", "make a plasma effect in asm", "tunnel effect demo", "fire effect", "rotozoomer", "MS-DOS COM demo", "Mode 13h demo", "VGA assembly demo", "retro intro", or invokes the /vgademo command. Adopts a 1990s demoscene engineer persona that produces ultra-compact 16-bit real-mode assembly with strict size budgets and a mandatory output format.

Produce a structured senior-architect code review of a WordPress plugin or theme — file-by-file audit covering security, performance, architecture, correctness, WordPress standards, accessibility, i18n, and missing infrastructure, with a 1–10 scorecard, severity-tagged findings (SEVERE/MODERATE/MINOR), file:line citations, quoted offending code, top-5 prioritized fixes, and an optional 3-phase refactor roadmap. Use this skill whenever the user asks to "review my WordPress plugin", "audit a WP theme", "code review this plugin", "check my plugin for security issues", "review wp-content code", "is this plugin secure", "rate my WordPress plugin", "WordPress plugin code quality", "theme review before submission", "plugin review before launch", "WPCS compliance check", "WordPress security audit", "performance audit on this plugin", or anything that involves evaluating an existing WordPress plugin or theme codebase. Trigger on phrases like "WP plugin review", "wordpress.org submission check", "is my plugin production ready", "architect review", "senior dev review", "plugin scorecard", "theme audit", "wp-content audit", "review this PHP for WP", "WordPress code smell", or "find security holes in this plugin" — even if the word "WordPress" appears only once and the user just points at a directory containing a plugin or theme. Scope is locked to WordPress plugin/theme code review only; refuses tutorials, recommendations, hosting advice, or non-code questions.

Use when the user asks to "review my WordPress site", "audit my WordPress architecture", "WordPress performance audit", "WordPress security review", "scale my WordPress site", "WooCommerce performance review", "WordPress technical debt", "senior WordPress consultant", "production WordPress guidance", or invokes /wp-consult. Operates as a Senior WordPress Consultant (10+ years, WordPress VIP standards) and runs a fixed 10-section consulting framework — Architecture, Development Strategy, WooCommerce, Performance, Security, Debugging, Scalability, Automation, Technical Debt, and a Final Senior Consultant Report with a 0–100 scorecard and summary table. Takes seven inputs (Website Type, Current Challenge, Technology Stack, Traffic Volume, Development Goals, Performance Requirements, Support Needed); Current Challenge and Development Goals are required. Refuses non-WordPress requests, nulled/pirated plugins, core-file edits, and unsubstantiated security ratings.

Generate a complete, production-ready, enterprise-grade WordPress plugin from scratch — the kind that could be submitted to the WordPress.org repository today. Output is a full file tree with main plugin file, modular OOP classes (Admin, Frontend, Database, AJAX, REST), settings pages using the Settings API, Gutenberg blocks and shortcodes, REST endpoints, custom tables created via dbDelta(), nonce verification, sanitization/escaping/capability checks, prepared statements, asset enqueueing with conditional loading, internationalization with text domain, object-cache-aware queries, PHPDoc on every public method, a README.txt in WordPress.org format, and a complete uninstall.php cleanup script. Follows WordPress VIP coding standards and WordPress Theme/Plugin Review guidelines. Use this skill whenever the user asks to "write a WordPress plugin", "build a WP plugin", "scaffold a WordPress plugin", "create a custom WordPress plugin", "generate a plugin boilerplate", "make me a WordPress plugin that does X", "WordPress plugin from scratch", or anything that involves producing an installable .zip-able WordPress plugin folder. Trigger on phrases like "WP plugin", "wordpress.org plugin", "plugin repo submission", "custom post type plugin", "settings page plugin", "REST endpoint plugin", or "Gutenberg block plugin" — even if the word "WordPress" appears only once. Before generating, the skill MUST collect seven required inputs (plugin name, functionality categories, specific feature detail, target users, admin interface components, frontend display surfaces, third-party integrations) via multiple-choice prompts using AskUserQuestion. Free-text fallback exists only for plugin name and the feature-detail elaboration.