ansible-automation-eng…
Ansible automation: playbooks, roles, collections, Molecule testing, Vault security.
**Scope**: Task-to-agent routing table; capabilities and boundaries per agent.
$ npx -y skills add notque/vexjoy-agent --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
**Scope**: Task-to-agent routing table; capabilities and boundaries per agent.
> **Scope**: Task-to-agent routing table; capabilities and boundaries per agent.
---
| Task Type | Primary Agent | Fallback | Avoid | |-----------|--------------|----------|-------| | Go source code | `golang-general-engineer` | — | general-purpose | | TypeScript backend API | `nodejs-api-engineer` | `typescript-frontend-engineer` | general-purpose | | TypeScript frontend/React | `typescript-frontend-engineer` | — | nodejs-api-engineer | | Python scripts/data | `python-general-engineer` | `python-openstack-engineer` | general-purpose | | Database schema/migrations | `database-engineer` | — | application agents | | Kubernetes/Helm | `kubernetes-helm-engineer` | — | ansible-automation-engineer | | Ansible playbooks | `ansible-automation-engineer` | — | kubernetes-helm-engineer | | OpenSearch/Elasticsearch | `opensearch-elasticsearch-engineer` | — | database-engineer | | Prometheus/Grafana | `prometheus-grafana-engineer` | — | — | | Swift iOS/macOS | `swift-general-engineer` | — | — | | Kotlin Android/JVM | `kotlin-general-engineer` | — | — | | PHP backend | `php-general-engineer` | — | — | | React Native / Expo | `react-native-engineer` | — | typescript-frontend-engineer | | Code review | `reviewer-code-playbook` | `reviewer-system-playbook` | — | | Security audit | `security-threat-model` | — | — | | Performance | `performance-optimization-engineer` | — | — | | Documentation | `technical-documentation-engineer-playbook` | — | — |
Verify agent exists: `ls ~/.claude/agents/ | grep {agent-name}`
---
**golang-general-engineer**: CAN modify `.go` files, run `go build/test/vet`, add packages, fix linting. CANNOT modify non-Go files, make architectural decisions, run migrations.
**nodejs-api-engineer**: CAN do REST endpoints, middleware, auth, webhooks, DB integration. CANNOT do frontend components, native code, infrastructure.
**database-engineer**: CAN do schema design, migrations, indexes, query optimization. CANNOT do application code. **Mandatory sequencing**: database agent ALWAYS before application agents on schema changes.
**performance-optimization-engineer**: CAN do Core Web Vitals, bundle analysis, rendering optimization, profiling. CANNOT fix unrelated logic bugs.
---
1. database-engineer → schema migration 2. nodejs-api-engineer → endpoint (parallel with 3 if no shared types) 3. typescript-frontend-engineer → UI 4. reviewer-code-playbook → full-stack review
1. performance-optimization-engineer → profile, identify hotspot (read-only) 2. golang-general-engineer → fix 3. golang-general-engineer → benchmark validation
1. kubernetes-helm-engineer → Helm chart (parallel with 2 if isolated) 2. ansible-automation-engineer → provisioning 3. Application agent → smoke test
---
**Signal**: Dispatching undefined subagent_type for Go errors. **Fix**: Look up task type in routing table, specify exact `subagent_type`.
**Signal**: TypeScript backend work sent to frontend engineer. **Fix**: Check imports — `express`/`@nestjs`/`fastify` → nodejs-api-engineer. `react`/`next` → typescript-frontend-engineer.
rg "import.*express|import.*@nestjs" --files-with-matches src/ # → backend rg "import.*react|import.*next" --files-with-matches src/ # → frontend
**Signal**: Asking nodejs-api-engineer to add a column. **Fix**: database-engineer first for migration, then application agent for ORM models.
---
.go files? → golang-general-engineer TypeScript backend/API? → nodejs-api-engineer TypeScript frontend/React? → typescript-frontend-engineer Database schema? → database-engineer (first, before app agents) K8s/containers? → kubernetes-helm-engineer VM provisioning? → ansible-automation-engineer Performance? → performance-optimization-engineer Code review? → reviewer-code-playbook Otherwise? → Check agents/ for domain match → general-purpose as last resort
Essays and writing behind this toolkit live at vexjoy.com. VexJoy Agent connects plain-English requests to specialist agents, skills, and workflows. /do selects the knowledge and tools needed for your task.
Repo: notque/vexjoy-agent
Ansible automation: playbooks, roles, collections, Molecule testing, Vault security.
**Scope**: Module selection patterns, builtin vs command/shell decisions, collection modules, and version-specific module changes **Version range**:…
**Scope**: Molecule test scenarios, ansible-lint rules, idempotency validation, and check-mode patterns **Version range**: Molecule 6.0+ / ansible-lint 6.0+ /…
Universal rules injected by /do at dispatch. Each agent's .md file supplies domain rules.
**Scope**: Failure modes in agent output style — over-reporting, self-congratulation, verbose narration, and hedging. Covers what to detect and how to fix…
Zero-dependency combat visual upgrades: CSS particle replacement, Framer Motion combat juice, CSS 3D card transforms.