DeFi

This skill should be used when creating or updating PROJECT.md files, planning sprints, defining project goals, or managing project scope. It provides templates and best practices for PROJECT.md-first development.

Plans technical projects with risk-first development, milestone structuring, and managed deferral. Use when planning software projects, defining milestones, structuring development phases, or breaking down complex tasks into manageable iterations.

Nuxt 4 server-side development with Nitro: API routes, server middleware,database integration, and backend patterns.Use when: creating server API routes, implementing server middleware,integrating databases (D1, PostgreSQL, Drizzle), handling file uploads,implementing WebSockets, or building backend logic with Nitro.Keywords: server routes, API routes, Nitro, defineEventHandler,getRouterParam, getQuery, readBody, setCookie, createError,server middleware, D1, Drizzle, PostgreSQL, WebSocket, file upload

Use when integrating Drizzle ORM with Bun's SQLite driver for type-safe schema definitions and migrations.

Type-safe ORM for Cloudflare D1 databases using Drizzle. Use when: building D1 database schemas, writing type-safe SQL queries, managing migrations with Drizzle Kit, defining table relations, implementing prepared statements, using D1 batch API, or encountering D1_ERROR, transaction errors, foreign key constraint failures, or schema inference issues.Keywords: drizzle orm, drizzle d1, type-safe sql, drizzle schema, drizzle migrations,drizzle kit, orm cloudflare, d1 orm, drizzle typescript, drizzle relations, drizzle transactions,drizzle query builder, schema definition, prepared statements, drizzle batch, migration management,relational queries, drizzle joins, D1_ERROR, BEGIN TRANSACTION d1, foreign key constraint,migration failed, schema not found, d1 binding error, schema design, database indexes, soft deletes,uuid primary keys, enum constraints, performance optimization, naming conventions, schema testing

This skill should be used when the user wants to create a new looplia workflow, generatea workflow definition file, or compose workflow steps from skill recommendations. Use whensomeone says "create a looplia workflow", "generate workflow.md", "compose workflow steps","build me an automation pipeline", or "/build" (final step).Final step in looplia workflow building: transforms skill recommendations into valid v0.6.3workflow YAML/Markdown files. Each step uses skill: + mission: syntax, following the oneworkflow step → one skill-executor → multiple skills architecture.v0.6.3: Supports input-less workflows using input-less capable skills (e.g., search).

Pinia v3 Vue state management with defineStore, getters, actions. Use for Vue 3 stores, Nuxt SSR, Vuex migration, or encountering store composition, hydration, testing errors.

Comprehensive guide for building meshes in TX V4. Covers SDK-based worker architecture, agent design, prompt templates, message protocols, and HITL workflows. Use when creating new meshes, defining agent roles, or debugging multi-agent systems.

Unified Memory Contract for Flowbaby integration. Defines when and how to retrieve and store memory. Load at session start - memory is core to agent reasoning, not optional.

TanStack AI (alpha) provider-agnostic type-safe chat with streaming for OpenAI, Anthropic, Gemini, Ollama. Use for chat APIs, React/Solid frontends with useChat/ChatClient, isomorphic tools, tool approval flows, agent loops, multimodal inputs, or troubleshooting streaming and tool definitions.

Tether Wallet Development Kit (WDK) for building non-custodial multi-chain wallets. Use when working with @tetherto/wdk-core, wallet modules (wdk-wallet-btc, wdk-wallet-evm, wdk-wallet-evm-erc-4337, wdk-wallet-solana, wdk-wallet-spark, wdk-wallet-ton, wdk-wallet-tron, ton-gasless, tron-gasfree), and protocol modules including swap (wdk-protocol-swap-velora-evm), bridge (wdk-protocol-bridge-usdt0-evm), and lending (wdk-protocol-lending-aave-evm). Covers wallet creation, transactions, token transfers, DEX swaps, cross-chain bridges, and DeFi lending/borrowing.

TypeScript-first schema validation and type inference. Use for validating API requests/responses, form data, env vars, configs, defining type-safe schemas with runtime validation, transforming data, generating JSON Schema for OpenAPI/AI, or encountering missing validation errors, type inference issues, validation error handling problems. Zero dependencies (2kb gzipped).

Provides Nette DI and services configuration guidelines. Use when configuring services.neon, common.neon, autowiring, or service definitions.

Use when teams need shared direction and decision-making alignment. Invoke when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or setting behavioral standards. Use when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.

Cypress end-to-end testing guidance for opal-frontend, including Cucumber feature layout, tags, step definitions, Actions or Flows, selectors, and accessibility specs. Use when adding or updating E2E scenarios.

Use when clarifying fuzzy boundaries, defining quality criteria, teaching by counterexample, preventing common mistakes, setting design guardrails, disambiguating similar concepts, refining requirements through anti-patterns, creating clear decision criteria, or when user mentions near-miss examples, anti-goals, what not to do, negative examples, counterexamples, or boundary clarification.

Defines code quality benchmarks, standards compliance, and best practices for maintaining high-quality codebases

Use when designing database schemas, need to model domain entities and relationships clearly, building knowledge graphs or ontologies, creating API data models, defining system boundaries and invariants, migrating between data models, establishing taxonomies or hierarchies, user mentions "schema", "data model", "entities", "relationships", "ontology", "knowledge graph", or when scattered/inconsistent data structures need formalization.

Use when defining stopping rules for projects, avoiding sunk cost fallacy, setting objective exit criteria, deciding whether to continue/pivot/kill initiatives, or when users mention kill criteria, exit ramps, stopping rules, go/no-go decisions, project termination, sunk costs, or need disciplined decision-making about when to quit.

Validate that quality, security, and release gates are correctly defined, implemented, and enforced with evidence.