Search

PythonReactSEOPDF

Documentation AI Skills

Discover Documentation skills, compare source repositories and read the instructions for each workflow.

Categories: Documentation

Showing 30,169–30,192 of 83,400

Documentation Clear filters

Browse skills

GitHub

ai-sdk

meetsmore

Vercel AI SDK reference for building AI-powered applications. Use when implementing text/object generation (generateText, streamText, generateObject, streamObject), building chatbots with useChat/useCompletion...

GitHub

brane-ship

noise-xyz

Complete workflow for verifying and committing Brane SDK changes. Run after implementing fixes/features to verify impact, test affected modules, and prepare for commit.

GitHub

brane-debugging

noise-xyz

Systematic approach to debugging Brane SDK issues. Use when diagnosing transaction failures, RPC errors, encoding mismatches, or unexpected behavior.

GitHub

brane-impact

noise-xyz

Analyze change impact and discover affected tests. Use after making changes to understand what depends on the modified code, find relevant tests, and determine what to run.

GitHub

brane-docs

noise-xyz

Update Javadoc and public documentation after implementing features. Use when finishing implementation to ensure both internal (Javadoc) and external (website docs) documentation are accurate and complete.

GitHub

brane-code-review

noise-xyz

Review Brane SDK code for correctness, Java 21 patterns, type safety, and architectural consistency. Use when reviewing PRs, checking code changes, or validating implementations against Brane standards.

GitHub

brane-research

noise-xyz

Research EVM SDK patterns from viem (TypeScript) and alloy (Rust) when designing Brane features. Use when implementing new functionality, designing APIs, or solving problems that other SDKs have already address...

GitHub

mermaid-diagrams

rstacruz

Has guidelines for creating Mermaid diagrams and fixing its syntax errors. Use this before creating or updating Mermaid diagrams.

GitHub

plan-with-tdd-and-prd

rstacruz

Use when initiating new features, complex code changes, or technical research tasks that require structured planning and documentation before implementation.

GitHub

high-density-writing-style

rstacruz

Guidelines for a writing style that's concise and direct. aka High density language, HD style Use for writing/editing prompts, artefact documents, TDD, PRD, discovery documents, research, AGENTS.md, and more.

GitHub

plan-mode

rstacruz

Guidelines for Plan Mode - focus on planning before implementation

GitHub

explain-code

rstacruz

Gives guidelines on how to explain code with call graphs and pseudocode. Invoke this when creating code explanations. Common user requests: - "Explain {feature or function}" - "Show me how {feature} works" - "C...

GitHub

solution-options-document

rstacruz

Write solution options documents to evaluate and compare different technical approaches with trade-off analysis Common user requests: - "Evaluate options for [problem]" - "Compare [solution A] vs [solution B]"...

GitHub

verify-implementation

rstacruz

Guidelines for automated and manual verification of code changes. When to use: - After making code changes to ensure correctness As part of the implementation workflow

GitHub

execute-plan

rstacruz

Use when executing implementation plans from planning phase to verified completion

GitHub

reflect

rstacruz

Distill learnings into improvements for the skills and AGENTS.md instructions

GitHub

layered-summary

vicnaum

Create hierarchical, bottom-up "layered summaries" by generating `AGENTS.md` files per directory in a subtree (e.g., `reth/crates/engine`). Deep directories summarize files and key APIs; parent directories roll...

The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.

More filters

Popularity

Popular tags