All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 65,696
- 2,738
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 browserBrowse development skills
Showing 10,633–10,656 of 65,696 skills
- Design SystemDefines 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'.Votes: 0GitHub stars: 4
- Create StoriesSlices 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'.Votes: 0GitHub stars: 4
- Code ReviewReviews 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'.Votes: 0GitHub stars: 4
- Architecture ReviewCross-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'.Votes: 0GitHub stars: 4
- Api ContractDesigns 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.Votes: 0GitHub stars: 4
- AdoptBrownfield 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.Votes: 0GitHub stars: 4
- Usage DashboardUse 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...Votes: 0GitHub stars: 3
- Usage AnalysisUse 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...Votes: 0GitHub stars: 3
- Setup ProspectorSet 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.Votes: 0GitHub stars: 3
- Session AnalysisUse 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...Votes: 0GitHub stars: 3
- Claude AuditAudit 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...Votes: 0GitHub stars: 3
- Source Driven DevelopmentGrounds 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.Votes: 0GitHub stars: 3
- Iphone Duo AdaptationAdapt 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...Votes: 0GitHub stars: 11
- Bug TriageTriage bugs reported in chat/issues, search for duplicates, file or update GitHub issues with full context, and push fix PRs.Votes: 0GitHub stars: 2
- Ao Desktop DevLaunch, 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.Votes: 0GitHub stars: 2
- Reverse EngineerPerform static analysis on Android APK, iOS IPA, or bundled web apps to extract endpoints, secrets, permissions, code flow, and other security-relevant dataVotes: 0GitHub stars: 5
- Mobile Vuln HuntHunt mobile vulnerability classes in decompiled Android (jadx/apktool) and iOS (class-dump/otool/nm) trees — ripgrep signature scan first (zero deps), optional semgrep taint analysis for dataflow classes, then triage (exported check, attacker-APK discipline) and pick the matching dynamic PoC (adb/drozer/Frida) per class from the bundled reference docs.Votes: 0GitHub stars: 5
- Afl FuzzingGreybox fuzz Android native libraries (.so) on-device with AFL++ — cross-compile the fuzzer for Android arm64, harness a JNI parser with a stub JNIEnv, detect memory bugs with ASan/libdislocator, and validate the harness actually reaches the target.Votes: 0GitHub stars: 5
- Improve WorkflowReview coding-agent execution reports and SpecStory history to find workflow bottlenecks, repeated work, and verification gaps; propose or implement evidence-based workflow improvements. Use for workflow audits and improving orchestration, not for implementing product features.Votes: 0GitHub stars: 4
- ImplementTake a feature, fix, or PR from request to checked, independently reviewed code. Claude acts as chief of staff, delegating scoped work to subagents. Use for /implement and implementation requests.Votes: 0GitHub stars: 4
- Designing Mobile UiThe design doctrine for the mobile app: typography roles, spacing rhythm, motion tokens, state choreography, and per-surface "default beautiful" checklists. Use when building or restyling any screen, component, list, form, modal, or interaction — BEFORE composing the JSX.Votes: 0GitHub stars: 9
- Authoring Vertical SliceThe migration -> RLS -> ./client read -> tRPC procedure -> web screen -> mobile screen -> test recipe for shipping one whole feature slice through the Next 16 web + Expo 57 mobile + Supabase monorepo in a single turn. Use when asked to add a feature, procedure, or screen end-to-end.Votes: 0GitHub stars: 9
- Authoring E2ee FeatureThe decide-the-columns -> schema -> ciphertext DAL -> seal/open at the screen -> store-policy -> DSR record -> reviewers recipe for encrypting one feature end-to-end with the opt-in e2ee module, so the server never holds plaintext or a key that decrypts it. Use when asked to encrypt a feature, add client-side encryption, or make a column unreadable to the server.Votes: 0GitHub stars: 9
- GenerateGenerates a project-specific /find-bugs skill with stack-specific security and correctness checklists. Run once per project. Usage: /generate-find-bugsVotes: 0GitHub stars: 42