DeFi
1145 skills in Blockchain > DeFi
quality-metrics
Measure quality effectively with actionable metrics. Use when establishing quality dashboards, defining KPIs, or evaluating test effectiveness.
worker-handover
Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.
architecture-synthesis
Generate a reference architecture specification from analyzed frameworks. Use when (1) designing a new agent framework based on prior art, (2) defining core primitives (Message, State, Tool types), (3) specifying interface protocols, (4) creating execution loop pseudocode, or (5) producing architecture diagrams and implementation roadmaps.
workspace-orchestrator
Meta-skill for AI-User collaboration within the BL1NK Monorepo. Defines rules for file creation, redundancy management, and systematic workflow execution based on historical interaction patterns.
ash-relationships
Defining, loading, and managing relationships between Ash resources
consult-expert
Get expert perspective on a problem by synthesizing an ideal consultant. Use when: (1) asked to consult expert or get specialist input, (2) problem involves specialized domain, (3) analyzing from expert viewpoint, (4) right expertise is not predefined.
refine-story
Transform vague or incomplete user stories into sprint-ready stories with clear acceptance criteria, test scenarios, and technical guidance. This skill should be used before sprint commitment for definition of ready check.
arktype
Expert knowledge for runtime validation in TypeScript using ArkType, a syntax-first validation library with TypeScript-like definitions, JIT compilation for 10x-100x performance over Zod, native recursion support, morphs for data transformation, and Standard Schema compatibility
build-functors
Define functors from domain to target categories. Uses targets.yaml todetermine which functors to create. Maps domain objects and morphismsto target representations. Use when: mapping domain to API, persistence,events; formalizing structural transformations.
prototype-planning
Define what to build at what fidelity to learn what you need without over-investing. Use before starting any prototype.
documenting-ui-states
Documents all UI state variations (default, empty, error, loading, success) from Figma designs. Use when defining complete UI specifications before implementation.
zod-form-validation
Zod schema validation and React Hook Form integration for TypeScript frontends. This skill should be used when creating forms, defining API schemas, validating form data, implementing type-safe validation, using ZodResolver with React Hook Form, or migrating legacy forms to the Zod + React Hook Form pattern.
epic-identification
This skill should be used when the user asks to "identify epics", "break down vision into epics", "find major features", "discover capability areas", "decompose vision", "group requirements into themes", "define high-level features", "what epics do I need", "turn vision into work items", or "split project into epics". Provides methodology for deriving epics from a vision statement using user journey mapping, capability decomposition, and stakeholder analysis.
needs-articulation
Distinguish user wants from underlying needs to guide solution design. Use when stakeholders make feature requests or during Define phase.
graphql
Provides GraphQL API schema design and implementation expertise. Ensures proper type definitions, query/mutation patterns, pagination strategies, and error handling standards. Specializes in schema-first design, resolver implementation, DataLoader for N+1 prevention, subscription patterns, and federation architecture. Implements Relay cursor connections and Apollo best practices.Use when: designing GraphQL schemas, defining types and interfaces, implementing queries and mutations, creating resolvers, designing pagination with connections and edges, solving N+1 query problems with DataLoader, implementing subscriptions for real-time updates, handling errors and nullability, setting up GraphQL federation, or integrating with Apollo Server/Client or other GraphQL libraries.
mcp-narsil
Deep code intelligence via Narsil MCP providing 76 tools for security scanning (OWASP, CWE, taint analysis), call graph analysis (CFG, DFG, callers/callees), structural queries (symbols, definitions, references), and supply chain security (SBOM, license compliance). Accessed via Code Mode for token efficiency.
mcp-documentation-skill
Access cached codebase documentation via MCP. Use when searching for project architecture, agent definitions, skill documentation, or deployment procedures. Provides 90% token savings vs. reading files directly.
Backend Models
Design and implement domain entities, DTOs, and data transfer objects following the project's domain-driven design patterns. Use this skill when creating or modifying domain entity classes in shared/domain/, DTO classes in features/{feature}/dto/, entity mappers in shared/mapper/, or shared type interfaces in packages/shared/types/src/dto/. This includes implementing the static factory pattern (Entity.create()), writing DTO validation decorators (class-validator), creating response DTOs with static from() methods, and defining shared interfaces that API DTOs must implement. Apply when working with @imkdw-dev/types package interfaces, ArticleContent value objects, or any file ending in .dto.ts, domain entities, or mapper classes.
trade-study-analysis
Conduct systematic trade study analyses using the DAU 9-Step Trade Study Process. Guides engineers through problem definition, root cause analysis (5 Whys, Fishbone), data collection from alternatives and datasheets, normalization calculations, weighted scoring, sensitivity analysis, and professional report generation with visualizations and decision matrices. Use when evaluating alternatives, comparing solutions, conducting trade-offs, or making engineering decisions.
project-structure
Provides comprehensive project folder structure design guidelines and best practices. Defines standard directory organizations for diverse project types including monorepos, web frameworks, backend services, libraries, and extensions. Ensures scalable, maintainable architecture through consistent file organization patterns. Specializes in separation of concerns, modular architecture, and tooling integration.Use when: designing new project structures, organizing monorepo workspaces with tools like Turborepo/Nx, structuring NestJS backend projects, organizing React/Next.js frontend applications, designing Go service architectures, creating NPM package structures, organizing VSCode extension projects, structuring Chrome extension codebases, planning directory hierarchies, migrating legacy project structures, or establishing code organization conventions for teams.