Loading...
Loading...
Found 2,897 Skills
Writing technical blog posts about tldraw features and implementation details. Use when creating blog content about how tldraw solves interesting problems.
Use when designing system architecture, making high-level technical decisions, or planning major system changes. Focuses on structure, patterns, and long-term strategy.
Add ADR references to code for traceability. TRIGGERS - ADR traceability, code reference, document decision in code.
Use when user asks to search the web, look something up online, find current/recent/latest information, or needs cited answers. Triggers on "search", "look up", "find out about", "what is the current/latest", image searches, news lookups. NOT for searching code/files—only for web/internet searches.
Document project tools and CLI utilities in docs/define/tools/. Use when documenting internal CLIs, scripts, development tools, or third-party integrations that team members need to understand and use.
This skill should be used after creating or modifying skills to update the main README.md file. It scans all skills in ~/.claude/skills/, extracts metadata from SKILL.md files, and regenerates the README with categorized skill listings. Triggers on requests mentioning "update skills readme", "refresh skills list", or after adding new skills.
Create Data Contracts (CTR) - Optional Layer 8 artifact using dual-file format (.md + .yaml) for API/data contracts
Automatically sync Agents.md, claude.md and gemini.md files in the project to maintain content consistency. Supports automatic monitoring and manual triggering.
Use this when users need help starting or continuing their writing (not diaries). Trigger scenarios include "don't know what to write", "help me brainstorm", "write a travelogue", "record TIL", "write something". For diary writing, please use the diary-assistant skill instead.
Design scalable, reliable software systems. Use when planning new systems, major features, or architecture changes. Covers C4 diagrams, trade-off analysis, and system decomposition.
Metodología completa para levantamiento de requerimientos de software y negocios. Usar cuando se necesite documentar un proyecto nuevo, validar una idea de negocio, crear especificaciones técnicas, o generar documentación completa que cubra visión de negocio, stakeholders, procesos, requerimientos funcionales y no funcionales, modelo de datos, integraciones, riesgos y roadmap. Ideal para proyectos que requieren cotización, desarrollo, delegación o presentación a inversores.
Use this skill proactively and automatically after completing ANY development work. AI agent summarizes: what was done, what was changed/improved, and suggests future additions/improvements - all concisely in Korean.