tomevault-io/skills-registry - Page 194

github-changelog

Generate changelog from merged PRs and commits Use when this capability is needed.

github-health

Repository health dashboard and status overview Use when this capability is needed.

github-issue

Create, link, and manage GitHub issues with templates Use when this capability is needed.

github-mine

Show my assigned and mentioned GitHub items Use when this capability is needed.

github-pr-merge

Merge a pull request with strategy selection Use when this capability is needed.

github-pr-request-review

Request reviewers for a pull request Use when this capability is needed.

github-pr-respond

View and respond to PR review comments Use when this capability is needed.

github-pr-status

Check PR status, CI results, and merge readiness Use when this capability is needed.

github-pr-update

Update PR branch with latest changes from base branch Use when this capability is needed.

github-release

Create a GitHub release with changelog Use when this capability is needed.

github-tag

Create semantic version tags Use when this capability is needed.

github-triage

Batch label and prioritize GitHub issues Use when this capability is needed.

git-status

Quick git queries - status, diff, log, blame. Triggers on "git status", "what changed", "show diff", "recent commits". Use when this capability is needed.

git-workflows

Local git operations for syncing, branching, merging, and conflict resolution Use when this capability is needed.

github-workflow

GitHub interactions for issues, PRs, releases, and repository management Use when this capability is needed.

growth-engineering

Use when designing growth infrastructure including onboarding funnels, referral mechanics, A/B test instrumentation, and re-engagement loops. Covers activation metrics, funnel mapping, and experimentation design. Do not use for pricing or paywall architecture…

helm-generation

Use when creating Helm values.yaml files, converting docker-compose to Helm, or reviewing Helm configurations. Produces minimal-diff values that only override chart defaults. Triggers on 'helm values', 'create values.yaml', 'deploy to kubernetes'.

impact-estimation

Use when comparing multiple features or initiatives to determine prioritization order. Covers RICE scoring with quantified reach, impact, confidence, and effort dimensions, tier ranking, and success metric definition. Do not use for MVP scope definition (use…

interaction-design

Use when designing component interaction specs with visual states, transitions, and accessibility requirements. Covers state matrices, responsive behavior, ARIA compliance, and content constraints. Do not use for multi-step user journey mapping (use…

invariant-analysis

Use when enumerating security claims from a design, formalizing them as invariants, checking for hidden assumptions, and assessing verification feasibility. Covers safety invariants, temporal properties, and verification tool recommendations. Do not use for…

isolation-review

Use when mapping isolation boundaries, enumerating crossing points, verifying enforcement mechanisms, and testing for bypass paths across trust domains. Covers containers, VMs, enclaves, namespaces, seccomp, and network segmentation. Do not use for kernel…

journey-mapping

Use when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component…

language-conventions

Language and project convention references for Python, TypeScript, and Terraform. Use when setting up new projects, reviewing code conventions, or ensuring consistency. Covers tooling, configs, patterns, testing, and project structure. Use when this…

library-evaluation

Use when adding new packages, choosing between dependency alternatives, or auditing existing libraries. Covers popularity metrics, maintenance health, bundle impact, API quality, and license compatibility with weighted scoring. Do not use for evaluating…

load-modeling

Use when planning capacity or projecting infrastructure needs under growth. Covers traffic modeling, endpoint heat maps, scaling triggers, benchmark design, and cost-at-scale estimates. Do not use for runtime bottleneck profiling (use performance-audit) or…

git-merge-main

Merge main branch into current feature branch Use when this capability is needed.

messaging-strategy

Use when developing product messaging frameworks including value propositions, feature naming, microcopy guidelines, and CTA strategy. Covers voice and tone definition, conversion copy, and upgrade prompt language. Do not use for pricing architecture or…

microarch-analysis

Use when analyzing microarchitectural attack surfaces by mapping shared hardware structures, identifying speculative execution vectors, quantifying speculative windows, and proposing countermeasures. Covers cache timing, transient execution, and contention…

ml-workflow

Use when designing end-to-end ML workflows. Covers experiment tracking, feature engineering and storage, model training pipelines, serving and deployment, A/B testing, and drift monitoring. Do not use for data warehouse schema design (use schema-evaluation)…

monetization-design

Use when designing monetization architecture including pricing tiers, paywall placement, subscription infrastructure, and upgrade flows. Covers freemium models, billing integration, and retention mechanics. Do not use for product copy or naming conventions…

motion-design

Use when designing the motion language for a feature or system. Covers transition specs, micro-interaction definitions, choreography principles, performance constraints, and reduced-motion alternatives. Do not use for visual design critique (use visual-audit)…

mvp-scoping

Use when defining minimum viable scope for a product or feature launch. Covers MoSCoW prioritization, value-effort matrix analysis, MVP cut-line definition, and phased roadmap planning. Do not use for quantified feature comparison (use impact-estimation) or…

navigation-design

Use when designing navigation architecture for mobile or cross-platform features including screen hierarchy, deep linking schemes, and state preservation strategies. Covers stack navigation, modal flows, universal links, and process death recovery. Do not use…

observability-design

Use when designing monitoring, alerting, logging, tracing, and SLI/SLO strategies for services or systems. Covers metric collection, structured logging, distributed tracing, dashboard design, and error budget management. Do not use for deployment pipeline…

page-component-mapper

> Use when this capability is needed.

pattern-analysis

Use when auditing codebase patterns or evaluating proposed changes for convention consistency. Covers file naming, component patterns, data fetching, state management, and type conventions. Do not use for test plan design or coverage targets (use…

performance-audit

Use when profiling application performance or diagnosing slow page loads. Covers full-stack bottleneck identification including Core Web Vitals, bundle analysis, database queries, and network waterfall. Do not use for cache architecture design (use…

physical-design-security

Use when reviewing physical implementation security for power domain coupling, timing-related leakage, clock domain crossing issues, and layout-level information exposure. Covers DPA/SPA resistance, EM emanation, fault injection countermeasures, and probing…

pipeline-design

Use when designing data pipelines for moving, transforming, and delivering data. Covers ETL vs ELT pattern selection, orchestration tool choice, batch vs streaming trade-offs, idempotency guarantees, data quality checkpoints, and lineage tracking. Do not use…

platform-audit

Use when auditing a feature or implementation against platform-specific guidelines such as iOS HIG, Material Design 3, and WCAG. Covers compliance scoring, violation identification, remediation steps, and App Store risk assessment. Do not use for navigation…