Documentation

Toma notas estruturadas em markdown com timestamps e categorização

General MongoDB aggregation pipeline optimization techniques including early filtering, index usage, array operators vs $unwind, $lookup optimization, and performance debugging. Use when writing aggregation queries for ANY MongoDB project, debugging slow pipelines, or analyzing query performance. For M32RIMM-specific patterns, use mongodb-m32rimm-patterns skill.

Comprehensive guidance for writing high-quality unit tests in Java projects using JUnit 5 and AssertJ. Use when writing unit tests, creating test classes, or need guidance on mocking strategies, assertions, test builders, or JUnit 5 best practices. Requires JUnit 5, AssertJ, and Mockito dependencies.

Write clean, consistent, maintainable code following established naming conventions, formatting standards, and the DRY principle across all files in the codebase. Use this skill when writing or refactoring any code file regardless of language or framework to ensure consistent style. Use this skill when naming variables, functions, classes, and files, when formatting code with proper indentation, when creating small focused functions, or when removing dead code and unused imports. Use this skill for Python files, JavaScript/TypeScript files, CSS files, configuration files, or any programming language file. Use this skill when establishing code formatting standards with tools like Prettier, ESLint, Black, or RuboCop, or when applying the DRY principle to eliminate code duplication.

Use when implementing features, writing production code, providing technical feedback on designs, or making implementation decisions. Apply when user asks to implement, build, code, develop, or create software. Also use when reviewing design documents from the architect perspective of implementation feasibility. Use proactively after system design is complete.

Create and manage database migrations with reversible changes, zero-downtime deployments, and proper version control practices. Use this skill when creating database migration files, schema change scripts, or any files that modify database structure. Use this when writing migration files with up/down methods, implementing rollback strategies, creating or modifying database tables, adding or removing columns, creating indexes, or handling data migrations separately from schema changes. Use this when working on files in migration directories like db/migrate/, migrations/, or database/migrations/, or when modifying schema definition files.

Understand vault organization, weekly writing pipeline (Mon-Sun stages), file conventions, and Make commands. Use when working with vault files, daily notes, blog posts, projects, or referencing vault structure and workflows.

Strict TypeScript rules. Use when writing ANY TypeScript.

Jira Wiki Markup (Text Formatting Notation) for formatting issue descriptions, comments, and custom fields. NOT Markdown—Jira uses different syntax. Use when formatting Jira text, creating tables/panels/code blocks in Jira, linking users/issues/attachments, writing Jira templates, or when any Jira formatting question arises. Triggers include "Jira markup", "Jira formatting", "Jira table", "Jira code block", "Jira panel", "link in Jira", "format Jira comment/description", "Jira wiki syntax".

Use when you have architecture documentation from system-archaeologist and need critical assessment, refactoring recommendations, or improvement prioritization - routes to appropriate architect specialist skills

search the web for information when user explicitly requests web searches, by identifying the nature of the request and delegating to appropriate subagents (@code-researcher for documentation/code examples, @web-researcher for general information)

Write self-documenting code with minimal, evergreen comments that explain complex logic without documenting changes or temporary fixes. Use this skill when adding comments to any code file. When deciding whether code needs a comment or should be made more self-explanatory. When writing comments for complex algorithms or business logic. When tempted to add comments about recent changes, fixes, or TODOs. When reviewing existing comments for relevance and accuracy.

Write E2E tests using Playwright with Cucumber/Gherkin for this project. Use when creating tests, writing test cases, testing UI flows, API testing, or when user mentions e2e, playwright, cucumber, gherkin, bdd, test automation, or QA.

Use PROACTIVELY when auditing code quality, running security scans, assessing technical debt, reviewing code for production readiness, setting up CI quality gates, or tracking DORA metrics. Analyzes codebases against OWASP Top 10, SOLID principles, Testing Trophy, and 2024-25 SDLC standards. Supports incremental audits for large codebases. Not for runtime profiling or real-time monitoring.

Comprehensive node reference documentation for all 110+ Kailash SDK nodes organized by category: AI, API, Code, Data, Database, File, Logic, Monitoring, Admin, Transaction, and Transform nodes. Use when asking about 'node reference', 'available nodes', 'node list', 'AI nodes', 'API nodes', 'code nodes', 'data nodes', 'database nodes', 'file nodes', 'logic nodes', 'monitoring nodes', 'transaction nodes', 'transform nodes', 'which nodes', 'node documentation', or 'node capabilities'.

Convert Product Requirements Documents (PRDs) into technical blueprints and implementation plans

Autonomously execute exploratory implementation of one approach from spike definition, working independently until natural stop. Use when partner provides spike definition and assigns you an approach number to explore in isolation, when comparing multiple implementation alternatives, or when evaluating technical feasibility before committing to an approach

Reference and maintain consistency with the project's technical stack including frameworks, runtimes, languages, frontend libraries, databases, ORMs, testing tools, deployment platforms, and third-party services. Use this skill when making technology choices or selecting libraries that need to align with the existing stack, adding new dependencies to package.json, pnpm-workspace.yaml, requirements.txt, or other dependency management files, implementing features using the project's established frameworks, ORMs, databases, or APIs, writing code in the project's primary language and runtime environment, setting up testing infrastructure with the project's test frameworks, configuring CI/CD pipelines or deployment settings, integrating third-party services that match the project's existing integrations, ensuring compatibility with the project's build tools and bundlers, or ensuring any technical implementation decision aligns with the project's established technologies, architectural patterns, and conventions doc

Generate comprehensive, publication-quality technical manuals with thematic storytelling using multi-agent orchestration. Use when user asks for themed documentation, narrative technical guides, memorable training materials, or mentions themes like Victorian, steampunk, art deco, medieval, pharmaceutical, or nautical combined with technical topics. Triggers on phrases like "create themed manual", "documentation with storytelling", or requests to make docs "more engaging" or "memorable".

Analyze text to identify technical domains and suggest appropriate specialized agentsfor delegation following Constitutional Principle X (Agent Delegation Protocol).This skill examines specifications, plans, tasks, or any technical text to detectdomain keywords and recommend whether to use single-agent or multi-agent delegation.It ensures specialized work is routed to specialists rather than handled by generalists.Triggered by: User request for "which agent?", "who should do this?", domainidentification needs, or automatically by /specify, /plan, /tasks commands.