Explorar skills

Extracts individual entities from a large source document and creates separate .md files for each one. Use when a source contains multiple distinct entities that should each have their own file, or when user says "extract", "pull out entities", "split this file", or "create files from this source". Does NOT compile scattered info about one entity — use /compiling-entities for that.

Create an agent team to analyze data engineering architectural changes from multiple perspectives (performance, architecture/design patterns, data quality). Teammates work in parallel to review changes, then synthesize findings into a design document with recommendations.

Generate clean architecture and system-design diagrams as SVG files. Use this skill whenever the user wants to visualise how services, systems, or components connect: migration diagrams, current-state vs target-state architectures, integration maps, data-flow diagrams, platform overviews, or any diagram that shows technology boxes with arrows between them. Triggers on phrases like: "draw a diagram

Esta skill oferece contexto pré e pós-visualização para um filme específico, tornando a experiência mais gratificante. A pré-visualização prepara a atenção sem spoilers, destacando a relevância do filme e o que observar, enquanto a pós-visualização enriquece a experiência ao revelar detalhes perdidos e o contexto histórico.

Turn organizational goals and user insights into a clear product vision and mission statement. Use this skill when a team needs to articulate where the product is going and why it exists.

Set up a build/test/lint validation loop for the current project. Detects the tech stack and configures CLAUDE.md with verification commands.

Plan a feature before writing any code. Use this skill at the START of non-trivial feature work — when the user says they want to "add", "build", "implement", "create", "develop", or "ship" a feature, endpoint, component, page, service, or capability. Especially trigger when the user's prompt is short or under-specified ("add a dashboard", "build an auth flow", "let's do user activity reports") —

Este kit de ferramentas de integração inclui adaptadores de API REST/GraphQL, conversores de formato de dados e uma estrutura de tratamento de erros. Suas funções principais são chamadas de API, conversão de formato, recuperação de erros e processamento em lote, ideal para integração de API, processamento de dados, tratamento de erros e ETL.

Find where a feature, component, or concept lives in the ODD codebase. Uses the navigation index for O(1) lookups.

TypeScript and Angular coding best practices. Use when working with TypeScript, Angular, or Node.js files: implementation, testing, refactoring, RxJS Observables, type system, strict mode, generics, and async patterns.

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"

Use when repository documentation is stale and the user asks to refresh docs to match the current codebase and workflows.