tomevault-io/skills-registry - Page 193

git-stash

Stash management - save, pop, list, and drop stashed changes Use when this capability is needed.

git-switch

Switch branches safely with uncommitted change handling Use when this capability is needed.

testing-strategy

Design comprehensive test strategies with test pyramid coverage and quality gates Use when this capability is needed.

visual-audit

Structured visual design critique with specific actionable feedback Use when this capability is needed.

workflow

Use when planning implementation steps, deciding commit format, or structuring development approach. Provides brainstorm-plan-implement flow with conventional commits. Triggers on 'how should I approach this', 'commit format'.

component-fix-and-verify

> Use when this capability is needed.

css-layout-debugger

> Use when this capability is needed.

regression-test-generator

> Use when this capability is needed.

skill-name

> Use when this capability is needed.

ui-bug-investigator

> Use when this capability is needed.

git-abort

Abort failed merge, rebase, or cherry-pick operations Use when this capability is needed.

adr-template

Use when recording significant architectural or design decisions that affect the system. Covers decision framing, context documentation, options analysis with tradeoff evaluation, consequence mapping, and review trigger definition. Do not use for…

ai-evaluation

Use when designing an evaluation framework for AI/LLM features. Covers golden dataset creation, automated scoring rubrics, hallucination detection, regression testing infrastructure, and production monitoring. Do not use for prompt design (use…

analytics-design

Use when planning measurement strategy for a feature or product area. Covers metrics hierarchy design, event taxonomy, funnel instrumentation, A/B test framework, and data pipeline planning. Do not use for feature prioritization scoring (use…

api-design

Use when designing REST or RPC endpoint contracts with request/response types and error handling. Covers endpoint specification, TypeScript type definitions, authentication requirements, pagination, and caching strategies. Do not use for database schema…

audit-trail-design

Use when designing audit logging systems for accountability and compliance evidence. Covers event catalogs, log schemas, retention policies, immutability requirements, and compliance reporting. Do not use for regulatory gap analysis (use compliance-review) or…

git-branch

Create new branches with naming conventions Use when this capability is needed.

git-branches

List and visualize branch status Use when this capability is needed.

caching-strategy

Use when designing or auditing a caching architecture. Covers multi-layer cache hierarchy, key schema, TTL policies, invalidation flows, and warming strategies. Do not use for runtime performance profiling (use performance-audit) or capacity planning (use…

changelog-design

Use when preparing release changelogs, migration guides, or breaking change communication for consumers. Covers change categorization, before/after documentation, migration step authoring, semver version strategy, and release communication planning. Do not…

cicd-generation

Use when creating GitHub Actions workflows, adding CI/CD to a project, or reviewing pipeline security. Produces fail-fast, security-hardened workflows with OIDC auth and SHA-pinned actions. Triggers on 'add CI', 'create workflow', 'github actions'.

code-search

Fast codebase searches using grep/glob. Triggers on "find", "search", "where is", "grep for". Use when this capability is needed.

codebase-context

Use when analyzing an existing codebase for architecture, tech stack, conventions, and infrastructure. Covers project structure mapping, data model discovery, integration point cataloging, and constraint identification. Do not use for schema changes (use…

competitive-analysis

Use when designing features that exist in competing products or analyzing prior art in the market. Covers feature mapping, UX evaluation, technical trade-off assessment, and differentiation opportunity identification. Do not use for evaluating individual…

compliance-review

Use when reviewing proposed features and data flows against GDPR, CCPA, HIPAA, and other privacy regulations. Covers regulatory applicability, PII data flow mapping, consent mechanism assessment, retention policies, and right-to-deletion compliance. Do not…

git-conflicts

Guided conflict resolution for merge and rebase conflicts Use when this capability is needed.

cost-analysis

Use when modeling infrastructure costs, projecting scaling expenses, or identifying optimization opportunities across cloud providers and third-party services. Covers per-unit cost estimation, growth milestone projections, and budget alerting setup. Do not…

css-layout-debugger

> Use when this capability is needed.

data-classification

Use when classifying data elements by sensitivity tier and defining per-tier handling requirements. Covers data inventory, sensitivity classification, PII flow mapping, encryption and masking specifications, and cross-boundary transfer documentation. Do not…

dbt-skill

Use when working with dbt (data build tool) - creating models, writing tests, CI/CD pipelines, materializations, sources, staging/intermediate/marts layers, Snowflake/BigQuery warehouse configuration, incremental strategies, Jinja macros, data quality,…

git-delete-branch

Delete local and remote branches with safety checks Use when this capability is needed.

deployment-plan

Use when designing deployment strategies including environment progression, CI/CD pipelines, zero-downtime releases, rollback procedures, and feature flag management. Covers blue-green, rolling, and canary deployment patterns with database migration…

design-system-architecture

Use when designing a token-based design system architecture. Covers primitive, semantic, and component token hierarchy, theming strategy for dark/light mode, and cross-platform implementation planning. Do not use for visual critique of existing interfaces…

device-integration

Use when designing integration strategies for device hardware APIs including camera, sensors, biometrics, and Bluetooth. Covers permission flows, cross-platform abstraction evaluation, fallback behavior, and power impact analysis. Do not use for platform…

documentation-plan

Use when designing documentation architecture for a project or team. Covers audience mapping, Diataxis framework classification, onboarding path design, format and location decisions, documentation testing, and maintenance scheduling. Do not use for recording…

embedded-architecture

Use when designing firmware architecture for embedded or IoT devices. Covers RTOS selection, memory layout, power state machine, task decomposition, and watchdog recovery design. Do not use for wireless protocol selection (use protocol-design) or fleet-scale…

failure-mode-analysis

Use when systematically identifying failure scenarios for proposed features and infrastructure changes. Covers component enumeration, failure mode discovery, cascade analysis, mitigation design, monitoring signals, and rollback planning. Do not use for…

fleet-management

Use when designing fleet management infrastructure for IoT device fleets. Covers device provisioning, OTA firmware update strategy, telemetry pipeline design, fleet monitoring, remote management, and scaling projections. Do not use for firmware architecture…

formal-spec

Use when writing formal specifications in TLA+ to verify system properties, defining state variables, configuring TLC model checker, and documenting assumptions and limitations. Covers safety and liveness properties for protocols and concurrent systems. Do…

github-activity

Recent repository activity summary Use when this capability is needed.