Explore skills
Showing 28951–28980 of 77104 skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
gentleeduck/duck-mc
Stars: 4Claude CodeCodexGuide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
gentleeduck/duck-mc
Stars: 4Claude CodeCodexVite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.
gentleeduck/duck-mc
Stars: 4Claude CodeCodexgreat_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.
avelikiy/great_cto
Stars: 117Claude CodeCodexAfter a build is delivered, delete its intermediate copies and old versions — keep exactly the version that runs and one previous for rollback — and report the space freed as measured by `df`, never `du`. Covers local build output, mobile build caches, container images, release dirs and stale browser-session copies, with a never-delete list (volumes, databases, installed SDKs, simulator runtimes, the rollback version). Use after any release or image build, before heavy builds when free disk is low, and when disk space drops fast ("диск кончается", "почисти старые сборки", "ENOSPC"). Loaded by release-manager, devops.
avelikiy/great_cto
Stars: 117Claude CodeCodexStructured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.
avelikiy/great_cto
Stars: 117Claude CodeCodexHow to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when starting a new brand surface with no reference, or when authoring a house style you want executed the same way twice.
avelikiy/great_cto
Stars: 117Claude CodeCodexScaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).
avelikiy/great_cto
Stars: 117Claude CodeCodexThe methods a financial-ML result has to survive before it is evidence — purged cross-validation with an embargo, triple-barrier labelling, sample uniqueness under overlapping labels, fractional differentiation, meta-labelling, and multiple-testing correction. Written because the invariants were required of quant-researcher and nothing in the project explained how to satisfy them: a rule without a method produces either an invention or a block. Applied whenever a backtest, a feature or a label is being designed or judged.
avelikiy/great_cto
Stars: 117Claude CodeCodexRisk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
datit309/supergraph
Stars: 23Claude CodeCodexProactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.
datit309/supergraph
Stars: 23Claude CodeCodexAutonomous human-like browser control and professional QA/QC testing. Powered by agent-browser (Rust native CDP, zero Playwright) with ISTQB test matrix generation, automated testcase execution, console/network error tracing, and defect reporting.
datit309/supergraph
Stars: 23Claude CodeCodexDatabase migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
datit309/supergraph
Stars: 23Claude CodeCodexAnti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
datit309/supergraph
Stars: 23Claude CodeCodexStructured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.
datit309/supergraph
Stars: 23Claude CodeCodexDispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.
datit309/supergraph
Stars: 23Claude CodeCodexPlan-aware auto-fix loop after coding. Runs tests, lint, format, and graph checks. Updates plan task status. Use after execute/tdd.
datit309/supergraph
Stars: 23Claude CodeCodexLibrary-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
datit309/supergraph
Stars: 23Claude CodeCodexBuild Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
datit309/supergraph
Stars: 23Claude CodeCodexCompact current session context into a handoff document for seamless continuation in a new session. Use when context window is exhausted, switching machines, handing work to another agent, or ending a long session mid-task.
datit309/supergraph
Stars: 23Claude CodeCodexRun integration and e2e tests after unit tests pass. Use after /supergraph:fix when unit tests are green.
datit309/supergraph
Stars: 23Claude CodeCodexTest mobile apps using connected iOS WebDriverAgent or Android UiAutomator2 backends. Verify MCP availability, device selection and driver readiness before actions; collect snapshots and evidence without claiming unexecuted tests passed.
datit309/supergraph
Stars: 23Claude CodeCodexCreate graph-informed implementation plans before writing code. Use before any non-trivial task. Skip for small changes (≤2 files, <20 lines, no hub/bridge).
datit309/supergraph
Stars: 23Claude CodeCodexConvert current conversation context into a structured Product Requirements Document (PRD) and optionally post it to GitHub Issues. Use before /supergraph:plan when requirements came from a conversation, user story, or feature discussion rather than a formal spec.
datit309/supergraph
Stars: 23Claude CodeCodexBuild throwaway code to validate an uncertain approach before committing to a plan. Two branches — Logic (terminal state machine) or UI (multiple designs on one route with URL-param switcher). No persistence, no tests, single-command start. Use between analyze and plan when the approach itself is uncertain.
datit309/supergraph
Stars: 23Claude CodeCodexPlan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
datit309/supergraph
Stars: 23Claude CodeCodexScan project once per session. Run first — all other skills depend on this.
datit309/supergraph
Stars: 23Claude CodeCodexCreate a Software Design Document (SDD) defining component architecture, data contracts, API schemas, and platform compatibility before planning. Use in Tier 3 (Full Pipeline) or when modifying interfaces, hooks, databases, or multi-platform contracts.
datit309/supergraph
Stars: 23Claude CodeCodexSerena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
datit309/supergraph
Stars: 23Claude CodeCodexStrict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.
datit309/supergraph
Stars: 23Claude CodeCodex