.dotfiles

Create and schedule CrossFit workouts on Garmin Connect. Use when user asks to 'create a CrossFit workout', 'make a WOD', 'build an EMOM', 'schedule a CrossFit session', 'AMRAP workout', 'Tabata', 'for time workout', or any request to create a non-running workout for Garmin.

This skill should be used when the user asks to 'design a feature', 'evaluate approaches', 'plan the architecture', 'domain modeling', 'DDD design', 'bounded contexts', 'functional core imperative shell', 'how should I structure this', 'what pattern should I use', or needs upfront architectural design for Java/Spring Boot, TypeScript/Next.js, or Rust codebases. For DESIGN decisions before implementation - not for reviewing existing code (use the architecture-agent via /review-pr for that).

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

This skill should be used when the user asks to 'implement', 'write code', 'build a feature', 'create a function', 'add functionality', 'code this', 'make this work', or needs to write production code for Java/Spring Boot or TypeScript/Next.js following FP, DDD, and testability patterns. Ensures code follows functional core/imperative shell, proper invariants, Either-based error handling, and is designed for testing without mocks.

This skill should be used when the user asks to 'check spec alignment', 'verify requirements coverage', 'detect drift', 'spec audit', or automatically at wave gates. Verifies implementation aligns with specification - different from code review which checks quality.

This skill should be used when the user asks to 'specify a feature', 'write requirements', 'define what we're building', 'capture requirements', 'document the spec', or before invoking /architecture-tech-lead for non-trivial features. Produces formal specifications (WHAT/WHY) that feed into architecture and planning phases.

This skill should be used when the user asks to 'plan this', 'orchestrate', 'break down', 'split into phases', 'coordinate tasks', 'create a plan', 'multi-step feature', or has complex tasks needing structured decomposition. Decomposes work into wave-based parallel tasks, assigns specialized agents, creates GitHub Issue for tracking, and manages execution through phase artifacts on disk.

Run after wave implementation complete. Executes test + spec-check + review gate sequence. Usage: /wave-gate

This skill should be used when the user asks to 'clarify requirements', 'resolve uncertainties', 'answer spec questions', or when auto-triggered by /opencode-specify with >3 NEEDS CLARIFICATION markers. Systematically surfaces and resolves ambiguities in specifications.

Add events to iCloud calendar by writing .ics files and triggering vdirsyncer sync. Use when user asks to 'add to calendar', 'create an event', 'schedule X on Tuesday', 'put this on the calendar', or any request to create a calendar event.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

This skill should be used when the user asks to 'design a feature', 'evaluate approaches', 'plan the architecture', 'domain modeling', 'DDD design', 'bounded contexts', 'functional core imperative shell', 'how should I structure this', 'what pattern should I use', or needs upfront architectural design for Java/Spring Boot, TypeScript/Next.js, or Rust codebases. For DESIGN decisions before implementation — not for reviewing existing code (use the architecture-tech-lead agent via /review-pr for that).

This skill should be used when the user asks to 'review a skill', 'audit skill quality', 'validate a skill', 'check my skill', 'improve my skill', 'skill feedback', or wants expert assessment of a SKILL.md against Anthropic best practices and the open Agent Skills specification. Performs structural validation, content quality analysis, triggering assessment, and token efficiency review. NOT for creating skills — use /skill-creator instead.

This skill should be used when the user asks to 'create a skill', 'build a skill', 'make a skill', 'new skill', 'write a skill', 'skill for X', or wants to package a workflow as a reusable Claude Code skill. Guides through use case definition, frontmatter, instructions, testing, and file structure. NOT for reviewing existing skills — use /skill-content-reviewer instead.

Generate JPA entity classes from Oracle CREATE TABLE DDL statements. Use when the user provides a CREATE TABLE definition and wants a Hibernate entity. Handles Oracle types (VARCHAR2, NUMBER, CLOB, CHAR, DATE, TIMESTAMP, BLOB), schema-qualified tables, and follows the hibertable11 repo conventions.

This skill should be used when the user asks to 'write landing page copy', 'improve conversion', 'optimize CTA', 'review signup flow', 'write headlines', 'form microcopy', 'trust signals', 'onboarding copy', 'lead gen copy', or needs high-converting copy for signup forms, multi-step flows, and lead generation funnels.

This skill should be used when the user asks to 'improve UX', 'fix mobile experience', 'optimize signup flow', 'increase conversions', 'design better CTAs', 'reduce form abandonment', 'improve form UX', 'add trust signals', 'write microcopy', 'mobile-first design', 'responsive layout', 'onboarding flow', 'reduce friction', 'improve checkout', or needs guidance on desktop/mobile UX patterns, conversion rate optimization, form design, CTA placement, user psychology, or high-converting user flows.

Critically analyzes business ideas from documents, YouTube transcripts, blog posts, URLs, or pasted text. Detects hype/affiliate marketing, assesses viability, and evaluates fit for dotslash.dev — an AI consultancy AND productized SMB agency targeting Copenhagen. Use when user mentions 'analyze this idea', 'is this worth pursuing', 'evaluate this', 'idea-analyzer', or pastes content asking if a business idea is good. Supports deep analysis with competitive research.

This skill should be used when the user asks to "design an MCP server", "review my MCP server", "MCP best practices", "MCP tool design", "design MCP tools", "MCP security review", "consolidate MCP tools", "reduce MCP tool count", "audit MCP server", "MCP resources vs tools", or mentions designing tools for AI agents following Model Context Protocol patterns.

This skill should be used when the user asks to 'review skill', 'audit skill', 'check skill quality', 'review hooks', 'review plugin', or wants a comprehensive multi-agent review of a skill and its hooks/agents/helpers. Spawns skill-reviewer, skill-content-reviewer, and claude-code-guide in parallel.

Summarizes YouTube videos by extracting transcripts and producing structured summaries. Use when user pastes a YouTube URL and wants a summary, key takeaways, or notes from a video. Supports youtube.com and youtu.be links.