Loading...
Loading...
Found 2,070 Skills
Run a comprehensive multi-perspective code review on current changes. Activates the Review Council (security, quality, documentation, domain review) and runs automated security scanning. Use before creating a pull request or when you want a thorough review of your work.
Create and improve README documents for GitHub projects. Use when the user wants to write a new README, improve an existing one, audit README quality, or asks about documentation best practices for their repository.
Apply Cognitive Load Theory to optimize instructional design by managing intrinsic, extraneous, and germane load within working memory limits. Use this skill when the user needs to diagnose why learners are overwhelmed, redesign training or documentation for better comprehension, evaluate UI/UX information architecture for cognitive burden, or when they ask 'why is this tutorial confusing', 'how to simplify complex instructions', or 'what causes information overload'.
Generate enterprise-grade documentation for NetSuite SDF projects. Analyze scripts, object XML files, `manifest.xml`, and SuiteQL queries to produce README.md, architecture diagrams (Mermaid/ASCII), deployment guides, and troubleshooting tables. Can integrate with post-deployment documentation workflows when automation (for example, hooks) is available.
Generate reference documentation entry by entry for the public surface of a library (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental difference from guidedoc: guidedoc teaches you how to use something, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When the user says "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are discovered after feature-acceptance.
Sync skills documentation to match recent source changes. On load, immediately finds commits newer than the skills-sync tag, identifies doc-relevant changes, and implements updates.
README style guide for concise, direct documentation. Use when writing or editing README files.
Converts Notion databases and pages to structured Markdown format using Notion MCP. Use when working with Notion data visualization, documentation, or exporting Notion content.
Build a complete agent-readable Obsidian vault for a Tailwind-based web codebase, eight flat top-level domain docs (PRODUCT/RUNTIME/ARCHITECTURE/DATA/AUTH/ENGINEERING/TESTING/DESIGN), folder-level deep specs, bidirectional wikilinks for graph navigation, and a `DESIGN.md` that conforms to the google-labs-code/design.md spec with tokens derived from `tailwind.config.{ts,js}` or the v4 `@theme` block. Use when asked to "set up project docs", "write project documentation", "create an Obsidian vault from this repo", "document this codebase for agents", "add a DESIGN.md", or "make the design system machine-readable".
Deep codebase analysis to generate 8 comprehensive documentation files. Adapts based on path choice - Greenfield extracts business logic only (tech-agnostic), Brownfield extracts business logic + technical implementation (tech-prescriptive). This is Step 2 of 6 in the reverse engineering process.
Use this skill for writing, reviewing, and editing documentation (`/docs` directory or any .md file).
Create and write documentation sites using Movk Nuxt Docs. Provides MDC component usage, content structure, configuration guides, and writing standards.