DeFi

Connecting StickerNest widgets via pipelines and ports. Use when the user asks about widget communication, connecting widgets, ports, inputs, outputs, pipelines, event routing, widget I/O, or making widgets talk to each other. Covers port definitions, type compatibility, event emission, and pipeline configuration.

Autonomous agent creation skill that generates specialized agent definitions from templates. Use when you need to create new Claude Code agents for specific tasks like code review, deployment automation, testing, documentation, security analysis, or general-purpose research. This skill automates the creation of agent definition files (.md) with proper structure, workflow instructions, and tool access patterns following Miyabi framework standards.

Manages the lifecycle, configuration, and synchronization of specialized sub-agents (Planner, Implementer, Reviewer, etc.) across various platforms (Claude, Copilot, OpenCode). Use this skill when you need to: (1) Sync sub-agent instructions from master templates, (2) Add new sub-agent definitions, (3) Update agent capabilities or permissions, or (4) Validate that agent instructions are in sync across platforms.

Design framework-agnostic AI agents using Oracle's Open Agent Specification for portable, interoperable agentic systems with JSON/YAML definitions

Guides implementation of new MCP tools from specification to production-readycode, following the braiins-pool-mcp-server architecture patterns and bestpractices defined in ARCHITECTURE.md.

Role definition for code reviewer agents. Defines review criteria, feedback patterns, and approval workflows. Use to understand how to review PRs and provide constructive feedback.

Define and evolve WPF XAML styling for the widget host app: control styles, templates, visual states, typography, and theme variants. Use when working in `App.xaml`, theme dictionaries, `Styles/*.xaml`, or control templates to achieve the Fluent-inspired design system with Light/Dark themes.

Provides type-safe database access with Prisma ORM including schema definition, migrations, queries, and relations. Use when setting up database connections, defining data models, writing queries, or managing database migrations.

Use when creating or updating agent evaluation suites. Defines eval structure, rubrics, and validation patterns.

Conducts comprehensive project specification interviews to clarify architecture, tech stack, design decisions, and implementation details.TRIGGERS - Keywords: interview, specification, spec, requirements, architecture, design decisions, project setup, new project, empty project, unclear requirements, /interview, SPEC.md, project planning, tech decisions, stack decisions, clarify requirements, gather requirements, requirements gathering.TRIGGERS - Phrases: "what should we build", "help me plan", "new project", "start a project", "define the architecture", "unclear what to build", "need to specify", "create a spec", "interview me", "ask me questions", "help me decide", "what technology should".TRIGGERS - Conditions: tech stack confidence LOW, project appears empty, no existing SPEC.md, architecture decisions needed.

[Extends e2e-tester] BDD/Cucumber specialist. Use for Gherkin feature files, step definitions, Cucumber-JVM/JS, Spring/Playwright integration. Invoke alongside e2e-tester for BDD testing approach.

Transform stakeholder needs into structured, testable specifications with user stories, acceptance criteria, and business rules. Use when: (1) creating requirements documents, (2) writing user stories with acceptance criteria, (3) defining business rules and process flows, (4) analyzing feature requests.

Rapid MVP validation and launch framework following Y Combinator and lean startup principles. Use when user wants to validate a business idea, launch an MVP, define product strategy, calculate unit economics, or needs structured approach to test product-market fit. Includes monetization models, metrics frameworks, and execution templates.

Use this skill for the requests related to the geometry definitions of USA counties; it provides a way to get the geometries of USA counties as a geodataframe.

This skill should be used when implementing tracks, following workflow methodologies, updating plan status, or when the user asks about "TDD workflow", "how to follow workflow", "task execution", "phase completion", or "status updates". Provides patterns for executing work according to defined methodologies.

This skill should be used when the user asks to "implement a contract", "implement contract X", "fulfill this change contract", "execute contract at path", "implement the definition of done", or wants to autonomously implement requirements from a Change Contract file. Produces working implementations with proof of compliance through tests and verification reports.

Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion, and follows the spec-driven methodology.

Decompose large epics into manageable, ordered user stories with clear dependencies and implementation strategy. Analyzes epic scope, identifies task dependencies, plans implementation sequence, estimates effort, and defines integration requirements for WCS migration projects.

Creates BDD feature files for Golang Clean Architecture projects using Gherkin syntax. Use when users need to write .feature files for integration tests, create test scenarios for APIs, or generate Cucumber/Godog test specifications. Specifically for projects that follow Clean Architecture patterns with existing step definitions.

Design and implement RESTful API endpoints following REST principles with proper HTTP methods, status codes, and URL conventions. Use this skill when creating or modifying API routes, route handlers, API endpoint files, controller files that handle HTTP requests and responses, or any server-side files that define RESTful endpoints. Use this when working on API versioning, implementing rate limiting, designing resource-based URLs, handling query parameters for filtering/sorting/pagination, or structuring nested resource endpoints. Use this when writing code in files like routes.js, api.js, controllers/, handlers/, endpoints/, or any file that defines HTTP API routes and responses.