Search

PythonReactSEOPDF

Documentation AI Skills

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

Categories: Documentation

Showing 37,153–37,176 of 83,400

Documentation Clear filters

Browse skills

GitHub

smart-contract-security

gmh5225

Guide for EVM/solidity smart contract security work: vulnerability taxonomy, review workflow, and where to place resources in README.md.

GitHub

wallet-security

gmh5225

Guide for wallet security topics: MPC/TSS, key management, wallet UX security, phishing, and how to categorize related resources in README.md.

GitHub

solana-security

gmh5225

Guide for Solana/Sealevel security research and where to organize Solana-specific resources in README.md.

GitHub

awesome-web3-security-overview

gmh5225

Guide for understanding and contributing to the awesome-web3-security curated resource list. Use this skill when adding resources, organizing categories, or maintaining README.md consistency (no duplicates).

GitHub

agent-browser

heyJordanParker

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web appl...

GitHub

review

heyJordanParker

Use for code review - runs all reviewers in parallel on uncommitted changes

GitHub

commit-messages

heyJordanParker

MANDATORY when writing commit messages. Structures commits with type prefix, what+why body, and architectural file tree.

GitHub

execute

heyJordanParker

Use when executing implementation plans. Modes: batched with checkpoints, subagent per task, or parallel agents for independent failures.

GitHub

naming

heyJordanParker

MANDATORY for all naming decisions - variables, functions, files, folders, classes, database tables, routes, CSS classes. Must be followed when creating or renaming any identifier. Non-negotiable baseline for c...

GitHub

writing-tests

heyJordanParker

MANDATORY when writing tests. Test behavior, not implementation. Functional tests are primary. Unit tests ONLY for state mutations. Includes fixing flaky tests with condition-based waiting.

GitHub

debug

heyJordanParker

Use when encountering bugs, test failures, or unexpected behavior. Combines systematic debugging framework, root cause tracing, and defense-in-depth validation.

GitHub

show-architecture

heyJordanParker

Use when exploring/explaining code, designing/updating architecture, or when asked to visualize structure. Shows annotated file trees inline.

GitHub

design

heyJordanParker

Use when building UI components, styling pages, or making visual/interaction decisions. Guides design thinking, anti-patterns, CSS architecture, and responsive patterns.

GitHub

plan

heyJordanParker

Use when planning implementation - either writing detailed plans for engineers or structuring complex decisions via questions.

GitHub

pragmatic-engineering

heyJordanParker

Use when user says KISS, pragmatic, don't overengineer, ship it, keep it simple. Also for planning features, reviewing code, or architectural decisions.

GitHub

verification-before-completion

heyJordanParker

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...

GitHub

using-git-worktrees

heyJordanParker

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

GitHub

claude-code

heyJordanParker

Use when working with Claude Code itself - skills, agents, commands, hooks, settings, documentation. Alias "cc". Covers building, testing, sharing skills, updating Claude.md files, and context engineering.

GitHub

codebase-exploration

heyJordanParker

Use when exploring a codebase to understand structure, find files, check dependencies, or see recent changes. Provides verified commands for effective exploration.

GitHub

reviewing-readability

thkt

Code readability review based on "The Art of Readable Code" and Miller's Law (7±2). Triggers: 可読性, 理解しやすい, わかりやすい, 明確, 命名, 変数名, 関数名, ネスト, 深いネスト, 関数設計, コメント, 複雑, 難しい...

GitHub

accessing-google-workspace

thkt

gcloud CLI を使用して Google Sheets/Docs にアクセス。 ユーザーが Google Sheets/Docs の URL を共有したとき、または スプレッドシート, Sheets, Docs, Google ドキュメントに言及したときに使用。

GitHub

reviewing-security

thkt

OWASP Top 10-based security review and vulnerability detection. Use when reviewing code for security issues, performing vulnerability analysis, or when user mentions security, OWASP, XSS, SQL injection, セキュ...

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