Browse Skills

6825 skills found

config-validator.md
2
1 export config-validator
2 sovrium from "sovrium/sovrium"
3 Validates eslint.config.ts and tsconfig.json against documented architecture patterns and infrastructure requirements. Checks ESLint plugin configurations, TypeScript strict mode, FP enforcement, layer boundaries, and alignment with docs/architecture/ and docs/infrastructure/. Use when user requests "validate config", "check eslint", "verify typescript settings", or mentions config audits.
2026-01-05
generating-smart-commits.md
2
1 export generating-smart-commits
2 jeremylongshore from "jeremylongshore/claude-code-plugins-nixtla"
3 This skill generates conventional commit messages using AI analysis of staged Git changes. It automatically determines the commit type (feat, fix, docs, etc.), identifies breaking changes, and formats the message according to conventional commit standards. Use this when asked to create a commit message, write a Git commit, or when the user uses the `/commit-smart` or `/gc` command. It is especially useful after changes have been staged with `git add`.
2026-01-05
prompt-engineer.md
2
1 export prompt-engineer
2 wpfleger96 from "wpfleger96/ai-rules"
3 Provides expert guidance for writing and optimizing prompts for large language models. Use this skill when: (1) user mentions "prompt", "prompting", or "prompt engineering", (2) user requests to write, create, improve, optimize, or review any prompt, (3) user is creating or updating AGENTS.md, CLAUDE.md, .claude/commands/*.md, or .claude/skills/*/SKILL.md files, (4) user is writing system prompts, custom instructions, or LLM agent configurations.
2026-01-05
documentation-lookup.md
2
1 export documentation-lookup
2 krmcbride from "krmcbride/claude-plugins"
3 Look up library and framework documentation. Use when the user asks about API docs, library usage, framework features, or mentions specific libraries/packages by name.
2026-01-05
best-practices-checker.md
2
1 export best-practices-checker
2 sovrium from "sovrium/sovrium"
3 Validates code against framework-specific best practices documented in docs/infrastructure/. Checks Effect usage patterns, React 19 conventions, Drizzle ORM patterns, Hono RPC implementations, and other framework-specific guidelines. Identifies anti-patterns and suggests corrections. Use when user requests "check best practices", "validate framework usage", "review code patterns", or mentions framework compliance.
2026-01-05
technical-writer.md
2
1 export technical-writer
2 daffy0208 from "daffy0208/ai-dev-standards"
3 Create clear, comprehensive technical documentation for developers and users. Use when documenting APIs, writing user guides, creating tutorials, or setting up documentation sites. Covers API docs, user guides, architecture documentation, and documentation best practices.
2026-01-05
testing-requirements.md
2
1 export testing-requirements
2 andyngdz from "andyngdz/exogen"
3 Use when writing tests - test structure, verification steps, coverage goals
2026-01-05
global-tech-stack.md
2
1 export global-tech-stack
2 adigunners from "adigunners/adigunners.github.io"
3 Standards for this static HTML/CSS/JavaScript project. Use this skill when working with vanilla JavaScript modules, HTML templates, CSS stylesheets, Node.js tooling scripts, or package.json configuration. Apply when editing .html files, .js files in js/ directory, css/styles.css, package.json scripts, or configuring Prettier/Lighthouse/markdownlint tooling.
2026-01-05
smart-contract.md
2
1 export smart-contract
2 rocky2431 from "rocky2431/ultra-builder-pro"
3 Multi-chain smart contract development skill for Ethereum, Solana, and Move-based chains.This skill should be used when: writing smart contracts (ERC20/ERC721/ERC1155/esToken/custom),auditing contract security vulnerabilities, generating Foundry test cases, optimizing gas usage,or automating deployment workflows. Triggers on queries like "write a contract", "audit this contract","generate tests", "optimize gas", or "deploy contract".
2026-01-05
dev-onboarding-builder.md
2
1 export dev-onboarding-builder
2 patricio0312rev from "patricio0312rev/skillset"
3 Creates comprehensive developer onboarding documentation and materials including step-by-step setup guides, first-task assignments, expected time per step, common troubleshooting, team introductions, and code walkthrough tours. Use when preparing "new developer onboarding", "first day setup", "junior dev training", or "team member onboarding".
2026-01-05
claude-code-analyzer.md
2
1 export claude-code-analyzer
2 modille from "modille/dotfiles"
3 Analyzes Claude Code usage patterns and provides comprehensive recommendations. Runs usage analysis, discovers GitHub community resources, suggests CLAUDE.md improvements, and fetches latest docs on-demand. Use when user wants to optimize their Claude Code workflow, create configurations (agents/skills/commands), or set up project documentation.
2026-01-05
grant-proposal.md
2
1 export grant-proposal
2 poemswe from "poemswe/co-researcher"
3 Guidance for structuring and writing PhD-level funding applications and grant proposals (e.g., NSF, NIH, ERC). Focuses on narrative arc, significance, innovation, and methodological feasibility.
2026-01-05
support-data-analyzer.md
2
1 export support-data-analyzer
2 jeffvincent from "jeffvincent/claude-config"
3 Analyze customer support data (Excel/CSV with PIT, Support Tickets, CSAT) to categorize issues, prioritize by impact (P0-P3), and generate strategic markdown reports with examples and trends.
2026-01-05
brainstorming.md
2
1 export brainstorming
2 heyJordanParker from "heyJordanParker/dotfiles"
3 Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
2026-01-05
react-conventions.md
2
1 export react-conventions
2 benaor from "benaor/claude-config"
3 React and React Native coding conventions with TypeScript. Use this skill when creating components, writing hooks, or reviewing React/React Native code. Enforces naming conventions, component structure, typing patterns, accessibility, and performance best practices.
2026-01-05
api-contract-design.md
2
1 export api-contract-design
2 daishiman from "daishiman/AIWorkflowOrchestrator"
3 RESTful APIの設計と互換性管理を行うためのスキル。APIバージョニング、Breaking Changes対応、スキーマ設計を含む。**Anchors**:• RESTful Web APIs(Leonard Richardson)/ 適用: API設計全般 / 目的: リソース指向設計の原則の習得• OpenAPI 3.1 仕様(OpenAPI Initiative)/ 適用: API契約設計 / 目的: 標準的なAPI仕様定義• JSON Schema(IETF)/ 適用: スキーマ設計 / 目的: バリデーションルールの明確化**Triggers**: API設計やAPIスキーマの定義が必要な時、バージョニング戦略を策定する時、Breaking Changes対応が必要な時、後方互換性を確保する時に使用
2026-01-05
pre-pr-checklist.md
2
1 export pre-pr-checklist
2 Euda1mon1a from "Euda1mon1a/Autonomous-Assignment-Program-Manager"
3 Validate documentation requirements before creating a PR. Checks for scratchpad entries, CHANGELOG updates, tests, and plan files based on change type. Use before creating pull requests to ensure all documentation gates are satisfied.
2026-01-05
maintaining-documentation-after-code-changes.md
2
1 export maintaining-documentation-after-code-changes
2 cipherstash from "cipherstash/cipherpowers"
3 Two-phase workflow to keep project documentation synchronized with code changes
2026-01-05
technical-writing.md
2
1 export technical-writing
2 mkobit from "mkobit/dotfiles"
3 Enforces ventilated prose and concise technical writing standards when the user is writing or editing standalone documentation files (e.g., Markdown, AsciiDoc). This skill should not be used for code documentation or docstrings.
2026-01-05
claude-code-hooks.md
2
1 export claude-code-hooks
2 daishiman from "daishiman/AIWorkflowOrchestrator"
3 Claude Code の hooks 設計・実装・検証を支援し、セッション/ツール連携の自動化と品質ゲートを安全に構築するスキル。イベント(SessionStart/PreToolUse/PostToolUse/Stop)の選定、スクリプト設計、検証フローを整理する。Anchors:• Claude Code Documentation / 適用: Hook events and configuration / 目的: 正しいイベント選定• Continuous Delivery (Jez Humble) / 適用: 自動化と検証 / 目的: 品質ゲート設計• The Pragmatic Programmer (Hunt/Thomas) / 適用: 自動化と安全性 / 目的: 安全なフック運用Trigger:Use when configuring Claude Code hooks, designing pre/post tool automation, writing hook scripts, or validating hook-driven workflows.claude code hooks, pretooluse, posttooluse, sessionstart, stop, hook scripts, automation
2026-01-05
nodejs-stream-processing.md
2
1 export nodejs-stream-processing
2 daishiman from "daishiman/AIWorkflowOrchestrator"
3 Node.jsにおけるストリーム処理とバックプレッシャー管理の専門知識。大容量ファイルの効率的処理、メモリ使用量の最適化、Readable/Writable/Transform/Duplexストリームの適切な活用方法を提供。Anchors:• Node.js Streams API Documentation / 適用: ストリームAPI全般 / 目的: 公式APIの正確な使用• Backpressuring in Streams (Node.js official) / 適用: バックプレッシャー管理 / 目的: メモリ効率最適化• The Pragmatic Programmer (Hunt and Thomas) / 適用: 実装品質 / 目的: 保守性とテスタビリティTrigger:Use when implementing stream processing in Node.js, handling large files, managing backpressure, or building data transformation pipelines.nodejs stream, stream processing, backpressure, readable stream, writable stream, transform stream, duplex stream, pipeline, large file
2026-01-05
receiving-code-review.md
2
1 export receiving-code-review
2 HTRamsey from "HTRamsey/claude-config"
3 Use when receiving code review feedback - requires technical rigor and verification, not performative agreement or blind implementation
2026-01-05
cuda.md
2
1 export cuda
2 technillogue from "technillogue/ptx-isa-markdown"
3 CUDA kernel development, debugging, and performance optimization for Claude Code. Use when writing, debugging, or optimizing CUDA code, GPU kernels, or parallel algorithms. Covers non-interactive profiling with nsys/ncu, debugging with cuda-gdb/compute-sanitizer, binary inspection with cuobjdump, and performance analysis workflows. Triggers on CUDA, GPU programming, kernel optimization, nsys, ncu, cuda-gdb, compute-sanitizer, PTX, GPU profiling, parallel performance.
2026-01-05
rfc-generator.md
2
1 export rfc-generator
2 patricio0312rev from "patricio0312rev/skillset"
3 Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".
2026-01-05