#SkillRepo stars
- 1729Unity CLI ContractNice-Wolf-Studio/unity-claude-skillsUse when a unity command fails with exit 2 or "unknown option"; when a subcommand's help prints the root help instead of its own; when the CLI hangs on a pager or a first-run prompt; when a flag documented in the skill does not exist on the installed binary; before parsing or scripting any unity output; when the unity-cli skill is not installed.40
- 1730Unity Game ArchitectureNice-Wolf-Studio/unity-claude-skillsUnity game architecture decision patterns. Service Locator vs Singleton vs DI, Event Bus vs ScriptableObject channels, MonoBehaviour vs plain C#, component composition, manager bootstrap sequences. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.40
- 1731Unity Game LoopNice-Wolf-Studio/unity-claude-skillsUnity game loop and progression design-to-code translation. Core loop scaffolding, session lifecycle, win/lose condition architecture, meta loop hooks, tunable difficulty, pacing & encounter timing. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.40
- 1732Unity Npc BehaviorNice-Wolf-Studio/unity-claude-skillsUnity NPC behavior design-to-code translation. Perception system architecture, decision layer patterns, action execution pipeline, faction & relationship systems, NPC memory & forgetting, crowd & squad coordination. DESIGN INTENT format: INTENT/WRONG/RIGHT/SCAFFOLD/DESIGN HOOK. Based on Unity 6.3 LTS.40
- 1733Unity Save SystemNice-Wolf-Studio/unity-claude-skillsUnity save/load system architecture. Serialization format selection, save data DTOs, versioning and migration, cloud sync, PlayerPrefs scoping, auto-save strategies, mobile persistence. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.40
- 1734Unity State MachinesNice-Wolf-Studio/unity-claude-skillsUnity state and behavior system architecture. FSM, Hierarchical FSM, Behavior Trees, stack-based state machines, Animator-vs-code decisions, state machine testing. DECISION format: WHEN/DECISION/SCAFFOLD/GOTCHA. Based on Unity 6.3 LTS.40
- 1735Backend Patternsjoneqian/claude-skills-suiteBackend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, NestJS, FastAPI, and Next.js API routes.32
- 1736Codexiamneilroberts/claude-skillsDelegate a task or question to the OpenAI Codex CLI running as an isolated subagent, then relay its answer. Use when the user invokes /codex <prompt>, says "ask codex", "have codex look at / do X", or wants a second independent model to investigate a question or make a self-contained edit. Read-only by default; /codex --write lets Codex edit the working tree. Distinct from /codex-review, which is the structured JSON review gate — /codex is a general-purpose Codex delegate.37
- 1737Codex Reviewiamneilroberts/claude-skillsGet a second opinion on the current change or a plan from a different model (Codex), and enforce its verdict mechanically. Codex returns a structured JSON verdict — findings scored by priority (0 critical, 1 important, 2 minor, 3 nit) against sev.schema.json — and a gate script turns that into a pass/fail exit code, so a critical or important finding gets fixed or escalated rather than re-argued by the model that wrote the code. Infra failures (rate limit, model reject, empty output) are their own outcome and never count as a clean pass. Use after writing tests, before a deploy or merge, or to37
- 1738Comment Refactoriamneilroberts/claude-skillsRefactor the comments in AI-generated (or long-lived) code — strip the accumulation of fix-history narration, obsolete explanations, and code-restating noise while preserving load-bearing WHY/TODO/warning comments. Works over a path, glob, or the whole repo; skips dead/abandoned/unused and vendored/generated files; and stamps each cleaned file with a content-hash marker so re-runs skip files that haven't changed. Incorporates the /remove-comments and /deslop (humanizer) heuristics plus a used-code filter and incremental idempotency. Triggers on `/comment-refactor [path|glob]`, "refactor the co37
- 1739Crispiamneilroberts/claude-skillsUse this skill when the user wants shorter, more direct responses. Activate on: "crisp mode", "go crisp", "/crisp", "be brief", "less tokens", "cut the fluff", "shorter answers", "stop being verbose", "drop the filler", "skip the pleasantries", "no fluff", "just the answer". Do NOT activate for: "explain in detail", "walk me through", "full report", or any question answerable correctly in one sentence without the skill.37
- 1740Session Endiamneilroberts/claude-skillsWrap up a coding session — run a right-sized end-of-session self-critique, optionally curator-verify the claims, prepend a SESSION_LOG.md entry, and print a rename + counter summary. Use before you /clear or stop for the day. Triggers on `/session-end`, "end this session", "wrap up and log what we did".37
- 1741Session Startiamneilroberts/claude-skillsBegin a documented coding session — create a per-session log so progress is tracked and later wrap-up (/session-end) has something to append to. Use at the start of a work session. Triggers on `/session-start`, "start a coding session", "begin a session".37
- 1742Wechat Miniprogramjoneqian/claude-skills-suiteWeChat Mini Program development framework. Use for building WeChat mini apps, WXML templates, WXSS styles, WXS scripting, component development, and WeChat API integration.32
- 1743Google Workspace CLIArogyaReddy/alirezarezvani-claude-skillsGoogle Workspace administration via the gws CLI. Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. Run security audits, execute 43 built-in recipes, and use 10 persona bundles. Use for Google Workspace admin, gws CLI setup, Gmail automation, Drive management, or Calendar scheduling.40
- 1744Hard CallArogyaReddy/alirezarezvani-claude-skills/em -hard-call — Framework for Decisions With No Good Options40
- 1745Test Driven Developmentlifangda/claude-pluginsUse when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first43
- 1746Adversarial Reviewrobbyt/claude-skillsHave Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (42
- 1747API Reviewrobbyt/claude-skillsThis skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions", 42
- 1748Codebase Analysisrobbyt/claude-skillsDeep architectural analysis of the current workspace using Google Antigravity (`agy`). Trigger when the user needs an architecture overview ("analyze this codebase with agy", "map dependencies with Google Antigravity"), is onboarding to unfamiliar code, exploring legacy systems, or hunting technical debt. Replaces the deprecated gemini-cli `codebase_investigator` workflow.42
- 1749Codebase Analysisrobbyt/claude-skillsCodebase analysis via the Codex MCP server with a read-only sandbox. Trigger when user needs architecture overview ("analyze this codebase with Codex", "have Codex map dependencies"), onboarding to unfamiliar code, understanding legacy systems, or identifying technical debt.42
- 1750Codebase Analysisrobbyt/claude-skillsDeep architectural analysis using Gemini's codebase_investigator tool. Trigger when user needs architecture overview ("analyze this codebase", "map dependencies"), onboarding to unfamiliar code, understanding legacy systems, or identifying technical debt.42
- 1751Go Style Guiderobbyt/claude-skillsReview Go code for adherence to Go Style Guide. Use when the user requests a code review of completed work, pull requests, or feature branches in Go projects. Focuses on critical bugs, race conditions, and important maintainability issues. Trigger phrases include "review this Go code", "check against style guide", "review my PR", or "review the work done so far".42
- 1752Web Searchrobbyt/claude-skillsReal-time web research using Google Search via Google's Antigravity (`agy`) CLI — the replacement for the deprecated `gemini-cli`. Trigger when user needs current information ("search with agy", "search with Google Antigravity", "find current info about X with agy", "what's the latest on Y"), library/API research, security vulnerability lookups, or comparisons requiring recent data.42
- 1753Architecture Well Architected Commercevtex/skillsApply when scoping, reviewing, or documenting cross-cutting VTEX commerce architecture across storefront, IO, headless, marketplace, payments, or any other VTEX module. Grounds work in the Well-Architected Commerce framework—Technical Foundation (reliability, trust, integrity; security, infrastructure, compliance), Future-proof (innovation, simplicity, efficiency; scalable and adaptable solutions), and Operational Excellence (accuracy, accountability, data-driven improvement; process and customer experience). Routes implementation detail to product tracks (IO caching and paths, Master Data str47
- 1754Headless Bff Architecturevtex/skillsApply when designing or modifying a BFF (Backend-for-Frontend) layer, middleware, or API proxy for a headless VTEX storefront. Covers BFF middleware architecture, public vs private API classification, VtexIdclientAutCookie management, API key protection, and secure request proxying. Use for any headless commerce project that must never expose VTEX_APP_KEY or call private VTEX APIs from the browser.47
- 1755Marketplace Rate Limitingvtex/skillsApply when implementing retry logic, rate limit handling, or resilience patterns in VTEX API integrations. Covers VTEX rate limit headers (X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After), 429 status handling, exponential backoff with jitter, circuit breaker patterns, and request queuing. Use for any VTEX marketplace integration that must gracefully handle API throttling and maintain high availability.47
- 1756Vtex Io App Settingsvtex/skillsApply when defining, validating, or consuming VTEX IO app settings. Covers settingsSchema, app-level configuration boundaries, and how backend or frontend code should depend on settings safely. Use for merchant-configurable behavior, settings forms, or reviewing whether settings belong in app configuration rather than hardcoded logic or custom data entities.47
- 1757Vtex Io Application Performancevtex/skillsApply when improving VTEX IO Node or .NET services for latency, throughput, and resilience: in-process LRU, VBase, stale-while-revalidate, AppSettings loading, request context, parallel client calls, and avoiding duplicate work. Covers application-level performance patterns that complement edge/CDN caching. Use when optimizing backends beyond route-level Cache-Control.47
- 1758Vtex Io Auth Tokens and Contextvtex/skillsApply when choosing which VTEX IO authentication token should back a request from a backend app. Covers `ctx.authToken`, `ctx.storeUserAuthToken`, `ctx.adminUserAuthToken`, `authMethod`, and how requester context should determine the identity used by VTEX clients. Use for deciding which identity talks to VTEX endpoints in storefront-backed requests, Admin actions, or app-level integrations that should avoid hardcoded VTEX credentials.47
- 1759Vtex Io Client Integrationvtex/skillsApply when designing or implementing how a VTEX IO backend app integrates with VTEX services or external APIs through @vtex/api and @vtex/clients. Covers choosing the correct client type, registering clients in IOClients, configuring InstanceOptions, and consuming integrations through ctx.clients. Use for custom client design, VTEX Core Commerce integrations, or reviewing backend code that should use VTEX IO client patterns instead of raw HTTP libraries.47
- 1760Vtex Io Data Access Patternsvtex/skillsApply when deciding where and how a VTEX IO app should store and read data. Covers when to use app settings, configuration apps, Master Data, VBase, VTEX core APIs, or external stores, and how to avoid duplicating sources of truth or abusing configuration stores for operational data. Use for new data flows, caching decisions, refactors, or reviewing suspicious storage and access patterns in VTEX IO apps.47
- 1761Vtex Io Graphql APIvtex/skillsApply when working with GraphQL schema files in graphql/ or implementing resolvers in node/resolvers/ for VTEX IO apps. Covers schema.graphql definitions, @cacheControl and @auth directives, custom type definitions, and resolver registration in the Service class. Use for exposing data through GraphQL queries and mutations with proper cache control and authentication enforcement.47
- 1762Vtex Io Rootpathvtex/skillsApply when building VTEX IO apps that must work correctly in multi-binding stores where bindings use path prefixes (e.g. store.com/us/, store.com/br/). Covers rootPath extraction from x-vtex-root-path header, useRuntime().rootPath in React, URL construction in backends, link generation, asset paths, and API route considerations. Use when the app breaks or produces wrong URLs in cross-border or multi-binding setups.47
- 1763Vtex Io Service Appsvtex/skillsApply when building backend service apps under node/ in a VTEX IO project or configuring service.json routes. Covers the Service class, middleware functions, ctx.clients pattern, JanusClient, ExternalClient, MasterDataClient, and IOClients registration. Use for implementing backend APIs, event handlers, or integrations that must use @vtex/api clients instead of raw HTTP libraries.47
- 1764Vtex Io Service Paths and Cdnvtex/skillsApply when defining service.json routes, choosing public vs segment vs private URL prefixes for VTEX IO services, or setting HTTP cache headers that interact with the VTEX edge and CDN. Covers path patterns, cookie visibility, edge caching behavior, and aligning Cache-Control with data sensitivity. Use for Node or .NET IO backends where request path and response headers determine CDN safety.47
- 1765Vtex Io Service Runtimevtex/skillsApply when designing or implementing the runtime structure of a VTEX IO backend app under node/. Covers the Service entrypoint, typed context and state, service.json runtime configuration, and how routes, events, and GraphQL handlers are registered and executed. Use for structuring backend apps, defining runtime boundaries, or fixing execution-model issues in VTEX IO services.47
- 1766Build MethodSamueleBassoli/hermes-fleet-appsUse when building or designing software. The method.44
- 1767Code Generated VideoSamueleBassoli/hermes-fleet-appsUse when a short teaser is asked for in the ff-tracking style: every pixel and sound from code.44
- 1768Open Source ReleaseSamueleBassoli/hermes-fleet-appsUse when a project may go public. Repo and licence.44
- 1769Acos Metafrankxai/claude-skills-libraryACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.48
- 1770API Documentation0xranx/agentbriefCreate comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.43
- 1771Architecture Review0xranx/agentbriefWhen reviewing code that involves architectural decisions, new modules, data flow changes, or system design. Use when the PR introduces new services, changes API boundaries, modifies database schemas, adds new dependencies, or restructures significant portions of the codebase. Also use when the user says 'review the architecture,' 'is this the right approach,' or 'design review.43
- 1772Brainstorming0xranx/agentbriefDesign-first approach that generates and evaluates multiple alternatives before coding43
- 1773Doubt Driven Developmentfrankxai/claude-skills-libraryCross-examine a non-trivial decision with a fresh, adversarial reviewer before it stands, ideally a different model family. Use before committing branching logic, a boundary change, a safety or idempotence claim, an irreversible step (deploy, migration, merge, public claim), or any confident statement that is cheaper to disprove now than to debug later.48
- 1774Feynman Thinkingfrankxai/claude-skills-libraryExplains a software architecture, algorithm, or control flow in plain language, using a mental model (inputs, transformation, outputs), a text or ASCII flow diagram, and Socratic questions that expose hidden assumptions, then flags needless abstraction. Use when the user asks to explain something simply, "Feynman style", to build a mental model of a system, to explain an architecture to a junior developer, or to challenge a design for over-engineering. Do not use for mechanical edits (renames, typo fixes, formatting, format conversions), boilerplate config, or when the user asks for code only 48
- 1775Hyperframes CLIfrankxai/claude-skills-libraryHyperFrames CLI dev loop — `npx hyperframes` for scaffolding (init), validation (lint, inspect), preview, render, and environment troubleshooting (doctor, browser, info, upgrade). Use when running any of these commands or troubleshooting the HyperFrames build/render environment. For asset preprocessing commands (`tts`, `transcribe`, `remove-background`), invoke the `hyperframes-media` skill instead.48
- 1776Metrics Framework0xranx/agentbriefWhen the user needs to define KPIs, set up a metrics framework, choose what to measure, or says 'what should we track,' 'define our metrics,' 'KPIs,' 'north star metric,' 'how do we measure success,' 'OKRs,' 'dashboard metrics,' or is starting a new product/feature and needs to decide what data matters.43