Explore skills
Showing 23401–23430 of 77104 skills
Writes a competitor brief or sales battlecard: positioning, recent moves, SWOT, and how to win, with every claim sourced. Use whenever someone asks about a competitor, how two products compare, or for talking points against a rival, even with no web access and only a pasted page or notes to go on.
marcosmodly/marketing-skill
Stars: 144Claude CodeCodexUse when building a new module in apps/marketplace-api from its business-architecture plan, or when checking one just built against what this repo actually requires - which document answers which question, the order the work has to happen in (plan, schema, migration, model, DTOs, service, controller, IAM, seed, tests, README, SDK), and the traps that have already cost a rebuild here. Part 4 (IAM) is the part people forget. Every rule in it came from something that went wrong on this codebase, and it says so where that is true.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
gentleeduck/duck-iam
Stars: 9Claude 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.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexSet up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexMigrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexCreate exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexConfigure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexMove issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexBundle TypeScript and JavaScript libraries with blazing-fast speed powered by Rolldown. Use when building libraries, generating type declarations, bundling for multiple formats, or migrating from tsup.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexTurborepo 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.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexMaster TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexReact composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
gentleeduck/duck-iam
Stars: 9Claude CodeCodexReact 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-iam
Stars: 9Claude 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-iam
Stars: 9Claude 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-iam
Stars: 9Claude CodeCodexLook up the private sample code for a color using the bundled lookup script. Use only for sample-code lookup requests, not arithmetic.
NVIDIA/SkillEvaluator
Stars: 3.3kClaude CodeCodexOne-command multilingual blog creation. Writes a blog post, translates it into user-specified languages, applies cultural adaptation, and emits hreflang tags, sitemap entries, and a CMS-ready language map. The complete write-to-publish pipeline for international content. Orchestrates blog-write, blog-translate, blog-localize, and (optionally) seo-hreflang. Use when user says "multilingual blog", "blog multilingual", "write in multiple languages", "international blog", "mehrsprachiger Blog", "blog multilingue", "blog multilingue", "create blog in German and French".
AgriciDaniel/claude-blog
Stars: 2.7kClaude CodeCodexDrive the codex CLI (GPT-6 astra) as a delegate — debugging, test writing, scoped implementation. Not for reviews, which go to Opus subagents. Read BEFORE invoking codex.
clice-io/kotatsu
Stars: 31Claude CodeCodexkotatsu C++ coding conventions — redundancy elimination (the rule we care most about), file organization, macro.h isolation, dual-mode exception policy, template deduction and type-trait rules, naming, modern C++ preferences. Read BEFORE writing or modifying any C++ code.
clice-io/kotatsu
Stars: 31Claude CodeCodexPull unresolved review threads of the current PR, apply the fixes in the worktree, resolve the threads, and return a compact summary. Runs inline; the digest script keeps the bot boilerplate out of the conversation.
clice-io/kotatsu
Stars: 31Claude CodeCodexRun kotatsu test suites. Optional args = suite (ctest | integration | all, default all) and cmake preset for the ctest suites (default `debug`). Runs in a forked context — test output stays out of the main conversation; only a digest returns.
clice-io/kotatsu
Stars: 31Claude CodeCodexHow kotatsu's tests are organized and written — levels (unit, system, integration), the module-first layout, dependency and trust rules, naming, zest checks, determinism. Read BEFORE writing, moving or reviewing any test.
clice-io/kotatsu
Stars: 31Claude CodeCodexUse liter-llm mcp reference documentation.
xberg-io/liter-llm
Stars: 266Claude CodeCodexUse liter-llm mcp reference documentation.
xberg-io/liter-llm
Stars: 266Claude CodeCodexUse liter-llm mcp reference documentation.
xberg-io/liter-llm
Stars: 266Claude CodeCodexCreate structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users should be able to X, Y, Z"), vague-noun patterns ("a system for", "a way to", "an app that", "functionality for"), and explicit build verbs ("build", "create", "add a feature", "help me implement", "I need to build"). Do NOT use this for "implement the plan" or "run the plan" - those should use plan-orchestrate instead. Skip for quick bug fixes, single-line changes, questions, or documentation.
markshust/hcf
Stars: 84Claude CodeCodexExecute implementation plans with parallel TDD workers. Use when ready to run, execute, or start a plan. Triggers on "run the plan", "execute the plan", "implement the plan", "start the plan", "start implementation", "orchestrate", "begin autonomous execution". Requires a plan created by plan-create.
markshust/hcf
Stars: 84Claude CodeCodex