Explore skills
Showing 62611–62640 of 77080 skills
Diagnosing 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).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing browser-facing freshness for live dashboards, notifications, progress views, feeds, and data that can change after initial render. Covers freshness contracts, transport choice among adaptive polling, Server-Sent Events, and bidirectional sockets, webhook-to-UI propagation, client cache invalidation, stale-data indicators, reconnect and catch-up behavior, centralized subscription ownership, and non-disruptive update UX. Do NOT use for low-level stream/backpressure protocol design (use `streaming-architecture`), async event envelope/topic contracts (use `event-contract-design`), recurring schedule design (use `cron-scheduling`), durable worker execution semantics (use `background-jobs`), generic UI action feedback (use `interaction-feedback`), or serialization/trust boundaries (use `client-server-boundary`). Do NOT use for design the backpressure protocol for an HTTP stream. Do NOT use for choose the cron expression for a daily refresh.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing or reviewing React ref usage: refs as mutable handles that survive renders without triggering them, useRef for DOM access and instance values, ref callbacks for mount/unmount hooks, forwardRef and React 19 ref-as-prop, useImperativeHandle for controlled imperative APIs, and ref forwarding through compound-component primitives such as Radix Slot. Use for focus, measurement, animation, third-party DOM integration, and sparse imperative APIs; never as a substitute for reactive state. Do NOT use for the broader hook discipline (use react-hooks-patterns), state ownership decisions (use state-management), component-layering strategy (use component-architecture), Client/Server serialization boundaries (use client-server-boundary), or form validation UX (use form-ux-architecture). Do NOT use for design the Rules of Hooks and dependency-array discipline for useEffect (use hooks-patterns).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing or reviewing Next.js App Router Route Handlers: route.ts file placement, HTTP method exports, Web Request/Response APIs, body parsing, GET caching and opt-outs, dynamic segments, search params, CORS, Edge vs Node runtime choice, streaming responses, status and header discipline, error responses, and webhook endpoint shape. Use when the caller is mobile, third-party, webhook, server-to-server, cross-origin, or otherwise not your own typed UI. Do NOT use for internal UI mutations, broad API design, abstract HTTP semantics, request preprocessing, or full webhook reliability design. Do NOT use for design an internal create-comment form mutation triggered only from this app's UI (use server-actions-design). Do NOT use for read application data inside a Server Component during render (call the data source directly, not a self-fetch to your own Route Handler). Do NOT use for define the REST contract and resource model for a v2 public API (use api-design).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexScenario planning: a strategic-foresight method for making decisions under deep uncertainty by constructing and stress-testing several plausible future worlds. Do NOT use for Scan political, economic, social, technological, environmental, and legal forces for market entry. Do NOT use for We have three options with probabilities and payoffs. Compute expected value and recommend one. Do NOT use for Update our confidence in this forecast after new evidence arrived. Do NOT use for Balance our innovation portfolio across core, adjacent, and transformational bets. Do NOT use for Turn strengths, weaknesses, opportunities, and threats into SO, WO, ST, and WT options. Do NOT use for Answer the five Playing to Win choices for this business. Do NOT use for constructing and using alternative futures from critical uncertainties (use pestel). Do NOT use for deep-uncertainty exploration (use expected-value). Do NOT use for multiple plausible future worlds and strategic robustness (use bayesian-reasoning).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when reasoning about how a database schema changes over time without breaking deployed application code — the multi-release path from current to target schema: the expand/contract pattern (parallel change), zero-downtime change rules, the backwards/forwards compatibility envelope (deploy ordering + rollback), the catalog of schema changes (add/drop/rename column, type change, add constraint/index) and the safe procedure for each, dual-write/dual-read transitions with a named source-of-truth, the lock-acquisition hazard (bounded lock_timeout + retry), cross-engine online-change mechanisms (Postgres CONCURRENTLY/NOT VALID, MySQL Online DDL, gh-ost/pt-osc, Vitess/PlanetScale), view-based multi-version tooling (pgroll, Reshape), and migration-lint enforcement (Strong Migrations, Squawk, Atlas). Do NOT use for executing one migration (use database-migration), schema design from scratch (use data-modeling), query tuning (use query-optimization), or partitioning (use sharding-strategy).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when a decision, intervention, policy, product change, metric target, or system fix needs analysis beyond the immediate effect: ask what happens next, how actors respond, what incentives change, and what delayed or compounding consequences follow. Covers consequence chains, time horizons, stakeholder reactions, feedback loops, second- and third-order effects, and guardrail design. Do NOT use for reversing a goal to find failure paths (use inversion), decomposing assumptions to primitives (use first-principles-thinking), recurring issue clustering (use pattern-recognition), or system leverage-level diagnosis (use meadows-leverage-points when available). Do NOT use for Invert this plan and list how to make it fail. Do NOT use for Break this strategy into irreducible premises. Do NOT use for The same issue appears in many files; cluster the pattern. Do NOT use for Find the highest leverage point in this system.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when you need to explain how parts of a system, feature, concept, page, workflow, or problem connect; identify the single most important part of something; untangle dense dependencies into a core plus typed relations; or answer 'what is the load-bearing part?' without drifting into implementation or task prioritization. Provides a five-step workflow — classify the unit of analysis, find the single primary part using removal/governance/purpose/weight/decision tests, map secondary parts via typed relations (dependency, input/output, parent/child, owner/owned, cause/effect, constraint/enabler, and others), produce a structured output, and reduce the whole to one final sentence — that forces explanation through one-primary reduction rather than flat lists or chronology. Do NOT use for implementation work (use the relevant domain skill), choosing what to do next (use a prioritization skill), or formal architectural-ownership design (use a domain-modeling skill).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexSemantics: choosing and auditing the meaning encoded by names, status codes, versions, commits, tokens, and signals across code, APIs, and UIs. Do NOT use for Should onboarding be hyphenated, and how does English compound morphology affect that decision? Do NOT use for What casing should a new database timestamp column use -- kebab, snake, or camel? Do NOT use for Rename this function and update every call-site across the repo. Do NOT use for Type the relation between refund and payment as IS-A, PART-OF, causal, or thematic. Do NOT use for Design the full REST resource surface with pagination, idempotency keys, and auth boundaries.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexSEO implementation strategy for building pages that rank -- covering content strategy, programmatic SEO at scale, marketplace-specific SEO, and AI search optimization.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing or reviewing React Server Functions / Next.js Server Actions for mutations: the 'use server' directive, function-to-POST endpoint semantics, form integration through action/formAction, React useActionState and useFormStatus, progressive enhancement, server-side validation, authentication, authorization, rate limiting, cache revalidation, redirect/refresh/updateTag behavior, bound arguments, and the security boundary that makes actions public HTTP endpoints despite function-like syntax. Covers Next.js App Router as the canonical implementation. Do NOT use for read-path data fetching with React Server Components (use server-components-design), broader serialization/directive mechanics (use client-server-boundary), externally consumed API contracts (use api-design), or form visual/interaction UX (use form-ux-architecture). Do NOT use for choose between SSR and SSG (use rendering-models). Do NOT use for debug React hook dependency arrays in a client form (use hooks-patterns).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing or reviewing React Server Components: what an RSC can do (async, data fetching, server-only imports) versus what it cannot (state, effects, event handlers, browser APIs), where to draw the server/client boundary in the tree, how to keep private data from leaking across that boundary, and how RSC composes with Suspense to stream content without a separate API layer. Covers Next.js App Router as the canonical implementation, but the discipline is framework-agnostic. Do NOT use for the 'use client' directive mechanics (use client-server-boundary), hook discipline on Client Components (use hooks-patterns), rendering strategy choice (use rendering-models), the server-action mutation surface (use server-actions-design), or the wider Suspense discipline (use suspense-patterns). Do NOT use for add a click handler to an existing component (use hooks-patterns and client-server-boundary). Do NOT use for design the public API for a third-party integration (use api-design).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when diagnosing whether a business has, can build, or is falsely claiming durable strategic power using Hamilton Helmer's Seven Powers: scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, and process power. Covers Power as benefit plus barrier, persistent differential returns, moat-source classification, Power Progression by company phase, false-positive checks, and strategy implications. Do NOT use for industry-structure analysis alone (use porters-five-forces), integrated strategy-cascade formulation (use playing-to-win), generic prioritization, financial valuation, or surface-level SWOT lists. Do NOT use for analyze the attractiveness of this industry using entrants, suppliers, buyers, substitutes, and rivalry. Do NOT use for turn this market-entry plan into a winning aspiration, where to play, how to win, capabilities, and systems. Do NOT use for rank these roadmap items by impact and effort. Do NOT use for make a SWOT table for this company.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing or auditing deterministic health tooling for a skill library: schema/source validation, manifest/protocol parity, relation integrity, routing health, drift/export checks, supply-chain scanning, and eval-verdict evidence honesty. Covers checker ownership, the library-as-database model, release gates, and maintenance workflows after batch skill changes. Do NOT use for authoring one SKILL.md (use `skill-scaffold`), repo conformance audits (use `graph-audit`), generic lint rules (use `lint-overlay`), or reviewing checker code (use `code-review`). Do NOT use for scaffold a new SKILL.md for our team''s deploy procedure. Do NOT use for audit this Skill Graph repo for schema conformance and dangling relation targets. Do NOT use for the manifest sample drifted from the generator — find the mismatch. Do NOT use for improve this prompt''s wording to get better outputs. Do NOT use for review this AI-generated PR for correctness. Do NOT use for review this PR that changes scripts/skill-lint.js.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when creating a new SKILL.md from scratch, restructuring a draft before it becomes a stable skill, or teaching another author the canonical Skill Metadata Protocol frontmatter, body, and audit-state.json sidecar structure. Covers flat schema-conformant frontmatter, the sidecar split, v8 classification, body layout by skill intent, semantic-layer discipline (description vs activation vs Coverage), teaching-layer mechanics (TEMPLATE NOTE blockquotes), native skill-creator handoff, public/private safety, and routing-eval honesty. Do NOT use when modifying an already-written skill (edit it directly), writing general technical documentation, routing an existing request across skills, or fixing malformed library health at scale (use `skill-infrastructure`). Do NOT use for refactor my existing skill to be more concise. Do NOT use for my skill's routing isn't activating — why? Do NOT use for audit my skill library for stale frontmatter. Do NOT use for write a developer guide for the contributor docs.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when reasoning about snapshot testing as a tactical technique: capture-and-compare against a reviewed baseline, data snapshots, DOM snapshots, text/file snapshots, visual snapshots, approval-cycle discipline, snapshot churn, unstable inputs, large unreadable diffs, golden files, characterization tests, and visual regression review with tools such as Jest, Vitest, Playwright screenshots, Storybook/Chromatic, and Percy. Do NOT use for the overall test-level mix (use `testing-strategy`), universal property claims (use `property-based-testing`), test double construction (use `test-doubles-design`), strict test-first workflow design (use `test-driven-development`), or end-to-end user journey design (use `e2e-test-design`). Do NOT use for choose the overall unit integration e2e and performance test mix for this feature. Do NOT use for use property-based testing with fast-check generated arrays to assert sort output is ordered and preserves items.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when starting a non-trivial feature, refactor, or agent implementation that needs a written spec, plan, task breakdown, and verification path before code changes. Covers Spec Kit-style SDD phases, requirements-vs-plan separation, task traceability, review gates, and spec-compliance verification. Do NOT use for one-line edits, README-only fixes, post-implementation code review (use `code-review`), or test-level decisions (use `testing-strategy`).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when building, reviewing, or repairing an STP marketing strategy: segmentation, targeting, and positioning as one linked sequence from market definition to segment profiles, target selection, positioning statement, and marketing-mix implications. Covers consumer, B2B, nonprofit, and product-led contexts; segment bases; segment attractiveness; fit; primary/secondary targets; differentiated versus concentrated targeting; perceptual maps; positioning statements; evidence gaps; and handoff to campaign, product, pricing, channel, or sales work. Do NOT use for standalone product positioning/category design without segmentation and target choice (use positioning), macro-environment scanning (use pestel), industry profit-pressure diagnosis (use porters-five-forces), value-curve redesign/new-demand creation (use blue-ocean-strategy), product-market growth-path selection (use ansoff-matrix), or tactical marketing-mix design alone.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when reasoning about systems that emit a sequence of values over time and consume them incrementally: the producer/stream/consumer/backpressure/termination primitives, the difference between streaming and request-response, the difference between streaming and pub-sub messaging, how WHATWG Streams, Server-Sent Events, HTTP chunked transfer, WebSockets, gRPC streaming, and React Server Component streaming compose, push vs pull backpressure, and the failure modes (slow consumer, abandoned consumer, partial-result correctness). Do NOT use for the message-history protocol between a model and a tool runtime (use tool-call-flow), browser freshness or live dashboard UX transport choice (use real-time-updates), single-response API design (use api-design), durable worker execution and retry semantics (use background-jobs), or event payload/domain-event contracts (use event-contract-design). Do NOT use for design the JSON shape and status codes for a single request-response API payload.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing or reviewing React Suspense usage: where to place Suspense boundaries to control loading granularity, the difference between Suspense for data fetching and Suspense for code splitting, how Suspense interacts with Server Components for streaming HTML, how error boundaries pair with Suspense (and why they must be distinct components), the relationship between Suspense and React's transition APIs (useTransition, startTransition), and the design rules that prevent waterfall fetches, layout shift, and SEO regressions. Covers React 18+ and 19's `use` hook for unwrapping Promises in Client Components. Do NOT use for general React rendering strategy choice (use rendering-models), for the underlying hook primitives (use hooks-patterns), for streaming protocols beyond Suspense (use streaming-architecture), or for Server Component design (use server-components-design).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when turning internal/external situation analysis into strategic options with SWOT and TOWS: strengths, weaknesses, opportunities, threats, evidence quality, SO/WO/ST/WT option generation, and action hypotheses. Covers separating internal from external factors, avoiding unsupported laundry lists, crossing quadrants into strategy options, and naming what evidence or method should follow. Do NOT use for industry profit-pressure diagnosis (use porters-five-forces), durable moat classification (use seven-powers), value-curve redesign (use blue-ocean-strategy), integrated strategy cascades (use playing-to-win), or quantified option comparison (use expected-value). Do NOT use for Analyze supplier power, buyer power, entrants, substitutes, and rivalry. Do NOT use for Classify this company's durable moat source. Do NOT use for Create a strategy canvas and ERRC grid for a new market space. Do NOT use for Turn this strategy into winning aspiration, where to play, how to win, capabilities, and systems.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when auditing a route, defining a route contract, reviewing onboarding or setup flows, diagnosing why a page feels confusing, or when the user asks about top tasks, time-to-value, branching, dead ends, or task complexity. Provides goal-driven UX analysis that turns vague critique into explicit goal -> task -> subtask decomposition and a primary / secondary / supporting hierarchy contract for the first viewport. Do NOT use for control-pattern choice (use `interaction-patterns`), visual craft (use `visual-design-foundations`), responsive layout (use `layout-composition`), or accessibility-only QA (use `a11y`). Do NOT use for review this PR for code quality. Do NOT use for audit this UI for WCAG 2.2 violations. Do NOT use for decide the CSS grid layout for this hero section. Do NOT use for pick the right colors for this status badge. Do NOT use for build the navigation taxonomy for the whole product. Do NOT use for should we use a dropdown or a stepper here.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when balancing an innovation, growth, transformation, or venture portfolio across McKinsey's Three Horizons: Horizon 1 current core businesses, Horizon 2 emerging growth businesses, and Horizon 3 future options. Covers concurrent portfolio balance, resource allocation (the 70-20-10 benchmark and its caveats), evidence maturity, governance and metrics by horizon, metered funding, ring-fenced budgets, transitions from option to emerging business to core, the collapsed-time critique that disruption can now arrive on core timelines, and the risk that short-term core demands or incentives starve future growth. Do NOT use for BCG growth-share portfolio allocation (use bcg-matrix), Ansoff product-market growth path selection (use ansoff-matrix), Blue Ocean value-curve redesign (use blue-ocean-strategy), scenario construction and stress-testing across alternative futures (use scenario-planning), OKR goal-setting (use okrs), or quantified probability-weighted valuation (use expected-value).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when reasoning about the protocol-level cycle by which a language model uses external tools: declaration, request, execution, continuation, model-visible transcript or provider-resumed state, ID pairing, tool-result formatting, vendor encodings (Anthropic Messages, OpenAI Responses and Chat Completions, MCP, Gemini generateContent and Interactions), client tools vs hosted/server tools, strict schemas and grammar-constrained custom tools, streaming arguments, tool search/deferred loading, programmatic tool calling, computer-use/browser-control screenshot-action loops, parallel vs sequential calls, error handling, and the separation between model intent and runtime execution. Do NOT use for deciding when or how many tools to call (use tool-call-strategy), multi-agent architecture (use agent-engineering), prompt wording (use prompt-craft), or eval design for tool-use behavior (use eval-driven-development).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when an agent is making too many tool calls, when context is filling from verbose tool outputs, when the same operation could be a script instead of N individual calls, or when designing a tool-use protocol for a new agent or harness. Covers the three costs of every call (token, latency, context pollution), the script-vs-call decision gate, tool-selection decision trees (file-search vs content-search vs targeted-read vs full-read), call batching and parallelization, redundancy avoidance, the poka-yoke principle, subagent delegation for context protection, and cost-benchmark heuristics by task type. Do NOT use for prompt wording (use `prompt-craft`), broader context stack design across the five layers (use `context-engineering`), runtime tool failures or production debugging (use `debugging`), or behaviour-preserving refactor mechanics (use `refactor`). Do NOT use for improve this prompt's wording to get better outputs. Do NOT use for design what skills get loaded for which prompts.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when reasoning about the I in ACID: the isolation level a database provides between concurrent transactions; the four SQL-standard levels plus practical snapshot/read-versioning modes; the anomalies each level can admit or prevent; the Berenson/Adya critique of label-based isolation; locking, MVCC, row-versioning, SSI, key-range/gap/predicate locks, RCSI, and distributed-SQL serializable/external-consistency defaults; and how to choose isolation per workload by naming the anomalies, invariants, retry contract, and engine-specific behavior. Do NOT use for the broader ACID frame (outside this active skill corpus), distributed-replica consistency or CAP/PACELC choices (use cap-theorem-tradeoffs and replication-patterns), query performance tuning (use query-optimization), durable index design (use indexing-strategy), or schema design (use entity-relationship-modeling). Do NOT use for explain the four ACID properties (outside this active skill corpus).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when reasoning about types as a quality property of code: what guarantees the type system actually provides, the difference between sound and unsound systems, structural vs nominal typing, type narrowing and exhaustiveness, the runtime/compile-time boundary, and where validation must happen because the type system cannot. Covers TypeScript, Flow, Hindley-Milner languages, and gradual typing in general. Do NOT use for runtime input validation library choice (use api-design for API surface validation; use individual library docs for library mechanics), for SQL type mapping (use entity-relationship-modeling), or for type system implementation (compilers — out of scope). Do NOT use for implement HMAC verification for an inbound webhook (use webhook-integration). Do NOT use for design the JSON shape of an API endpoint (use api-design).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when decomposing how an organization, business unit, product, service, platform, or operating model creates value and cost through Porter's Value Chain and adjacent activity-system lenses. Covers primary and support activities, value configurations, virtual information activities, value-system dependencies, activity-level cost and differentiation drivers, linkages, fit, margin, mapping activities, comparing activity configuration to rivals or alternatives, and diagnosing cost or differentiation opportunities. Do NOT use for industry profit-pressure diagnosis (use porters-five-forces), resource/capability advantage testing (use vrio), durable moat classification (use seven-powers), full strategy-cascade design (use playing-to-win), market-boundary reconstruction (use blue-ocean-strategy), portfolio allocation (use bcg-matrix), product-market growth paths (use ansoff-matrix), macro scanning (use pestel), or quantified option valuation (use expected-value).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when designing or maintaining the shape of a repository's git history — choosing a branching model, deciding rebase vs merge, sizing commits, linking commits to tracker tickets, tagging releases, running parallel work across worktrees, and resolving the merge conflicts that arise from any of the above. Covers trunk-based development, short-lived feature branches, atomic commit discipline, linear-history conventions (rebase + squash), release tagging with annotated tags and SemVer, hotfix flows from tags, and worktree lifecycle for parallel agents or contributors. Do NOT use for the words inside the commit message (Conventional Commits format, identifier naming — use `naming-conventions`), for chasing a release-pipeline failure (use `debugging`), or for reviewing a PR's content (use `code-review`). Do NOT use for draft a Conventional Commits message for this change. Do NOT use for the release pipeline failed at the tag-creation step — find out why. Do NOT use for review this PR before we merge it.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexUse when evaluating whether a firm's resources or capabilities can create sustained competitive advantage with VRIO: Valuable, Rare, costly to Imitate, and Organized to capture value. Covers resource/capability inventory, sequential VRIO testing, competitive implication classification, inimitability mechanisms, organization gaps, investment/protection priorities, and handoff to broader strategy methods. Do NOT use for external industry profit-pressure diagnosis (use porters-five-forces), generic internal/external factor inventory (use swot-tows), durable moat-source taxonomy (use seven-powers), portfolio allocation (use bcg-matrix), product-market growth paths (use ansoff-matrix), or quantified option valuation (use expected-value). Do NOT use for Analyze buyer power, supplier power, substitutes, entrants, and rivalry for this industry. Do NOT use for Turn strengths, weaknesses, opportunities, and threats into TOWS strategy options.
jacob-balslev/skill-graph
Stars: 3Claude CodeCodex