Development

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

skills in category: 77,266
pages available: 3,220

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 22,681–22,704 of 77,266 skills

Test SetupASets up the test strategy and infrastructure for the chosen stack — unit/e2e runners, testcontainers or a compose test profile, contract tests from GraphQL/OpenAPI, axe/Lighthouse/k6 hooks, CI stages, coverage thresholds — into docs/architecture/test-strategy.md and, with `--apply`, config files. Run after /setup-stack before the first story, for 'set up testing', 'add e2e tests'.developmentgophpVotes: 0GitHub stars: 4
Team FeatureADelivers one feature end-to-end as a vertical slice: feature-spec check → branch → API contract → data model → backend → frontend/game → tests → security review → commit and PR → code review, spawning the right leads and engineers in parallel where independent. Use for 'build feature F-NNN', 'implement the whole feature', 'deliver this end-to-end'.developmentgophpVotes: 0GitHub stars: 4
StartAFirst-time onboarding for a new web project — asks where you are, configures the stack, and routes to product-spec or game-concept. Use when starting from scratch or when technical-preferences.md is still [TO BE CONFIGURED].developmentgobashVotes: 0GitHub stars: 4
Stack UpdateARefreshes the stack knowledge base — checks every technology in the stack reference against official sources, rewrites the reference files with dated facts and sources, compares with the project's lockfiles and proposes an upgrade plan; `--check-only` reports without writing. Run when the reference is older than 60 days or before planning upgrades, for 'is our stack current', 'latest versions'.developmenttypescriptgoVotes: 0GitHub stars: 4
Setup StackASelects and pins the technology stack — project type, backend, frontend, UI kit, API style (GraphQL default), game engine, database, tests, CI, deploy target, observability, layout — and writes technical-preferences.md with exact versions from the stack reference. Run at project start after /init or when the stack changes, or for 'choose the stack', 'which framework should we use', 'pin the versions'.developmentgophpVotes: 0GitHub stars: 4
RefactorARefactors Go or PHP code without changing behaviour: dry-run plan by numbers (build, tests, coverage, dependency graph), stories via /create-stories, `--apply S-NNN` execution with characterisation tests first and one green step per commit; modes <package|namespace|file>, layout, tests, framework (PHP), or every applicable mode without an argument. Use for 'refactor this package', 'migrate the layout'.developmentgophpVotes: 0GitHub stars: 4
Skills DirectorySkills Directory Pro Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills.See Pro
InitBScaffolds the Web Studio in a project (the studio's init, not Claude Code's): asks the conversation language and review mode, creates/updates CLAUDE.md sections, seeds .claude/docs, .claude/rules, docs/ and production/, merges settings; a re-run adds only what is missing and hands off to /update or /adopt. Run first in plugin mode (copy mode: to set the language), for 'set up the studio'.developmentgobashVotes: 0GitHub stars: 4
Feature SpecAAuthors a feature specification (scenarios, rules, data, API operations, UI states, edge cases, security, accessibility, acceptance criteria) from the product spec. Produces docs/specs/features/F-NNN-name.md. Run per feature before stories.developmentgobashVotes: 0GitHub stars: 4
Dev StoryAImplements a story end-to-end: loads spec/contract/ADR/rules, routes to the right engineers (Go/PHP/Node/GraphQL/Angular/Vue/three.js/DB), drives code + tests, runs checks, confirms each acceptance criterion. The core implementation skill — run after stories exist, before /code-review and /story-done.developmentpythongoVotes: 0GitHub stars: 4
Design SystemADefines the project design system — principles, --ds-* tokens (colour roles, spacing, type, radius, motion) for light/dark, component inventory with states and aria patterns, mapping onto the chosen UI kit, game HUD rules — into docs/specs/design-system.md and a tokens CSS draft. Run before UI implementation, or for 'design tokens', 'dark theme', 'component library'.developmentbashvueVotes: 0GitHub stars: 4
Create StoriesASlices a feature spec into implementable vertical-slice stories (contract → backend → frontend/game → tests) with acceptance criteria mapped to tests, size, layer and ADR links, in production/stories/F-NNN/. Run after /feature-spec and before /sprint-plan, or for 'break this feature into stories', 'create stories for F-NNN', 'what are the tasks'.developmentgobashVotes: 0GitHub stars: 4
Code ReviewAReviews the branch's diff (`--diff`, the PR's changes) or given files for correctness, standards, ADR adherence, OWASP security, performance and testability, routing files to the studio's lead and specialist and to appsec-engineer for sensitive paths. Read-only BLOCKING/WARNING/INFO. The studio's review, not Claude Code's built-in: use for 'review my changes', 'review the diff', 'review this PR'.developmenttypescriptgoVotes: 0GitHub stars: 4
Architecture ReviewACross-checks ADRs, API contracts, data model, threat model and feature specs for consistency and feasibility, with stack facts verified against the stack reference; `code` mode checks the repository itself against them and records drift. Read-only PASS / CONCERNS / FAIL. Run at the architecture→build gate, quarterly, after /adopt, or for 'does the code still match the ADRs'.developmentgophpVotes: 0GitHub stars: 4
Api ContractADesigns the API contract before implementation — GraphQL SDL by default (types, Node/connections, inputs, mutations with payload errors, subscriptions, @auth, persisted operations) or OpenAPI 3.1 / AsyncAPI for REST/events; validates with graphql-inspector / spectral, generates types, documents in docs/architecture/api/. Also game WebSocket protocols.developmenttypescriptgoVotes: 0GitHub stars: 4
AdoptABrownfield onboarding — detects the real stack of an existing project (Go/PHP/Node, Angular/Vue/Nuxt, GraphQL/REST, three.js, Kubernetes charts, OpenTelemetry/Prometheus), fills technical-preferences from the facts, audits existing artifacts against studio formats, merges settings/CLAUDE.md, and produces a numbered adoption plan. Run when installing the studio into an existing project.developmentgophpVotes: 0GitHub stars: 4
Usage DashboardAUse when the user explicitly asks to regenerate, rebuild, or refresh the `claude-prospector` token-usage dashboard with no interpretive question attached — runs `python -m claude_prospector dashboard`, writes the HTML file, and reports the output path. Do NOT use when the user is asking what the data means, where their budget stands, or what to change (use `usage-analysis` instead — it regenerates as part of answering). Trigger phrases: "regenerate the usage dashboard", "rebuild my claude-pro...developmentpythonbashVotes: 0GitHub stars: 3
Usage AnalysisAUse when the user asks an interpretive question about their Claude Code token spend — what's interesting, what's anomalous, what to change. This skill produces insights and questions; it does NOT enumerate top consumers (the dashboard does that). Use `usage-dashboard` for "show me the numbers." Use `claude-audit` for "audit my config overlap." Use this skill for "tell me what's interesting / what should I change." Trigger phrases: "am I close to my Claude limit", "how much Sonnet am I using...developmentpythongoVotes: 0GitHub stars: 3
Setup ProspectorBSet up claude-prospector's plugin-owned Python venv. Invoked via /setup-prospector or natural-language triggers: "set up claude-prospector", "install prospector dependencies", "prospector isn't working", "fix prospector", "repair prospector". Do not trigger on "dashboard", "usage analysis", or "skill adoption" — those are distinct skills.developmentpythonrustVotes: 0GitHub stars: 3
Session AnalysisAUse when the user wants a judgment-level read on whether a Claude Code session stayed on task — did the agent do what was originally asked, and what did it acknowledge skipping. This is the interpretive (LLM) complement to the deterministic `session-audit` CLI: 1a extracts ask-vs-done for free; this skill adds the `Variance` and `What was NOT done` judgment that a parser can't compute, then persists a combined record for drift analysis. Cost: ~1-3k tokens of the current session, paid only wh...developmentpythonshellVotes: 0GitHub stars: 3
Claude AuditAAudit a project's effective Claude Code configuration — custom and plugin-provided agents and skills — and produce a structured overlap/conflict report with keep / modify / drop recommendations scoped to the project's stated objectives. Trigger this skill whenever the user types `/claude-audit`, asks to "audit my claude config", "find overlap in my agents", "check for skill conflicts", "are any of my agents duplicates", "what's redundant in my setup", or any similar request to review the agen...developmenttypescriptpythonVotes: 0GitHub stars: 3
Source Driven DevelopmentAGrounds every implementation decision in project documentation AND official framework docs. Use before writing any code — check project artifacts first, then verify framework APIs. Prevents "retraining from scratch" each session.developmenttypescriptpythonVotes: 0GitHub stars: 3
Iphone Duo AdaptationAAdapt iOS apps (SwiftUI and UIKit) for iPhone Duo, Apple's folding iPhone: two displays, a hinge, toolbars and tab bars that move to the side, reserved regions, and the iOS 27.1 layout APIs (ArrangementView, UIArrangementViewController, reservedRegions, onHingeChange, axisBehavior, toolbarVerticalBehavior). Use this skill whenever the user mentions iPhone Duo, a foldable or folding iPhone, the hinge or fold, book or laptop pose, inner or outer display, Device Hub, vertical bars, or Arrangemen...developmentrustgoVotes: 0GitHub stars: 11
Bug TriageATriage bugs reported in chat/issues, search for duplicates, file or update GitHub issues with full context, and push fix PRs.developmenttypescriptpythonVotes: 0GitHub stars: 2
Ao Desktop DevALaunch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data.developmentrustgoVotes: 0GitHub stars: 2