Loading...
Loading...
Found 2,062 Skills
Skill for writing and updating scalar.config.json — Scalar Docs configuration reference for users and LLMs.
Conversationally guides the user to a CLAUDE.md file. Starts by inferring what it can from the repo, asks ~8 core questions, then offers optional depth across business, voice, and working-style topics. Use when the user wants a CLAUDE.md but would rather have a conversation than fill out a form.
Use this skill when you learn one or more design pattern(s) in the Langroid (multi) agent framework, and want to make a note for future reference for yourself. Use this either autonomously, or when asked by the user to record a new pattern.
Capture implementation notes after code implementation and review/fix. Records design decisions, deviations, tradeoffs, and open questions to docs/issue#XXXX.html. Triggers on: /note-it, 记录笔记, implementation notes.
Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.
Create and manage Architecture Decision Records (ADRs) using MADR 4.0.0 format. Use this skill when evaluating technology choices, documenting design decisions, or reviewing past architectural choices.
Inspeccionar un proyecto existente para descubrir decisiones arquitectónicas implícitas y proponer ADRs candidatos. Usar cuando el usuario quiera auditar un repositorio en busca de decisiones no documentadas, pida "descubrir ADRs", "qué decisiones arquitectónicas tiene este proyecto", "busca ADRs en el repo", "analiza la arquitectura del proyecto" o cualquier variante que implique explorar el código/estructura para inferir decisiones relevantes que merezcan un ADR. Activar también cuando el usuario llegue a un proyecto nuevo y quiera entender qué decisiones ya se tomaron, aunque no mencione explícitamente "ADR".
Validate ASCII diagram alignment in markdown. TRIGGERS - diagram alignment, ASCII art, box-drawing diagrams.
Research codebase comprehensively using parallel sub-agents to answer user questions. Use when the user asks to "research the codebase", "understand how X works", or "investigate Y".
This skill should be used when the user asks to "create ADR", "document decision", "architecture decision", "add decision record", or mentions needing to record a technical decision with status tracking and category organization.