Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 38011–38040 of 39779 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| indexing-strategyjacob-balslev/skillsUse when designing or auditing the maintained index set for a database workload: choosing index structures, matching access patterns, setting composite order, balancing read speed against write/storage cost, and deciding when to add, keep, or drop indexes. Do NOT use for tuning one slow query (use query-optimization), applying production DDL (use database-migration), isolation choices, schema design, or sharding. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| observability-modelingjacob-balslev/skillsUse when designing telemetry semantics before or during implementation: logs, metrics, traces, events, spans, attributes, correlation IDs, SLOs, alert signals, and diagnostic questions. Do NOT use for domain/business event contracts (use `event-contract-design`), configuring an error tracker alone (use `error-tracking`), performance optimization (use `performance-engineering`), or debugging a current incident (use `debugging`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| query-optimizationjacob-balslev/skillsDiagnosing and tuning a specific slow relational-database query from plan evidence: workload impact, exact query context, EXPLAIN / actual execution plans, row-estimate accuracy, access path choice, join order, sort/hash spills, JIT/planning overhead, parameter-sensitive plans, plan regressions, statistics, and rewrite-vs-index-vs-operational response selection. Start from the actual plan and runtime evidence, not from the reflex to add an index; modern engine features such as Query Store, PSP/OPPO, SQL Plan Management, pg_stat_statements, auto_explain, MySQL histograms, Oracle DBMS_XPLAN, and PostgreSQL planner improvements are evidence sources and response tools, not replacements for diagnosis. Do NOT use for designing the durable index portfolio (use indexing-strategy), schema design (use entity-relationship-modeling), distributed partitioning (use sharding-strategy), isolation-level correctness (use transaction-isolation), or whole-system load testing (use performance-testing). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| replication-patternsjacob-balslev/skillsUse when designing how a database keeps multiple copies of its data in agreement across nodes for availability, read scaling, and disaster recovery: the three foundational topologies (single-leader / primary-replica, multi-leader / multi-primary, leaderless / quorum), synchronous vs asynchronous replication and the replication-lag trade-off, log shipping vs statement replication vs trigger-based replication, the read-after-write consistency problem and its mitigations (sticky session, read-from-leader, monotonic reads), the failover model and split-brain risk, and the relationship to the CAP/PACELC choices the topology realizes. Do NOT use for horizontal partitioning across nodes (use sharding-strategy), the CAP theoretical frame itself (use cap-theorem-tradeoffs), single-node transactional guarantees (use transaction-isolation), or query tuning (use query-optimization). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| schema-evolutionjacob-balslev/skillsUse when reasoning about how a database schema changes over time without breaking deployed application code — the multi-release path from the current schema to a target schema: the expand/contract pattern (Ambler & Sadalage / Fowler's parallel change), the zero-downtime change rules, the backwards-and-forwards compatibility envelope (deploy ordering and rollback discipline), the catalog of schema changes (add column, drop column, rename, type change, add constraint, add index) and the safe procedure for each, the dual-write and dual-read transitions (with named source-of-truth and production consistency-check discipline) that make non-trivial changes safe, the lock-acquisition hazard (why even a metadata-only DDL needs a bounded lock-acquisition budget — Postgres lock_timeout + retry, or the engine equivalent — because lock acquisition is a FIFO queue), the cross-engine online-change mechanisms (Postgres CONCURRENTLY / NOT VALID, MySQL INSTANT/INPLACE/COPY Online DDL, gh-ost / pt-osc ghost-table cutover, Vitess/PlanetScale deploy requests and revert windows), the view-based multi-version tooling that automates expand/contract (pgroll, Reshape), the migration-lint enforcement layer (Strong Migrations, Squawk, Atlas), and the relationship between schema evolution as a design discipline and database-migration mechanics as its tooling. Do NOT use for the mechanical execution of one migration (use database-migration), schema design from scratch (use entity-relationship-modeling), query tuning (use query-optimization), or distributed-data partitioning (use sharding-strategy). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| sharding-strategyjacob-balslev/skillsUse when reasoning about horizontal partitioning of data across nodes for storage capacity and write throughput beyond a single node: the three foundational partitioning schemes (range, hash, directory/lookup), the shard-key choice that determines whether the system scales or hotspots, the resharding problem and how consistent hashing addresses it, cross-shard queries and the joins-and-transactions trade-off, the relationship to replication (sharding partitions data; replication copies each shard), and the failure modes (hot shard, skewed distribution, cross-shard transactions, range-end overload). Do NOT use for replicating the same data across nodes (use replication-patterns), the CAP/PACELC frame (use cap-theorem-tradeoffs), single-node performance tuning (use query-optimization), or indexing within a shard (use indexing-strategy). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| color-system-designjacob-balslev/skillsUse when designing a color system — palette construction, semantic color tokens, WCAG contrast pairings, perceptual scale generation in OKLCH/LCH/HCT, wide-gamut fallbacks, and light/dark/high-contrast parity. Do NOT use for single brand-color picks, runtime theme-switching mechanics, token delivery architecture, or non-color design tokens. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| component-architecturejacob-balslev/skillsThe architectural discipline of structuring a UI component library — layering, API surface design, headless/styled split, and state contracts — so component APIs survive reuse across products, themes, and teams. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| dark-mode-implementationjacob-balslev/skillsUse when implementing dark mode — prefers-color-scheme detection, theme persistence, flash-of-unstyled-theme prevention, color token mirroring, image and asset variants, and meta theme-color updates. Do NOT use for designing the dark palette itself, designing the token architecture, or generic theme-switching across more than two themes. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| design-module-compositionjacob-balslev/skillsUse when designing reusable component modules — composition patterns, compound components, slot/children APIs, render props, headless component contracts, and the choice between configuration and composition. Do NOT use for application-level architecture, single-use feature components, or visual styling decisions. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| design-thinkingjacob-balslev/skillsUse when orchestrating a full human-centered design process across discovery, definition, ideation, prototyping, and testing — when uncertain which stage of the arc a team is in, when deciding whether to loop back, or when routing to the right stage-specific sibling skill. Do NOT use for single-stage execution (go directly to problem-framing, user-research, research-synthesis, journey-mapping, ideation, prototyping, or usability-testing) or for engineering domain discovery (use event-storming). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| form-ux-architecturejacob-balslev/skillsUse when designing or auditing form structure and validation UX: field grouping, required vs optional inputs, validation timing, client/server validation split, submission lifecycle, recovery, multi-step forms, and high-risk data entry. Do NOT use for labels and announcements alone (use `a11y`), validation-message wording (use `microcopy`), API schema design (use `api-design`), or stored data modeling (use `entity-relationship-modeling`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| ideationjacob-balslev/skillsUse when generating a wide range of solution concepts before converging on a direction, running structured idea-generation sessions, breaking out of solution fixation, or moving from divergent to convergent selection with explicit criteria. Do NOT use for collaborative engineering domain discovery (event-storming), solo deep technical design, or making final go/no-go investment decisions — those require different methods. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| information-architecturejacob-balslev/skillsUse when structuring information for findability: navigation, page hierarchy, docs architecture, sitemap shape, labeling systems, wayfinding, and content grouping. Do NOT use for formal category-governance work (use `taxonomy-design`), responsive page composition (use `layout-composition`), component/token architecture (use `design-system-architecture`), or sentence-level UI text (use `microcopy`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| interaction-feedbackjacob-balslev/skillsUse when designing UI feedback around user actions and system state: loading, skeletons, optimistic updates, progress, success, errors, empty states, retries, disabled/pending states, autosave, undo, and perceived latency. Do NOT use for the words inside feedback (use `microcopy`), accessibility announcement mechanics (use `a11y`), business lifecycle modeling (use `state-machine-modeling`), or performance optimization (use `performance-engineering`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| interaction-patternsjacob-balslev/skillsUse when choosing or auditing UI interaction patterns and controls: tabs vs pages, dropdown vs combobox, stepper vs wizard, modal vs inline edit, disclosure, command menus, selection, filtering, and gesture alternatives. Do NOT use for accessibility compliance (use `a11y`), task decomposition (use `task-analysis`), feedback-state staging (use `interaction-feedback`), or reusable component API design (use `design-system-architecture`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| journey-mappingjacob-balslev/skillsUse when mapping a user's experience across multiple touchpoints and time, surfacing emotional peaks and troughs, identifying opportunity moments in a cross-channel flow, or aligning a team on the end-to-end experience including back-stage support processes. Do NOT use for decomposing a single screen into UI steps (use task-analysis) or for drawing back-end service architecture diagrams — journey maps describe human experience, not system topology. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| layout-compositionjacob-balslev/skillsUse when deciding responsive page or screen structure: section order, scan pattern, grid/flex composition, breakpoints, viewport hierarchy, responsive media, and density. Do NOT use for user-goal decomposition (use `task-analysis`), navigation taxonomy (use `information-architecture`), visual polish (use `visual-design-foundations`), or component/token contracts (use `design-system-architecture`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| microcopyjacob-balslev/skillsUse when writing or reviewing functional UI text: button labels, empty states, tooltips, dialogs, placeholders, loading/progress messages, toasts, inline validation, permission copy, or onboarding steps. Covers interface-copy patterns such as verb-first action labels, acknowledge-explain-guide empty states, one-sentence tooltips, consequence-first confirmations, progressive loading language, and blur/fix validation messages. Do NOT use for marketing persuasion, documentation prose/guide structure, feedback-state staging, or general linguistic rationale behind wording. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| prototypingjacob-balslev/skillsUse when building an artifact whose purpose is to answer a specific question — paper sketch, wireframe, clickable mockup, wizard-of-oz, role-play, service prototype, or code spike — at the lowest fidelity sufficient to produce that learning. Do NOT use for production-grade component construction, design-system contribution, or building the actual ship-ready feature — those are design-module-composition and engineering implementation. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| research-synthesisjacob-balslev/skillsUse when turning raw qualitative research output (interview transcripts, field notes, diary entries, observation logs) into themes, patterns, insight statements, and design-ready artifacts via affinity mapping, empathy maps, and jobs-to-be-done framing. Do NOT use for collecting new research, quantitative analysis, statistical inference, or summarizing a single document — synthesis specifically operates on a corpus of qualitative evidence. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| semioticsjacob-balslev/skillsUse when designing or auditing icon systems, colors/badges/shapes, visual metaphors, interface signs, or naming-plus-visual surfaces that users misread. Covers semiotic reasoning across icon/index/symbol, signifier/signified, denotation/connotation/myth, color/shape/position/iconography, affordances, code/API signifiers, and semiotic-coherence audits. Do NOT use for actual UI wording (use `microcopy`), palette/typography craft (use `visual-design-foundations`), accessibility or contrast compliance (use `a11y`), formal class hierarchies, or word morphology rules. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| typography-systemjacob-balslev/skillsUse when designing a typography system — typeface selection and pairing, modular type scale, vertical rhythm, line-height and measure rules, and web font delivery (subsetting, font-display, variable fonts). Do NOT use for body copy writing, single-headline font pairing, or non-text design tokens. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| usability-testingjacob-balslev/skillsUse when observing representative real users attempting realistic tasks on a prototype or live product to surface usability issues: moderated or unmoderated, remote or in-person, concurrent or retrospective think-aloud, task scenarios, participant screening, tree/first-click testing for IA findability questions, pilot runs, severity rating, sample sizing by claim type, and ethical recording/consent. Do NOT use for automated test suites, code coverage, CI pipelines, unit/integration testing, load testing, or replacing participants with AI/synthetic users; those are engineering verification or synthetic-analysis concerns, not human-behavior observation. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| user-researchjacob-balslev/skillsUse when planning or conducting generative qualitative research with real users — interviews, contextual inquiry, ethnographic observation, diary studies — to learn what people do, think, and need in their own context. Do NOT use for analytics review, survey statistics, A/B test interpretation, or agent-side intent classification — those are different research practices entirely. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| visual-design-foundationsjacob-balslev/skillsUse when designing or auditing visual craft at foundation level: color palette, typography, spacing, elevation, rhythm, density, optical alignment, visual hierarchy direction, brand fit, contrast intent, and motion feel — making a surface more legible, polished, scannable, and tone-appropriate without changing its task structure. Do NOT use for sign-system meaning (use `semiotics`), token/component architecture (use `design-system-architecture`), responsive structure (use `layout-composition`), accessibility compliance (use `a11y`), or the DEEP contract of one dimension — formal color systems (use `color-system-design`), full type systems (use `typography-system`), deep hierarchy modeling (use `visual-hierarchy`), theming/token delivery (use `theme-system-design`), or interaction-state feedback (use `interaction-feedback`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| visual-hierarchyjacob-balslev/skillsUse when establishing visual hierarchy — type scale ratios, spacing rhythm, contrast as ordering signal, weight and size as importance, and the layered relationship between primary, secondary, and tertiary information. Do NOT use for content writing, information architecture, or specific color palette construction. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| writing-humanizerjacob-balslev/skillsUse when writing or editing human-readable prose such as docs, PRs, issues, release notes, errors, UI copy, commits, tooltips, or support replies, especially when text sounds robotic, padded, monotonous, or overly formal. Covers AI-tell removal, active voice, hedging reduction, readability diagnosis, sentence rhythm, vocabulary variety, tone mapping, paragraph rhythm, bullets-vs-prose choice, and the 5-step humanization workflow. Do NOT use for documentation routing/type selection, code-identifier naming, or in-product UI-text pattern catalogs. | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| client-server-boundaryjacob-balslev/skillsUse when reasoning about the line where execution context changes between server runtime and client runtime: what values can cross via the active serializer, what cannot, how `'use client'`, `'use server'`, guard imports, and server-only file conventions mark module/function transitions, how React Server Components differ from server-rendered HTML, why Server Functions / Server Actions are reachable network endpoints, why client input is adversarial, and how server-only modules, secrets, raw records, or closures leak into client bundles and payloads. Do NOT use for choosing when and where UI is produced (use rendering-models), full Server Component read-path placement (use server-components-design), full Server Action mutation/form/cache design (use server-actions-design), public Route Handler endpoint design (use route-handler-design), HTTP wire semantics (use http-semantics), frontend codebase organization (use frontend-architecture), or API JSON contract design (use api-design). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |
| design-system-architecturejacob-balslev/skillsUse when designing or auditing a design system's architecture: token taxonomy, semantic tokens, component APIs, theming, accessibility contracts, documentation, governance, and migration strategy. Do NOT use for information hierarchy and navigation (use `information-architecture`), page-specific layout (use `layout-composition`), visual craft direction (use `visual-design-foundations`), sentence-level UI copy (use `microcopy`), or accessibility-only audits (use `a11y`). | Stars: 2 | Updated | Claude CodeCodex | Unverified | Install |