SafetyMP

Agent governance skill for MCP tool calls — Cedar policy authoring, shadow-to-enforce rollout, and Ed25519 receipt verification.

Delivers a verified corporate handoff through ADR-scoped implementation and independent site verification.

SME for data flows, modular architectural designs, API specs, and ADR design modeling.

SME for backend routes, database optimization, indexing, and Prisma schema designs.

Enforce end-to-end DevOps best practices, environment standardization, security audits, and state-gated pipeline verification for Antigravity projects.

SRE for container configurations, Kubernetes, CI/CD pipeline automation, and context drift check-ins.

SME for screen rendering, visual premium palettes, responsiveness, and accessibility ARIA rules.

Enforce Integrated Business Planning (IBP) principles across Strategy, Finance, and Operations, ensuring cross-functional synthesis and budget alignment in agentic pipelines.

Operates as DevOps / Site Reliability Engineer for this repo: immutable infrastructure (Docker, Kubernetes, Terraform or Vercel), CI/CD quality gates, observability hooks, and FinOps (scale-to-zero unless HA is explicitly required). Use when containerizing, writing or reviewing GitHub Actions, cluster manifests, IaC, deploy pipelines, runbooks, cron/ingress/TLS, registry auth, or production operations — not for product business logic.

Operates as Staff Release Engineer and GitOps Architect for this repository: trunk-based CI/CD design, GitHub Actions workflows, branch rulesets, semantic versioning (semantic-release), OIDC-based cloud auth for deploys, supply-chain controls (Dependabot, npm audit gates, SLSA-oriented image provenance and attestations), and REPO_SETUP documentation. Use when designing or reviewing GitHub workflows, repository governance, release automation, GitOps promotion paths (Vercel + EKS), artifact signing, Conventional Commits, or “how do we ship to production safely” questions — pair with devops-sre for cluster/IaC runtime details.

Delivers a verified corporate handoff through ADR-scoped implementation and independent site verification.

Adopts an elite Competitive Intelligence Strategist and AI Market Analyst persona (mid-2020s). Produces engineering-focused competitive reports: codebase deep-dive vs market (web/GitHub), feature gaps, differentiation, and actionable technical roadmaps—not generic business advice. Use when the user asks for competitive analysis, market positioning, competitor landscape, feature gap vs incumbents, GTM from a technical moat angle, “attack vector” engineering roadmap, or intelligence on EHS/EHSQ/IMS SaaS and OSS alternatives for this repository.

Guides Developer Experience work for Autonomous EHS: turnkey local demos, Docker/Codespaces/devcontainer setup, realistic database seeds, DEMO_MODE / read-only sandbox flags, README “storefront” quick starts, and auth friction reduction without weakening production. Use when the user asks for demo environments, one-command spin-up, seed data, sandbox mode, DevEx, onboarding developers, GitHub Codespaces, docker-compose for Postgres/pgvector, or stakeholder previews; or when improving contributor docs and npm scripts for local parity with CI.

Reviews the codebase for modernization opportunities against a May 2026 lens: agentic orchestration, resilient AI/adaptive outputs, edge or client SLMs, WASM and data-plane patterns, with mandatory ROI and domain alignment. Use when the user requests an innovation audit, architecture modernization, future-proofing, “2026 standards,” agentic workflows, or a technology strategy review of this repository.

Acts as Principal Software Architect and Technical Documentation Specialist (Context Guardian): defines architecture, proposes repo structure, directory containment rules, Mermaid architecture/data-flow diagrams, and CONTEXT.md-style master instructions—without implementing application routing, UI, or business logic. Use when the user asks for system architecture blueprints, Memory Bank deliverables, directory trees, CONTEXT.md generation or revision, onboarding docs for coding agents, or technical governance articulation for Autonomous EHS.

Adopts an offensive-minded DevSecOps / application security auditor persona for rigorous SAST and logic review against OWASP-style and Zero Trust thinking. Use when the user asks for SAST, security audit, threat modeling, vulnerability assessment, DevSecOps review, OWASP, penetration-style code review, or hardening of auth, APIs, edge, rate limits, crypto, or AI/LLM surfaces in this repository.

Community PR/issue triage, appreciative contributor review, docs sync, and orchestrator handoff JSON. T1 advocate lane — not FinOps/swarm. Co-load lint-and-validate and security review when diff warrants.

HR ERP database migrations and packaging: Prisma/SQL surfaces, expand-migrate-contract, RLS-safe seeds, db:verify, distroless/GHCR supply chain. Use for DDL, backfills, dual-write cutovers, Dockerfile, or publish-ghcr workflows.

HR ERP DevOps overlay: Vercel git deploy, GHA quality gate, Redis workers, Phase 1 topology. Co-loads @devops-product-lifecycle. Use for ops paths in this repo.

Agent harness foundation — manifest v4, hooks, lint, ALARP, Cursor native unlock, Phase 2 evidence. Use for .cursor/**, governance scripts, and meta docs.

Adaptation plane — learning ledger, reflect/promote L0-L3, DMAIC/PDCA, CTQ snapshots, router hints. Human-invoked for RGF workflows.

Collaboration plane (Harness HITL) — seven-phase human-agent loop: proposal, options, human tradeoffs, execute, revalidate, specialized tools, output review. Use at T1+ before specialized skills; load routing portion automatically at orchestration.

HR ERP function-lane recipes: payroll T3 counsel, migration custodian isolation, security sentinel SLA, parallel scout+architect greenfield. Use with manifest v4 and ADR 0011 / 0016.

Product-runtime HR copilot MCP: catalog, transport, tenant isolation, HITL, hybrid protect-mcp shadow→enforce. Use for lib/copilot, MCP tool additions, red-team scenarios. Not Cursor IDE MCP plugins.

Generate or update a CHANGELOG.md from git history following Keep a Changelog conventions.

Guide schema or data migrations — write up/down steps, guards, backfill, and rollback plan.

Audit code and changes for secrets, injection, and unsafe patterns. Run before commits or on demand.