🔌
Plugins
Loading...
Showing 30 of 27329 results
Build a WordPress block theme (FSE) from a canonical, self-validating starter.
WordPress / CMS engineering team — 3 agents (wordpress-architect, wordpress-developer, wordpress-ops-engineer) for building, extending, and operating WordPress done right: the build-approach decision (classic vs block/FSE theme, plugin vs theme vs must-use, headless/decoupled vs traditional, single vs multisite), secure block & theme & plugin development (block.json, hooks/filters, WP_Query, the REST API, sanitize-in/escape-out, $wpdb->prepare, nonce + capability checks), and operations (page + object cache/Redis, security hardening, safe updates with staging & backups, migrations). 5 skills, a decision-tree knowledge bank (4 Mermaid trees + a dated 2026 stack map), 8 best-practices, 3 templates, 3 commands, 1 advisory hook. Seams: decoupled front-end -> frontend-engineering, non-WP backend/APIs -> backend-engineering, infra perf budget -> performance-engineering, formal security verdict -> security-engineering. Requires ravenclaude-core@>=0.7.0.
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, and optimizes performance through caching and query tuning.
work — general-purpose work across the fleet, not just code. `/work:loop` is the unattended multi-project drain: spreads load with agents teams + balanced accounts, uses browser/computer/secrets for non-coding, drives each item to landed, merging engineering PRs on green behind a non-author review. Its `triage` mode (`/work:loop triage`) instead forces every open board item to keep-and-schedule-this-cycle or cancel, never a hedge state. `/work:dispatch` is ONE unit of work (coding or not) routed to the right executor. `/work:demo` (top-level alias `/demo`) is the post-ship capstone: recover the original intent, exercise the shipped thing in its REAL environment on real representative inputs signed in as the owner, put before/after side by side with a measured delta, and deliver an analyzed report. Kind-agnostic layer above `code:loop`.
Hooks, Subagents, ClickUp/Slack-Integration, 3-Layer-Eskalation für Empire-Apps.
Cross-session memory for long-running work: append-only diary (LOG) and decision (DEC) logs under .claude/memory, grouped by work item (JIRA-123, RFC-7, …), with derived open-item tracking so any later session can answer what is still pending, what changed on a ticket, and what was done since a date. Ships its own clock-in/clock-out protocol via a UserPromptSubmit hook.
Evidence-linked work objects — one work/<id>-<slug>/ dir per code-change task holding spec, captured diff, captured test output, run manifest, and review; in-review/approved transitions are gated by a checker script and enforced by a PreToolUse hook.
Track-aware daily planning over GitHub issues. Shared tracks (git-synced .work-plan/) optionally pinned to a canonical plan branch (plan-branch; push-track promotes a private track to it), AI clustering (group/auto-triage), coverage, plan-status doc liveness with drift detection, batched GraphQL fetches, and dependency-aware next-up with per-track ordering presets. Includes a theme-aware, accessible VS Code viewer — sidebar tree with a visibility×tier exposure badge, a repo-qualified Mermaid dependency graph, per-issue in-progress badge/toggle and dependency chips, next-up controls, proactive auto-slot suggestions with a compare-and-swap collision guard, and a Plans view with confirm-gated frontmatter writes and repository-contained plan links. Installer ownership is content-verified so unmanaged or modified launchers are preserved.
Git-native work tracking shared by Claude and Codex, with root, Salesforce delivery, and existing engagement paths, deterministic status, handoffs, relationships, Git landing verification, generated dashboards, and optional GitHub Issues and Projects synchronization.
Triage open PRs and issues after completing epics — identify abandoned, superseded, or stale work items and recommend close/update/keep
Orchestrated /work command with pre-computed action plans
Set up and maintain a Claude Code workspace: initialize project-side configuration, check and update Toolshed plugins, diagnose local health, and run retrospectives.
The complete Workshop toolkit — every skill, agent, methodology doc, and safety hook in one package. Plan, build, and ship with the full first-party dev workflow on Claude Code, Codex, and Cortex Code.
BuJo ritual system: daily, weekly, monthly, and yearly interactive reflections in Apple Notes. Scheduled rituals with on-demand slash commands.
Core infrastructure: persistent agent identity, session lifecycle hooks, operational memory, and meta skills. Customizable agent name and memory path.
The Index-driven dev pipeline: Inspector Lestrade (triage), Dr. Watson (dev work), and Sherlock Holmes (code review) as subagents. Interactive or unattended dispatch.
Generate a prioritized morning workday report with GitHub PRs and Jira issues grouped by priority
Review and author Cloudflare Workers code against production best practices and common anti-patterns.
Day-to-day control: enforces the layer (hooks/routing) and produces trend reports. Depends on the other two.