design-system-token-enforcer
Enforce design system token usage in espresso-engineered-1 frontend UI work. Use when creating or editing Svelte components, layout sections, typography, spacing, colors, surfaces, or buttons, especially when introducing new UI components or section headers.
ios-input-hints
Ensure iOS/iPadOS-friendly form inputs (keyboard type, inputmode, autocomplete, autocapitalize/autocorrect, enterkeyhint) when editing or reviewing UI forms in web apps. Use when adding or modifying form fields (Svelte/HTML/TSX/etc.), auditing form UX, or fixing mobile Safari keyboard issues.
translate-image
Translate text in images, extract text via OCR, and remove text using TranslateImage AI. Use when user says 'translate image', 'OCR image', 'extract text from image', 'remove text from image', 'manga translate', or wants to process images with foreign-language text.
pr-review-helper
Gather PR review context: all comments (including review suggestions), diff context, and CI status; download GitHub Actions logs on failures. Prefer GitHub MCP for reads, fall back to gh CLI when needed.
plan-replayer-testing
Expertise in adding new test cases for the TiDB plan replayer. Use when the user provides a plan replayer zip file and wants to create a new test.
context-management
Use for projects, tasks, or code that involve context engineering and context management for AI agents: keep prompt prefixes stable for KV-cache, use append-only context, prefer tool masking over tool removal, offload large observations into filesystem memory, recite goals/todos to control attention, preserve errors for recovery, and avoid few-shot pattern lock-in. Use when building or debugging agent loops, prompt/context schemas, memory strategies, or tool-availability policies.
bugfix
Fix software bugs with root-cause analysis, minimal diffs, regression tests, and a mandatory self-check loop. Use for general bugfix work that is not covered by a more specific domain skill.
tidb-profiler-analyzer
Processes and analyzes TiDB profiler zip packages (CPU or heap) for components like TiDB, TiKV, PD, or TiFlash. It unzips, aggregates the profiler data, and uses `go tool pprof` to report on the most time-consuming functions (CPU) or highest memory allocations (heap).
tidb-optimizer-bugfix
Fix TiDB optimizer bugs with minimal diffs, hypothesis-driven validation, and regression tests. Use the bundled issue precedents only to avoid re-fixing already solved bugs or inspect suspect historical fixes.
tidb-doc-finder
TiDB-specific documentation lookup guided by this repo's llms.txt hub: read llms.txt, pick the best linked source (tidb-dev-guide llms-full.txt, TiDB user guide llms.txt, or Uber Go style guide), fetch it, then search within it to answer with precise references. Use when asked to find docs, research, or provide doc-grounded answers about TiDB development or usage.
resilience-patterns
Resilience and error recovery patterns including circuit breaker, retry strategies, and graceful degradation
elixir-guidelines
Official Elixir community standards, naming conventions, and best practices
elixir-scribe
Single Responsibility Code in Self-Documented Folder Structure
ecto-query-analysis
Analyzes Ecto queries for N+1 problems, missing preloads, and performance issues.
ai-orchestration
LLM keyring management, multi-provider support, and AI agent orchestration
observability
Telemetry, metrics, tracing, and observability for Elixir/BEAM applications
liveview-patterns
Phoenix LiveView UI and real-time feature patterns
migration-patterns
Zero-downtime Elixir/Phoenix database migrations and rollback strategies
otp-patterns
Implements OTP design patterns including GenServer, Supervisor, and Application behaviors.
graphql-patterns
GraphQL patterns with Absinthe framework for Elixir/Phoenix applications
performance-profiling
Performance profiling and optimization for Elixir/BEAM applications
git-workflow
Git and GitHub workflow automation skills for OpenCode agents
api-design
REST vs GraphQL, API versioning, rate limiting, and documentation for Elixir/BEAM APIs
nx-patterns
Nx and Livebook patterns for machine learning in Elixir
api-versioning
API versioning strategies including URL-based, header-based, and breaking change management
data-pipeline
GenStage, Broadway, and Flow for Elixir data pipelines
containerization
Docker and Kubernetes deployment patterns for Elixir/Phoenix applications
distributed-systems
Distributed systems patterns for BEAM/OTP including clustering, supervision, and multi-region deployment
security-patterns
Elixir-specific security patterns, OWASP mitigations, and compliance best practices
nerves-patterns
Nerves embedded development patterns for Elixir/Nerves systems
test-generation
Generates comprehensive Elixir tests using ExUnit following TDD principles.
elixir-architect
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
big-jump
Turn a vague software or product idea into a verified, explainable first release, or grow an existing project through scoped, testable slices. Use for substantial build requests involving web apps, APIs and backends, CLI or automation tools, data or AI systems, libraries, mobile or desktop apps, and mixed systems—especially when a beginner wants the agent to choose a practical path, implement autonomously, use Git safely, verify with stack-appropriate evidence, and teach briefly. Do not use for explanation-only requests, code review without implementation, or a tiny isolated fix that does not need a project workflow.
big-jump
Turn a vague software or product idea into a verified, explainable first release, or grow an existing project through scoped, testable slices. Use for substantial build requests involving web apps, APIs and backends, CLI or automation tools, data or AI systems, libraries, mobile or desktop apps, and mixed systems—especially when a beginner wants the agent to choose a practical path, implement autonomously, use Git safely, verify with stack-appropriate evidence, and teach briefly. Do not use for explanation-only requests, code review without implementation, or a tiny isolated fix that does not need a project workflow.
smith-xml
XML tag standards for runtime prompts that mix instructions with embedded data (subagent prompts, assembled system messages). Use when constructing such a prompt, NOT when authoring a SKILL.md body — see smith-skills for that. Covers tag conventions for Claude, GPT-5.x, Gemini, and Harmony, with source-credibility notes verified 2026-07-11.
smith-ctx-kiro
Kiro-specific context management with terminal limitations, Serena MCP as mandatory tool, and file operation workarounds. Use when operating in Kiro IDE. LOAD FIRST in all Kiro sessions - critical platform constraints that prevent hangs and failures.
smith-checkpoint
Memory checkpoint — save the current session's durable state into all three memory systems (Serena memory, Basic-Memory note, auto-memory) in their required formats. Invoke with /smith-checkpoint.
smith-ctx-cursor
Cursor context management with /summarize command, @ mentions for file inclusion, and @codebase discovery. Use when operating in Cursor IDE or when context exceeds 60%. Activate for context optimization in Cursor sessions.
smith-git
Git workflow gotchas and non-obvious practices. Use when performing Git commits, merges, branch management, rebasing, or raw `git worktree` commands. Covers GPG signing, atomic commits, raw worktree patterns, and safety flags. For the Claude Code worktree tools (EnterWorktree/ExitWorktree) see smith-worktree.
smith-gh-pr
GitHub PR workflows including creation, review cycles, merge strategies, stacked PRs (creation, merge order, rebase after parent merges, squash handling), posting review findings, and confirming a CodeRabbit review actually ran. Use when creating PRs, stacked PRs, or dependent PRs, replying to review comments, running or interpreting a CodeRabbit review (GitHub App or `coderabbit` command line), merging branches, or fetching PR threads. Covers rebase decision trees and AI-generated descriptions. For the stacked shipping pipeline see smith-ship (stacked mode).
smith-gh-cli
GitHub CLI gotchas and best practices. Use when executing gh commands. Covers token efficiency, pagination limits, and common pitfalls.
smith-dialectic
Socratic interview that stress-tests a plan against project docs and code, one question at a time. Use when user says "grill my plan", "challenge this", "stress-test", or wants to reach shared understanding before implementing.
smith-dev
Development workflow standards and code quality requirements. Use when starting ANY task that will modify repo files (implement, fix, add, refactor, harden), initializing projects, running quality checks, or managing agent tasks. Covers branch-first setup, pre-commit checks, task decomposition, and script organization patterns.
smith-design
SOLID principles and architecture design patterns. Use when starting new features, refactoring code, conducting architecture reviews, or applying object-oriented design principles.
smith-automation
Claude Code scheduling primitives — /loop (interval, dynamic, bare), CronCreate/List/Delete, ScheduleWakeup, Monitor, and /schedule (Routines), with a decision matrix and provider/session-scope caveats. Use when setting up a recurring or scheduled task, polling for external state, self-pacing iterations, or the user mentions /loop, /schedule, cron, ScheduleWakeup, or Monitor.
smith-auto_mode
Claude Code auto mode classifier — what gets blocked, how to recover from a denial without silently retrying, and where to configure trusted infrastructure. Use when the agent invokes a classifier-sensitive action (push, deploy, external-content duplication), when a prior turn ended in "auto mode classifier" denial, or when the user mentions auto mode / `defaultMode` / `hard_deny`.
smith-ctx
Universal context-management foundation — proactive context-level checks and reset recommendations. Use when context usage grows high, when deciding whether to /clear or /compact, or when choosing what to retain across a context reset.
smith-browser_mcp
Browser MCP plugin reliability for chrome-devtools-mcp and @playwright/mcp. Take each server's own default browser — both resolve to Chrome's stable channel — and set no browser override at all; launching Vivaldi/Brave/Arc/Opera/Edge is forbidden, though attaching to an already-running one over the Chrome DevTools Protocol (CDP) is the documented escape hatch. Use when invoking chrome-devtools-mcp or Playwright MCP tools, editing .mcp.json / settings.json, triaging browser MCP launch failures, or when a site needs an interactive login the user must complete.
smith-slack
Slack message/reply drafting discipline — a hard pre-send checklist (draft-not-send, attribution footnote, evidence URLs, no formatting, confirm-before-send). Use when drafting or replying in Slack, invoking any slack_send_message* / slack_* MCP tool, or running a /slack:* command.
smith-standards
Universal coding standards for emoji usage, comments, acronym expansion, datetime formatting, and file conventions. Use when writing code, logs, documentation, or any text output. Always active as universal rules for all development.
Page 1438 of 1708 · 85390 results
