DeFi

Use this skill when creating or refining Claude Code skill definitions. Skills are model-invoked capabilities that Claude activates autonomously based on context. Helps design focused skills with discovery-optimized descriptions, proper directory structures, and supporting resources. Automatically invoked when user requests "create a skill", "make a capability", "add autonomous behavior", or mentions skill development. Ensures skills follow Anthropic specifications with clear activation triggers.

Apply Domain-Driven Design patterns. Use when modeling complex business domains, defining bounded contexts, or designing aggregates. Covers entities, value objects, and repositories.

This skill should be used when the user asks to "verify protocols", "check consistency before commit", "validate definitions", "run pre-commit checks", "verify soundness", or wants to ensure epistemic protocol quality. Invoke explicitly with /verify for pre-commit validation.

Creates comprehensive skill documents that define specialized Claude capabilities. Use when creating new skills, documenting reusable AI behaviors, establishing automated task patterns, or building autonomous capabilities. Takes skill name, plugin, and optional instructions to generate complete skill files with frontmatter and orchestration logic.

Test how a strategy performs across multiple plausible futures defined by key uncertainties to build adaptive plans. Use when: (1) asked "how does this hold up if X changes" or "what if the future turns out differently" with long-term decisions, (2) a plan assumes a single future will unfold and doesn't account for how uncertainty could change outcomes dramatically, (3) building strategies that must stay viable across different scenarios rather than betting on one forecast, (4) identifying early warning signals that indicate which future is emerging

Create eBPF maps (hash, array, ringbuf, LRU, per-CPU) with corresponding Go userspace code for reading and writing data between kernel and userspace. Includes map definitions, update/lookup operations, and event handling. Use when implementing state management or kernel-userspace communication in CNFs.

Define and use code interfaces for calling Ash resources from domains

Draft and enforce system-level persona/rules for Ollama SYSTEM blocks. Use to translate role/constraints into Modelfile SYSTEM text.

Defines Android/Kotlin coding conventions for the project. Includes naming rules, forbidden patterns, preferred practices, and code style guidelines. Use when writing code to ensure consistency. Use when user mentions: 네이밍, 컨벤션, 코딩 규칙, 스타일 가이드, 금지 패턴, 권장 패턴, 이름 규칙, 코드 스타일, 컨벤션 확인, 네이밍 규칙.

This skill should be used when the GM needs to help players create Daggerheart characters, select a class/ancestry/community, define Experiences with bounded constraints, choose domain cards, or handle level advancement (1-10). Provides templates for character sheets, session state, and Experience definitions to prevent semantic drift during gameplay.

Frontend-backend pagination standard, defining minimal parameter naming to reduce transmission characters, applicable to all system pagination scenarios.

Defines form field specifications including validation rules, error states, and submission behavior. Updates the "フォーム仕様" section in screen spec.md.

Browse, search, and reference saved persona definitions. Use when: (1) asked to list or search existing personas, (2) starting reasoning session with expert perspective, (3) finding relevant expert viewpoint for topic, (4) checking for existing persona before creating new.

Provides categorical organization for tasks using a predefined set of seven standard tags (Work, Personal, Shopping, Health, Finance, Learning, Urgent). Enforces tag validation rules including duplicate prevention and 5-tag maximum per task.

Write clear, testable requirements using User Stories and Gherkin scenarios for Manifest Logistics SaaS. Capture functional and non-functional requirements with proper acceptance criteria. Use when defining new features or documenting system behavior.

Design safe migration strategies for breaking changes by planning how systems evolve without disrupting users. Use when: (1) asked to make breaking changes to APIs, schemas, or contracts without migration planning, (2) proposals assume all callers can update simultaneously without considering external dependencies, (3) changes lack definitions of migration completion criteria or rollback strategy, (4) plans omit how old and new versions will coexist during transition.

Enforces functional TypeScript patterns with Effect ecosystem. Use when (1) writing TypeScript functions or modules, (2) defining types or schemas, (3) handling errors or async operations, (4) structuring files with section separators, or (5) creating factories, dispatch tables, or Effect pipelines.

This skill should be used when the user asks to "create user stories", "write user stories", "break down epic into stories", "define user stories", "what stories do I need", "apply INVEST criteria", "write acceptance criteria", "split a large story", "story is too big", "story splitting", or when decomposing epics into specific, valuable user stories.

Kubernetes and Helm patterns - use for deployment configs, service definitions, ConfigMaps, Secrets, and Helm chart management

TypeScript enum pattern with Castable interface for model integration. Use when creating enums with behavior methods (colors, labels), defining fixed value sets, or integrating enums with the model casting system.