error-handling-base
Foundation for error handling patterns. This is a base skill designed to be extended by language-specific error handling skills.
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Foundation for error handling patterns. This is a base skill designed to be extended by language-specific error handling skills.
Common testing patterns and practices. This skill is designed to be included in composite skills via the 'includes' feature.
Build beautiful terminal UIs with Charmbracelet. For SHELL/BASH scripts: use Gum (prompts, spinners, selection), VHS (recording), Mods (AI), Freeze (screenshots), Glow (markdown). For GO applications: use Bubbl...
Craft professional README.md files for GitHub open source projects. Generates hero sections, installation instructions, feature tables, and architecture diagrams. Use when creating or revising a README, documen...
Create OpenGraph and Twitter share images for Next.js applications using next/og ImageResponse. Generates dynamic social preview cards with gradients, SVG icons, and proper dimensions. Use when building OG imag...
A comprehensive skill for Rust development that combines error handling, testing, and logging patterns. Demonstrates the 'includes' composition feature by merging content from multiple standalone skills.
Rust-specific error handling patterns, building on the base error handling skill. Demonstrates the 'extends' composition feature.
Security review for Scalus/Cardano smart contracts. Analyzes @Compile annotated validators for vulnerabilities like redirect attacks, inexact value validation, missing token verification, integer overflow, and...
Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright. Use when fixing broken tests, debugging failures, writing unit/SSR/e2e tests, or working with vitest/Playwright.
Use when user asks to explain, break down, or help understand technical concepts (AI, ML, or other technical topics). Makes complex ideas accessible through plain English and narrative structure. Use the provid...
Use when creating or modifying Elysia API routes. Ensures proper validation with t schema, auth guards, error handling, and performance patterns.
Use when creating or modifying React components. Ensures proper Server/Client component patterns, performance optimization, and accessibility.
Use when modifying Prisma schema or database queries. Ensures proper migrations, type safety, and query performance.
Convert Markdown to Word (DOCX) documents. Use when user wants to export, convert, or create Word documents from Markdown content.
Lint a clojure project using clojure-lsp CLI when user requests to lint
Brief description of what this skill enables. Include trigger keywords that should activate this skill. Triggers on keyword1, keyword2, keyword3.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.