All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 65,763
- 2,741
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 11,953–11,976 of 65,763 skills
- Permission Scope AuditDetects over-broad permission requests where a narrower permission or privacy-preserving alternative API is sufficient, violating Guideline 5.1.1(iii) data minimization requirements.Votes: 0GitHub stars: 18
- Screenshot GuidelinesDetects screenshot submission issues including launch-screen-only assets and cross-platform UI references, enforcing Guideline 2.3.3 which requires screenshots to show the app in actual use.Votes: 0GitHub stars: 18
- Metadata AccuracyDetects mismatches between features claimed in App Store metadata and features actually implemented in the codebase, enforcing Guideline 2.3.1 which prohibits misleading app descriptions.Votes: 0GitHub stars: 18
- Age Rating AccuracyDetects feature patterns that require a higher age rating than commonly submitted, enforcing Guideline 2.3.6 which requires age ratings to accurately reflect the app's content and social features.Votes: 0GitHub stars: 18
- Orientation SupportDetects missing iPad orientation keys, portrait-only orientation locks, and forced-rotation patterns that cause layout failures when an iPad reviewer rotates their device, violating guideline 2.4.1.Votes: 0GitHub stars: 18
- Subscription DisclosureDetects missing or obscured subscription disclosure elements on paywall screens, enforcing Guideline 3.1.2(c) requirements for auto-renewal terms, trial end dates, and actual price.Votes: 0GitHub stars: 18
- Sign In With AppleDetects apps that offer third-party social login without offering Sign in with Apple, violating Guideline 4.8 which requires Sign in with Apple wherever third-party authentication is used.Votes: 0GitHub stars: 18
- Iap ComplianceDetects external payment processors and WebView payment flows used for digital goods and verifies StoreKit integration, enforcing Guideline 3.1.1's requirement to use Apple IAP for all digital content purchases.Votes: 0GitHub stars: 18
- Search Context7External-package truth: any signature, member, or capability of an imported library resolves through Context7 over memory or a guessed git tag. Load before the first lookup. Fires on any Context7 mention, doc or API lookup, a new import, "how does <lib> do X", and before coding against an uninstalled member. Un-indexed sources belong to search-tavily.Votes: 0GitHub stars: 2
- Rhino McpDrives a live Rhino session: on-demand slot spawn or adoption of a user-started Rhino, slot lifecycle, RhinoCommon scripting in C# and Python, `.3dm` open/save, scene and selection queries, layer materials, camera framing, cost-bounded viewport capture, and Grasshopper2 canvas authoring. Use when working within Rhino for code development, or dedicated Rhino session work, creating Grasshopper scripts and layouts, or when its MCP tools are absent — "work in Rhino", "work in Grasshopper', "show ...Votes: 0GitHub stars: 2
- AdhdParallel divergent ideation for coding agents. Spawns N isolated branches under different cognitive frames (regulator, biology, speedrunner, 10-year-old, $0 budget), scores, clusters, prunes traps, and deepens top survivors. Use on /adhd, "ADHD mode", brainstorm/ideate intents, or open-ended design, architecture, naming, API/SDK surface, and fuzzy-debugging decisions. Skip for syntax, lookups, bugs with known root cause, or closed phrasing ("quick", "standard", "canonical", "textbook").Votes: 0GitHub stars: 2
- Shift DocsRoute Shift documentation, architecture notes, and tickets correctly. Use when Codex is about to create or move docs, write an architecture plan, capture a design decision, create a ticket, or update repo documentation for Shift.Votes: 0GitHub stars: 336
- DocsUpdate or create DOCS.md files for Shift subsystems. Use this skill whenever the user asks to update docs, refresh documentation, create a DOCS.md, write module documentation, or says "update docs for X". Also trigger after completing a large feature when Claude.md says to update docs — check if any DOCS.md in the affected subsystem needs refreshing.Votes: 0GitHub stars: 336
- Docs AuditAdversarially fact-check DOCS.md files against the actual source code, verifying every concrete claim rather than trusting structure checks. Use when the user asks to audit docs, verify documentation accuracy, check whether docs are still true, or on a scheduled documentation review. This is the semantic layer the mechanical checkers cannot cover.Votes: 0GitHub stars: 336
- Writing TestsCanonical rules for writing tests in the Shift codebase. Use whenever you add, rewrite, or review a `.test.ts` or `.spec.ts` file — or any time you're about to mock, stub, or spy your way around a testing problem. Covers TestEditor-based tests and desktop E2E tests driven through EditorDriver.Votes: 0GitHub stars: 336
- UiDesign, implement, audit, or review Shift user interfaces and shared UI components. Use for React components, Base UI primitives, Tailwind styling or theme tokens, Figma/reference matching, accessibility, icon-only actions, tooltips, menus, popovers, dialogs, forms, layout, and visible UI regressions.Votes: 0GitHub stars: 336
- RustdocAdd or revise source-level Rustdoc for Shift Rust APIs. Use before writing or editing documentation comments in `.rs` files, especially for public or crate-visible APIs, domain structures, compiler adapters, persistence boundaries, trait implementations, unsafe code, or any API where ownership, units, coordinate spaces, mutation, I/O, sparse behavior, failure modes, panics, or concurrency are easy to misunderstand.Votes: 0GitHub stars: 336
- JsdocAdd or revise source-level JSDoc for Shift APIs. Use this skill before writing or editing documentation comments for exported classes, methods, constructors, domain data structures, render frames, reactive state, or any API where caller intent, side effects, lifetime, ownership, or nullability are easy to misunderstand.Votes: 0GitHub stars: 336
- IssueCanonical rules for finding, creating, and updating Shift GitHub issues. Use whenever the user asks to file, create, open, update, triage, or search for an issue, or when substantial work needs an issue before a pull request. Prevents duplicates and defines acceptance criteria and pull-request closure semantics.Votes: 0GitHub stars: 336
- CommitCanonical rules for writing git commits in the Shift codebase. Use whenever the user asks to commit, stage and commit, create a pull request that requires commits, or draft a commit message. Enforces Conventional Commits, release-note quality, concise subjects, and logical commit boundaries.Votes: 0GitHub stars: 336
- Tufte VisualizationUse as an evidence-design overlay to create, revise, or critique charts, dashboards, analytical figures, visual tables, maps, KPI displays, evidence-rich diagrams, and decision-grade reports. Governs truthful comparison, uncertainty, documentation, restraint, accessibility, and rendered QA while medium-specific skills own implementation mechanics. Do not use for generic frontend or marketing design, decorative graphics, analysis without visual output, or diagrams without an evidentiary claim.Votes: 0GitHub stars: 9
- Prose QualityDraft, revise, or review a substantive writing deliverable when editorial quality is itself part of the requested outcome. Use for authored documentation, reports, public copy, or explicit editing and style critique. Do not trigger for ordinary conversation, engineering reasoning, explanations of current work, or requests for longer or more expressive answers alone.Votes: 0GitHub stars: 9
- Performance TradeoffMeasure and judge hardware-bound optimization tradeoffs involving latency, throughput, CPU/GPU/device or unified memory, headroom, capacity, OOM, fallback, offload, admission limits, or workload size. Use for benchmark design or execution, performance-claim review, hardware qualification, and optimization acceptance decisions. Do not use for routine cleanup or performance-neutral refactors with no material resource claim.Votes: 0GitHub stars: 9
- VerifyRun this after every code change in this Vue project, before committing, before opening a PR, or whenever the user says "verify", "check", "lint", "run tests", "build", "audit". Diff audit (router guards, store boundaries, UX, /ui consistency, error handling) → lint → tests + coverage gate → build. Coverage drops → add tests, never lower thresholds. Triggers on "is this ready to commit?", "any issues?", "tests passing?".Votes: 0GitHub stars: 20