phoenix-channels-essentials
Use when building WebSocket features with Phoenix Channels — socket auth and tokens, join authorization, handle_in/push/broadcast, intercept/handle_out, Presence. Not for LiveView updates (use phoenix-pubsub-patterns).
phoenix-json-api
Use when building JSON API endpoints — :api pipeline, phx.gen.json-style JSON views, FallbackController, pagination, Bearer tokens, rate limits, CORS. Not for HTML/LiveView controllers.
phoenix-liveview-auth
Use when protecting LiveViews with the generated phx.gen.auth code — on_mount hooks, live_session, mount_current_scope, sudo mode, logout disconnects, auth tests. Not for extra user fields (phoenix-auth-customization) or per-record permissions (phoenix-authorization-patterns).
phoenix-liveview-essentials
Use when writing LiveView modules or HEEx templates — mount/handle_params lifecycle, forms with to_form and phx-change, streams, assign_async/start_async, JS commands, hooks, function components.
phoenix-pubsub-patterns
Use when adding real-time updates to LiveViews with Phoenix.PubSub — scoped topics, broadcasting from contexts, handle_info with streams, Presence in LiveView. Not for raw WebSocket APIs (use phoenix-channels-essentials).
phoenix-scopes-and-generators
Use when running phx.gen.live/html/json/context with scopes (--scope, --no-scope), editing config :my_app, :scopes, extending the %Scope{} struct with an org, or adopting scopes in a pre-1.8 app. Not for login plumbing (phoenix-liveview-auth) or permission rules (phoenix-authorization-patterns).
phoenix-tailwind-daisyui
Use when styling Phoenix 1.8 UI — Tailwind v4 app.css (@source, @plugin, no tailwind.config.js), dynamic classes, daisyUI themes/dark mode, core_components (<.input>, <.button>, <.icon>), Layouts.app, flash, accessibility. Not for LiveView forms/lifecycle or JS hooks (use phoenix-liveview-essentials).
phoenix-uploads
Use when implementing file uploads or serving uploaded files — allow_upload, consume_uploaded_entries, content-type allowlists, validators, local vs S3/external storage, authorized downloads.
security-essentials
Use when Elixir/Phoenix code handles params or other user input, String.to_atom on external strings, tokens, redirects, raw SQL, deserialization, outbound HTTP or security headers, or when asked to review code for security — injection, XSS, atom exhaustion, SSRF, open redirects, CSP, timing attacks, Sobelow. Not for permission rules (use phoenix-authorization-patterns).
telemetry-essentials
Use when adding logging, metrics, or instrumentation — Logger metadata, :telemetry handlers, Telemetry.Metrics tags, Ecto/Phoenix events, LiveDashboard, OpenTelemetry. Not for deployment config (use deployment-gotchas).
testing-essentials
Use when writing or fixing ExUnit tests — DataCase/ConnCase, generated fixtures and scopes, LiveView test helpers, uploads, Mox and Req.Test stubs, async and sandbox rules.
iris-development
Iris is Redis's umbrella for AI-focused products. Use this skill when integrating with the Iris Redis Agent Memory (RAM) data plane on Redis Cloud — recording session events for an AI agent, creating or searching long-term memories, configuring a memory store, or tuning background memory promotion. Code examples use the official `redis-agent-memory` (Python) and `@redis-iris/agent-memory` (TypeScript) SDKs.
redis-clustering
Redis Cluster and replication guidance covering hash tags for multi-key operations, avoiding CROSSSLOT errors, and reading from replicas to scale read-heavy workloads. Use when designing keys for a sharded Redis Cluster, debugging CROSSSLOT errors on MGET / SDIFF / pipelines, configuring a multi-key transaction in a cluster, or routing reads to replicas for caches, analytics, or dashboards.
redis-connections
Redis client and connection guidance covering connection pooling, multiplexing, pipelining, client-side caching with RESP3, avoiding slow commands (KEYS, SMEMBERS, HGETALL), and tuning socket timeouts. Use when configuring a Redis client (redis-py, Jedis, Lettuce, NRedisStack), batching commands for throughput, eliminating per-request connection creation, iterating large keyspaces with SCAN, enabling client-side caching for read-heavy workloads, or setting connect and read timeouts.
redis-core
Core Redis modeling guidance — choose the right data structure (String, Hash, List, Set, Sorted Set, JSON, Stream, Vector Set) and use consistent colon-separated key names. Use when designing a Redis data model, caching objects, deciding between Hash and JSON, building counters, leaderboards, membership sets, or session stores, or when reviewing/cleaning up Redis key naming.
redis-observability
Redis observability guidance — which metrics to monitor (memory, connections, hit ratio, ops/sec, rejected connections), which built-in commands to reach for during incident triage (SLOWLOG, INFO, MEMORY DOCTOR, CLIENT LIST, FT.PROFILE), and when to use the Redis Insight GUI. Use when setting up monitoring or alerts for a Redis instance, diagnosing a performance regression, profiling a slow FT.SEARCH query, or wiring Redis metrics into Prometheus, Datadog, or similar.
redis-search
Redis Search guidance covering FT.CREATE schema design, field type selection (TEXT, TAG, NUMERIC, GEO, GEOSHAPE, VECTOR, JSON path), DIALECT 2 query syntax, FT.SEARCH / FT.AGGREGATE / FT.HYBRID command selection, vector similarity with HNSW or FLAT, hybrid retrieval combining lexical and vector ranking, RAG pipelines, zero-downtime index updates via aliases, and debugging with FT.PROFILE and FT.EXPLAIN. Use when defining a search index on Hash or JSON documents, writing FT.SEARCH queries with filters, sorting, aggregation, or vector KNN, tuning HNSW parameters, building a RAG retrieval pipeline, or troubleshooting slow or empty search results.
redis-security
Redis security guidance covering authentication (requirepass and ACL users), TLS, ACL-based least-privilege access control, restricting network exposure via bind and protected-mode, firewall rules, and disabling dangerous commands. Use when deploying Redis to production, defining ACL users for an application, configuring TLS connections, locking down a Redis instance behind a firewall, or auditing a Redis deployment for security hardening.
redis-semantic-cache
Redis LangCache guidance for semantic caching of LLM responses on Redis Cloud — calling search/set via the SDK or REST API, tuning the similarity threshold, separating caches per task type, and filtering with custom attributes. Use when caching LLM completions or RAG answers to cut API cost and latency, building a cache-aside layer in front of OpenAI / Anthropic / etc., tuning hit rate vs precision, or splitting one app's LLM workloads into multiple LangCache caches.
autoconference
Run one budgeted research conference: parallel researcher children, adversarial review, synthesis; plus plan, resume, analyze, debate, survey and ship modes.
autoresearch
Runs a bounded experiment loop under an approved budget: one change per iteration, scored by a declared metric or evaluator, kept or reverted, logged; ten modes.
browser-drive
Drive a real browser to navigate, fill, click and extract from live pages, or name the blocker.
comment-checker
Audit code comments in a diff or named files: keep intent and reasons, remove stale narration, fix misleading text.
debugging
Fix a bug: reproduce it, test several hypotheses, isolate the cause, lock it with a failing test, then verify on the real surface.
deep-interview
Ask one focused question per round about a vague request, score the ambiguity, and write a spec that lit-plan can use. Use before planning broad work.
frontend-ui-ux
Build or restyle a UI: clear hierarchy, accessible contrast, responsive layout, browser-checked.
lit-adhd
Cross-session briefing: what each recent agy session was asked, did and waits on, with progress gauges and one next step. Alias: lit-rewind.
lit-brainstorm
Spread out on ideas before choosing: technique rounds, clusters, a scored shortlist and a hand-off packet. Use when the solution space is open.
lit-burnoff
Strip generated bloat from a bounded scope of files after locking their behavior with tests. Use to deslop a diff, folder or file list; one file goes to lit-burnoff-file.
lit-burnoff-file
Strip generated residue from exactly one file with behavior unchanged. Use for a single named file; a scope of many files goes to lit-burnoff.
lit-code
Shapes every code edit: build-decision gate, language references first, tests before code, input parsed once, typed seams, files under 250 pure LOC, clean lint and types.
lit-commit
Git work: atomic commits in the repo's own message style, staging, rebase and fixup, blame, bisect, log search.
lit-comprehend
Builds one self-contained HTML explainer of agent-written work: intuition, literate walkthrough, a micro-world to poke, and a quiz. Use when someone must understand a change.
lit-crucible
Pressure-test a brief before planning: independent risk lanes, ranked failure modes and the constraints that survive. Use for risky or hard-to-undo work.
lit-diagram-drawer
Draw an architecture, workflow, data-model or timeline diagram as editable SVG, check it, and export PNG. Use when a picture explains faster than prose.
lit-docx
Make a Word .docx report, proposal, manual, memo or manuscript from a request or sources in a chosen design direction, or convert DOCX/PDF to Markdown, gated and render-checked. Needs Python 3.10+.
litgoal
Set, check or close a durable goal in .litgravity/goals with criteria, status and evidence. Use when work must outlive this conversation.
lit-handoff
Write a verified continuation packet to .litgravity/handoff/latest.md: state, what was done and checked, what is left, and exact resume commands.
lit-hijack
Port someone else's published technique into your own skill or system, clean-room: capture with provenance, licence gate, source-free spec, isolated build, parity proof, provenance report.
lit-humanizer
Rewrites Korean or English prose so it reads in the writer's own voice for its reader, keeping meaning, facts, numbers and uncertainty. Use to polish or de-template text.
lit-init
Map an unfamiliar repository once and leave sparse AGENTS.md files: layout, commands, gates and traps. Use when onboarding a codebase or refreshing its agent guidance.
lit-loop
Bare lit default: take a task from request to verified PASS or named BLOCKED, with criteria, tests first, real-surface proof and a ledger.
lit-plan
Plan before code: write a decision-complete plans/<slug>.md with tasks, files, tests and checks. Use for planning, scoping and plan-then-build requests.
lit-pptx
Make a .pptx slide deck from a request or sources in a chosen design direction, gate it mechanically, then look at every rendered page. Needs Python 3.10+.
lit-recap
Read-only recap of where the work stands: goals, plan rows, ledger, evidence, blockers and the next safe step, from .litgravity/ and plans/.
litresearch
Researches a question across sources down to primary evidence (prior art, landscapes, disputed claims) and returns a referenced synthesis. A one-fact lookup needs no skill.
lit-schematic
Draw a P&ID, PFD, equipment layout, journal apparatus figure or isometric cutaway as editable SVG with QA gate and 600 dpi PNG export. For real hardware and piping, not abstract diagrams.
lit-scientific-visualization
Make a publication-ready figure from measured data: chart form, units, colorblind-safe color, export and visual check.
lit-team
Coordinate two or more child agents behind a durable team packet: owned slices, evidence reports, archive receipt. Use for team mode, not a single delegation.
lit-typographic-motion
Film director for a finished short film from a one-line request, made the same way every time with house styles, a scaffold, a storyboard board round, an original layered score and a QA gate.
Page 509 of 1695 · 84731 results
