zivtech

Use when you have an existing component, flow, or interface and need an evidence-backed accessibility design review after basic checks pass. Best for focus management, ARIA pattern quality, semantics, and state communication gaps automated tools miss.

Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning requirements into an accessible implementation plan before code hardens bad interaction and state patterns.

Review content for Google AI Overview eligibility — RAG retrievability, E-E-A-T signal completeness, fan-out coverage, semantic HTML for agent parsability, schema markup quality.

Plan AI Overview readiness improvements — RAG retrievability, E-E-A-T signals, query fan-out coverage, semantic HTML, schema markup, agentic channel setup.

Assess organizational AI readiness — capabilities, gaps, adoption roadmap for strategic planning.

Alex Urevick-Ackelsberg's personal writing voice and style. Use this skill whenever writing AS Alex or ghostwriting content that should sound like him — emails to clients, community posts, conference session descriptions, proposals, LinkedIn posts, listserv replies, internal strategy docs, or any communication where Alex is the named author. Also use when Alex asks you to 'write this up,' 'draft a response,' 'help me write,' or when the output needs his voice rather than a generic professional tone. This is Alex's PERSONAL voice — for Zivtech brand/marketing content, use zivtech-writing-style instead (though both can apply when Alex is writing on behalf of Zivtech).

Define brand voice standards — tone, vocabulary, style rules for aligning content teams.

Plan community health needs assessments — data collection, stakeholder engagement, reporting.

Review WordPress performance risks in queries, object cache, autoloaded options, cron, HTTP calls, REST, block rendering, assets, and measurement plans.

Review WordPress security boundaries: capabilities, nonces, sanitization, escaping, SQL, REST permissions, files, secrets, and supply chain.

Review WordPress themes for theme.json correctness, templates, patterns, accessibility, performance, and editor/frontend parity.

Review WordPress performance risks in queries, object cache, autoloaded options, cron, HTTP calls, REST, block rendering, assets, and measurement plans.

Review WordPress security boundaries: capabilities, nonces, sanitization, escaping, SQL, REST permissions, files, secrets, and supply chain.

Review WordPress themes for theme.json correctness, templates, patterns, accessibility, performance, and editor/frontend parity.

Generate WordPress block implementation packets from approved wordpress-block-planner specs.

Generate WordPress Playground Blueprint JSON and reproducible demo/test environment packets from approved specs.

ARRM-based accessibility role audit — responsibility-based review lenses

Deep accessibility review from 7 access perspectives — activated by escalation from a11y-planner or a11y-critic when one or more perspectives are flagged at MEDIUM or HIGH alarm level.

ARRM-based accessibility role audit — runs responsibility-based review lenses (visual design, UX design, front-end dev, content authoring, business analysis, testing) to produce role-attributed findings. Complements the access-method perspectives in perspective-audit.

Orchestrate the a11y accessibility lifecycle: scout → plan → critique → [perspective audit] → test → critique. Dual-mode: full lifecycle automation or step-by-step dispatch. Spawns specialist agents at depth-1 from the main session.

Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning WCAG 2.2 requirements into an accessible implementation plan with WAI-ARIA APG patterns before code hardens bad interaction and state patterns.

Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning WCAG 2.2 requirements into an accessible implementation plan with WAI-ARIA APG patterns before code hardens bad interaction and state patterns.

Evaluate a Drupal accessibility patch end-to-end: baseline evidence, patch hygiene, after-patch verification, manual/AT checks, critic gate, and upstream handoff. Evidence-gated — never VERIFIED without before/after proof under the same conditions.

How to verify changes in this prompt-only repo: reproduce committed evidence-harness recipes from scratch, don't re-run CI. Covers the evals/results/* harness pattern.

Evidence-backed critic for code, plans, and analysis using structured gap analysis, multi-perspective review, calibrated verdicts, and missing-case discovery.

Thorough review of math, data logic, formulas, assumptions, and numerical correctness in code

Evidence-backed critic for plans, proposals, and specs using pre-mortems, assumptions analysis, competing alternatives, backcasting, and calibrated verdicts.

Evidence-backed critic for plans, proposals, and specs using pre-mortems, assumptions analysis, competing alternatives, backcasting, and calibrated verdicts.

Thorough accessibility design reviewer evaluating ARIA patterns, focus management, state communication, and multi-perspective access (screen reader, keyboard, low vision, cognitive). Read-only critic that reviews design decisions, not just test violations.

Plan accessible implementations before coding. 9-phase protocol covering semantic structure, ARIA patterns, focus management, state communication, visual accessibility, content strategy, and testing approach. Companion to a11y-critic.

Plan Drupal implementations (entity types, config schema, migrations, cache strategy, permissions, module architecture) before coding. Use when designing new features, modules, config entities, or migrating existing sites. Produces architecture plans with entity diagrams, module decisions, permission models, cache tags, and migration paths.

Plan React/Next.js/React Native implementations with built-in correctness for state design, render performance, and component architecture. Use before writing any component code.

Execute Drupal configuration changes from drupal-planner specs.

Drupal code, config, and architecture review for PRs, implementations, and migration plans.

Plan Canvas Code Components — definition, metadata, props, data fetching, styling, validation.

Plan Drupal content models — entity types, bundles, paragraphs, field architecture, computed fields.

Plan Drupal search — Search API, Solr/Elasticsearch, faceted search, indexing strategies.

Plan Drupal implementations — entities, config, migrations, cache, permissions.

Plan Drupal taxonomies — vocabularies, term hierarchies, faceted navigation, Views integration.

Plan Drupal themes — base theme, component strategy (SDC/traditional), CSS methodology, responsive design.

Orchestrate the a11y accessibility lifecycle: scout → plan → critique → [perspective audit] → test → critique. Dual-mode: full lifecycle automation or step-by-step dispatch. Spawns specialist agents at depth-1 from the main session.

Evaluate a Drupal accessibility patch end-to-end: baseline evidence, patch hygiene, after-patch verification, manual/AT checks, critic gate, and upstream handoff. Evidence-gated — never VERIFIED without before/after proof under the same conditions.

Use when you have an existing component, flow, or interface and need an evidence-backed accessibility design review after basic checks pass. Best for WCAG 2.2 compliance, focus management, ARIA pattern quality, semantics, and state communication gaps automated tools miss.

Use when you need to run real accessibility tests — Playwright keyboard interactions, axe-core scanning, visual regression, and WCAG 2.2 compliance checks. The measurement layer that feeds evidence into a11y-critic reviews.

Deep accessibility review from 7 access perspectives — activated by escalation from a11y-planner or a11y-critic when one or more perspectives are flagged at MEDIUM or HIGH alarm level.

Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning WCAG 2.2 requirements into an accessible implementation plan with WAI-ARIA APG patterns before code hardens bad interaction and state patterns.

Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning WCAG 2.2 requirements into an accessible implementation plan with WAI-ARIA APG patterns before code hardens bad interaction and state patterns.

Delegate a task to a subagent with its own clean context window. Keeps heavy file reading out of your main session. Use when reading many files, doing codebase audits, or research tasks. Part of claude-cost-helpers (subagent-isolation).

Load the most recent session file and resume work with full context from where the last session ended. Use at the start of a new session after a save-session or split. Part of claude-cost-helpers (idle-tax).

Save session state and recommend starting fresh instead of compacting. A safer alternative to lossy compaction — compaction discards context permanently with no recovery. Part of claude-cost-helpers (compact-gamble).

Save current session state for handoff to a future session. Creates a structured file capturing what worked, what failed, and the exact next step. Use when stepping away, before cache expires, or when context is getting heavy. Part of claude-cost-helpers (idle-tax).

Save current session and split — start fresh to avoid context rot and rising costs. Use when context is heavy (300K+ tokens estimated) or response quality is degrading. Part of claude-cost-helpers (just-one-more-turn).

Run a command and redirect output to a temp file instead of dumping it into context. Returns the file path, line count, and a preview (first/last 10 lines). Use for test runs, build logs, or any command with large output. Part of claude-cost-helpers (watching-cost).

Use when you have a drupal-planner.content-model, .taxonomy, or .search spec and need actual Drupal config YAML generated. Consumes planner output and produces config/install/*.yml files ready for drush config:import.

Plan Drupal content model architectures — entity types, bundles, paragraphs, field architecture, composition patterns, and editorial workflows. Use when designing or redesigning Drupal content structures before implementation.

Plan Drupal search architectures — Search API configuration, Solr/Elasticsearch backends, faceted search with Facets module, Views integration, autocomplete, and content discovery patterns. Use when designing Drupal search before implementation.

Plan Drupal implementations (entity types, config schema, migrations, cache strategy, permissions, module architecture) before coding. Use when designing new features, modules, config entities, or migrating existing sites. Routes to focused sub-planners for content model, taxonomy, theme, and search architecture.

Plan Drupal taxonomy architectures — vocabularies, term hierarchies, faceted navigation, Views integration, and Drupal-specific classification patterns. Use when designing or redesigning Drupal taxonomy structures.

Plan Drupal theme architectures — base theme selection, component strategy (SDC/traditional), CSS methodology, preprocess design, template organization, asset management, and accessibility. Use when designing Drupal themes before coding.

Drupal-specific harsh review orchestration for plans, code, and implementation notes. Use when reviewing Drupal modules/themes/config/deploy workflows, contrib patch decisions, cache behavior, migration plans, Drush/DDEV/Composer updates, or any Drupal change where you need evidence-backed critique. Always run security/new-hire/ops perspectives; activate open-source-contributor, site-builder, and content-editor perspectives when context indicates they will reveal additional fixes.

Create and repair on-brand Drupal presentations using Manus. This skill uses the slide tools to build and fix decks, leveraging the assets and learned best practices from the drupal-brand-skill repo. Use this for creating new presentations or fixing existing ones with Manus.

Review RFCs, ADRs, and architecture decisions with evidence-backed critique.

U.S. labor law scheduling compliance database. Use when answering questions about overtime, meal breaks, rest breaks, predictive scheduling, minor labor, reporting time pay, or split shift regulations across federal, state, and local jurisdictions. Provides structured JSON data for 88 regulations covering all 50 states, DC, and select municipalities.