All categories
Business & Operations
Operations, strategy, finance, sales, support, management, and planning
- 35,221
- 1,468
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 business & operations skills
Showing 15,457–15,480 of 35,221 skills
- Gof Strategy Pattern> Encapsulate interchangeable algorithms behind a common interface for runtime selection.Votes: 0GitHub stars: 20
- Gof Singleton> Ensure a class has exactly one instance using module-level singletons and WeakRef patterns.Votes: 0GitHub stars: 20
- Gof Command Pattern> Encapsulate operations as command objects to support undo, redo, and command queuing.Votes: 0GitHub stars: 20
- Gof Builder Pattern> Construct complex objects step-by-step using fluent builders and director classes.Votes: 0GitHub stars: 20
- Fleet Command> Conductor for the `-fleet` family — one tier above the members, coordinating the fleets themselves rather than fanning out over an item-queue. It derives the run as a hybrid DAG whose wave boundaries come from a dependency edge **or** an evidence-fidelity exclusivity requirement — either one alone sufficient — instead of accepting a hand-picked order, enforces **one global** leaf-slot budget across every fleet in flight rather than the sum of their per-fleet governors, deconflicts the lanes...Votes: 0GitHub stars: 20
- Events Websocket Pattern> Implement bidirectional real-time communication using WebSocket protocol and Socket.io.Votes: 0GitHub stars: 20
- Events Saga Choreography> Coordinate distributed workflows through event chains and compensation events without an orchestrator.Votes: 0GitHub stars: 20
- Events Message Queue> Use message queues for reliable async delivery with competing consumers and dead letter queues.Votes: 0GitHub stars: 20
- Events Kafka Patterns> Produce and consume Kafka messages with partitioning, consumer groups, and offset management.Votes: 0GitHub stars: 20
- Events Idempotency> Handle duplicate message delivery safely using idempotency keys and deduplication stores.Votes: 0GitHub stars: 20
- Design Information Architecture> Structuring information — card sorting, tree testing, mental models, labeling systems, organization schemes, findabilityVotes: 0GitHub stars: 20
- Design Design Audit> Evaluating existing design — heuristic evaluation (Nielsen's 10), consistency inventory, accessibility audit, competitive analysis, identifying and quantifying design debtVotes: 0GitHub stars: 20
- Design Content Density> Information density as a deliberate design variable — compact, comfortable, and spacious modes, matching density to user context, and the tradeoff between showing more and showing clearlyVotes: 0GitHub stars: 20
- Db Eventual Consistency> If no new updates are made, all replicas will eventually converge to the same value -- a consistency model that trades immediate agreement for higher availability and lower latency.Votes: 0GitHub stars: 20
- Db Connection Sizing> Tuning max_connections, understanding per-connection memory overhead, and right-sizing database connections for on-premise and serverless environments.Votes: 0GitHub stars: 20
- Db Btree Index> The default index type in PostgreSQL and MySQL, B-tree indexes support equality and range queries on ordered data with O(log n) lookup performance.Votes: 0GitHub stars: 20
- Db Adjacency List> The simplest hierarchical model where each row stores a reference to its parent, traversed with recursive CTEs for subtree and ancestor queries.Votes: 0GitHub stars: 20
- Craft Fleet> Ceiling-raising code-quality elevation sweep across the standing codebase — compose the eleven `-craft` skills into ranked `(scope, domain)` targets, confirm one batch in a single up-front round that carries a **taste-calibration sample of verbatim findings**, fan out worktree-isolated subagents that each run the **real** `harness-refactoring` pipeline over one target's cited findings, admit nothing that lacks a cited craft finding and that a re-critique cannot show as **net better**, and h...Votes: 0GitHub stars: 20
- Cli Ergonomics Craft> LLM-judgment critique of command-line ergonomics quality — the ceiling counterpart to mechanical CLI checks. The direct structural twin of harness-docs-craft, but with no rule-based floor twin: a mechanical linter can confirm a flag is documented, but only judgment can tell whether the name is predictable, whether the help teaches, and whether the error says what to do next. Emits 3-axis findings (tier × impact × confidence per ADR 0019).Votes: 0GitHub stars: 20
- Burn Hud> Install, calibrate, verify and diagnose a local usage-pace HUD — an always-visible statusline plus reminder hooks that show weekly burn, flag when a session's context has stopped paying for itself, and refuse to report a comfortable green they have not earned.Votes: 0GitHub stars: 20
- Api Webhook Design> WEBHOOKS ARE A PUSH-BASED CONTRACT — REGISTRATION, PAYLOAD SCHEMA, DELIVERY GUARANTEES, AND RETRY POLICIES ARE ALL CONSUMER-FACING COMMITMENTS THAT DETERMINE WHETHER INTEGRATIONS REMAIN RELIABLE UNDER PARTIAL FAILURES, AND DESIGNING THESE PROPERTIES EXPLICITLY UPFRONT PREVENTS AN AD-HOC SYSTEM THAT FAILS SILENTLY AT THE WORST POSSIBLE MOMENT.Votes: 0GitHub stars: 20
- Api Versioning Url> URL PATH VERSIONING EMBEDS THE API VERSION DIRECTLY IN THE URI (/v1/, /v2/) — IT TRADES CLEAN URI SEMANTICS FOR MAXIMUM VISIBILITY AND CACHEABILITY, MAKING IT THE DEFAULT CHOICE FOR PUBLIC APIs WHERE DEVELOPER EXPERIENCE AND REVERSE-PROXY ROUTING SIMPLICITY OUTWEIGH STRICT REST PURITY.Votes: 0GitHub stars: 20
- Api Validation Errors> FIELD-LEVEL VALIDATION ERROR DESIGN — RETURNING ALL VALIDATION FAILURES IN A SINGLE RESPONSE WITH JSON POINTER PATHS AND PER-FIELD MESSAGES ELIMINATES THE ONE-ERROR-AT-A-TIME DEBUGGING LOOP AND GIVES CLIENTS ENOUGH INFORMATION TO HIGHLIGHT EVERY INVALID FIELD WITHOUT A SECOND REQUEST.Votes: 0GitHub stars: 20
- Api Status Codes> HTTP STATUS CODES ARE THE RESPONSE CONTRACT BETWEEN SERVER AND CLIENT — CORRECT CODE SELECTION ENABLES ERROR HANDLING, RETRY LOGIC, AND MONITORING WITHOUT PARSING RESPONSE BODIES. MISUSING STATUS CODES FORCES CLIENTS TO TREAT 200 OK AS AN AMBIGUOUS SIGNAL THAT MUST BE INSPECTED FOR HIDDEN FAILURES.Votes: 0GitHub stars: 20