en un clic
loxel
loxel contient 10 skills collectées depuis bizimind, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Add a new language server to loxel with full integration across all layers (build/download, server manager, server routing, client connection, Monaco registration, highlighting/icons, editor URI scheme, packaging). Use when adding support for a new programming language or file type that needs LSP features like completions, hover, diagnostics, or go-to-definition.
Compact the current conversation into a handoff document for another agent to pick up. Use when ending a session, switching contexts, or preparing work for a fresh agent to continue.
Apply Convex implementation rules and review standards for backend work. Use when creating or modifying Convex queries, mutations, actions, HTTP endpoints, schema/indexes, validators, pagination, cron jobs, or TypeScript types in Convex codebases.
Create or improve a Claude Code skill (SKILL.md). Use when building a new skill, reviewing an existing skill for quality, or converting a repeated workflow into a reusable skill.
Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, generate excalidraw files or describe flows visually.
Explore locally cloned open source package internals in ~/git/open-source/. Use when checking a dependency's internal API, types, behavior, feature availability, or docs — e.g. "how does convex handle pagination", "what args does excalidraw's convertToExcalidrawElements accept", "check if dockview supports custom tab renderers".
Address review comments on a pull request
Query the loxel Axiom dataset to investigate logs. Use the `axiom query` CLI with APL (Axiom Processing Language).
Get an independent review of the current plan
Build a zoomable nested d3 treemap from hierarchical data (slash-separated paths + numeric values or counted records). Use when the user asks to visualize a distribution, breakdown, or proportion grouped by a path-like hierarchy — e.g., lines of code, disk usage, bundle sizes, dependencies, languages, git churn, lint issues, test durations, messages per channel.