Showing 30 of 15102 results
Behavioral guidelines that reduce common LLM coding mistakes via four principles: Think Before Coding, Simplicity First, Surgical Changes, and Goal-Driven Execution.
from pluginagentmarketplace/custom-plugin-android
Set up and manage React Native (Expo/EAS) Android releases via GitHub Actions: local EAS build, version bump from tag, and Google Play internal-track submit
Channel plugin for Android Remote Control MCP โ receives device events and pushes them into Claude Code sessions.
AndThen workflow system: structured agentic development from requirements to shipped code
Router-First architecture, enterprise patterns, modular design with lazy loading
Modern Angular development with standalone components, Signals, and RxJS patterns
from pluginagentmarketplace/custom-plugin-angular
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
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.
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