Explorar skills

Use when auditing project documentation through the evaluation platform with mandatory research, coordinated audit workers, and structured summaries.

Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.

Use when an evaluation run needs review-driven documentation updates and a structured documentation summary.

Checks document semantic content against SCOPE and project goals, coverage gaps, off-topic content, SSOT. Use when auditing documentation relevance.

Checks hierarchy, links, SSOT, compression, requirements compliance, freshness, legacy cleanup. Use when auditing documentation structure.

Verifies claims in .md files (paths, versions, counts, configs, endpoints) against codebase, cross-checks contradictions. Use when auditing docs accuracy.

Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.

Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.

Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

Creates core project docs (requirements, architecture, tech stack, patterns catalog). Use for any project regardless of type.

Creates reference docs (ADRs, guides, manuals) for nontrivial tech stack choices. Use when project needs justified architecture decision records.