Loading...
Loading...
Found 282 Skills
Provides comprehensive guidance for creating Mermaid diagrams. Mermaid is a JavaScript-based diagramming and charting tool that uses Markdown-inspired text definitions and a renderer to create and modify complex diagrams. The main purpose of Mermaid is to help documentation catch up with development. Mermaid is particularly well-suited for use in Markdown documents, GitHub, GitLab, wikis, blogs, and other Markdown-based platforms. Use when the user wants to draw, create, generate, make, build, or visualize any diagram, chart, graph, flowchart, architecture diagram, sequence diagram, class diagram, state diagram, Gantt chart, mindmap, timeline, or any other visual diagram in Markdown-friendly format. This skill covers all 23+ Mermaid diagram types including flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, Gantt charts, pie charts, quadrant charts, Git graphs, C4 diagrams, mindmaps, timelines, and more. Always use this skill when the user mentions Mermaid, needs diagrams for Markdown documentation, or wants quick diagrams that render directly in Markdown renderers.
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation. Use when creating OpenAPI/Swagger specs, generating SDKs, writing user guides, creating README files, documenting architecture, writing design specs, creating ADRs, writing migration guides, or generating changelogs from git commits. Handles versioning, examples, developer experience, and user-facing documentation.
Use when developing astrology/numerology apps, validating chart calculations (timezone/DST, quadrant handling), or producing psychology-first interpretations. Expert advisor (30+ years) catches common bugs (D026-D028) and defines accuracy/test standards. (project)
Skill S (Artista) - Diseñador UI/UX del Escuadrón BLAST. Experto en "UI Sniping", estética visual premium y micro-animaciones. Usa este skill cuando necesites: diseñar interfaces, aplicar estilos visuales, crear sistemas de diseño, o mejorar la experiencia de usuario.
Build a 4-quadrant empathy map (Says, Thinks, Does, Feels) to synthesize user research into actionable insights. Use when you need to quickly capture and share user understanding across the team.
Automated SYS generation from ADR decisions - generates system requirements with REQ-Ready scoring
Zoomd platform help — mobile user acquisition across 600+ media sources, mobile DSP with real-time bidding, creator-generated content (CGC), Albert.ai autonomous campaign optimization, and Digital 360 performance marketing. Use when app install costs (CPI/CPA) are too high and you need multi-channel optimization, you want to manage UA campaigns across Meta/Google/TikTok/programmatic from one dashboard, mobile DSP campaigns aren't scaling or hitting ROAS targets, you need creator content for app marketing, Albert.ai isn't optimizing as expected, or you're comparing Zoomd with other mobile UA platforms. Do NOT use for web retargeting or display ads (use /sales-retargeting or /sales-adroll), B2B account-based advertising (use /sales-b2b-advertising).
Write a new doc-site page (guide, tutorial, reference, concept) following the project's docs conventions. Use when user says 'write a doc', 'add a page to the docs site', 'create a guide for X', 'write a tutorial', 'document this concept', or 'add reference for our API'. Do NOT use for feature-specific end-user docs (use document-feature), ADRs (use document-decision), or CLAUDE.md updates (use create-or-audit-claude-md).
Revisar um contrato contra o playbook de negociação da organização — sinalizar desvios, gerar redlines e fornecer análise de impacto de negócios. Use ao revisar acordos com fornecedores ou clientes, ao precisar de análise cláusula por cláusula contra posições padrão, ou ao preparar estratégia de negociação com redlines priorizadas e posições de fallback.
Create editorial-quality diagrams in HTML + SVG matching your brand — architecture, flowcharts, sequences, timelines, quadrants, and 9 more types.
Systematic documentation authoring workflow for AI coding agents. Analyzes repositories to determine what documentation is needed, classifies each document by Diataxis type (tutorial, how-to, reference, explanation), and generates accurate, maintainable documentation that stays synchronized with the codebase. Handles greenfield projects (no docs exist), brownfield updates (refresh, enhance, rewrite existing docs), and doc audits with workflow-specific guidance for each. Use when the user requests documentation for a project: README creation, API reference, architecture docs, developer guides, changelogs, or any technical writing tied to a codebase. Also use when existing docs need auditing, updating, rewriting, or restructuring. Triggers on phrases like "write a README", "document this project", "API reference", "architecture doc", "developer guide", "getting started guide", "tutorial", "how-to", "audit our docs", "what docs are missing", "refresh the docs", "Diataxis", "doc the public API", "write a CHANGELOG", "explain this codebase", "onboarding doc", or "ADR". Triggers when creating or editing `README.md`, `CONTRIBUTING.md`, `CHANGELOG.md`, `docs/`, `mkdocs.yml`, `docusaurus.config.*`, `sphinx`/`conf.py`, ADRs, or any markdown file paired with code. Triggers when public APIs, CLI flags, configuration options, or environment variables change and the user wants the docs kept in sync. Do NOT use for standalone prose, marketing copy, blog posts, design documents, RFCs unrelated to a codebase, or documents where the source of truth is not source code.
Você é uma Arquiteta de Software Sênior especialista em Clean Code e engenharia de software. Use esta skill sempre que o usuário pedir para revisar, criticar, refatorar ou avaliar trechos de código, funções, classes, módulos ou arquiteturas inteiras. Ative também quando o usuário mencionar problemas como "código duplicado", "classe muito grande", "difícil de manter", "código espaguete", "muita dependência", "quero melhorar esse código", "está violando SOLID?", "como refatorar isso?", "esse código está limpo?", "tem code smell aqui?", "como aplicar injeção de dependência?", "preciso de um code review", ou qualquer variação dessas frases. Ative inclusive quando o usuário perguntar sobre boas práticas de design, padrões de código, ou pedir explicações sobre KISS, DRY, YAGNI, TDA, SOLID e seus subprincípios. Se estiver no SynkOS, chame `pane_set_identity` com skill="clean-code-architect" e role="architect".