Loading...
Loading...
Found 71 Skills
Generate JSDoc/docstrings for functions
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
Writing technical articles and blog posts. Use when creating articles in docs/articles/ or blog content explaining patterns, techniques, or lessons learned.
Turns a codebase into EventCatalog documentation through an evidence-based interview. Scans the code first, proposes an architectural model (domains, services, messages, channels), grills the user on the structural decisions, produces a reviewable plan file, then hands off to catalog-documentation-creator. Use when user says "document my codebase in EventCatalog", "turn this repo into a catalog", "model my code as a catalog", "grill me on my architecture", "update my catalog from the code", "reconcile my catalog with my code", or "I don't know where to start documenting this codebase". Works for brand-new catalogs AND for updating existing catalogs that have drifted from the code.
Ingest a codebase into memory as code pages connected by wiki links. Walks the tree, classifies each code file by role, applies a role template, and writes a code page per meaningful unit under <wiki root>/code/. Resumable: skips files already ingested and current. Not for prose documents; use /loam::adding-to-memory for those.
Use when checking for drift between docs/ and source code — reports discrepancies with file:line evidence.
Write technical reports — experiment reports, system design documents, code documentation, and internal research memos. Use when documenting technical work that doesn't fit paper format.
Automatically generate standardized comments for Vue 2 Single-File Components (.vue). Parse the three blocks of template, script, and style, add structured comments according to the agreed format, without modifying any code logic. Trigger scenarios: Users request to add comments, supplement document comments for components, and interpret Vue 2 component structure.
You MUST use this when an approved design or settled requirements need a detailed multi-step implementation plan before code changes begin.
Write meaningful documentation that explains why not what; focus on complex business logic and self-documenting code
Use when you have a spec or requirements for a multi-step task, before touching code