Results for “bea”

HTTP middleware, JWT authentication, auth middleware, custom guards, JWT guard, route middleware, request filter, middleware group, Acorn middleware, guard, rate limiting, CORS, CheckRole, throttle, bearer token, request filtering, middleware registration, HTTP Kernel — using Acorn's Laravel middleware stack inside WordPress/Sage/Bedrock

Expert real-time VFX artist specializing in particle systems, shader effects, and the invisible craft that makes games feel satisfying. Masters Niagara, VFX Graph, Godot GPU particles, and understands the AAA principles that make effects read clearly at 60fps. Use when "particle system, visual effects, vfx, particles, niagara, vfx graph, flipbook, sprite sheet, explosion effect, magic effect, trail effect, beam effect, dissolve, distortion, force field, hit effect, muzzle flash, impact effect, smoke particles, fire effect, soft particles, game juice, screen shake, particle overdraw, effect optimization, vfx, particles, effects, niagara, vfx-graph, game-juice, visual-effects, shaders, flipbook, trails, beams, explosions, optimization, gpu-particles" mentioned.

Use when adding a fixed full-screen WebGL laser background with a thin white-hot vertical core, restrained brand-colored halo, and soft smoky fog. Prefer this over mengto-corner-lasers when the beam is a full-viewport WebGL background, not corner ornaments; not for full page layout, copy, or unrelated particle systems.

Bidirectional conversion between Erlang and Roc. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Erlang↔Roc specific patterns. Use when migrating Erlang projects to Roc, translating BEAM/OTP patterns to functional patterns, or refactoring Erlang codebases. Extends meta-convert-dev with Erlang-to-Roc specific patterns.

Bidirectional conversion between Elixir and Roc. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Elixir↔Roc specific patterns. Use when migrating Elixir projects to Roc, translating BEAM/OTP patterns to platform-based architecture, or refactoring Elixir codebases. Extends meta-convert-dev with Elixir-to-Roc specific patterns.

Bidirectional conversion between Elixir and Scala. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Elixir↔Scala specific patterns. Use when migrating Elixir/Phoenix applications to Scala, translating BEAM OTP patterns to Akka actors, or refactoring dynamic concurrency to statically-typed JVM patterns. Extends meta-convert-dev with Elixir-to-Scala specific patterns.

Save working context. Captures git state, decisions made, and remaining work so any future session can pick up without losing a beat. Use when asked to "save progress", "save state", "context save", or "save my work". Pair with /context-restore to resume later. Formerly /checkpoint — renamed because Claude Code treats /checkpoint as a native rewind alias in current environments, which was shadowing this skill. (gstack)

Makes iOS apps feel premium, polished, and unmistakably native — SF Symbols mastery, SwiftUI spring animations, haptic feedback choreography, blur/vibrancy materials, Dynamic Type, color system design, and the specific spacings and radii Apple uses. This is about TASTE, not syntax. Activate on 'iOS design polish', 'SwiftUI animation', 'SF Symbols', 'haptic feedback', 'premium iOS feel', 'Apple HIG', 'native iOS look', 'Liquid Glass', 'iOS visual design', 'app polish'.

Bidirectional conversion between Elixir and Erlang. Use when migrating projects between these languages in either direction. Extends meta-convert-dev with Elixir↔Erlang specific patterns. Use when migrating Elixir projects to Erlang, translating Elixir patterns to Erlang idioms, or refactoring Elixir codebases to Erlang. Both run on the BEAM VM with the same OTP framework, making this conversion primarily syntactic with semantic preservation. Extends meta-convert-dev with Elixir-to-Erlang specific patterns.

A complete tour of the intelli-verse-x 5-layer stack — Leantime/GitHub at the top, Beads/Bernstein/Claude-Squad in the middle, Gas Town as the multi-project fabric, and LiteLLM/Infisical/Langfuse/n8n/GH-Actions underneath. Use whenever the user asks "what does X service do", "where does Y data live", "how do I get to Z", or you need to understand which tool to reach for. This is the architecture map.

Use when building a dark glass sci-fi instrument UI with frosted shells, soft beam grids, and circular clock-like calibration dials. Prefer this over mengto-dark-glass-clean-layout when clock dials and instrument framing are the signature, not multi-column workspace shells; prefer over mengto-blue-laser-clean-glass-layout when dials matter more than a blue laser atmosphere; prefer over mengto-glass-dark-ui when calibration dials matter more than gradient-border glass cards.