DeFi

ARCHITECT PHASE: Architectural design patterns, component templates, and system design guidance.Provides proven architectural patterns including microservices, layered architecture,event-driven systems, C4 diagram templates, API contract formats, and design anti-patterns.Use when: designing system architecture, creating component diagrams, defining interfaces,planning component boundaries, choosing architectural patterns, organizing system modules,or when user mentions: architecture, components, system design, diagrams, C4, microservices,API contracts, service boundaries, architectural patterns.Use for: component design, interface definition, system boundaries, dependency management,architecture documentation, design patterns, integration patterns.DO NOT use for: code implementation details, specific framework syntax, database schema design,frontend-specific patterns, testing strategies, or security implementation (use dedicated skills).

CROSS-CUTTING: API contract design patterns for architects and implementers.Provides REST API design patterns, GraphQL schema design, API versioning strategies,error response formats, pagination patterns, and API documentation standards.Use when: designing API contracts, choosing between REST/GraphQL, planning versioning,defining error formats, implementing pagination, documenting APIs.

Analyze a failed test by inspecting the code in the current project and artifacts in Prow CI job. Provide a detailed analysis of the test failure in a pre-defined format.

Create or update an ADR (Architecture Decision Record) under `docs/ADR/` using `docs/templates/ADR-Template.md`: context, decision, alternatives, consequences, rollout, and verification. Use when changing architecture, boundaries, dependencies, data model, or cross-cutting patterns; ensure it is self-contained, has a Mermaid diagram, and defines testable invariants.

Use when defining data contracts, consent policies, and monitoring for automation programs.

Use when defining events, fields, and governance for GTM analytics pipelines.

Use to define guardrails that pause signal-driven plays when accounts are risky, saturated, or in-flight elsewhere.

Framework for defining, approving, and auditing GTM metrics and KPIs.

Use to define incident tiers, response protocols, and stakeholder communications.

Use when defining ABM tiers, scoring logic, and coverage rules.

Operating model for defining, enforcing, and auditing BI data contracts.

Use to define validation, freshness, and compliance checks for enriched data.

Use to define KPIs, alert thresholds, and reporting cadences for social calendars.

Use when defining or adjusting marketing-to-sales assignment rules.

Use to define schemas, topic tags, and lineage metadata for enriched signals.

Use to enforce stage definitions, next-step requirements, and data completeness across the pipeline.

Use when defining nurture pacing, triggers, and suppression logic.

Methodology for defining product-qualified lead (PQL) signals, scoring, and routing.

Framework for defining, monitoring, and enforcing guardrail metrics across experiments.

Use when defining dynamic content rules, tokens, and conditional offers inside nurture programs.