Development

Programming, frameworks, implementation, frontend, backend, and app development

skills in category: 68,871
pages available: 2,870

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse development skills

Showing 16,225–16,248 of 68,871 skills

Hook DevelopmentAThis skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on adva...developmentrustgoVotes: 0GitHub stars: 954
Command DevelopmentAThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.developmenttypescriptgoVotes: 0GitHub stars: 954
Agent DevelopmentAThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.developmentgobashVotes: 0GitHub stars: 954
Writing RulesAThis skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.developmenttypescriptpythonVotes: 0GitHub stars: 954
Gstack ReviewAPre-landing code review for the current OPC branch or diff. Use before merging, shipping, or asking whether a change is safe.developmentrustbashVotes: 0GitHub stars: 954
Gstack Qa OnlyARead-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey. Does not modify code.developmentbashtestingVotes: 0GitHub stars: 954
Skills DirectorySkills Directory 3 slots · $399/mo · one ad per page · sponsors can never buy grades.See placements
Gstack InvestigateASystematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior, provider issue, or unexplained output. Requires evidence before fixes.developmentbashdebuggingVotes: 0GitHub stars: 954
Gstack Document ReleaseAUpdate or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or plugin surfaces changed.developmentbashapiVotes: 0GitHub stars: 954
Gstack CsoASecurity audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.developmentrustshellVotes: 0GitHub stars: 954
Claude Opus 4 5 MigrationAMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.developmentpythongoVotes: 0GitHub stars: 954
Silicon Grade DisciplineAUse when writing hardware, firmware, verification, or tooling code that will reach real silicon, and you face a tradeoff between shipping fast and shipping correct; covers failures-should-fail, no over-engineering, no-panic, and test coveragedevelopmentrustgoVotes: 0GitHub stars: 21
clone-siteAClones a website with high fidelity from its live source of truth. Use when the user says clone this site, copy this page, rebuild this landing page, recreate this design, make me a site like X, or pastes a URL and asks for the same thing in their stack. Drives Chrome DevTools MCP to measure computed styles, CSSOM, fonts, geometry, motion, and breakpoints, mirrors every asset byte-for-byte, recovers the motion system from the site's own bundle when it is hand-rolled, then builds it with a par...developmentgoshellVotes: 0GitHub stars: 2
Secure Coding KbALook up the safe idiom and known-risky API/library for a language or framework (Python, JS/TS/Node, Java, Go, C/C++, Ruby) before or while writing code — a design/build-time cheat-sheet, distinct from post-hoc scanning. Use when writing or reviewing code, scoping a PRD's tech stack, or advising an AI-assisted/vibe-coded change on which APIs and libraries to avoid up front.developmentpythongoVotes: 0GitHub stars: 8
Mobile PentestARun a MASTG-based mobile penetration test (Android/iOS) combining static and dynamic analysis: storage inspection, traffic interception, platform-interaction abuse, and resilience checks. Use to actively test a mobile app you're authorized to assess.developmentgotestingVotes: 0GitHub stars: 8
Pre Commit GateAAggregate a fast, diff-scoped security check before `git commit`/`git push` — secrets/gitignore hygiene, SAST/SCA on changed files, and IaC/Claude-config checks where relevant — into a single go/no-go verdict. Use before committing or pushing, not as a full-repo audit.developmentpythonrustVotes: 0GitHub stars: 8
RecapBRead a Claude Code session as a story with the git-receipts CLI — what was asked, what the agent did, what landed, commit by commit. Use when the user asks what happened, what an agent did, to catch up on an unattended or overnight run, to recap a session or a commit, to understand work from a while ago, or after any long run. ALSO use to catch up on a lane or sub-agent the user did not watch, and after this conversation has been compacted — the receipt holds the prompt-to-commit chain the se...developmentpythongoVotes: 0GitHub stars: 2
HelpAExplain what the gitreceipts plugin can do — its commands, scopes, switches, and setup. Use when the user asks for gitreceipts help, how to use the gitreceipts plugin, or what its skills can do.developmentgobashVotes: 0GitHub stars: 2
Ultra FrontendAMaster frontend skill for Claude Code. Synthesizes ultra-frontend design system, uiuxpromax design intelligence, superdesign.dev aesthetics, framer-motion + GSAP full plugin ecosystem, 21st.dev component patterns, Three.js 3D, shadcn/ui, and production-grade architecture. Invoke for ANY visual web task: landing pages, portfolios, dashboards, SaaS apps, React components, interactive experiences, scroll animations, 3D scenes, design systems, component libraries, "make it look sick", "world-clas...developmentjavascriptpythonVotes: 0GitHub stars: 2
DeployADeploy skill for knit-statusline. Cut a release by tagging main; GoReleaser publishes the GitHub Release and the npm packages. Triggers on `/deploy` or any release/version bump/tag request.developmentrustgoVotes: 0GitHub stars: 2
Setup Rust SkillsAConfigure a Rust repo for this skill set — lint and format configuration, and a recorded project posture (edition, MSRV, async runtime, no_std, unsafe policy) at docs/agents/rust.md.developmentrustgoVotes: 0GitHub stars: 2
Rust TestingADesign Rust tests that catch real regressions — unit, integration, doc, property, snapshot, and golden tests, and differential tests that prove a port matches its source. Use when writing or reviewing Rust tests, when a change lands without tests, when deciding what form a test should take, when a port needs parity evidence, or when the user asks about proptest, insta, rstest, or test coverage.developmentrustgoVotes: 0GitHub stars: 2
Rust Skills MapAThe router for this skill set — which Rust skill covers which decision, how they relate, and which one to reach for from where you are.developmentjavascripttypescriptVotes: 0GitHub stars: 2
Rust Code ReviewAReview Rust changes on two axes at once — standards (idioms, ownership, errors, API surface, unsafe) and spec (does the change do what was asked) — with a Rust smell baseline layered on the repo lint configuration. Use when reviewing a Rust diff, pull request, or branch, when asked whether a change is ready to merge, or when a review needs to cover more than what clippy already reports.developmentrustgoVotes: 0GitHub stars: 2
Unsafe RustAJustify, document, and verify unsafe Rust — safety invariants on every unsafe block, sound safe wrappers, undefined behaviour hazards, and verification with Miri. Use when writing or reviewing unsafe code, when working across an FFI boundary, when raw pointers or transmute appear, when a safe API wraps an unsafe primitive, or when the user asks whether an unsafe block is justified.developmentrustgoVotes: 0GitHub stars: 2