🔌
Plugins
Loading...
Showing 30 of 15484 results
GIS integration with Leaflet, OpenLayers, PostGIS, and spatial data visualization
Performance optimization with OnPush, bundle analysis, and change detection strategies
Security best practices with XSS prevention, authentication, and OWASP compliance
Comprehensive testing strategies with Jasmine, Jest, Cypress, and Playwright
Twelve-skill bundle covering the Annals of the American Association of Geographers (Annals of the AAG) manuscript lifecycle across the journal's four areas and cross-disciplinary track.
Twelve-skill bundle covering the Annals of Mathematics manuscript lifecycle.
Tournament consensus architecture. N parallel planners with biases, synthesizer blends. Best for novel architecture.
Linear single-pour architecture. One planner, one pass. Fastest of the three. Best for scoped tasks.
Fixed-point deepen architecture. Iterative refinement with variance-based convergence. Best for complex but scoped tasks.
Twelve-skill bundle covering the Annual Review of Economics manuscript lifecycle.
Twelve-skill bundle covering the Annual Review of Psychology invited-review lifecycle.
Twelve-skill bundle covering the Annual Review of Sociology invited-review lifecycle.
Answer Ansible questions and review Ansible code using official documentation. Use when the user asks about Ansible concepts, syntax, best practices, deprecations, or wants Ansible code reviewed against official docs. Use when user says "check my playbook against docs", "what does Ansible say about X", "how do I use module Y", or "review my role". Do NOT use for CoP good practices review (use ansible-good-practices instead). Do NOT use for general Python or YAML questions unrelated to Ansible.
Review Ansible code against Red Hat CoP automation good practices. Use when the user wants to audit, lint, review, check, or validate Ansible roles, playbooks, collections, or inventory for compliance with CoP rules. Use when user says "lint my role", "check my playbook", "review best practices", or "audit my Ansible code". Do NOT use for general Python or YAML linting unrelated to Ansible.
Create Ansible playbooks for configuration management
Scaffold a new Ansible content collection following all Red Hat CoP good practices. Use when the user wants to create, generate, or bootstrap a new Ansible collection. Use when user says "create a collection", "new collection", "scaffold collection", or "init collection". Leverages ansible-creator when available. Do NOT use for reviewing existing collections (use ansible-good-practices instead).
Scaffold a new Ansible execution environment project following good practices. Use when the user wants to create, generate, or bootstrap a new EE. Use when user says "create an EE", "new execution environment", "scaffold EE", or "build EE project". Leverages ansible-creator when available. Do NOT use for building existing EEs or managing containers.
Scaffold a new Ansible role following all Red Hat CoP good practices. Use when the user wants to create, generate, or bootstrap a new Ansible role. Use when user says "create a role", "new role", "scaffold role", or "generate role skeleton". Leverages ansible-creator when available. Do NOT use for reviewing existing roles (use ansible-good-practices instead).
Display the Zen of Ansible principles and review Ansible code against them. Use when the user wants to see the Zen of Ansible, get philosophical guidance on their automation approach, or review code for simplicity, readability, and clarity. Use when user says "zen of ansible", "simplify my playbook", "is this too complex", or "clean code review". Do NOT use for strict rule compliance (use ansible-good-practices instead).
Document processing (Excel, Word, PowerPoint, PDF) and example skills (design, MCP builder, web artifacts).
Anthropic official skills — document generation (PDF, DOCX, PPTX, XLSX), web app building, frontend design, MCP server building, brand guidelines, internal comms, and more
Verify-first discipline for Claude Code. SessionStart injects the full Iron-Law protocol (rationalization table + rule K output-presentation), the always-on SCOPE & FIDELITY discipline (simplest sufficient solution; intent over letter; confirm before expanding scope; match rigor to blast radius; finish asked work / drop nothing), and a skill primer, re-injecting after compaction; a per-turn nudge keeps it salient. Always-on guards: api-guard (blocks fabricated stdlib/builtin APIs in code by verifying against the installed python3/node; opt-in 3rd-party), git-guard (blocks force-push + AI/assistant self-credit in commit trailers AND gh pr/issue/release bodies), command-guard (delegate heavy commands off the coordinator), swarm-guard (anti-fork-bomb), speculation guards, and task-guard + tasklist-guard (task-list + progress-file discipline) — all with a user-override escape hatch. Also ships an opt-in mcp-reaper companion (macOS + Linux) that kills ONLY orphaned MCP-server processes (Windows is a documented no-op). Skills: root-cause debugging, orchestration, deadly-loop + deadly-loop-multi review, ship-it, install-statusline, and doctor. Pure Node, zero dependencies, runs unchanged on Windows/macOS/Linux, Node >= 18.
Anti-hallucination guidelines for Claude Code based on Anthropic's research.