The working skills behind the design lab and the product. Each is a SKILL.md an agent loads for one kind of task, published here by name and description: the engineering and productivity skills from the wiki, and the General Translation repository skills as a third group. Every skill has its own page with the full SKILL.md; the list on the left follows the row in view, and a row opens the page.
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
Declarative web framework for building browser-based 3D, VR, and AR experiences using HTML and entity-component architecture. Use this skill when creating WebXR applications, VR experiences, AR experiences, 360-degree media viewers, or immersive web content with minimal JavaScript. Triggers on tasks involving A-Frame, WebXR, VR development, AR development, entity-component-system, declarative 3D, or HTML-based 3D scenes. Built on Three.js with accessible HTML-first approach.
Default browser automation surface for Kevin's agents. Use when automating browsers, opening sites, scraping pages, filling forms, taking screenshots, testing UIs, extracting data, checking logged-in Chrome sessions, debugging localhost, validating frontend behavior, inspecting React/Web Vitals, or when the user asks for Playwright/Puppeteer-style browser interaction without explicitly requesting committed test files. Use Playwright only for regression tests or existing test suites.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, embed, tools, WorkflowAgent, Agent, HarnessAgent, useChat, or useCompletion, (2) Want to build AI agents, chatbots, RAG systems, durable workflows, or text generation features, (3) Have questions about AI providers, streaming, tool calling, structured output, embeddings, reasoning, approvals, telemetry, MCP Apps, file/skill uploads, or AI SDK testing. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat", "WorkflowAgent", "AI SDK test".
Route polished React, Tailwind, shadcn/Radix/Base/React Aria, chart, toast, shader, animated-icon, timeline, interaction, and creative-design-app work to the strongest source before hand-crafting. Use for landing pages, dashboards, design systems, agent artifacts, uncommon components, charts, narrative timelines, notifications, shaders, icons, hover/scroll micro-interactions, or a canvas-and-controls design tool. Triggers on component libraries or vocabulary; Toolcraft; Component Gallery; Design Engineer Tools; shadcn/ui; Radix; Base UI; Astryx; Kumo; Blocks.so; Tailark; 8bitcn; Kibo UI; Intent UI; SmoothUI; UI-Layouts; Shadcn Blocks; Shadcn Studio; Shadcn Space; Kokonut; Bklit; Chanh Dai; Evil Charts; Lifeline; Sonner; Skiper; Cult UI; Magic UI; Motion Primitives; React Bits; Originkit; Fancy Components; Origin UI; Componentry; Iconsax; Its Hover; lucide-animated; Super Hover; Shaders.com; Tailwind components; or "find better design sources."
Versatile JavaScript animation engine for DOM, CSS, SVG, and JavaScript objects. Use when creating timeline-based animations, stagger effects, SVG morphing, keyframe sequences, or complex choreographed animations. Triggers on tasks involving Anime.js, timeline animations, staggered sequences, SVG path animations, morphing, or multi-step animation choreography. Alternative to GSAP for SVG-heavy animations and React-independent projects.
Design and build high-converting questionnaire-style app onboarding flows modelled on proven conversion patterns from top subscription apps (Headspace, Noom, Duolingo). Use when building onboarding flows, sign-up funnels, questionnaire UIs, or conversion-optimized first-run experiences. Triggers on "onboarding flow", "sign-up questionnaire", "first-run experience", "conversion funnel", "paywall flow", "app onboarding", "welcome screen", or "user activation". Based on adamlyttleapps/claude-skill-app-onboarding-questionnaire (374 GitHub stars).
Skill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, or deploying an Astro project.
Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.
Use for AWS work: IAM, CDK, CloudFormation, Lambda, serverless, S3, RDS, VPC, Route 53, CloudFront, MSK, Flink, data lakes, Bedrock, cost, observability, security, and SDK usage. Load folded AWS references only for the named service or failure mode.
Use for Azure work: app deployment, azd, Bicep, Terraform on Azure, resource lookup, diagnostics, cost, compliance, RBAC, storage, messaging, Kusto, Kubernetes, AI Gateway, Foundry, hosted Copilot SDK, App Insights, Entra, migration, upgrade, and validation.
Comprehensive skill for Babylon.js 3D web rendering engine. Use this skill when building real-time 3D experiences, browser-based games, interactive visualizations, or immersive web applications. Triggers on tasks involving Babylon.js, 3D scenes, WebGL/WebGPU rendering, entity-component systems, physics simulations, PBR materials, shadow mapping, or 3D model loading. Alternative to Three.js with built-in editor integration and game engine features.
Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain `.gcode`, using Bambu LAN FTPS/MQTT handoffs.
Page transitions library for creating fluid, smooth transitions between website pages. Use this skill when implementing page transitions, creating SPA-like experiences, adding animated route changes, or building websites with smooth navigation. Triggers on tasks involving Barba.js, page transitions, routing, view management, transition hooks, GSAP integration, or smooth page navigation. Works with gsap-scrolltrigger for transition animations.
Agent-led beta DX/UX readiness walk. Walk a product's critical user journeys as a skeptical first-time user and treat friction as a bug: anything that makes the user pause, guess, reread, or ask for help is a logged issue. At every step test two things - can the user understand what to do next, and can they recover when something fails. Triage each finding as blocks-beta, confuses-beta, or polish, with tried / expected / happened plus evidence, and end with a ship-or-hold readiness verdict. Use for beta readiness, onboarding and first-run QA, pre-launch UX gates, "walk the beta path", "is this ready for users", or "treat friction as a bug". Project-agnostic.
Blender to web export workflows for 3D models and animations. Use this skill when exporting Blender models to glTF for web, optimizing 3D assets for Three.js or Babylon.js, batch processing models with Python scripts, automating Blender workflows, or creating web-ready 3D pipelines. Triggers on tasks involving Blender glTF export, bpy scripting, 3D asset optimization, model compression, texture baking, or Blender automation. Exports models for threejs-webgl, react-three-fiber, and babylonjs-engine skills.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
CTF-style security and correctness audit. Dispatches parallel Opus subagents to hunt for day-0 bugs in security-critical files. Each agent must find a real bug or honestly admit failure. Use when you want a thorough adversarial review of a codebase area.
Create, modify, inspect, and validate STEP-first parametric CAD parts and assemblies. Use for natural-language CAD specs, reference images, 2D technical drawings, STEP/STP generation or direct inspection, Python CAD source, source-level joints, selector references, geometry facts, measurements, mating deltas, snapshots, and secondary STL/3MF/native GLB outputs from CAD geometry.
Start CAD Viewer and return review links for explicit CAD, implicit CAD, and robot-description files. Use when visually reviewing `.step`, `.stp`, `.implicit.js`, `.implicit.mjs`, `.glb`, `.stl`, `.3mf`, `.dxf`, `.urdf`, `.srdf`, or `.sdf` files, especially when handed off from CAD, implicit-cad, URDF, SRDF, or SDF generation skills.
Apply Dedalus CI/CD workflow rules for runner placement, Docker build verification, artifact publication, and self-hosted runner orchestration. Use when editing GitHub Actions workflows, Docker build pipelines, deploy jobs, Terraform/ECS/Flux workflows, or self-hosted runner automation.
Audit CI-related changes across one or more PRs to prove a green build was EARNED, not gamed. Use after getting a batch of PRs green, before merging a stack, or whenever you suppressed a warning / skipped a test / touched a config to make a check pass. Enumerates every check-suppression anti-pattern (lint-disable, ts-ignore, test skips, deleted tests, threshold/budget bumps, editing the gate or a guard, swallowed failures, hook bypass, fake-green, silent fallbacks, retry-until-green), greps every PR diff for them, and judges each hit as justified vs. green-washing with file:line evidence. Especially important for agent-authored PR batches, where the temptation to silence a check instead of fixing it is highest.
Use for Clerk authentication work: setup, users, sessions, middleware, backend API, organizations, billing, webhooks, testing, custom UI, mobile auth, and framework integrations for Next.js, React, Astro, TanStack, Vue, Nuxt, Expo, Android, Swift, React Router, and Chrome extensions.
Use for Cloudflare work: Workers, Wrangler, Durable Objects, Agents SDK, Sandbox SDK, Turnstile, email service, Cloudflare One, migrations, web performance, tunnels, and Workers best-practice review.
Design deep modules and clean seams. Use when the user wants to improve architecture, design or compare module interfaces, decide where a seam belongs, make code more testable or AI-navigable, run a deletion test, or when another skill needs deep-module vocabulary. Adapted from mattpocock/skills.
Enforce column-aligned inline comments on dataclass and enum fields. Use when writing or reviewing Python dataclasses, enums, TypedDicts, or any structured type with inline field comments.
Write doc comments, module docs, and inline comments that follow Dedalus conventions per language. Loads the canonical style guides from the monorepo. Covers Rust, Python, Go, and TypeScript.
Create a git commit with conventional commit format. Injects current git state automatically.
Control local Mac apps through Computer Use. Use for tasks that require reading or operating app UI by clicking, typing, scrolling, dragging, pressing keys, or setting values.
Control the in-app Browser. Use to open, navigate, inspect, test, click, type, screenshot, or verify local targets such as localhost, 127.0.0.1, ::1, file://, the current in-app browser tab, and websites shown side by side inside Codex.
Build or audit CopilotKit, AG-UI, Open Tag, and agent-frontend integrations. Use when the user mentions CopilotKit, Open Tag, AG-UI, generative UI, Slack/Teams/Discord/Google Chat agents, human-in-the-loop agent UI, or frontend surfaces for custom agents.
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
Compare the current implementation against the minimal correct algorithm. Use when debugging regressions, reviewing complex fixes, or when the user asks what should happen versus what is happening now.
Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth. Detect frameworks, configure database adapters, set up route handlers, add OAuth providers, and create auth UI pages. Use when users want to add login, sign-up, or authentication to a new or existing project with Better Auth.
Create polished, brand-aligned feature illustrations, architecture or workflow diagrams, infographics, and website graphics. Use when a user asks to illustrate a feature, explain a system visually, turn a workflow into a diagram, produce an editable whiteboard, make a social graphic, or replace generic AI-looking product art with a deliberate visual artifact.
Quality gate via a second AI model. Spawn a different model to review work before committing. Grades against the originating skill's Contract. Use when you want a second opinion from a different model, or the user says "second opinion", "cross-modal review", "double check this", or "get another perspective".
Check the current author's commits from the last 24 hours and proactively find and fix any bugs they introduced. Use when the user asks for a daily bugfix check, wants to review today's commits for issues, or asks to "check my recent code for bugs." Combines commit review with the recent-code-bugfix workflow.
Run read-only SQL queries against Supabase databases (local or remote). Use when inspecting schema, debugging data, checking migrations, or answering questions about database state.
Run mutating SQL (INSERT, UPDATE, DELETE, DDL) against Supabase databases. Requires explicit user invocation. Use for migrations, seed data, schema changes, or data fixes.
Run DCS test profiles against controlplane (Go), host-agent (Rust), storage-daemon, or live clusters. Use when testing DCS changes locally or triggering CI test suites.
Run vercel-labs/deepsec — an agent-powered vulnerability scanner — against any local codebase. Use when Kevin says "deepsec", "security scan", "scan this repo for vulns", "find security bugs in <repo>", "audit <project> for vulnerabilities", "production security review", or before shipping a new service. Performs a regex pre-scan, chooses a current benchmark-backed `best`, `value`, or `budget` model/harness profile, investigates candidates, revalidates to cut false positives, and exports actionable findings. Cost-aware: always preserve the benchmark snapshot and run a `--limit 50` calibration before a full scan.
Kevin's design-engineering polish route for building, auditing, planning, and discovering UI motion; prototyping design variants and signature-first visual directions; selecting UI libraries; improving component feel; and applying animation vocabulary and invisible interface details. Use when implementing or reviewing animation decisions, finding motion opportunities, preparing animation plans, prototyping alternatives, choosing a component library, polishing components, or when the user says "Emil", "animation review", "component polish", "motion details", "animations.dev", or "make it feel right".
Disciplined diagnosis loop for hard bugs, regressions, failures, flakes, and performance problems. Use when the user says "diagnose", "debug this", "this is broken", "why is this failing/slow", or reports a bug that needs a tight repro before fixing. Adapted from mattpocock/skills.
Auto-run the relevant codebase doctor(s) after large edit sessions or before committing. Detects which subsystems were touched and runs the matching doctor or security doctor chain. Use when the agent has completed a significant edit (5+ files), before claiming work is done, or when the user says "run doctors", "health check", "doctor pass", or "check everything."
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology, define a ubiquitous language, create or update CONTEXT.md / CONTEXT-MAP.md, record an ADR, resolve overloaded terms, or when another planning/code skill needs shared domain vocabulary. Adapted from mattpocock/skills.
Generate, regenerate, and validate 2D DXF drawings from Python ezdxf sources. Use for DXF files, `.dxf.py` generators, gen_dxf() sources, 2D profiles, outlines, templates, gaskets, panels, flat patterns, laser/plasma/waterjet cut layouts, and 2D drawing exports of CAD geometry.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Ensure Kevin's open-source repos ship with an MIT LICENSE before publish or on audit. Use when creating a new public repo, open-sourcing a project, publishing to npm/GitHub, Kevin says "add license", "MIT license", "missing LICENSE", "license audit", or before marking a repo public. Runs audit + apply via scripts/ensure-mit-license.ts and agent-docs license doctor check.
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", "generate an Excalidraw file", "show this system visually", or "draw the agent/system architecture". Supports flowcharts, relationship diagrams, mind maps, system snapshots, and architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw, with PNG/SVG previews when useful.
Compare implementation against canonical open-source references. Clone exemplars into /tmp, diff edge cases, error paths, and protocol invariants. Use when building a new subsystem, after a refactor, or when reviewing code that implements a known standard (POSIX, FUSE, WAL, S3, NFS, etc.).
Dedalus philosophy on conditional logic, error paths, and why we never write fallbacks. Use when writing or reviewing any branching logic that selects between strategies, modes, or error-recovery paths.
Use for Firebase work: CLI setup, project selection, Auth, Firestore, Hosting, Security Rules, Data Connect, AI Logic, App Hosting, Crashlytics, Remote Config, and Firebase MCP or firebase-tools workflows.
Audit code for loose types that allow semantically invalid values to compile. Introduces newtypes, checked casts, enums over booleans, and documents wire/DB discriminant contracts. Use when writing structs with bare primitives, reviewing database or protocol code, or when a function takes 2+ parameters of the same type.
Use when: the user asks to make or render charts with flint-chart, visualize tabular data, generate a ChartAssemblyInput, validate/render through MCP, or add Flint to a JS/TS project. Author the semantic spec, transform data before Flint when needed, install/import Flint only when executable code is needed, and reserve backend-specific style tweaks for after compiling from Flint.
Build a floating font selector dev tool for any Next.js app. Copies font files, generates @font-face CSS, creates a FontProvider context with localStorage persistence, and builds a floating selector UI. Use when evaluating candidate typefaces across an app, adding font preview capability, or when the user says "font switcher", "try fonts", "compare fonts", or "add a font selector."
Distinctive, production-grade frontend interfaces that reject generic AI aesthetics. Use when creating UI components, landing pages, design systems, or any frontend work. Triggers on "make it look good", "design direction", "avoid generic", "art direction", "design taste", "landing page", "UI design", or any frontend creation task. Based on anthropics/skills (259K weekly installs).
Build distinctive frontends that avoid generic AI aesthetics. Provides anti-slop enforcement, variance dials, art direction archetypes, product-specific icon-system admission, creative arsenal, and performance guardrails. Use when creating new landing pages, UI components, design systems, choosing or replacing an icon library, or when the user says "make it look good", "design direction", "avoid generic", "art direction", "design taste", "icon system", or "replace Lucide."
Use when the user wants a high-signal frontend, distinctive art direction, strong motion design, 3D/parallax, shader effects, landing pages, docs sites, dashboards, or a tokenized design system that avoids generic AI-generated UI.
Generate, inspect, dry-run, and statically validate plain FDM `.gcode` from 3D mesh files by orchestrating real slicer CLIs. Use when Codex needs to slice `.stl`, `.obj`, unsliced `.3mf`, `.ply`, `.glb`, or `.gltf` into printer-profiled G-code, discover local slicer backends, inspect whether a mesh is slice-ready, or validate generated G-code before any printer-specific handoff.
Define or refactor subsystem interfaces into small, explicit contracts with clear ownership, narrow scope, stable semantics, and README-first documentation. Use when designing a new API, collapsing ad hoc module boundaries into a few coherent interfaces, hardening internal contracts, or rewriting subsystem docs so engineers can understand the system by reading README.md files, docstrings, and code only.
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
Complete Go style reference for Dedalus. Loads the full guide, decisions, and best practices documents (~7000 lines). Use when writing, reviewing, or refactoring Go code and the rules file doesn't cover the specific pattern.
Safe Graphify sidecar workflow for repo architecture graphs, repo topology, "what touches what", project onboarding, focused subgraph queries, path/explain questions, PR and risk analysis, affected-node blast-radius checks, and Graphify save-result/reflect learning. Use when the user says graphify, graphify sidecar, build/query a repo graph, codebase knowledge graph, persistent repo map, focused subgraph, graph path, explain node, affected node, 71x token reduction, or wants repo-level memory without replacing qmd.
Explain system behavior, request flows, architecture, or implementation logic as short 4chan-style greentext lines. Use when the user asks for a step-by-step explanation, says "explain the logic", asks for "greentext", or wants terse sequential reasoning with each line starting with `>`.
Two-stage grilling session for any non-trivial app, feature, or refactor — FIRST map the SHAPE of the design tree (breadth: decision axes, branches, and dependencies), THEN resolve the current dependency frontier in numbered rounds with a recommendation for every question, escalating load-bearing uncertainty to prototypes and updating CONTEXT.md / ADRs as decisions crystallise. Use whenever the user wants to plan, stress-test, or align before a PRD or code, including "let's think through this", "grill me", "help me plan X", "what am I missing", or "interrogate this idea". Pre-PRD phase of the 7-phase AI-development pipeline.
Comprehensive skill for GSAP (GreenSock Animation Platform) and ScrollTrigger plugin. Use this skill when creating web animations, scroll-driven experiences, timelines, tweens, scroll-triggered animations, pinning, scrubbing, parallax effects, or animating DOM elements, SVG, Canvas, WebGL, or Three.js. Triggers on tasks involving GSAP, ScrollTrigger, smooth animations, scroll effects, or animation sequencing.
Design audit with UX usability tests plus change-scoped interface review for branches, diffs, and pull requests. Use when the user says "design review", "UX audit", "visual audit", "audit the UI", "review this UI change", "design regression check", "how does this site look", or wants a comprehensive design audit with usability testing.
QA lead with real browser testing. Tests your app, finds bugs, fixes them with atomic commits, generates regression tests. Use when the user says "QA", "test this", "find bugs", "exploratory test", "QA this", or "test the app".
Staff-engineer code review. Finds bugs that pass CI but blow up in production. Auto-fixes the obvious ones. Flags completeness gaps. Use when the user says "code review", "review this", "check for production bugs", "review my changes", or "/review".
Provision, audit, or operate Hetzner Cloud servers, networks, firewalls, volumes, snapshots, SSH keys, and remote validation boxes. Use when a task mentions Hetzner, hcloud, dedicated servers, cheap EU compute, or brokered remote machines.
Cherry-pick a commit from dev onto preview without a PR. Use when you need to cherry-pick a fix to preview without a PR, or for urgent fixes that can't wait for a full promote cycle.
Mandatory entry point: read this first for any request to make, create, edit, animate, or render a video, animation, or motion graphic, including a promo, explainer, captioned clip, title card, overlay, slideshow or interactive deck, Remotion port, or any HyperFrames HTML composition. Also use it to inspect, diagnose, validate, preview, publish, or batch-render an existing HyperFrames project. Inputs may be a website URL, GitHub PR, Figma design or URL, text or brief, existing footage, or music. It resumes project state, captures intent when applicable, selects and installs the owning workflow, and routes domain capabilities. HyperFrames is the default output framework unless the user explicitly chooses another framework for the deliverable or asks only to record a browser session.
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.
The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.
Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.
Use when a HyperFrames composition needs seek-safe 2D/3D keyframes, GSAP timelines, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.
Install, discover, and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json. Covers discovery, install locations, block sub-composition wiring, component snippet merging, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).
Creates original editorial illustrations where a recurring mascot character performs the idea — one caught scene by default, a hand-built explainer diagram (a flow, fan-out, timeline, loop, or stack) when the structure itself is the point, or a transparent character cutout (pose-only compositing asset, no scene or text) — in one of seventeen bundled looks (sixteen print, plus a photoreal toy-brick set). Also handles "surprise me" / "random" (optionally scoped to a focus or character): rolls provenance, builds three saying candidates, picks via interactive choice or auto-pick-best (`--autopick`), and renders one image. Triggers only when the skill is directly invoked or "illo" is requested; never on generic illustrate / draw / make-an-image requests.
Turn an object or character reference image into a quality-gated, animation-ready procedural Three.js model built in code. Use for image-to-3D reconstruction, detail-accurate object rebuilds, stylized/likeness-maximized human characters, sculpt specs, and staged code generation.
Implement a bounded piece of work from a PRD, issue, or agent-ready ticket. Use when Kevin invokes /implement or passes a specific PRD/issue and wants execution through TDD/checks/review.
Create, edit, render, and snapshot browser-native implicit CAD `.implicit.js` and `.implicit.mjs` files using GLSL signed-distance fields, shader primitives, smooth booleans, TPMS fields, and direct CAD Viewer raymarch rendering. Experimental.
Extract animation frame data from upstream Unicode spinner libraries into the wiki's runtime-agnostic `spinners-catalog.json`. Use when Kevin asks to "import spinners from X", "add more spinners", "pull the frames from this repo", evaluates a new spinner library, wants to expand the loading-screens catalog, or asks "should I swap unicode-animations for X?". Handles the full flow: 1v1 evaluation vs the canonical library, shallow clone, frame extraction from TSX/JS component files, JSON normalization, and wiki doc updates.
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Scan a codebase for deepening opportunities, present a visual architecture report, then grill through the selected candidate. Use when Kevin invokes /improve-codebase-architecture, asks for architecture deepening, ball-of-mud cleanup, or agent-navigability improvements.
Reason from proven invariants before coding. Use when reviewing fallback logic, narrowing types, handling conversions, deciding whether an error path is real or impossible, removing overdefensive code, or when the user questions whether code is being too theatrical, too hedged, or not fail-closed enough.
Create a GitHub issue using the Dedalus issue templates (bug, feature, question). Injects branch and commit context automatically, prompts for Linear link. Use when creating a GitHub issue using Dedalus templates, or the user says "file an issue", "create issue", "open a bug", or "report a feature request".
Design, implement, or review Apache Kafka-compatible event streaming. Use for Kafka, Redpanda, Confluent Cloud, AWS MSK, topics, partitions, consumer groups, schemas, retention, lag, producers, consumers, stream processing, or event-driven architecture.
Router for Kevin's engineering flow. Use when Kevin invokes /kevin-engineering-flow, asks which engineering skill or flow fits, or wants a path through grill-with-docs, prototype, PRD, issues, implement, triage, and architecture improvement.
Simplify a problem by replacing sequence reasoning with state invariants. Use when the user invokes /lamport, asks for Lamport-style reasoning, or when a task has many cases, phases, interactions, or edge conditions that are hard to reason about directly.
Audit prose (comments, docs, READMEs, commit messages, PR descriptions) for jargon, unexplained acronyms, and assumed context. Rewrites for the least experienced reader. Use after writing docs, READMEs, or any prose that will be read by someone who did not write the code.
Lightweight 3D effects for decorative elements and micro-interactions using Zdog, Vanta.js, and Vanilla-Tilt.js. Use this skill when adding pseudo-3D illustrations, animated backgrounds, parallax tilt effects, decorative 3D elements, or subtle depth effects without heavy frameworks. Triggers on tasks involving Zdog pseudo-3D, Vanta.js backgrounds, Vanilla-Tilt parallax, card tilt effects, hero section animations, or lightweight landing page visuals. Ideal for performance-focused designs.
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
Use when a task involves a document file (PDF, DOCX, PPTX, XLSX, or image) and the agent needs to read it, answer questions about contents, or extract text, tables, or specific values. Provides fast, local, model-free extraction via the `lit` CLI with low-cost search patterns.
Implement loading states using braille Unicode spinners and skeleton placeholders. Use when adding loading indicators, replacing spinners, or building new loading screens. Covers component API, sizing, spinner selection, and anti-patterns.
Comprehensive skill for Locomotive Scroll smooth scrolling library with parallax effects, viewport detection, and scroll-driven animations. Use this skill when implementing smooth scrolling experiences, creating parallax effects, building scroll-triggered animations, or developing immersive scrolling websites. Triggers on tasks involving Locomotive Scroll, smooth scrolling, parallax, scroll detection, scroll events, sticky elements, horizontal scrolling, or GSAP ScrollTrigger integration. Integrates with GSAP for advanced scroll-driven animations.
Lottie generation and playback for web and React applications. Use this skill when generating or implementing Lottie animations, text-to-Lottie assets, SVG-to-Lottie motion, JSON vector animations, interactive animated icons, micro-interactions, or loading animations. Triggers on tasks involving Lottie, text-to-lottie, diffusionstudio/lottie, lottie-web, lottie-react, dotLottie, After Effects JSON export, bodymovin, animated SVG alternatives, or designer-created animations. Complements GSAP ScrollTrigger and Framer Motion for scroll-driven and interactive animations.
Design engineering principles for making interfaces feel polished. Use when building or reviewing UI components, motion, typography, surfaces, icons, micro-interactions, and state feedback. Supports quick and full review modes. Triggers on UI polish, "make it feel better", "feels off", motion restraint, icon weight, optical alignment, and interaction-state review.
Build the smallest correct version first. Name every case, implement only what has a real consumer, return typed errors for the rest. Use when designing new systems, extracting shared packages, or deciding how much to build before shipping.
Mastering Mintlify's MDX pipeline — undocumented constraints, snippet sandbox rules, CSS override patterns, and npm bundling via yoink. Use when writing or debugging Mintlify snippets, customizing docs.json/styles.css, bundling npm packages into snippets, hitting cryptic MDX compile errors, or when the user says 'mintlify', 'snippet won't compile', 'MDX error', 'yoink', 'lint-snippets', 'docs.json', 'Mintlify CSS', 'function-body mode', 'baseUrl error', or 'findExport'. Reverse-engineered from Mintlify internals at Dedalus Labs.
Modern web design trends, principles, and implementation patterns for 2024-2025. Use this skill when designing websites, creating interactive experiences, implementing design systems, ensuring accessibility, or building performance-first interfaces. Triggers on tasks involving modern design trends, micro-interactions, scrollytelling, bold minimalism, cursor UX, glassmorphism, accessibility compliance, performance optimization, or design system architecture. References animation skills (GSAP, Framer Motion, React Spring), 3D skills (Three.js, R3F, Babylon.js), and component libraries for implementation guidance.
Modern animation library for React and JavaScript. Create smooth, production-ready animations with motion components, variants, gestures (hover/tap/drag), layout animations, AnimatePresence exit animations, spring physics, and scroll-based effects. Use when building interactive UI components, micro-interactions, page transitions, or complex animation sequences.
Use for Next.js work: App Router, Server Components, Server Actions, Cache Components, middleware/proxy, data fetching, rendering strategy, upgrades, next-forge, performance, and Vercel deployment behavior.
Run a strict Dedalus STYLE-informed code-quality doctor for agent-authored PRs. Use when Kevin says "no sus code", "strict review", "quality doctor", "get this to 100", "prove this works", "review try/catches/fallbacks/ensure patterns", "review retries/timeouts/hooks/lint ignores", or before shipping high-risk auth, billing, Stripe, fraud, onboarding, credit, admin, infra, or security changes.
OKLCH color space for web projects. Convert hex/rgb/hsl to oklch, generate palettes, check contrast, handle gamut boundaries, and theme with Tailwind v4. Triggers on oklch, color conversion, palette generation, contrast ratio, gamut, display p3, design tokens, hue drift, chroma, dark mode colors.
Discipline for performance investigations. Ramp up from cheap experiments to expensive ones. Profile before patching. Isolate hypotheses with standalone probes before touching production code. Numbers gate every decision. Use when the user says `/perf`, asks to speed up code, or asks why something is slow.
Fast, lightweight 2D rendering engine for creating interactive graphics, particle effects, and canvas-based applications using WebGL/WebGPU. Use this skill when building 2D games, particle systems, interactive canvases, sprite animations, or UI overlays on 3D scenes. Triggers on tasks involving PixiJS, 2D rendering, sprite sheets, particle effects, filters, or high-performance canvas graphics. Alternative to Canvas2D with WebGL acceleration for rendering thousands of sprites at 60 FPS.
Lightweight WebGL/WebGPU game engine with entity-component architecture and visual editor integration. Use this skill when building browser-based games, interactive 3D applications, or performance-critical web experiences. Triggers on tasks involving PlayCanvas, entity-component systems, game engine development, WebGL games, 3D browser applications, editor-first workflows, or real-time 3D rendering. Alternative to Three.js with game-specific features and integrated development environment.
Use for committed Playwright regression tests, existing Playwright suites, CI browser gates, traces for reproducible failures, and explicit user requests to write or run Playwright test files. Do not use for ordinary agent browser interaction, scraping, form filling, screenshots, or localhost visual QA; route those to agent-browser unless the repo's existing test suite requires Playwright.
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces via pnpm-workspace.yaml, or managing dependencies with catalogs, patches, overrides, config dependencies, or the global virtual store.
Set up and use portless for named local dev server URLs (e.g. https://myapp.localhost instead of http://localhost:3000). Use when integrating portless into a project, configuring dev server names, setting up the local proxy, working with .localhost domains, or troubleshooting port/proxy issues.
Use for PostHog work: product analytics, feature flags, experiments, session replay, heatmaps, surveys, error tracking, logs, LLM analytics, data warehouse syncs, endpoints, signals, alerts, and metric investigation.
Run a blameless postmortem for a production incident. Investigate with data, write a structured report, build verification queries, and track remediation. Use when something broke in production, money was lost, users were affected, or a security issue was exploited.
Create or update a pull request using the target repository's own conventions, with a neutral fallback when the project has no template.
Review PR comments from GitHub. Fetches inline review comments and issue comments, classifies by review.md prefix semantics (blocking vs non-blocking), and summarizes actionable items. Use when the user asks to check PR feedback, see reviewer comments, or address PR review.
Generate an executive briefing of the last 24 hours of commits for the current project or a specified directory. Use when the user asks for a project update, daily briefing, commit summary, "what changed today," or wants to stay up-to-date with recent work.
Create a changelog-style promotion PR from dev to preview (or other branches). Use when Kevin says promote, dev→preview, ship to preview, or open a promotion PR with generated changelog.
Build a throwaway prototype to answer one design question. Use when the user asks to prototype, spike, explore a design, compare UI variants, test a state machine, or flesh out a PRD decision before committing to production code. Adapted from mattpocock/skills.
Run React Doctor and React Security Doctor on React, Next.js, Vite, or React Native codebases. Use when Kevin says "react doctor", "React Security Doctor", "score React to 100", "fix bad React", "React hygiene", "scan React security", or asks for post-agent React health checks after UI edits.
Physics-based animation library combining React Spring (spring dynamics, gesture integration, 60fps animations) and Popmotion (low-level composable animation utilities, reactive streams). Use when building fluid, natural-feeling UI animations, gesture-driven interfaces, physics simulations, or spring-loaded interactions. Triggers on tasks involving React Spring hooks, spring physics, inertia scrolling, physics-based motion, animation composition, or natural UI movements. Alternative physics approach to motion-framer for more physically accurate animations.
Build declarative 3D scenes with React Three Fiber (R3F) - a React renderer for Three.js. Use when building interactive 3D experiences in React applications with component-based architecture, state management, and reusable abstractions. Ideal for product configurators, portfolios, games, data visualization, and immersive web experiences.
Read external reference material (RFDs, papers, blog posts, docs), extract actionable rules, then dispatch subagents to audit the codebase against those rules and fix violations. Use when the user shares a technical reference and wants it applied to the codebase.
Find and fix a bug introduced by the current author within the last week in the current working directory. Use when a user wants a proactive bugfix from their recent changes, when the prompt is empty, or when asked to triage/fix issues caused by their recent commits. Root cause must map directly to the author's own changes.
Compound quality pass over recently changed code. Orchestrates seven standalone skills in sequence: comment, lerp, style, fix-types, interface, test-invariants, exemplar-audit. Each pass is independently invokable. Use after any feature or refactor lands and before the final commit.
Build Remotion videos with remocn — a shadcn registry of copy-paste animation components and timeline-driven UI primitives. Use when composing video scenes, adding text animations, transitions, backgrounds, UI blocks, brand/social cards, or full compositions in a Remotion project. Triggers include "remocn", "video component", "add animation", "text reveal", "scene transition", "product demo video", "remotion component", "typewriter", "terminal simulator", "glass code block", and the UI-primitive tier: "video dialog", "video button", "command menu", "video select", "video tooltip". Even if the user doesn't mention remocn, activate when they need polished video primitives for Remotion.
Best practices for Remotion video creation in React. Use when writing, reviewing, debugging, or rendering Remotion code, including compositions, timelines, sequences, transitions, captions, audio, FFmpeg, media assets, charts, Three.js/R3F scenes, subtitles, voiceovers, and deterministic video exports.
Resolve an in-progress git merge or rebase conflict without discarding work. Use when conflict markers, MERGE_HEAD, rebase state, or "resolve conflicts" appears.
Route a Cursor code-review request to the Bugbot or Security Review subagent. Use when the user invokes /review, asks for Cursor Bugbot, asks for a Cursor Security Review, or wants the built-in readonly review subagents rather than the generic Kevin review doctors.
Run the Cursor Bugbot readonly subagent on branch changes, uncommitted changes, or a described diff. Use when the user invokes /review-bugbot, asks Bugbot to review code, or wants Cursor's built-in bug-finding review subagent.
Run the Cursor Security Review readonly subagent on branch changes or uncommitted changes. Use when the user invokes /review-security, asks for Cursor's security review, or wants the built-in security-focused review subagent.
State machine-based vector animation with runtime interactivity and web integration. Use this skill when creating interactive animations, state-driven UI, animated components with logic, or designer-created animations with runtime control. Triggers on tasks involving Rive, state machines, interactive vector animations, animation with input handling, ViewModel data binding, or React Rive integration. Alternative to Lottie for animations requiring state machines and two-way interactivity.
Verify claims against primary sources before writing code or docs. Read the actual API, run the actual command, check the actual docs. Do not guess. Do not assume. Do not ship until verified.
Use for Rust work: async patterns, ownership and borrowing issues, production Rust style, tests, performance, safety, and low-level systems code review. Load folded Rust references for deeper async, best-practice, or strict-review guidance.
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
Simple scroll-triggered reveal animations using AOS (Animate On Scroll). Use this skill when building marketing pages, landing pages, or content-heavy sites requiring basic fade/slide effects without complex animation orchestration. Triggers on tasks involving scroll animations, scroll-triggered reveals, AOS, simple animations, or basic scroll effects. Alternative to GSAP ScrollTrigger and Locomotive Scroll for simpler use cases. Compare with motion-framer for React-specific animations.
Build an immersive scroll-scrubbed cinematic landing page from a frame-locked chain of generated scenes and camera clips. Use for a "3D world" hero, fly-through brand world, Emons-style isometric diorama, scroll cinematic, browse-through-the-industry experience, native portrait companion, or a request to turn a business into a scrollable world. The procedure interviews for story, brand, art direction, camera grammar, mobile scope, and budget; renders through Monid Seedance by default with Higgsfield fallback; and wires a portable zero-dependency scrub engine with seam, reduced-motion, mobile, and cost gates.
SDFormat/SDF model and world authoring, validation, and simulator handoff. Use for `.sdf` files, SDFormat XML, models, worlds, links, joints, poses, frames, inertials, visual/collision geometry, mesh URIs, sensors, lights, physics, plugins, includes, Gazebo, static SDF review, or simulator-specific metadata. Do not use for signed-distance-field geometry.
Guide users building apps, scripts, CI pipelines, or automations on top of the Cursor SDK - TypeScript (`@cursor/sdk`) or Python (`cursor-sdk` / `cursor_sdk`). Use when the user mentions integrating, installing, or writing code against the Cursor SDK; says `Agent.create`, `Agent.prompt`, `Agent.resume`, `agent.send`, `run.stream`, `run.messages`, `CursorAgentError`, `@cursor/sdk`, `cursor-sdk`, or `cursor_sdk`; asks to run Cursor agents programmatically from a script, CI/CD pipeline, GitHub Action, backend service, or other code outside the Cursor IDE; wants to pick between local and cloud runtime, configure MCP servers for an SDK agent, or handle streaming, cancellation, or errors; or is wiring Cursor into an automation, bot, or REST `/v1/agents` migration. Use eagerly rather than answering from memory; the SDK surface evolves and this skill is the source of truth for the external packages.
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
Orchestrate Kevin's security/pre-ship doctor chain across React Security Doctor, deepsec, threat modeling, secure-coding review, adversarial bug hunts, vibe-code-doctor, and no-sus-code-doctor. Use when Kevin asks to string together doctors/tools, run a security doctor chain, run deepsec plus React Security Doctor, harden a production app, or decide which security doctors should gate a repo.
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Review DXF and STEP/STP uploads for SendCutSend.com orders using its ordering guide, catalog, and specs. Use only for SendCutSend.com preflight reports covering upload readiness, selected material/SKU/thickness/service availability, and service-specific checks for laser cutting, CNC routing, bending, tapping, countersinking, hardware insertion, and finishing.
Use for Sentry work: SDK setup and upgrades across web, Node, Next.js, React, TanStack, Cloudflare, Python, Go, Ruby, PHP, .NET, mobile, issue triage, alerts, OpenTelemetry, AI monitoring, code review, and workflow automation.
Route SaaS and infrastructure tasks to the right first-party CLI, MCP, generated client, or installed skill, and route project-CLI/release work through proportional typed-CLI, packaging, publication, and updater stages. Use when a task mentions Coolify, Shopify without a more specific commerce task, GitLab, AWS, Google Cloud, Docker, Kubernetes, Terraform, Sentry, Datadog, Snowflake, Databricks, Auth0, Twilio, Contentful, Sanity, Algolia, an uncovered SaaS/infra product, a TypeScript project CLI, release automation, multi-platform binaries, or self-update. Enforces auth/context checks, read-only-first exploration, previews before mutations, separate publish/update authority, and capability-harvest lookup for unknown services.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Runs the rest of a /shell request as a literal shell command. Use only when the user explicitly invokes /shell and wants the following text executed directly in the terminal.
Build, inspect, validate, or operate Shopify themes, Liquid sections, landing or product pages, Admin GraphQL, and store-scoped Shopify CLI workflows. Use for Shopify theme development, AI-authored ecommerce pages, Liquid, JSON templates, Theme Check, store reads or approved mutations, and Shopify AI Toolkit routing. Keeps Dev MCP documentation-only, uses development or unpublished themes by default, minimizes Admin scopes, protects customer data, and requires preview, accessibility, commerce, rollback, and human-publish proof.
Frame any technical answer as a reproducible five-part diagnosis. Use when the user asks for a root-cause explanation, a fix proposal, a debugging write-up, or says "explain why", "what's the problem", "propose a fix", or invokes `/simple`. Forces the answer into: problem, evidence, proposal, mechanism, test methodology.
Frame any technical answer as a reproducible five-part diagnosis. Use when the user asks for a root-cause explanation, a fix proposal, a debugging write-up, or says "explain why", "what's the problem", "propose a fix", or invokes `/simple`. Forces the answer into: problem, evidence, proposal, mechanism, test methodology.
Use Sites to build websites, including landing pages, portfolios, dashboards, portals, trackers, hubs, and internal tools. Always use Sites when the project contains `.openai/hosting.json`.
Host websites with Sites. Always use after `sites-building`, and use for website publishing, deployment, hosting management, or projects containing `.openai/hosting.json`.
Scan recent Cursor agent transcripts and update or create category skills based on recurring patterns, struggles, or inefficiencies. Use when asked to audit skills, improve automations, review recent sessions for skill opportunities, or when the user says "update my skills." Shared category skills only.
Security auditor for agent skills. Run before installing any new skill from skills.sh, GitHub, or any source. 6-step vetting protocol covering typosquatting, permissions, dependencies, prompt injection, network exfiltration, and content red flags. Use when about to install a skill, reviewing a SKILL.md, auditing existing skills, or when a skill update changes permissions. Triggers on "install skill", "add skill", "npx skills add", "vet this skill", "audit skill", or "is this skill safe." Based on useai-pro/openclaw-skills-security. MUST be invoked before any skill installation — this is part of the quality gate.
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
Use when styling any elevated surface (card, dialog, popover, dropdown, menu, tooltip, sheet, toast) in a Tailwind project that has shadow-plugin installed. Prevents the double-border artifact caused by pairing a border/ring with a shadow, by routing elevation through the smooth-shadow-ring-* utilities.
Browser-based 3D design tool with visual editor, animation, and web export. Use this skill when creating 3D scenes without code, designing interactive web experiences, prototyping 3D UI, exporting to React/web, or building designer-friendly 3D content. Triggers on tasks involving Spline, no-code 3D, visual 3D editor, 3D animation, state-based interactions, React Spline integration, or scene export. Alternative to Three.js for designers who prefer visual tools over code.
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
MoveIt2 SRDF authoring, validation, and planning-semantics workflow. Use when creating, editing, inspecting, or validating `.srdf` files, MoveIt planning groups, virtual joints, passive joints, end effectors, group states, disabled collisions, URDF-paired planning semantics, or SRDF handoff for live review. Use the URDF skill for robot structure, the SDF skill for simulator descriptions, and the cad-viewer skill for rendering, live review links, and optional MoveIt2 controls.
Document state machines with mermaid diagrams and DFA transition files. Use when writing, reviewing, or adding state-driven logic to modules that have sequential phase transitions, lifecycle management, or protocol handshakes.
Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers, bearings, standoffs, and other catalog components. Use when Codex needs to search the hosted step.parts catalog before creating simplified placeholder geometry, resolve fuzzy part names, standards, aliases, or dimensions, choose a matching part, fetch a canonical .step file, verify checksums, or use the step.parts API/OpenAPI/catalog endpoints for standard part discovery.
Use for Stitch MCP design workflows: generate designs, upload existing artifacts, extract design markdown, extract static HTML, manage design systems, code-to-design, and autonomous Stitch iteration loops.
Use for Stripe work: customers, payments, subscriptions, Checkout, refunds, events, products, prices, webhook hardening, API directory/project workflows, Stripe upgrades, and account-safe read/write operations. Writes require test-mode keys unless the user explicitly approves production mutation.
Dedalus style guide quick reference. Key rules for writing code that lasts. Use when writing or reviewing Python code.
Comprehensive skill for Adobe Substance 3D Painter texturing and material creation workflow. Use this skill when creating PBR materials, exporting textures for web/game engines, optimizing 3D assets for real-time rendering, or automating texture workflows. Triggers on tasks involving Substance 3D Painter, PBR texturing, material creation, texture export for Three.js, Babylon.js, Unity, Unreal, glTF optimization, or Python API automation. Creates optimized textures for threejs-webgl, react-three-fiber, and babylonjs-engine materials.
Use for Supabase work: Postgres, Auth, RLS, migrations, Edge Functions, Storage, Realtime, Vectors, Cron, Queues, SSR clients, CLI, MCP, security review, schema drift, and production data changes.
Use for TanStack library work: Query, Router, Start, Table, Form, Store, DB, Virtual, Pacer, Ranger, Devtools, Config, CLI, AI, and integration best practices. Verify installed package versions before applying examples.
Use for taste and UI style direction: brand kits, minimalist, brutalist, soft, GPT-motion, Stitch-informed design, redesigns, image-to-code, output polish, and the taste skills playbook.
Test-driven development with red-green-refactor. Use when the user wants test-first implementation, asks for TDD, mentions red-green-refactor, wants integration tests, or when a feature/bug should be built as thin vertical slices with public-interface tests. Adapted from mattpocock/skills.
Act as a wise, effective teacher who makes sure the human deeply understands the work an agent just did, before the session ends. Runs incrementally with a running checklist, has the human restate their understanding first, drills into the whys (plus what/how), supports eli5 / eli14 / elii (explain like an intern), quizzes with AskUserQuestion (shuffled answer order, hidden until submitted), shows code or the debugger as evidence, and gates completion on demonstrated mastery. Use when the user says "teacher mode", "/teacher", "teach me this session", "make sure I understand", "help me understand what you built/changed", "walk me through what you did", "quiz me", "eli5 / eli14 / elii", "stay in the loop", or after a substantial change when the human wants to actually understand it rather than rubber-stamp it.
Use for Terraform/OpenTofu work: modules, providers, tests, stacks, imports, refactors, acceptance tests, style, Azure verified modules, generated configuration, state safety, CI plans, and provider development.
Write test output, harnesses, and assertions in the terse Unix tradition. Covers Rust #[test], Go testing.T, Python pytest, typed CLI harnesses, and CI integration. Use when writing new tests, test harnesses, CI profiles, or reviewing test output verbosity.
Write tests that prove the right invariant at the smallest honest layer. Use when adding, reviewing, deleting, or refactoring tests; choosing test boundaries; turning bug reproductions into invariant tests; or deciding whether coverage, fuzzing, property tests, unit tests, integration tests, or end-to-end tests are appropriate.
Build a live Three.js landscape that stays quiet behind a subject — a noise heightfield on a polar grid so resolution follows the lens, ground coloured by slope and moisture rather than by texture, instanced GPU grass whose wind costs nothing on the CPU, scattered stones, a gradient sky dome, a star field you can actually see, and a time-of-day system that cross-fades instead of cutting. Use for hero backdrops, product stages, scroll worlds, or any scene where a building, object, or figure has to sit in a place rather than float on a gradient.
Generate architecture procedurally in Three.js and film it assembling — a small geometry vocabulary that builds pagodas, castles, domes and spires from parameters instead of mesh files, hip roofs with flying eaves driven by a single profile function, and a clipping-plane build animation where everything below a rising line is finished work and scaffolding stands above it. Use for construction studies, architectural title sequences, procedural landmarks, or any hero object that should build itself rather than fade in.
Put weather into a Three.js scene that reads as weather — rain anchored inside the frustum, a storm that is the rain leaned on rather than a second system, lightning on its own light with thunder scheduled by distance, snow that blows up into blizzards and keeps settling until the ground goes white, wet ground with puddles and splashes, and looping ambience that has no seam. Use for scene atmosphere, seasonal states, hero backdrops, or any world where clear/rain/storm/snow needs to be a control the viewer can turn.
Comprehensive skill for Three.js 3D web development. Use this skill when building interactive 3D scenes, WebGL/WebGPU applications, product configurators, 3D visualizations, or immersive web experiences. Triggers on tasks involving Three.js, 3D rendering, scenes, cameras, meshes, materials, lights, animations, textures, or WebGL/WebGPU rendering.
Break a PRD, plan, or spec into independently grabbable vertical-slice issues/tickets. Use when the user says "/to-tickets", "turn this into issues", "break this down", "make tickets", "create implementation tasks", or wants AFK/HITL agent-ready work packets. Adapted from mattpocock/skills.
Turn the current conversation, notes, or prototype findings into a PRD/spec without re-interviewing. Use when the user says "/to-spec", "write a PRD", "turn this into a spec", "make this a product brief", "capture the plan", or when a planning session needs a durable product spec. Adapted from mattpocock/skills.
Design engineering principles for removing special cases. Use when designing new systems, extracting shared packages, refactoring conditional logic, deciding whether to add a flag or change the interface, or when the user invokes "good taste" or asks for a cleaner algorithm.
Production-ready CSS transition recipes for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar hovers, error shakes, input clears, skeleton loaders, shimmer text, sliding tabs, tooltips, text reveals, card tilt, plus-to-menu morphs, accordions, or motion-token cleanup. Triggers on "add a transition", "make it animate", "motion tokens", "animate the dropdown", "modal open smoothly", "stagger animation", "skeleton loader", "loading shimmer", "segmented control", "accordion", or the commands transitions reveal/review/apply/refine.
Triage issues, bug reports, support threads, or external PRs into clear labels, verification state, and agent-ready briefs. Use when the user says "/triage", "triage these issues", "sort my backlog", "verify these reports", "label these tickets", or asks to turn messy reports into actionable work. Adapted from mattpocock/skills.
Bundle TypeScript and JavaScript libraries with blazing-fast speed powered by Rolldown. Use when building libraries, generating type declarations, bundling for multiple formats, or migrating from tsup.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
Identify an unfamiliar UI element or visual style from a plain-language description, screenshot, rendered page, accessibility tree, DOM, or code clue; rank the real names, distinguish confusable patterns such as popover vs tooltip vs dropdown, verify platform semantics and API symbols, and return prompt-ready wording. Use for “what is this called?”, “name this UI element”, ambiguous component terminology, or before implementing an unnamed interaction. Do not use when the component is already named or the task is only visual polish.
Zero-config linting and formatting via Ultracite (oxlint/oxfmt, Biome, or ESLint). Use when bootstrapping a new project, adding linting to an existing app, configuring agent hooks, setting up CI lint checks, or when the user says "lint", "format", "ultracite", "oxlint", "oxfmt", "code quality setup", or "add linting." Always prefer Ultracite over hand-rolled ESLint/Prettier/Biome configs.
UnoCSS instant atomic CSS engine, superset of Tailwind CSS. Use when configuring UnoCSS, writing utility rules, shortcuts, or working with presets like Wind, Icons, Attributify.
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
Update documentation after code changes. Covers source-level docs (module docs, docstrings, inline comments) and docs-site pages. Use after any code change to keep documentation in sync with reality.
URDF robot description authoring and validation. Use when creating, editing, inspecting, validating, or debugging `.urdf` files, robot links, joints, limits, inertials, visual/collision geometry, mesh references, frame conventions, or robot-description artifacts. Use the SRDF skill for MoveIt2 semantic groups and IK/path-planning semantics; use the cad-viewer skill for local MoveIt2 server controls; use the CAD skill for STEP/STL/3MF/DXF/GLB outputs.
Use for Vercel platform work: CLI, deployments, env vars, functions, routing middleware, firewall, observability, storage, queues, cron jobs, AI SDK, AI Gateway, v0, sandbox, Marketplace, Turborepo, Turbopack, Satori, Geist, and workflow verification.
Audit a vibe-coded project for the failure modes that make it collapse in production, score it 0-100, and drive fixes. Use when the user says "vibe code doctor", "is this vibe-coded project production-ready", "audit this AI-generated codebase", "why might this break", "harden my vibe-coded app", or inherits a codebase nobody fully understands. Complements react-doctor (React health/security) and deepsec (deep vuln scan) with the comprehension / integration / architecture / ops lens those miss.
Turn a planned product, UI, architecture, or agent workflow change into a visual, inspectable plan with flow maps, diagrams, file maps, storyboard states, risks, and verification gates. Use when Kevin says "visual plan", "/visual-plan", "storyboard this flow", "make the plan inspectable", "diagram the plan", or asks for a BuilderIO-style visual plan before implementation.
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
VitePress static site generator powered by Vite and Vue. Use when building documentation sites, configuring themes, or writing Markdown with Vue components.
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
Use for Vue ecosystem work: Vue, Vue Router, Vue testing, VueUse, Pinia, Nuxt, Nitro, and Slidev. Confirm installed versions and project conventions before applying examples.
Plan work too large or uncertain for one agent session as a durable map of decision tickets, blocking edges, a visible frontier, and fog of war. Invoke manually with /wayfinder when the route to a destination is not yet clear.
Build polished visual web artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use when the user wants a browser-rendered, interactive, or presentational front-end deliverable. Not for back-end, CLI, or non-visual coding tasks.
Audit UI code against Vercel's Web Interface Guidelines for design and accessibility compliance. Use when reviewing UI code, checking accessibility, auditing components, or when the user says "check design", "UI review", "accessibility audit", "web guidelines", or "interface compliance." Based on the Vercel Labs agent-skills lineage and the current web-interface-guidelines command source.
Meta-skill for combining Three.js, GSAP ScrollTrigger, React Three Fiber, Motion, and React Spring for complex 3D web experiences. Use when building applications that integrate multiple 3D and animation libraries, requiring architecture patterns, state management, and performance optimization across the stack. Triggers on tasks involving library integration, multi-library architectures, scroll-driven 3D experiences, physics-based 3D animations, or complex interactive 3D applications.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Solve a user-specified web task code-as-action style by driving a local Playwright browser through one bash command at a time, saving screenshots and an action log into `final_runs/run_<id>/`, and visually verifying the result. Use when the user asks to automate a web task (search, filter, form-fill, multi-step flow, data extraction) and wants reusable scripts plus screenshot evidence rather than a one-shot answer.
Generate an interactive bash wizard that walks a human through a manual setup, third-party service configuration, one-off migration, or A-to-B state transition. Use when Kevin invokes /wizard or explicitly asks for an interactive CLI that opens URLs, captures values, writes .env entries, sets GitHub secrets/vars, and confirms each step.
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
Rework a recent change as if the intended UX and architecture existed from day one, deleting compatibility cruft and accidental complexity. Use when Kevin invokes /zero-tech-debt, asks to clean AI-generated tech debt, says the code feels patched-on, or wants a feature refactored toward the final product surface rather than preserved history.
Zustand adapter for json-render's StateStore interface. Use when integrating json-render with Zustand for state management via @json-render/zustand.
Capture and analyze saved evidence from Discord, X, Hacker News, articles, repositories, media, notes, or pasted URLs; correlate sources; bind every useful signal to stable Kevin Wiki objects; interrogate current instructions, workflows, skills, design rules, projects, and knowledge; write back justified changes; and prove retrieval and routing. Use whenever Kevin asks to read, save, absorb, replay, review, research, or incorporate sources into the brain or harness.
Bootstrap and maintain a persistent agent memory file (memory.md) in any project. Use when setting up a new project for agent-assisted development, when the user says "add memory", "activity log", "agent memory", "track changes", "memory.md", "set up agent logging", or when starting work on any project that doesn't already have a memory.md. Also triggers on "what did I do last session" or "what's the history of this project."
Enroll and maintain the Agent-Docs Mesh on any Kevin project — layered AGENTS.md + per-dir SKILL.md, auto-blocks, Graphify repo-graph awareness, docs-doctor. Use when entering a new repo, starting work on loop/Dedalus/any project, "enroll this repo", "agent docs", "scaffold AGENTS.md", "docs-doctor", "agent-docs mesh", "use graphify with projects", after substantive edits to refresh machine facts, or when Kevin says keep agent documentation current.
Build, run, and evolve Kevin's agent self-evaluation library. Use when the user says "benchmark yourself", "self improve", "agent eval library", "evaluate the agent", "make the judge harder", "Red Queen", "Gödel Machine", "eval the loop", "optimize this guardrail", or asks to turn an agent failure into a benchmark, receipt, rubric, or regression case.
Disciplined end-to-end loop for agent-led implementation and testing: isolate work in a git worktree, read before editing, make the minimal correct change, validate empirically (typecheck, lint, format, targeted tests, build), reuse or start live servers and verify the UI in a real browser, run review skills and resolve Bugbot/Greptile/CI findings, then ship small well-documented PRs without pushing or touching prod/growth surfaces unasked. Use when taking a feature or fix from implementation through validation, review, and follow-up; when hardening, reviewing, consolidating, or splitting PRs; or whenever the user wants work driven and verified rather than just written.
Internet access for AI agents — read and search Twitter/X, Reddit, YouTube, GitHub, LinkedIn, RSS, and web pages. Zero API fees, CLI-based, fully local. Use when the user asks to research a topic across the internet, fetch live social media posts, get YouTube transcripts, search Reddit threads, read web pages, monitor RSS feeds, or when the user says "search Twitter", "what are people saying about", "research this topic", "get the latest on", "read this tweet", "YouTube transcript", "Reddit discussion", or "check GitHub repos for". Based on Panniantong/Agent-Reach (16K+ GitHub stars).
Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.
Create Cursor Automations through the interactive editor handoff. Use when the user explicitly asks to create, set up, draft, or open a new Cursor Automation, scheduled agent, Slack-triggered automation, git-triggered automation, or editor-backed automation draft.
Keep a PR merge-ready by triaging comments, resolving clear conflicts, and fixing CI in a loop.
A Cursor Canvas is a live React app that the user can open beside the chat. You MUST use a canvas when the agent produces a standalone analytical artifact — quantitative analyses, billing investigations, security audits, architecture reviews, data-heavy content, timelines, charts, tables, interactive explorations, repeatable tools, or any response that benefits from visual layout. Especially prefer a canvas when presenting results from MCP tools (Datadog, Databricks, Linear, Sentry, Slack, etc.) where the data is the deliverable — render it in a rich canvas rather than dumping it into a markdown table or code block. If you catch yourself about to write a markdown table, stop and use a canvas instead. You MUST also read this skill whenever you create, edit, or debug any .canvas.tsx file.
Run the agent process tracking, audit, and cleanup script, including the portable Agent Broom package. Use before starting another localhost/dev server, while keeping track of what is running, before ending a turn that spawned long-runners, when CPU/memory is high, disk is low, or when the user says "Agent Broom", "agent-broom", "what is running", "track processes", "audit localhost", "high CPU", "clean up terminals/processes", "kill stray processes", "orphaned MCP", "devclean", "deep cleanup", "optimize crash reporters", "too many browsers", "localhosts out of control", "clear turbo/build cache", or "free disk space".
Manage Codex automations (list, create, pause, delete) using the sqlite database. Use when asked to create, pause, list, end, or modify Codex automations, or when referencing the Codex automation schema.
Stage, commit, and push changes without opening a PR. Use when the user says "commit and push", "commit these to a new branch", "push this branch", "push everything", or wants a branch + commit summary but does not want PR creation. ALWAYS runs a pre-commit interview first — branch target, scope, mixed-agent changes, wiki housekeeping, skill gaps. Distinct from `yeet`, which owns commit + push + PR.
Build, configure, and troubleshoot Conductor workspaces, repository setup, settings.toml files, run scripts, files-to-copy behavior, MCP setup, agent harnesses, and review workflows. Use when helping someone set up or operate Conductor.
Create Cursor hooks. Use when you want to create a hook, write hooks.json, add hook scripts, or automate behavior around agent events.
Create Cursor rules for persistent AI guidance. Use when you want to create a rule, add coding standards, set up project conventions, configure file-specific patterns, create RULE.md files, or asks about .cursor/rules/ or AGENTS.md.
Create Cursor Agent Skills. Use when authoring a new skill or asking about SKILL.md structure.
Create custom subagents for specialized AI tasks. Use when you want to create a new type of subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants with custom prompts.
Discover and install agent skills from skills.sh — the definitive open skills registry. Use when the user asks "how do I do X", "find a skill for X", "is there a skill for X", wants to extend agent capabilities, or when a task might benefit from a specialized skill you don't already have. Based on vercel-labs/skills (900K+ weekly installs).
Use for Google Workspace CLI work with Gmail, Drive, Calendar, Docs, Sheets, Slides, Tasks, and shared gws authentication/formatting patterns. Read/list first; require confirmation before send, write, upload, append, create, or delete operations.
Clipboard-ready handoff prompt for another agent to investigate or continue a task.
Audit and configure Kevin's Hermes Mac Mini operator stack: Hermes memory providers, Hindsight, Honcho, Telegram/Discord/WhatsApp gateway, launchd or Hermes cron jobs, agent-browser browser automation, ACP/SSH coding workers, Obsidian/qmd writeback, and information-intake monitors. Use when the user asks about Hermes configuration, personal agent OS, Mac Mini agent stack, Hindsight, Honcho, Hermes Desktop, Telegram gateway, launchd monitors, agent-browser enforcement, software-factory loops, or persistent agent memory.
Open a local HTML file, rendered Markdown document, or localhost page for the user to edit and annotate directly, then apply one durable feedback batch to source. Use when the user asks to review a page visually, edit copy in place, annotate a plan or spec, or send precise UI feedback without describing every location in chat.
Sync iMessage contacts into wiki person pages following STYLE.md. Use when Kevin says "sync iMessage", "update people pages", "add people from messages", "who am I texting most", or wants to bring person pages up to date with recent contacts. Reads ~/Library/Messages/chat.db, ranks 1:1 contacts, resolves names via AddressBook, drafts pages preserving Kevin's voice.
Mine recent agent transcripts across ALL of Kevin's projects (not just the wiki) into candidate wiki learnings, behind a candidate→codify promotion gate. Use when Kevin says "harvest learnings", "what have I learned", "mine my sessions", "cross-project learnings", "pour learnings into the brain", or when the cross-project-learning automation runs. Turns the second brain into a system that compounds from every repo, every agent.
Run a prompt or skill in this session on a recurring or variable interval (e.g. /loop 5m /foo).
Interview Kevin about recurring day-to-day work and turn it into agent-delegable workflow specs. Use when Kevin says "/loop-me", "loop me", "find work to delegate to AI", "what should I automate", "what day-to-day work can agents take over", or asks to design recurring workflows. Adapted from mattpocock/skills@loop-me.
Craft, audit, adapt, run, and debrief bounded agent loops using Forward-Future/loopy and Kevin's no-one-off workflow. Use when the user says "use loopy", "craft loop skills", "make a loop", "loop skill", "agentic loop", "run this loop", "audit this loop", "make the loop stop", or asks to turn repeated work into a loop with checks and stopping conditions.
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.
Use /onboard for a focused Cursor onboarding flow that learns basic preferences, picks a first goal, and routes the user to the right next action.
Route and execute private PDF work. Use when Kevin asks to read, search, merge, split, reorder, compress, convert, OCR, sign, redact, secure, edit, batch, or automate PDF files. Uses pdf-inspector for fast local text/scanned/mixed preflight when OCR routing is uncertain, chooses the extraction stack for reading, PDFCraft for browser-local one-off or visual workflows, and Stirling-PDF for self-hosted multi-user, API, OCR, or persistent automation. Preserves originals and requires output verification.
Scaffold a project's own parameterized health "doctor" that scores 0-100 and is driven to a perfect 100, following the doctor-pattern methodology (score on unique rules, fix loop, ratcheting --min-score gate). Use when starting or hardening any project and the user says "add a doctor", "project doctor", "health check for this repo", "create our own doctor", "seek 100", "score this codebase", or when a failure pattern has repeated 3+ times and should become an enforced check. Every Kevin project should have one.
Adversarially audit a business, product, launch, pricing page, or project plan. Use when Kevin asks to red-team an idea, attack a business, find blind spots, run a premortem, simulate competitors/customers/investors, or pressure-test pricing/moat/distribution.
Configure a repo for Kevin's engineering flow: issue tracker, triage labels, domain docs, and AGENTS.md/agent-docs integration. Run once before first use of kevin-engineering-flow, triage, to-prd, to-issues, implement, or improve-codebase-architecture in a repo.
Create, test, prune, and iteratively improve agent skills with structured evaluation. Use when creating a new skill, turning a workflow into a skill, improving/tightening an existing skill, pruning no-op instructions, reducing skill token cost, or when the user says "create a skill", "make a skill", "turn this into a skill", "skill for X", "improve this skill", "tighten this skill", or "remove no-ops." Based on anthropics/skills plus Matt Pocock's writing-great-skills/no-op pruning guidance. Wiki-aware — always checks the wiki before creating skills and updates the wiki after.
Use when the human wants to deeply understand a session, PR, code change, bug, architecture, or decision. Teaches incrementally, keeps a running Markdown checklist, asks the human to restate their model first, fills gaps, and quizzes before moving on.
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Run the wiki system doctor to validate wiki structure, skills, rules, automations, and config sync. Use when the user says "doctor", "audit", "health check", "validate wiki", "check my system", "run doctor", or when you suspect something is misconfigured after a large edit session.
Deep absorption of X bookmarks into the wiki graph. Goes beyond hub-page entries to create dedicated pages, cross-references, resolver updates, durable object and workflow changes, and index entries. Use when Kevin says "absorb bookmarks", "process bookmarks", "bookmark absorption", "sync bookmarks to wiki", "research bookmark replies/artifacts/images", "review X bookmark media one by one", "parse bookmark screenshots", or asks for a daily X bookmark automation. Also triggers when running the source-compile automation on x-bookmarks data and after any `ft sync` / `sync-x-bookmarks.sh` run.
Guidance for deciding when and how to add normalized audit event log calls in gt-cloud product code. Use when writing or reviewing security-sensitive mutations, auth flows, membership/permission changes, SSO/SCIM changes, API key changes, super-user access, or sensitive data-access actions that should create audit events.
Comment purpose and style for the gt-cloud monorepo. RULE - A comment states what the code does or a constraint the code cannot show; never feature justification, implementation history, or design narrative. Use whenever writing or reviewing a code comment, docblock, or module header.
App-specific rules for apps/admin. RULE - Use this whenever writing, reviewing, or debugging code under apps/admin/**. The .agents/skills/gt-admin directory is the source of truth for admin app rules.
App-specific rules for apps/dashboard. RULE - Use this whenever writing, reviewing, or debugging code under apps/dashboard/**. The .agents/skills/gt-dashboard directory is the source of truth for dashboard app rules.
App-specific rules for apps/landing. RULE - Use this whenever writing, reviewing, or debugging code under apps/landing/**. The .agents/skills/gt-landing directory is the source of truth for landing guidance.
Testing and code structuring practices for the gt-cloud monorepo. RULE - Use whenever writing or reviewing tests, deciding what (or whether) to test, extracting logic from I/O-heavy code, or structuring a new module that mixes logic with Prisma/S3/LLM/network calls. The .agents/skills/gt-testing directory is the source of truth for these rules.
Design system rules for the GT UI component library (packages/ui). Use when writing or reviewing UI components, styling, colors, buttons, typography, dark mode, or shadcn/ui configuration.
Locadex typed error classes and error handling rules. RULE - Never throw generic `new Error()` in locadex workflow code — use typed error classes from `@generaltranslation/locadex/errors`. Use when writing, reviewing, or debugging locadex workflow/activity/processing code that throws or catches errors.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
React useEffect best practices and team policy. RULE - Never use useEffect directly — use useMountEffect() for mount-only external sync. Use when writing/reviewing useEffect, useState for derived values, data fetching, or state synchronization.
Audit and reuse existing repository types before adding or changing TypeScript type declarations. RULE - Use whenever writing or reviewing a type, interface, enum, typed API payload, component props type, schema-derived type, or other named data shape anywhere in the repository.
Configure and verify apps/internal-docs against an explicit local generaltranslation/company checkout with development-only hot reload. Use when starting internal docs locally, setting COMPANY_DOCS_PATH, debugging stale Markdown or sidebar metadata, checking the development content-version poller, or confirming production remains immutable and statically generated.
Security rules for Next.js server actions in gt-cloud — authentication, authorization, and binding every parameter to the authorized entity. Use when writing or reviewing server actions (files marked 'use server') that mutate data or accept resource parameters.