All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 66,163
- 2,757
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 13,393–13,416 of 66,163 skills
- Rust SerdeSerde as the boundary where untrusted input becomes a domain type — rename_all, default, skip_serializing_if, flatten, the four enum representations, deny_unknown_fields, and try_from validation. Use when deriving Serialize or Deserialize, when choosing an enum wire representation, when a JSON or YAML shape does not match the Rust type, or when the user asks how to validate deserialized data.Votes: 0GitHub stars: 2
- Rust MacrosWrite a macro only when a function, a trait, or a generic cannot do the job — then by-example before proc-macro, with hygiene, a `_private` helper module, and spanned compile errors instead of panics. Use when writing or reviewing macro_rules! or a proc macro, when a derive or attribute macro is being added, when macro hygiene or `$crate` comes up, or when the user asks whether something should be a macro.Votes: 0GitHub stars: 2
- Rust FfiDesign an FFI boundary meant to last — a thin translation layer with the logic in core crates, no panic across the boundary, explicit ownership on every pointer, repr(transparent) newtypes, and unsafe extern in edition 2024. Use when designing or reviewing a Rust FFI surface, when exposing a Rust library to another language, when a DLL or shared library keeps state, or when the user asks how to shape an extern function.Votes: 0GitHub stars: 2
- vue-ddd-architectureBuild and maintain scalable Vue 3 + TypeScript applications using a layered, module-per-domain architecture (domain / application / infrastructure / ui) with enforced dependency boundaries and a public API per module. Use this skill whenever the user adds a feature or a business module to a Vue app, bootstraps a new Vue project, asks where a file or piece of logic belongs, wonders whether their layering is correct, or wants to refactor a messy pages/components Vue codebase into modules — even...Votes: 0GitHub stars: 2
- DesignDesign partner for frontend interfaces. One command covers every visual discipline: color, typography, layout, motion, interaction, responsive behavior, voice, surface, review, and refinement.Votes: 0GitHub stars: 2
- Dev BrowserBrowser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.Votes: 0GitHub stars: 896
- TurborepoTurborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.Votes: 0GitHub stars: 896
- Spec ReviewReview a spec for under-specified areas, bugs, and adherence to the spec requirements in this skill. Use when asked to review, critique, or check a spec.Votes: 0GitHub stars: 896
- Improve Codebase ArchitectureFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.Votes: 0GitHub stars: 896
- Glimpse ChangesCreate a visual explanation of the current session diff as a single HTML page and show it in a native Glimpse window. Use when the user wants a visual walkthrough of local code changes instead of a plain text diff.Votes: 0GitHub stars: 896
- Generate Spec V2Create a code-based implementation spec in the specs/ directory for a significant feature, fix, or refactor. Use when the user asks to plan, spec, scope, or phase work before implementation and the plan should cover top-level Mermaid flows, important types, per-phase call-stack and code diffs, commit-sized phases, and checks.Votes: 0GitHub stars: 896
- Fix Merge ConflictsResolve Git merge, rebase, or cherry-pick conflicts by preserving intent from both sides. Use when unmerged paths or conflict markers are present, especially when you must inspect the PR title and description tied to conflicting commits before choosing a resolution.Votes: 0GitHub stars: 896
- Erroreerrore is Go-style error handling for TypeScript: return errors instead of throwing them. Instead of Go's two-value tuple (val, err), functions return a single Error | T union. Instead of checking err != nil, you check instanceof Error. TypeScript narrows the type automatically — forget to check and your code won't compile. No wrapper types, no Result monads, just unions and instanceof. The errore npm package provides helper utilities (createTaggedError, tryAsync, matchError, findCause, parti...Votes: 0GitHub stars: 896
- HandelsregisterSearch the German commercial register (Handelsregister), download registry documents for a company — Gesellschafterliste (shareholder list), Gesellschaftsvertrag (articles of association), current/chronological printouts (AD/CD), structured XML (SI) — and query date-based Registerbekanntmachungen (Löschungsankündigungen, UmwG announcements, new filings). Use when the user asks for a Handelsregisterauszug, Gesellschafterliste, registry documents, company data from handelsregister.de, or recent...Votes: 0GitHub stars: 2
- Icca HarnessICCA names the four separated roles that carry the method: Implementer, Checker, Control, Auditor. Mandatory development workflow for any task that changes production code, fixes a bug, adds a feature, performs a refactor, or creates a commit. MUST be loaded before implementation begins. Keeps the orchestrator's context lean (delegation to a cheaper implementer tier, index navigation, evidence ledger) and enforces Commit Contract, Red Proof, frozen acceptance tests, delegated implementation, ...Votes: 0GitHub stars: 2
- Typescript Clean CodeUse when writing, fixing, editing, reviewing, or refactoring any TypeScript code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.Votes: 0GitHub stars: 2
- Ts Clean TestsUse when writing, fixing, editing, or refactoring TypeScript tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test. Also trigger on: slow or flaky tests, `test.skip`/`it.skip`/`.todo` without a clear reason, `test.only` left in committed code, tests that only cover the happy path, tests with multiple assertions about different concepts, missing boundary cases (empty arrays, off-by-one, page zero), or asks about "coverage gap" / "edge case".Votes: 0GitHub stars: 2
- Ts Clean NamesUse when naming, renaming, or fixing names of variables, functions, classes, interfaces, or modules in TypeScript. Enforces Clean Code principles—descriptive names, appropriate length, no encodings. Also trigger on: single-letter or cryptic identifiers (`d`, `x`, `proc`), Hungarian notation (`strName`, `arrUsers`, `nCount`), `I`-prefixed interfaces (`IUserRepository`), function names that hide side effects (e.g. `getConfig` that also mutates state), ambiguous names like `rename(source, target...Votes: 0GitHub stars: 2
- Ts Clean GeneralUse when writing, fixing, editing, or reviewing TypeScript code quality. Enforces Clean Code's core principles—DRY, single responsibility, clear intent, no magic numbers, proper abstractions. Also trigger on: duplicated logic across files or branches (G5), magic numbers or hardcoded strings (G25), long if/else chains that should be union types plus polymorphism (G23), chained property access like `a.b.c.d` or long optional-chain trains (G36), functions juggling multiple responsibilities (G30)...Votes: 0GitHub stars: 2
- Ts Clean FunctionsUse when writing, fixing, editing, or refactoring TypeScript functions. Enforces Clean Code principles—maximum 3 arguments, single responsibility, no flag parameters. Also trigger on: functions (or React components) with 4+ parameters/props, boolean flag parameters like `isTest`, functions that mutate their parameters (e.g. push to an input array), unused exports or dead helper functions, or asks like "too many props", "split this function", "is this still used". Also trigger on: helpers defi...Votes: 0GitHub stars: 2
- Ts Clean CommentsUse when writing, fixing, editing, or reviewing TypeScript comments and TSDoc. Enforces Clean Code principles—no metadata, no redundancy, no commented-out code. Also trigger on: commented-out code blocks, TODO/FIXME banners, author/ticket/date metadata in comments or TSDoc, TSDoc that no longer matches the code, redundant comments that restate the code (e.g. `i += 1; // increment i`), or asks like "is this comment useful", "why is this block commented".Votes: 0GitHub stars: 2
- Ts Boy ScoutUse when fixing, editing, changing, debugging, or working with any TypeScript code. Applies the Boy Scout Rule—always leave code cleaner than you found it. Orchestrates other clean code skills as needed. Also trigger on: "while you're at it", "any quick wins", "improve this a bit", "anything else obviously wrong", or when editing existing TypeScript and an adjacent small cleanup is possible alongside the asked-for change.Votes: 0GitHub stars: 2
- Python Clean CodeUse when writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.Votes: 0GitHub stars: 2
- Py Clean TestsUse when writing, fixing, editing, or refactoring Python tests. Enforces Clean Code principles—fast tests, boundary coverage, one assert per test. Also trigger on: slow or flaky tests, `@pytest.mark.skip` without a clear reason, tests that only cover the happy path, tests with multiple assertions about different concepts, missing boundary cases (empty input, off-by-one, page zero), or asks about "coverage gap", "edge case", "did we test".Votes: 0GitHub stars: 2