Architecture & codebase
12,712 rows, by stacks then stars
1,011 of these skill files have been read, by 858 distinct authors, and what they tell an agent counted. What Architecture & codebase authors agree on, and what they forbid
richfrem/agent-plugins-skills/plugins/cli-agents/skills/project-setup Skill
5★ repoInteractive skill to scaffold and optimize configuration files for both Claude Code (.claude/) and Google ADK/Gemini (.agents/) directories. Trigger with "set up project", "scaffold agent config", "setup cli agent settings", or "configure agents for this project".
richfrem/agent-plugins-skills/plugins/dev-utils/skills/hf-init Skill
5★ repoInitialize HuggingFace integration - validates .env variables, tests API connectivity, and ensures the dataset repository structure exists. Use when onboarding a new project to HuggingFace or when credentials change.
richfrem/agent-plugins-skills/plugins/exploration-cycle-plugin/skills/vibe-togaf-architect Skill
5★ repoA system architecture scaffolder designed to synthesize visual discoveries and interactive Q&A responses into comprehensive C4 and TOGAF specs.
richfrem/agent-plugins-skills/plugins/obsidian-wiki-engine/skills/obsidian-canvas-architect Skill
5★ repoProgrammatically create and manipulate Obsidian Canvas (.canvas) files using JSON Canvas Spec 1.0. Enables agents to generate visual flowcharts, architecture diagrams, and planning boards. Use when creating or editing visual canvas files.
richfrem/agent-plugins-skills/plugins/obsidian-wiki-engine/skills/obsidian-init Skill
5★ repoInitialize and onboard a new project repository as an Obsidian Vault. Covers prerequisite installation, vault configuration, exclusion filters, and validation. Use when setting up Obsidian for the first time in a project.
AnmarHani/SwarmVault/skills/swarm-design Skill
5★ repoSystem design phase — architecture, tech-stack options, module boundaries, data model, and ADRs from a validated SRS. Use after requirements are validated, when choosing a tech stack, designing system structure/APIs/data models, or recording an architecture decision.
AnmarHani/SwarmVault/skills/swarm-init Skill
5★ repoStart a new project connected to the SwarmVault — register it, wire platform adapters, offer git init, set vault-as-default. Use when starting a new project, connecting a project to the vault, or when the user asks to set up SwarmVault in a directory.
SkillMedev/skills/skills/api-design Skill
5★ repoDesigns REST API surfaces - resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering - and delivers an endpoint spec a consumer can build against without asking questions. Use when someone asks "how should I name this endpoint", "what status code should this return", "should this be PUT or PATCH", "how do I paginate this list", or is reviewing an API before it ships to external consumers. Do NOT use for planning breaking-change rollouts and deprecation windows - use api-versioning-strategist instead; for GraphQL type and resolver design - use graphql-schema instead; for generating client SDKs from an existing spec - use api-client-generator instead; for designing inbound webhook endpoints - use webhook-receiver-hardener instead.
The same file is in 3 other repositories
SkillMedev/skills/skills/api-versioning-strategist Skill
5★ repoProduces an API version scheme (date-pinned header or URI), a breaking-vs-additive change policy, and a published deprecation/sunset timeline with translation shims. Use when removing or renaming a field or endpoint, tightening validation, cutting a "v2", binding a partner integration to a version, or planning how long an old version lives. Do NOT use when designing the resource shape, URLs, status codes, or pagination of a new endpoint - use REST API Design instead; this skill owns only the version scheme and deprecation path layered on top of that contract.
The same file is in 1 other repository
SkillMedev/skills/skills/characterization-test-writer Skill
5★ repoWrites pinning and characterization tests that lock in the current behavior of untested legacy code - bugs included - before a refactor, so any later behavior change trips an alarm. Use when someone says "I need a safety net before refactoring this", "this module has no tests and I have to change it", "capture what this function does today", or the correct behavior is simply whatever the code does now. Do NOT use for writing tests for new behavior built red-green - use tdd-expert instead; do NOT use to decide which code is worth testing or to rank coverage gaps - use coverage-gap-finder instead; do NOT use to verify existing assertions are strong - use mutation-test-runner instead.
The same file is in 1 other repository
SkillMedev/skills/skills/client-onboarding-system Skill
5★ repoRuns a first-14-days client onboarding procedure - kickoff agenda, asset and access collection checklist, a written communication contract, and the first-quick-win rule of shipping something visible in week one. Use when a freelancer or consultant says "new client just signed, now what", "how do I kick off this engagement", "set up my client onboarding", "the project stalled waiting on client assets", "client keeps Slacking me at 10pm", or "how do I start a retainer on the right foot". Do NOT use for onboarding a new employee into a role - use onboarding-plan-builder instead; for in-product user onboarding copy, use onboarding-copy.
The same file is in 2 other repositories
SkillMedev/skills/skills/contract-test-writer Skill
5★ repoWrites consumer-driven contract tests at service and API boundaries - Pact consumer tests, provider verification, broker publishing, and can-i-deploy gates - so an incompatible change fails a build instead of breaking integrations in production. Use when someone asks "how do I stop the backend breaking my client", "set up Pact between these services", "a renamed field broke a consumer that unit tests passed", or two separately deployed services must stay in sync. Do NOT use for designing a new API contract from scratch or reviewing its design - use api-design instead; do NOT use for end-to-end user-journey tests - use e2e-scenario-author instead; do NOT use for calls inside a single deployable - write a unit test.
The same file is in 1 other repository
SkillMedev/skills/skills/course-outline-architect Skill
5★ repoDesigns a paid online course structure backward from the student transformation - before/after states, one module per milestone, 5-12 minute lessons with one action each, and completion-first sequencing that front-loads quick wins. Use when a creator says "help me outline my course", "how many modules should my course have", "my course feels bloated, what do I cut", or "how do I structure the course so people actually finish". Do NOT use for planning a single lesson in depth - use lesson-plan-builder instead - or for sequencing objectives across multiple courses - use curriculum-mapper instead.
The same file is in 1 other repository
SkillMedev/skills/skills/dead-code-eliminator Skill
5★ repoProves code is unreachable with converging evidence, then removes it and its tests, fixtures, and flags in reversible slices without breaking dynamic callers. Use when deleting suspected dead code, cleaning up after a migration or feature retirement, trimming a bloated module, or before estimating work on unfamiliar code. Do NOT use when you want to survey and rank an area's debt without committing to deletion - use find-tech-debt instead.
The same file is in 1 other repository
SkillMedev/skills/skills/flutter-widget-architect Skill
5★ repoArchitects Flutter widget trees and Riverpod or Bloc state so rebuilds are scoped, build() stays pure, and const widgets skip recomposition. Use when someone asks "why is my Flutter screen janky", "should I use Riverpod or Bloc", "my whole page rebuilds when one field changes", or is building or refactoring Flutter screens, wiring StatelessWidget/StatefulWidget, Consumer, or BlocBuilder. Do NOT use for Android Jetpack Compose UI - use jetpack-compose-builder instead; do NOT use for React Native - use react-native-pro instead.
The same file is in 1 other repository
SkillMedev/skills/skills/graphql-schema Skill
5★ repoDesigns GraphQL schemas and resolvers that scale - domain-modeled types, Relay pagination, DataLoader batching to kill N+1, mutation payloads with typed user errors, and depth/complexity limits that stop abusive queries. Use when someone asks "how should I structure this GraphQL type", "my resolvers are hammering the database", "cursor or offset pagination", "how do I version a GraphQL API", or is designing or reviewing a schema or federation split. Do NOT use for REST or RPC endpoint design - use api-design instead; do NOT use for the underlying table design - use database-schema instead; for hunting existing N+1s in a codebase, use n-plus-one-hunter.
The same file is in 1 other repository
SkillMedev/skills/skills/idempotency-enforcer Skill
5★ repoDesigns client-supplied idempotency keys, deduplication storage, and replay semantics so at-least-once delivery and client retries return the first result instead of double-charging or double-shipping. Use when someone asks "how do I stop duplicate charges on retry", "add an Idempotency-Key header to this endpoint", "the queue redelivered a job and we shipped twice", or before exposing any unsafe POST behind a retrying client or queue. Do NOT use for inbound third-party webhook handlers whose dedup is keyed on a provider event ID - use webhook-receiver-hardener instead and reference this skill only for the storage pattern; do NOT use for designing the client-side retry/backoff policy itself - use rate-limit-handler instead.
The same file is in 1 other repository
SkillMedev/skills/skills/mobile-perf-profiler Skill
5★ repoDiagnoses and fixes mobile jank, dropped frames, slow startup, and growing memory by capturing a trace or heap snapshot on a real device, isolating the single worst cost, fixing it, and re-measuring against the 16ms frame and cold-start budgets. Use when someone says "the app stutters when I scroll", "startup takes forever", "memory keeps climbing after navigating around", or the UI feels laggy on a real device. Do NOT use when the bottleneck is a website or web app (LCP, bundle size, slow endpoint or query) - use web-performance instead; for Compose recomposition fixes pair with jetpack-compose-builder; for Flutter widget architecture use flutter-widget-architect.
The same file is in 1 other repository
SkillMedev/skills/skills/monorepo-expert Skill
5★ repoStructures and scales JavaScript/TypeScript monorepos with Turborepo, Nx, and pnpm workspaces - layout rules, task pipelines, remote caching, and affected-only CI so build times stay flat as the repo grows. Use when someone asks "should we use a monorepo", "how do I set up Turborepo or Nx", "our monorepo CI takes 40 minutes", "how do I share code between apps", or "why is the cache never hitting". Do NOT use for authoring the CI workflow files themselves - use github-actions instead - and do NOT use for deciding microservice boundaries, which is about runtime architecture, not repo layout - use microservices instead.
SkillMedev/skills/skills/onboarding-copy Skill
5★ repoWrites product onboarding microcopy - welcome emails, empty states, tooltips, setup checklists, and success messages - mapped to the activation milestone so new users reach the aha moment with less friction. Use when someone asks "write our welcome email", "what should this empty state say", "improve our onboarding flow copy", or reports drop-off between signup and first value. Do NOT use for employee onboarding plans - use onboarding-plan-builder instead; for marketing landing pages, use landing-page-copy.
SkillMedev/skills/skills/onboarding-plan-builder Skill
5★ repoProduces a 30/60/90-day onboarding plan for a specific role with phased milestones, first-week setup, observable success criteria, and ramp reviews. Use when a new hire has an accepted offer or start date, or when asked to write, draft, or improve a 30/60/90 / ramp / onboarding plan for a role. Do NOT use for the structure of ongoing recurring 1:1s - use 1on1-agenda instead.
The same file is in 1 other repository
SkillMedev/skills/skills/react-native-pro Skill
5★ repoBuilds and ships production React Native apps - architecture, navigation, list and startup performance against explicit budgets, native modules, and EAS release flow. Use when someone asks "why is my FlatList janky", "how do I speed up cold start", "should this be a TurboModule", "how do I set up EAS builds and OTA updates", or wants a React Native feature built to production quality. Do NOT use for Flutter apps - use flutter-widget-architect instead; do NOT use for offline-first sync and conflict resolution - use mobile-offline-sync instead; do NOT use for native-only iOS SwiftUI work - use swift-ui instead; for deep profiling sessions use mobile-perf-profiler.
The same file is in 1 other repository
SkillMedev/skills/skills/remotion-compose Skill
5★ repoTurns a natural-language video brief into a complete, ready-to-preview Remotion composition - extracts duration, scenes, brand colors, aspect ratio, and real copy; plans the frame budget; and writes data-driven React/TypeScript using useCurrentFrame, interpolate, spring, AbsoluteFill, and Sequence, registered in Root.tsx. Use when someone says "build a 20-second product demo video", "animate a feature walkthrough", "write the Remotion code for this marketing clip", or wants a scene-by-scene composition they can scrub in Studio. Do NOT use for rendering, iterating, or batching the finished MP4 - use remotion-render instead - or for installing and scaffolding the project - use remotion-setup instead.
The same file is in 1 other repository
SkillMedev/skills/skills/remotion-render Skill
5★ repoRenders a Remotion composition to MP4 and runs the edit-and-re-render loop - CLI render commands, 1080p/4K/9:16 presets, concurrency tuning, codec selection, batch variants from a JSON data file, and Lambda for cloud rendering. Use when someone says "render this Remotion video", "export the composition to MP4", "the animation is too fast, fix and re-render", "batch render one video per customer", or "move rendering to Lambda". Do NOT use for authoring or restructuring scenes, animations, or components - use remotion-compose instead; do NOT use for project scaffolding and initial setup - use remotion-setup instead. This skill owns everything from a finished composition to a delivered file.
The same file is in 1 other repository
SkillMedev/skills/skills/remotion-setup Skill
5★ repoScaffolds a new Remotion video project wired for Claude Code Agent Skills - Node check, create-video scaffold, skills install, folder conventions, Google Fonts, and a smoke-test render. Use whenever someone wants to start making videos with Remotion and Claude, even just "make product videos with Claude."
The same file is in 1 other repository
SkillMedev/skills/skills/secrets-hygiene Skill
5★ repoGuides detection, emergency rotation, and prevention of leaked secrets and credentials across source code, git history, CI pipelines, logs, and infrastructure config. Use when someone says "I think I committed an API key", "a secret leaked", "scan the repo for credentials", "how should we store secrets", or is setting up secrets management for an application, CI/CD, or Kubernetes. Do NOT use for detecting or redacting personal data like names, emails, or SSNs - use pii-scrubber instead; for routine non-secret environment configuration on Vercel, use vercel-env-management.
The same file is in 1 other repository
SkillMedev/skills/skills/story-structure-architect Skill
5★ repoUse when plotting or outlining a novel or screenplay, structuring its acts/chapters/sequences, fixing a sagging middle or broken pacing, mapping a character arc onto plot beats, planting setups and their payoffs, or deciding scene order. Produces the macro architecture - arc, beat sheet, tension curve - not prose. Do NOT use to write the actual prose of a scene (use Fiction Scene Writer, which sits downstream of this), to establish or mimic a narrative VOICE (use Ghostwriter), or to write a non-fiction book proposal or pitch (use Book Proposal).
The same file is in 1 other repository
SkillMedev/skills/skills/tech-debt-prioritizer Skill
5★ repoInventories tech debt and ranks it economically - scoring each item 1-3 on cost of delay (the interest rate) and leverage (the principal unblocked), multiplying into a priority index, and packaging the winners into a leadership proposal framed on business impact. Use when someone asks "which tech debt should we tackle first", "help me build a case for refactoring to leadership", "our backlog of debt is huge, where do we start", or is preparing quarterly planning. Do NOT use for finding and removing unused code - use dead-code-eliminator instead - for auditing third-party dependency risk - use dependency-risk-audit - or for planning the sprint the work lands in - use sprint-planning instead.
The same file is in 1 other repository
SkillMedev/skills/skills/technical-spec Skill
5★ repoWrites engineering design docs and RFCs that align a team before code - TL;DR, background, goals and explicit non-goals, quantified requirements, a concrete end-to-end design with failure modes, alternatives considered, rollout plan, and open questions surfaced at the top for reviewers. Use when an engineer asks "write a design doc for this feature", "turn my approach into an RFC", "reviewers keep asking why didn't you just X", or a project needs alignment before implementation. Do NOT use for designing the API contract itself - use api-design instead; for user-facing product documentation, use help-documentation.
The same file is in 1 other repository
Sudhakaran88/solopreneur-skills/skills/onboarding-cro Skill
5★ repoWhen the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also trigger on "onboarding flow", "activation rate", "user activation", "first-run experience", "empty states", "onboarding checklist", "aha moment", "new user experience", "onboarding sequence", "product walkthrough". For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
Sudhakaran88/solopreneur-skills/skills/site-architecture Skill
5★ repoWhen the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also trigger on "sitemap", "site structure", "page hierarchy", "information architecture", "IA", "navigation design", "URL structure", "breadcrumbs", "internal linking strategy", "website planning". NOT for XML sitemaps (see seo-audit). For SEO audits, see seo-audit.
zapgun-ai/clawback/.skills/verify-config Skill
no license5★ repoConfig doctor for clawback — loads the merged config (DEFAULTS < global < ./CLAWBACK.md < CLI overrides) exactly as the proxy's loadConfig does, prints a secret-free summary of the resolved values plus the merge-order sources, and exits non-zero if the canonical CLAWBACK.md did NOT take effect (host not 0.0.0.0, tls off, or adminToken missing) so a bad parse fails loudly instead of silently falling back to loopback defaults. Read-only; never prints the adminToken value, only its length. Use to confirm a CLAWBACK.md edit actually parsed and merged before starting the proxy, or to debug which config layer won.
zapgun-ai/clawback/.skills/write-config Skill
no license5★ repoGenerate or refresh the canonical CLAWBACK.md config. The front matter is built from the live DEFAULTS export in src/config.js (so it can never drift as options are added), with the only forced deviations being the two a LAN-reachable bind needs — host=0.0.0.0 and tls=true. adminToken is left as a null placeholder for you to set (it no longer mints one); a real existing token, or an explicit CLAWBACK_CANONICAL_TOKEN, is PRESERVED, and a token's value is NEVER printed (only presence and length). With no args it writes BOTH ./CLAWBACK.md and the global ~/.config/clawback/CLAWBACK.md. Use to (re)create a canonical config, or after adding an option or changing a default.
HsuanYuLee/polaris/.claude/skills/codex-mcp-setup Skill
5★ repoUse when the user wants to set up or sync Codex MCP servers for Polaris workflows. Trigger: 'codex mcp', '同步 mcp', '設定 codex mcp', '讓 codex 接 mcp', 'codex mcp setup'.
HsuanYuLee/polaris/.claude/skills/onboard Skill
5★ repoUse when the user wants to onboard a company workspace from scratch, add a company, or rerun workspace setup. Primary trigger: 'onboard'. Deprecated aliases: 'init', '/init', 'initialize', 'setup workspace', '初始化'.
shortcuts/radin/skills/radin-setup-hooks Skill
5★ repoWire up per-repo hooks/MCP config for radin's companion tools (code-review-graph). Use for "set up hooks", "wire up code-review-graph", "enable the knowledge graph here", or right after install.sh in a new project.
ramboz/jig/hosts/claude/skills/contracts Skill
5★ repoTeam baseline for external-interface contract artifacts: OpenAPI, JSON Schema, AsyncAPI, .proto, and GraphQL SDL, with spectral, ajv, buf, and graphql-inspector validation. Nudges devs toward contract-first artifacts; never writes them and never scaffolds a contracts/ directory. Auto-triggers for what contract should I use for this API, do we have an OpenAPI spec, add a JSON schema for this, recommend a schema for this endpoint, validate this API contract, or what's the right artifact for events. Defers to any other installed skill whose description identifies it as handling external-interface contract artifacts, API schema design, or contract-first workflow. Do not use for internal module-boundary refactoring, scaffolding a contracts/ directory, or auto-generating schemas from code.
ramboz/jig/hosts/claude/skills/migrate Skill
5★ repoInventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.
ramboz/jig/hosts/claude/skills/scaffold-init Skill
5★ repoInitialize an AI-native development workspace with spec-driven workflow infrastructure. Use when starting a new project, setting up Claude Code on a codebase for the first time, or when the user says scaffold, initialize, set up AI workflow, onboard this repo, or similar. Do not use for adding an individual skill or config to an already- scaffolded project — that is handled by the relevant tier skill directly.
ramboz/jig/hosts/claude/skills/vision-elicitation Skill
5★ repoLightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).
ramboz/jig/hosts/codex/plugins/jig/skills/contracts Skill
5★ repoTeam baseline for external-interface contract artifacts: OpenAPI, JSON Schema, AsyncAPI, .proto, and GraphQL SDL, with spectral, ajv, buf, and graphql-inspector validation. Nudges devs toward contract-first artifacts; never writes them and never scaffolds a contracts/ directory. Auto-triggers for what contract should I use for this API, do we have an OpenAPI spec, add a JSON schema for this, recommend a schema for this endpoint, validate this API contract, or what's the right artifact for events. Defers to any other installed skill whose description identifies it as handling external-interface contract artifacts, API schema design, or contract-first workflow. Do not use for internal module-boundary refactoring, scaffolding a contracts/ directory, or auto-generating schemas from code.
ramboz/jig/hosts/codex/plugins/jig/skills/migrate Skill
5★ repoInventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.
ramboz/jig/hosts/codex/plugins/jig/skills/scaffold-init Skill
5★ repoInitialize an AI-native development workspace with spec-driven workflow infrastructure. Use when starting a new project, setting up Codex on a codebase for the first time, or when the user says scaffold, initialize, set up AI workflow, onboard this repo, or similar. Do not use for adding an individual skill or config to an already- scaffolded project — that is handled by the relevant tier skill directly.
ramboz/jig/hosts/codex/plugins/jig/skills/vision-elicitation Skill
5★ repoLightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).
ramboz/jig/skills/contracts Skill
5★ repoTeam baseline for external-interface contract artifacts: OpenAPI, JSON Schema, AsyncAPI, .proto, and GraphQL SDL, with spectral, ajv, buf, and graphql-inspector validation. Nudges devs toward contract-first artifacts; never writes them and never scaffolds a contracts/ directory. Auto-triggers for what contract should I use for this API, do we have an OpenAPI spec, add a JSON schema for this, recommend a schema for this endpoint, validate this API contract, or what's the right artifact for events. Defers to any other installed skill whose description identifies it as handling external-interface contract artifacts, API schema design, or contract-first workflow. Do not use for internal module-boundary refactoring, scaffolding a contracts/ directory, or auto-generating schemas from code.
ramboz/jig/skills/migrate Skill
5★ repoInventory an existing spec-driven project and apply bounded migrations to jig defaults: `report`, `adopt-layout`, `rename-decisions`, `split-slices`, slice-to-spec, `seed-decisions`, and `copy-machinery`. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init refused — what now; introduce jig to an existing codebase; apply ADR-0004 to my project; migrate flat slices into nested specs; seed the lightweight-decisions home; or copy jig's machinery into my project. Reports are read-only; mutations support dry runs where available, refuse conflicts before writing, and preserve originals in the agentic slice-to-spec workflow.
ramboz/jig/skills/scaffold-init Skill
5★ repoInitialize an AI-native development workspace with spec-driven workflow infrastructure. Use when starting a new project, setting up Claude Code on a codebase for the first time, or when the user says scaffold, initialize, set up AI workflow, onboard this repo, or similar. Do not use for adding an individual skill or config to an already- scaffolded project — that is handled by the relevant tier skill directly.
ramboz/jig/skills/vision-elicitation Skill
5★ repoLightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).
zeikar/hyperclaude/skills/hyper-setup Skill
5★ repoDiagnose hyperclaude prerequisites and report fixes
Transformers config tokenizers expert
air-gapped/skills/.claude/skills/transformers-config-tokenizers-expert Skill
5★ repoPreflight reference for HuggingFace snapshots — what vLLM, sglang, and transformers.generate see at runtime. Covers config-file precedence (tokenizer.json, tokenizer_config.json, generation_config.json, chat_template.jinja), transformers v5 tokenizer-class taxonomy (TokenizersBackend, PythonBackend, MistralCommonBackend, TikTokenTokenizer), special-token discovery (all_special_ids, added_tokens_decoder, extra_special_tokens, backend_tokenizer.get_added_tokens_decoder), chat-template Jinja contract (ImmutableSandboxedEnvironment, loopcontrols, raise_exception, strftime_now, tojson, add_generation_prompt), and engine knobs (skip_special_tokens, trust_request_chat_template, chat_template_kwargs allowlist, adjust_request, incremental detokenizer, EOS merge). Ships verified 2026 hall-of-shame for Kimi-K2.6, GLM-5.1, Gemma-4, Qwen3, DeepSeek-V3, plus drop-in Python for resolving markers to IDs, detecting turn-primer-as-EOS leaks, and cross-referencing tokenizer.json vs tokenizer_config.json.
air-gapped/skills/.claude/skills/ubuntu-autoinstall Skill
5★ repoAuthor, validate, and debug Ubuntu Server autoinstall configuration (the Subiquity installer's `autoinstall:` schema, version 1) for Ubuntu Server LTS 24.04 and 26.04, focused on unattended on-premise and air-gapped installs — identity, storage (LVM/direct/ZFS/encryption/RAID), apt mirror-selection + proxy + offline fallback, ssh, packages, kernel, late-commands/early-commands, and zero-touch delivery via a NoCloud seed. The `network:` block is netplan v2 (use the ubuntu-netplan skill); the `user-data:` block is cloud-config for the installed system (use the ubuntu-cloud-init skill).
air-gapped/skills/.claude/skills/ubuntu-cloud-init Skill
5★ repoAuthor, validate, and debug cloud-init configuration for Ubuntu Server LTS 24.04 and 26.04, focused on on-premise and air-gapped hosts via the NoCloud datasource — `#cloud-config` user-data, the cloud-config modules (users, ssh, write_files, runcmd, apt with local mirrors, ca_certs for internal CAs, ntp, disk_setup), NoCloud seeding (seed dir, `cidata` ISO, `ds=nocloud;s=...` kernel cmdline, SMBIOS serial), boot stages, and pinning `datasource_list`. Public-cloud datasources (EC2/Azure/GCE…) are pointers only. For the `network:` block use the ubuntu-netplan skill; for the installer schema use the ubuntu-autoinstall skill.
air-gapped/skills/.claude/skills/ubuntu-netplan Skill
5★ repoAuthor, validate, and debug netplan network configuration (`/etc/netplan/*.yaml`) for Ubuntu Server LTS 24.04 and 26.04, focused on on-premise and air-gapped hosts — static addressing, bonds, bridges, VLANs, VRFs, routing/policy-routing, DNS, interface matching/renaming, and the systemd-networkd renderer (NetworkManager and desktop covered briefly). Also the shared `network:` substrate for the ubuntu-autoinstall and ubuntu-cloud-init skills, which both use netplan v2.
air-gapped/skills/.claude/skills/vllm-configuration Skill
5★ repoConfigure vLLM completely — YAML config file format, CLI arg precedence, full VLLM_*/HF_*/TRANSFORMERS_* env-var catalog, end-to-end recipe for air-gapped environments (internal HF mirrors, hf-mirror.com, ModelScope, HF_HUB_OFFLINE with pre-seeded cache, gated models offline, trust_remote_code supply-chain implications). VLLM_HOST_IP vs API-host confusion, Kubernetes-service-named-`vllm` env-var poisoning, usage-stats triple opt-out, YAML precedence surprises.
PANGKAIFENG/ai-product-manager-skills/prd-architect Skill
5★ repoPRD 架构师 / 需求文档起草:当用户要把一个产品想法、需求草稿、脑暴结果或功能说明整理成 PRD 时使用。 可用中文唤起:“帮我写 PRD”“帮我选 PRD 模板”“把这个需求整理成 PRD”“判断该用轻量 PRD 还是标准 PRD” “补一张可编辑 Draw.io 核心流程图”“PRD 里加架构图”。 会在 PRD-lite、PRD-standard、PRD-ai-native 中选择一个模板资产按需加载,并在需要时加载 mockup handoff、 Draw.io 图示或开发 handoff 附录;页面型 PRD 默认联动生成项目 UI 对齐的 HTML、关键截图和正文证据。 不用于直接编码、单纯画 UI,或评审一份已经写好的 PRD。
mr-kelly/skills/skills/kelly-agent-builder Skill
5★ repoBusabase-backed App-in-Skill low-code agent configuration and governance console for a platform team. Use when the user invokes $kelly-agent-builder or /kelly-agent-builder, wants to review or edit a catalog of mock LLM agent configs, check quota usage, find configs that need attention, move a draft to live, pause a live agent, or archive an agent. Mock config/governance console only — it never provisions or calls any real agent.
fabioc-aloha/Alex_Skill_Mall/plugins/ai-agents/multi-agent-architect Skill
5★ repoDesign and optimize production-grade multi-agent systems with LangGraph, LangChain, and DeepAgents for complex AI workflows.
The same file is in 4 other repositories
fabioc-aloha/Alex_Skill_Mall/plugins/ai-agents/rag-architecture Skill
5★ repo284 curated plugins for AI assistants across 16 categories: security, Azure, documentation, code quality, cloud infrastructure, and more. Works with GitHub Copilot. Drop into .github/skills/local/ and go.
fabioc-aloha/Alex_Skill_Mall/plugins/architecture-patterns/api-design Skill
5★ repoDesign APIs that developers love to use.
fabioc-aloha/Alex_Skill_Mall/plugins/architecture-patterns/architecture-audit Skill
5★ repoComprehensive project consistency review across code, documentation, diagrams, and configuration