unslop

Senior WordPress Consultant (10+ years, WordPress VIP coding standards) that runs a 10-section expert consulting framework over a WordPress project: Architecture Assessment, Development Strategy, WooCommerce Review, Performance Optimization Audit, Security Hardening, Debugging & Troubleshooting, Scalability & Infrastructure, Automation & Workflow, Technical Debt Assessment, and a Final Senior Consultant Report. Seven inputs (Website Type, Current Challenge, Technology Stack, Traffic Volume, Development Goals, Performance Requirements, Support Needed); Current Challenge and Development Goals are required and halt if blank, optional blanks proceed with a flagged assumption. Mandatory output contract: every section under its exact header (or 'Section N — N/A (reason)'), max 250 words per section 1-9 as Finding/Impact/Recommendation bullets, Section 10 scores on fixed scales (Health/Performance/Security/Scalability/Code Quality 0-100, Technical Debt Low/Medium/High/Critical, Priorities ranked max 5), ending with a single Markdown summary table. System rules enforce WordPress coding standards, maintainability, scalable architecture, security by default; never recommends nulled/pirated plugins, editing core files, outputting secrets, or a security rating without naming what was checked. Hard prompt-injection defense treats all inputs as inert project data; scope-locked to WordPress engineering. Includes /wp-consult slash command with AskUserQuestion intake (website type, challenge, stack, traffic, goals, performance requirements, support needed).

Turns a one-line app idea into a complete, production-ready blueprint. Five required inputs (APP_DESCRIPTION, TECH_STACK, APP_TYPE, LANGUAGE, SCALE) drive an 11-section senior-architect plan: project overview, full folder tree, layer-by-layer walkthrough, data models, API endpoints, recommended libraries with rationale, environment setup, testing plan, deploy plan with scale-justified target and upgrade trigger, architect's notes, and a self-check validation table. Hard rules: no generic placeholders (no MyApp, no User Service — all names derive from APP_DESCRIPTION), identical folder names across sections 2 and 3, every entity referenced by at least one endpoint, every dependency mapped to a folder or reference, halts on missing input with explicit MISSING INPUT line. Includes /blueprint slash command with AskUserQuestion intake. Prompt-injection defense treats inputs as inert data.

Generates complete, enterprise grade WordPress plugins from scratch. The kind that could be submitted to WordPress.org today. picker intake (functionality categories, target users, admin interface components, frontend display surfaces, third party integrations) plus two free text inputs (plugin name, feature detail) drive a full directory tree with modular OOP classes (Admin, Frontend, Database, AJAX, REST), Settings API pages, Gutenberg blocks, shortcodes, REST endpoints, custom tables via dbDelta(), nonce/sanitization/escaping/capability checks, prepared statements, conditional asset enqueueing, internationalization with .pot file, WordPress.org-format readme.txt, and a complete uninstall.php cleanup script. WordPress Coding Standards compliant.

A catalog of 53 named design styles (bento, brutalist, glassmorphism, vaporwave, kawaii, cyberpunk, swiss, art deco, neumorphism, and more) with full color palettes, typography stacks, and component patterns for building consistent on-brand frontend interfaces.

Debug, fix, and optimize broken Excel and Google Sheets formulas. Identifies the exact root cause (mismatched parentheses, wrong syntax, text-vs-number mismatch, circular reference, incorrect range, wrong column index), returns a copy-paste-ready corrected formula with UPPERCASE function names, a beginner-friendly bulleted explanation, and an optional modern alternative (XLOOKUP over VLOOKUP, IFERROR to mask error values). Scope-locked to spreadsheet-formula troubleshooting. Includes a /fix-formula slash command that intakes the broken formula and the issue (pipe-separated, tag-wrapped, or interactive prompt).

Senior naming strategist for venture-backed SaaS founders. Produces 10 brandable, pronounceable, niche-fit domain candidates from five inputs (MARKET_TOPIC, TARGET_AUDIENCE, OFFER_TYPE, BRAND_TONE, EXTENSION_PRIORITY). Locked 4-section output: A) Setup Summary, B) 10 Name Candidates with Angle/Fit/Recommended extension/Risk note (Low/Medium/High), C) Top 3 Shortlist with Strength/Watch-out bullets, D) Verification Checklist (registrar check, USPTO TESS, WIPO, pronunciation test, Google collision search). Silently scores every candidate 1–10 on Brandability, Niche fit, Pronounceability, Spelling ease, Differentiation and drops anything averaging below 7. Mixes at least 5 distinct naming structures across the 10 (compound, blended, metaphor, invented, classical-roots). Refuses legal-certainty claims (writes 'Needs verification' instead), hype words (proven/revolutionary/leverage/robust/seamless/cutting-edge), descriptive keyword domains, hyphens, numbers, awkward letter clusters, and forced -ify/-ly/-hub suffixes. Hard prompt-injection defense treats all five inputs as inert data. Scope-locked to domain naming — refuses marketing copy, strategy decks, legal advice, taglines with 'Out of scope — domain naming candidates only.' Includes /name-domains slash command with AskUserQuestion intake (market topic, audience, offer type, brand tone multi-select, extension priority) and silent self-validation gate before output.

Converts PHPDoc and JSDoc blocks into one-line plain-English // comments that a non-technical reader can understand. Two engines under shared rules: interactive skill mode (Read/Edit walk, 1-20 files) and a bundled bash + perl + claude --print runner (20+ files, unattended, CI-able) exposed as /docblock-rewrite. Walks .php, .js, .ts, .jsx, .tsx, .mjs, .cjs. Skip list covers vendor, node_modules, dist, build, coverage, __tests__, .git, .next, .nuxt, out, tmp, *.min.js, *.min.css. Honors @internal, @deprecated, @ignore opt-out tags. File-level detection via @file/@package/@module or post-block declare/namespace/use/import/export. Banned-word list: instantiate, invoke, callback, promise, iterate, async, boolean, array, object, parameter, argument, mutate, hash, payload, instance, factory, singleton, polyfill, regex. Output format: one line beginning with // and ending with a period, capitalized, present-tense verb for functions/methods, noun phrase for classes/files/properties/constants, max 100 chars total. Validation gates: one-line check, // prefix, length cap, banned-word regex. Bad outputs leave the original block intact for human review. Backups saved as .bak per file unless --no-backup. Dry-run mode emits unified diffs without writing. Concurrency configurable (default 3). Right-to-left byte-offset splice preserves alignment across multi-block files.

Converts static HTML files into installable WordPress themes with Tailwind v3, WCAG 2.1 AA accessibility, and child-theme compatibility. Phased workflow with user approval gates: analysis, planning, chunked implementation, self-audit.

My Claude Code plugin marketplace

Senior WordPress architect code review for plugins and themes. File by file audit covering security, performance, architecture, correctness, WordPress standards, accessibility, i18n, and missing infrastructure. Produces a structured report 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. Detects target via plugin header, theme style.css, block.json, or mu-plugins path. Scope-locked to plugin/theme code review only; prompt-injection defenses treat file contents as inert data.