DeFi

Copilot agent that assists with requirements analysis, user story creation, specification definition, and acceptance criteria definition Trigger terms: requirements, EARS format, user stories, functional requirements, non-functional requirements, SRS, requirement analysis, specification, acceptance criteria, requirement validation Use when: User requests involve requirements analyst tasks.

Creates structured output formats (JSON, YAML, Markdown-KV, XML) and response style configurations for Claude. Use when: (1) defining agent output schemas (.json, .yaml, .xml), (2) configuring response style scope hierarchy, (3) embedding formats in agents/commands, (4) building CLAUDE.md output sections, (5) creating format definitions in .claude/styles/, or (6) standardizing structured data serialization.

Generate type definitions from build artifacts. Creates effects module FIRST(Result, App monad, errors), then domain types, API schemas, storage models.Outputs ACTUAL source files. Use when: generating types, creating models.

LSP-powered context extraction using cclsp MCP tools, Solargraph, and Sorbet for type-safe code generation. Trigger keywords: cclsp, LSP, context compilation, interface extraction, vocabulary, Guardian, Sorbet, type checking, find_definition, get_diagnostics, Solargraph, type safety

Create a functional persona definition with expertise, question methodology, and research protocol. Use when an expert perspective needs definition for repeated use across dialogues or sessions.

Generate flowcharts from YAML/JSON definitions or Python DSL. Supports standard flowchart shapes, swimlanes, and PNG/SVG/PDF export.

Meta-validation skill that generates edge cases, production scenarios, and reality gaps not covered by original specifications. Identifies specification-reality mismatches by analyzing what tests claim versus what production data reveals. Creates test deficiency reports showing coverage gaps for Quinn review. Use before quality gate approval to ensure tests reflect production reality, not just specification compliance.

Comprehensive guide for the Echo web framework. Use when building scalable, high-performance web applications and REST APIs in Go with features like flexible routing, middleware support, request/response binding, static file serving, and template rendering. Applies to installing Echo, defining routes, implementing middleware, handling requests/responses, and building web services.

This skill should be used when the user asks to "create tasks", "break down story into tasks", "define tasks", "what tasks are needed", "write acceptance criteria", "implementation tasks", "task list", "create work items", "technical tasks", "work breakdown", "decompose story", "story to tasks", or when decomposing user stories into specific, executable tasks with clear acceptance criteria for GitHub Projects.

Use this skill when writing, reviewing, or discussing issue descriptions, acceptance criteria, or task breakdowns. Ensures consistent, high-quality issue structure that any developer or AI can pick up and execute. Triggers when drafting issues, defining requirements, or when users ask "how should I write this issue?" or "what should the acceptance criteria be?"

Create System Requirements (SYS) - Layer 6 artifact defining functional requirements and quality attributes

Analyzes bull-call-spread debit spreads for bullish directional plays with defined risk. Requires numpy>=1.24.0, pandas>=2.0.0, matplotlib>=3.7.0, scipy>=1.10.0. Use when expecting moderate price increase, comparing vertical spread configurations, analyzing debit spread opportunities, calculating Greeks for multi-leg positions, or evaluating defined-risk bullish strategies on liquid optionable securities.

Transform raw research into actionable insights that inform design decisions. Use during Define phase after completing research.

gRPC and Protocol Buffers - use for service-to-service communication, API definitions, streaming, and inter-service contracts

Write clear, testable requirements using User Stories and Gherkin scenarios. Capture functional and non-functional requirements with proper acceptance criteria. Use when defining new features or documenting system behavior. Trigger keywords: requirements, user stories, acceptance criteria, Gherkin, BDD, specifications, feature definition

Use when working with JSON Schema for validation, OpenAPI schemas, type definitions, and data structure specification

Define and enforce error budgets and SLO guardrails; use when asked to balance velocity with reliability targets.

Defines coding standards, test patterns, and language conventions for this project. Use this when writing code, comments, documentation, or git commit messages.

Expert guidance for Domain-Driven Design architecture and implementation. Use when designing complex business systems, defining bounded contexts, structuring domain models, choosing between modular monolith vs microservices, implementing aggregates/entities/value objects, or when users mention "DDD", "domain-driven design", "bounded context", "aggregate", "domain model", "ubiquitous language", "event storming", "context mapping", "domain events", "anemic domain model", strategic design, tactical patterns, or domain modeling. Helps make architectural decisions, identify subdomains, design aggregates, and avoid common DDD pitfalls.

Apply when designing RESTful APIs, defining endpoints, HTTP methods, status codes, and response formats.