ReddRadar
Topic: agents
2,643 skills in this topic.
-
loom-accessibility
cosmix/loom 36
-
loom-api-design
cosmix/loom 36
-
loom-api-documentation
cosmix/loom 36
-
loom-argocd
cosmix/loom 36
-
loom-auth
Authentication and authorization patterns including OAuth2, JWT, RBAC/ABAC, session management, API keys, password hashing, and MFA.
USE WHEN: Implementing login flows, access control, identity management, tokens, permissions, session handling, API key authentication, or MFA.
DO NOT USE: For security vulnerability scanning (use /loom-security-scan), for security audits (use /loom-security-audit), for threat modeling (use /loom-threat-model).
TRIGGERS: login, logout, signin, signup, authentication, authorization, password, credential, token, JWT, OAuth, OAuth2, OIDC, SSO, SAML, session, cookie, RBAC, ABAC, permissions, roles, MFA, 2FA, TOTP, API key, PKCE.
cosmix/loom 36
-
loom-background-jobs
Background job processing patterns including job queues, scheduled jobs, worker pools, and retry strategies. Use when implementing async processing, job queues, workers, task queues, async tasks, delayed jobs, recurring jobs, scheduled tasks, ETL pipelines, data processing, ML training jobs, Celery, Bull, Sidekiq, Resque, cron jobs, retry logic, dead letter queues, DLQ, at-least-once delivery, exactly-once delivery, job monitoring, or worker management.
cosmix/loom 36
-
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-code-review
cosmix/loom 36
-
loom-concurrency
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-dependency-scan
cosmix/loom 36
-
loom-diagramming
cosmix/loom 36
-
loom-docker
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-fluxcd
cosmix/loom 36
-
loom-git-workflow
cosmix/loom 36