Topic: claude
14,433 skills in this topic.
-
loom-before-after
Generates before/after verification pairs for loom plans. Proves a stage actually changed system behavior by capturing state before and after implementation. Use for delta-proof verification — proving new commands, endpoints, modules, or bug fixes work by comparing system state.
cosmix/loom 36
-
loom-caching
cosmix/loom 36
-
loom-ci-cd
Designs and implements CI/CD pipelines for automated testing, building, deployment, and security scanning across multiple platforms. Covers pipeline optimization, test integration, artifact management, and release automation.
cosmix/loom 36
-
loom-code-migration
cosmix/loom 36
-
loom-data-validation
Data validation patterns including schema validation, input sanitization, output encoding, and type coercion. Use when implementing validate, validation, schema, form validation, API validation, JSON Schema, Zod, Pydantic, Joi, Yup, sanitize, sanitization, XSS prevention, injection prevention, escape, encode, whitelist, constraint checking, invariant validation, data pipeline validation, ML feature validation, or custom validators.
cosmix/loom 36
-
loom-data-visualization
cosmix/loom 36
-
loom-database-design
cosmix/loom 36
-
loom-dead-code-check
Generates dead code detection configurations for loom plan verification. Provides language-specific commands, fail patterns, and ignore patterns for Rust, TypeScript, Python, Go, and JavaScript. Use when adding code quality checks to acceptance criteria or truths fields in loom plans. Dead code detection catches incomplete wiring by identifying code that exists but is never called.
cosmix/loom 36
-
loom-documentation
cosmix/loom 36
-
loom-error-handling
cosmix/loom 36
-
loom-feature-flags
Feature flag patterns for controlled rollouts, A/B testing, kill switches, and runtime configuration. Use when implementing feature toggles, feature flags, gradual rollouts, canary releases, percentage rollouts, dark launches, user targeting, A/B tests, experiments, circuit breakers, emergency kill switches, model switching, or infrastructure flags.
cosmix/loom 36
-
loom-i18n
cosmix/loom 36
-
loom-istio
cosmix/loom 36
-
loom-karpenter
Kubernetes node autoscaling and cost optimization with Karpenter. Use when implementing node provisioning, spot instance management, cluster right-sizing, node consolidation, or reducing compute costs. Covers NodePool configuration, EC2NodeClass setup, disruption budgets, spot/on-demand mix strategies, multi-architecture support, and capacity-type selection.
cosmix/loom 36
-
loom-kubernetes
cosmix/loom 36
-
loom-model-evaluation
cosmix/loom 36
-
loom-performance-testing
cosmix/loom 36
-
loom-plan-writer
cosmix/loom 36
-
loom-refactoring
Restructures existing code to improve readability, maintainability, and performance without changing external behavior.
USE WHEN: Restructuring code without changing behavior, extracting methods/classes, removing duplication, applying design patterns, improving code organization, reducing technical debt.
DO NOT USE: For bug fixes (use /loom-debugging), for adding tests (use /loom-testing), for new features (implement directly).
TRIGGERS: refactor, restructure, rewrite, clean up, simplify, extract, inline, rename, move, split, merge, decompose, modularize, decouple, technical debt, code smell, DRY, SOLID, improve code, modernize, reorganize.
cosmix/loom 36
-
loom-rust
cosmix/loom 36
-
loom-search
cosmix/loom 36
-
loom-terraform
cosmix/loom 36
-
loom-test-strategy
cosmix/loom 36
-
loom-testing
Comprehensive test implementation across all domains including unit, integration, e2e, security, infrastructure, data pipelines, and ML models. Covers TDD/BDD workflows, test architecture, flaky test debugging, and coverage analysis.
cosmix/loom 36