Skill UI

Guides recording architecture decision records (ADRs), inline comments, and API docs. Captures the why behind design choices, alternatives considered, and trade-offs so future engineers and agents can understand the codebase.

This skill provides comprehensive functionality for reading, creating, editing, and downloading content from Lark Feishu Docs (Docx/Wiki). Whether accessing via URL or token, it supports structured content manipulation using both XML and Markdown formats (v2 API). Use it for fetching document details, updating specific blocks, and managing embedded media and resources like whiteboards and images. Note that it requires prerequisite knowledge for advanced operations.

Explores Feishu/Lark native OpenAPI docs when existing lark-* skills or CLI commands lack coverage, fetching markdown indexes stepwise to surface raw API specs and ready-to-run `lark-cli api` invocations.

Checks Microsoft SDK code by verifying API signatures, fetching docs, and finding Azure samples before writing or reviewing code that touches .NET or Microsoft APIs.

This guide outlines comprehensive best practices for documenting C# APIs using XML comments. It provides detailed rules for writing summaries, documenting parameters, return values, constructors, properties, and handling exceptions. Following these standards ensures that C# codebases are highly maintainable, readable, and easily understood by other developers.

This guide outlines comprehensive best practices for documenting Java code using Javadoc comments. It covers how to properly document public, protected, package-private, and private members, along with the correct usage of various tags like @param, @return, @throws, @see, and specialized syntax for code snippets and versioning. Following these standards ensures API documentation is accurate, maintainable, and adheres to professional Java development norms.

Automates Coda document and data workflows through Rube MCP/Composio, covering searches, tables, formulas, exports, permissions, sharing, and publishing so bots can manage docs without manual API fiddling.

This skill creates a comprehensive, three-column documentation page in pure HTML. It is ideal when the brief requires a professional "guide," "tutorial," or "API reference." It includes structured elements like a sticky left navigation sidebar, a main article body, and a dynamic right Table of Contents, ensuring technical content is highly readable and navigable.

A comprehensive playbook for API reconnaissance and documentation review. Use this skill early in the testing process to enumerate all reachable endpoints, extract schemas, identify hidden versions (e.g., v1, v2, mobile), and discover undocumented parameters or fields across REST, GraphQL, and mobile APIs. Essential for mapping the full attack surface before deeper exploitation.

This skill transforms raw API specifications, Postman collections, or verbal descriptions into clean, developer-facing documentation. It produces comprehensive guides including detailed endpoints, parameters, request/response schemas, standardized error codes, and runnable code examples, making it ideal for developer portals or README files.

A comprehensive three-column layout template designed for high-readability technical documentation, such as API references, tutorials, and guides. It features a sticky side navigation, main article body with support for code blocks and callouts, and a scroll-spy Table of Contents (TOC). Includes search and version control.

Generate API documentation from TypeScript/JavaScript source code, extracting JSDoc annotations and producing OpenAPI 3.0 specs for HTTP endpoints.