development▌
157 indexed skills · max 10 per page
apify-actor-development
apify/agent-skills · Backend
Create, debug, and deploy serverless cloud programs for web scraping, automation, and data processing. \n \n Supports JavaScript, TypeScript, and Python templates with integrated Crawlee, Playwright, and Cheerio libraries for HTTP and browser-based crawling \n Includes local testing via apify run with isolated storage, schema validation for inputs/outputs, and deployment to Apify platform via apify push \n Requires Apify CLI authentication and mandatory generatedBy metadata in .actor/actor.json
hook-development
anthropics/claude-plugins-official · Productivity
Event-driven automation for Claude Code plugins using prompt-based and command hooks. \n \n Supports 9 hook events (PreToolUse, PostToolUse, Stop, SubagentStop, UserPromptSubmit, SessionStart, SessionEnd, PreCompact, Notification) for validation, policy enforcement, and workflow automation \n Prompt-based hooks use LLM reasoning for context-aware decisions; command hooks execute bash scripts for deterministic checks \n Includes matchers for filtering by tool name (exact, regex, wildcard) and par
voice-ai-development
davila7/claude-code-templates · AI/ML
Role: Voice AI Architect
command-development
anthropics/claude-plugins-official · Productivity
Markdown-based slash commands for defining reusable prompts with dynamic arguments, file references, and bash execution. \n \n Commands are instructions written for Claude (not users), stored as .md files in .claude/commands/ , ~/.claude/commands/ , or plugin directories \n YAML frontmatter configures description, allowed tools, model selection, and argument hints; use $ARGUMENTS , $1 , $2 for dynamic substitution and @file-path syntax for file inclusion \n Bash execution via backticks gathers d
hook-development
anthropics/claude-code · Productivity
$22
command-development
anthropics/claude-code · Productivity
$22
test-driven-development
obra/superpowers · Testing
Write tests first, watch them fail, then implement minimal code to pass. \n \n Follows the red-green-refactor cycle: write a failing test, verify it fails correctly, implement minimal code to pass, then refactor while keeping tests green \n Requires deleting any production code written before tests exist; no exceptions for \"reference\" or \"adaptation\" \n Emphasizes watching tests fail as proof they actually test the right thing; tests that pass immediately prove nothing \n Covers common ratio