agentsclimarketplace

Architecture & codebase

12,711 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

  • Nfs scaffold app

    juncoding/nextjs-fullstack-starter/skills/nfs-scaffold-app Skill

    0★ repo

    Scaffold a brand-new fullstack back-office app on pure Next.js (App Router) — Server Components for reads, Server Actions for writes, services in src/server/modules/. Use this whenever the user wants to start a new internal tool, admin dashboard, back-office app, line-of-business system, lightweight ERP, or CRUD app on Next.js without a separate API service — even if they don't name the stack. Walks the user through an interactive Q&A (project name, location, database, auth, cache, MCP, deployment target), then generates the canonical folder structure, dependencies, sample Server Action, sample service, Prisma schema starter, .env.example, and CLAUDE.md. Always trigger when the user wants a Next.js fullstack starter without tRPC, when they describe building a back office with Server Components, or when they say 'one Next.js app does everything'.

  • Socratic product

    Kimotep/skills/socratic-product Skill

    0★ repo

    Use this skill when a user wants to design an agentic system before writing any code. Triggers include: "help me plan an AI workflow", "I want to build an agent system", "help me structure my agentic project", "I have an idea for an AI tool", or any request to think through multi-agent logic, file scaffolding, or system design for an LLM-powered project. This skill runs a structured, time-boxed Socratic interview (target: 30 minutes) using multiple-choice UI for every question, and produces a linked set of MD documents plus a harness-specific root config file ready to drop into the repo — including a starter repo structure tailored to the project's type and stack, agent specs written to a defined quality standard (responsibilities, I/O contracts, tool scope, and failure handling), and a root config file for Claude Code, Cursor, Windsurf, OpenCode, or other AI coding tools.

  • Setup launchd

    yukihirop/nagi/.claude/skills/setup-launchd Skill

    0★ repo

    Set up nagi as a macOS launchd service for persistent background operation. Triggers on "setup launchd", "run as service", "background service", "auto start", "launchd".

  • Setup opencode

    yukihirop/nagi/.claude/skills/setup-opencode Skill

    0★ repo

    Set up Open Code agent as an alternative to Claude Code. Supports OpenRouter, Gemini, and OpenAI providers. Triggers on "setup opencode", "setup open code", "use opencode", "switch to opencode".

  • Setup

    yukihirop/nagi/.claude/skills/setup Skill

    0★ repo

    Run initial Nagi setup. Use when user wants to install dependencies, configure channels, register groups, or start services. Triggers on "setup", "install", "configure nagi", or first-time setup requests.

  • Adr drafter

    marzun9620/agent_skills/dev-process/skills/adr-drafter Skill

    no license0★ repo

    A skill for interactively creating Architecture Decision Records (ADRs). Act as a world-class software architect, facilitating collaborative discussions with the user to explore technology choices and design decisions, then generate ADR documents. Use this skill whenever the user brings up topics like "ADR", "technology selection", "design decision", "architecture decision", "I'm torn between X and Y", "which technology should I use", or "I want to discuss whether this design is right". Also handles updating and deprecating existing ADRs.

  • Improve codebase architecture

    marzun9620/agent_skills/dev-process/skills/improve-codebase-architecture Skill

    no license0★ repo

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

    The same file is in 10 other repositories

  • Effect ts configuration

    marzun9620/agent_skills/effect-ts/skills/effect-ts-configuration Skill

    no license0★ repo

    This skill should be used when the user asks about "Effect Config", "environment variables", "configuration management", "Config.string", "Config.number", "ConfigProvider", "Config.nested", "Config.withDefault", "Config.redacted", "sensitive values", "config validation", "loading config from JSON", "config schema", or needs to understand how Effect handles application configuration.

  • Setup matt pocock skills

    marzun9620/agent_skills/meta/skills/setup-matt-pocock-skills Skill

    no license0★ repo

    Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

    The same file is in 15 other repositories

  • Hv config

    l4ci/hv-skills/hv-config Skill

    0★ repo

    Change hv-skills configuration interactively — pick which settings to edit from a checklist showing current values, then choose new values from the same options used at init. Also supports positional shortcuts: `/hv-config <key>` jumps to the value picker, `/hv-config <key>=<value>` applies directly. Use on "change config", "switch to worktree mode", "turn on autonomy", "edit settings".

  • Hv init

    l4ci/hv-skills/hv-init Skill

    0★ repo

    Initialize the .hv/ folder structure with BACKLOG.md, KNOWLEDGE.md, counters.json, config.json, status.json, and CLI helpers. Also seeds a managed knowledge-index block in CLAUDE.md so future /hv-work runs can consult learnings. Called automatically by other hv: skills when the folder doesn't exist, or manually to set up a new project.

  • Hv migrate

    l4ci/hv-skills/hv-migrate Skill

    0★ repo

    One-shot codemod for v3 → v4 upgrades. Versioned arg required — `/hv-migrate v4`. Rewrites references to 8 commands cut by M01 (across BACKLOG, plans, designs, handoffs, qa, milestones, KNOWLEDGE, DECISIONS, project CLAUDE.md), migrates `.hv/CONTEXT.md` terms into `.hv/KNOWLEDGE.md` (## Glossary) via `hv-glossary-import`, and removes stale `.hv/bin/hv-context-*` files left behind. Umbrella projects are also supported: each registered sub-repo's legacy `.hv/contexts/<name>/CONTEXT.md` is migrated into that sub-repo's `.hv/knowledge/<name>/KNOWLEDGE.md` (## Glossary) via `hv-glossary-import --repo <name>`; the umbrella-root `.hv/CONTEXT.md` still migrates to the umbrella `.hv/KNOWLEDGE.md`; everything is backed up under `.hv/migrate-backup/` first. `--dry-run` is default; `--apply` writes; `--verbose` adds per-file diffs. Idempotent — a clean second `--apply` rewrites zero files. Refuses on uncommitted changes outside `.hv/`, pre-3.0 project version, or when run inside an existing backup directory. Use on "migrate to v4", "/hv-migrate v4", upgrading hv-skills from 3.x to 4.0.

  • Hv refactor

    l4ci/hv-skills/hv-refactor Skill

    0★ repo

    Run a full architectural refactor cycle — explores the codebase for friction, categorizes dependencies, designs competing approaches for structural changes, then fixes everything with parallel subagents. Use when you want to find and fix architectural issues.

  • Docker config qa regression

    aksheyw/claude-code-learned-skills/skills/docker-config-qa-regression Skill

    0★ repo

    Systematic verification checklist after modifying Docker container config (volumes, env vars, compose edits). Use after any docker-compose change to catch cascading failures (auth loss, ephemeral volumes, missing credentials) before they reach production. Originally derived from a real session debugging post-config-change auth failures.

  • Ssh docker remote config management

    aksheyw/claude-code-learned-skills/skills/ssh-docker-remote-config-management Skill

    0★ repo

    Reliable pattern for editing JSON config files in Docker containers on a remote VPS via SSH — avoids the triple-nested-quoting nightmare (SSH → docker exec → jq) using a pipe-and-copy approach. Includes hot-reload tricks (SIGUSR1) and gotchas around `docker cp` direction and `restart` vs `down/up`.

  • Roblox code maintenance refactor

    AshExplained/roblox-skills/roblox-code-maintenance-refactor Skill

    0★ repo

    Maintain and refactor Roblox Luau code safely. Use for technical debt, dead code removal, module boundaries, naming cleanup, duplicate logic, dependency review, regression prevention, and long-term codebase health.

  • Roblox luau architecture

    AshExplained/roblox-skills/roblox-luau-architecture Skill

    0★ repo

    Design, inspect, and refactor Roblox Luau game architecture. Use for ModuleScript/service boundaries, client-server flow, RemoteEvents/RemoteFunctions, ReplicatedStorage organization, reusable systems, script placement, and safe Studio MCP code-edit workflows.

  • Setup roblox skills

    AshExplained/roblox-skills/setup-roblox-skills Skill

    0★ repo

    Bootstrap the Roblox skill pack in a game project by injecting a `## Roblox Skills` block into CLAUDE.md — the full game-development lifecycle map, every skill's purpose, use case, and trigger words, and the next-skill routing so each skill ends by telling the user what to run next. Also records the project's tracker (GitHub issues or local roadmap), triage labels, and UI design artifact layout. Run once when setting up a Roblox project, or if the skills seem to be missing lifecycle, tracker, label, or routing context.

  • Tech debt prioritizer

    SkillMedev/engineering-manager-toolkit/skills/tech-debt-prioritizer Skill

    0★ repo

    Inventories 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

  • Onboarding plan builder

    SkillMedev/people-ops-recruiting/skills/onboarding-plan-builder Skill

    0★ repo

    Produces 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

  • Ship onboarding

    taskmasterpeace/ship-pack/skills/ship-onboarding Skill

    0★ repo

    Generates an in-app first-run onboarding tour from a project's user guide and screenshots — an ordered docs/onboarding.json (steps with target selectors, copy, and optional screenshot ids) plus an embeddable, themeable coachmark/tour web component. Derives the activation path from the guide's main workflows, themes from docs/brand.json, and stays in sync via docs/VERSION. Use when the user wants an onboarding tour, first-run experience, product tour, guided tour, coachmarks, walkthrough overlay, tooltips/hints for new users, a "show me around" flow, an onboarding checklist, or to turn the user guide into an in-app tour. Triggers on "onboarding tour", "first-run", "product tour", "coachmarks", "guided tour", "in-app walkthrough", "new-user tour", "ship-onboarding".

  • Api versioning strategist

    SkillMedev/api-integration-engineering/skills/api-versioning-strategist Skill

    0★ repo

    Produces 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

  • Idempotency enforcer

    SkillMedev/api-integration-engineering/skills/idempotency-enforcer Skill

    0★ repo

    Designs 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

  • Analytics setup

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/analytics-setup Skill

    0★ repo

    When to activate: analytics setup, GA4, Google Analytics, event tracking, conversion tracking, UTM strategy, attribution, dashboards, data layer, tag management

  • Nodejs typescript server

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/nodejs-typescript-server Skill

    0★ repo

    When to activate: Express with TypeScript, middleware patterns, REST API design, error handling, OpenAPI, JWT auth, rate limiting

  • Onboarding design

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/onboarding-design Skill

    0★ repo

    When to activate: employee onboarding, 30/60/90 day plans, new hire experience, buddy programs, knowledge transfer, ramp metrics, remote onboarding, role readiness

  • Python config

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/python-config Skill

    0★ repo

    When to activate: configuration management, pydantic-settings, env files, feature flags, environment-specific settings

  • Swift architecture

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/swift-architecture Skill

    0★ repo

    When to activate: iOS/macOS app architecture, MVVM, TCA, Clean Architecture, dependency injection, modular design in Swift apps

  • Typescript monorepo

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/typescript-monorepo Skill

    0★ repo

    When to activate: monorepo, Turborepo, pnpm workspaces, shared packages, workspace dependencies, TypeScript project references

  • Cubrid manual

    Srltas/claude-skills/cubrid-manual Skill

    0★ repo

    Look up CUBRID engine behavior in the official online manual: SQL syntax, built-in functions, data types, identifiers and reserved keywords, configuration parameters, and JDBC/driver APIs. Fetches the version-pinned manual at www.cubrid.org/manual. Use when you need to verify CUBRID SQL semantics, a function signature, a data type's range, whether a word is reserved, or a config parameter before writing dialect or JDBC code. For CUBRID Migration Toolkit (CMT) questions, use the cmt-manual skill instead. Triggers on phrases like 'how does X work in CUBRID', 'CUBRID syntax for', 'is X a reserved word in CUBRID', 'what functions does CUBRID have', 'check the CUBRID manual'.

  • Cleaner

    Swellshinider/janitor/integrations/opencode/skills/cleaner Skill

    0★ repo

    Use when AI-generated code has bloated the repo: oversized files or classes, dead or unused code (functions, imports, variables, types, whole files), or duplicated blocks that need merging. Behavior-preserving cleanup only. Run when the user says "clean up this code", "remove dead code", "split this file", "this file is too big", "deduplicate", or "refactor without changing behavior". Not for new features, bug fixes, performance work, or over-engineering review.

  • Manager

    Swellshinider/janitor/integrations/opencode/skills/manager Skill

    0★ repo

    Use when the codebase is structurally hard to navigate: oversized files or classes that should be split into cohesive modules, or a flat or misplaced directory layout that should be regrouped by feature or responsibility. Behavior-preserving structural refactor only: split files and move them into a cleaner layout, with import rewrites and re-export shims keeping callers unchanged. Run when the user says "this module is a mess", "split this giant file", "reorganize these folders", "group these files by feature", or "restructure this directory". Not for in-place dead-code removal or deduplication (that is the cleaner skill), nor for new features, bug fixes, or behavior changes.

  • Cleaner

    Swellshinider/janitor/skills/cleaner Skill

    0★ repo

    Use when AI-generated code has bloated the repo: oversized files or classes, dead or unused code (functions, imports, variables, types, whole files), or duplicated blocks that need merging. Behavior-preserving cleanup only. Run when the user says "clean up this code", "remove dead code", "split this file", "this file is too big", "deduplicate", or "refactor without changing behavior". Not for new features, bug fixes, performance work, or over-engineering review.

  • Manager

    Swellshinider/janitor/skills/manager Skill

    0★ repo

    Use when the codebase is structurally hard to navigate: oversized files or classes that should be split into cohesive modules, or a flat or misplaced directory layout that should be regrouped by feature or responsibility. Behavior-preserving structural refactor only: split files and move them into a cleaner layout, with import rewrites and re-export shims keeping callers unchanged. Run when the user says "this module is a mess", "split this giant file", "reorganize these folders", "group these files by feature", or "restructure this directory". Not for in-place dead-code removal or deduplication (that is the cleaner skill), nor for new features, bug fixes, or behavior changes.

  • Swiftui navigation architecture

    wei18/apple-dev-skills/apple-dev-skills/skills/swiftui-navigation-architecture Skill

    0★ repo

    Default navigation shape for SwiftUI Apps (iOS 18 / macOS 15, Swift 6) — value-based `NavigationStack(path:)` over a typed `Route` enum, one `@Observable @MainActor` Router in `.environment`, `navigationDestination(for:)` at the stack root (never in a lazy container), per-transition presentation semantics (push / sheet / `fullScreenCover` / popover / alert / root-swap) incl. macOS behavior (no native `fullScreenCover` → push fallback, pop-to-landing), `item:`-driven modal optionals, `.onOpenURL` deep-link funnel, `NavigationSplitView`, per-tab paths, `Codable` restoration. Invoke when wiring an App's navigation, choosing sheet vs cover vs push, adding deep links / restoration, migrating off `NavigationView`, or asked "router / coordinator in SwiftUI". Bugs → swiftui-interaction-footguns.

  • Secure deploy gate

    NeuralMedic-DE/claude-skills/secure-deploy-gate Skill

    0★ repo

    Harden and pentest a web deployment, gated by checks that actually run — a stdlib Python scanner probes a live target's TLS/HTTPS (cert validity, weak protocols, HTTP→HTTPS redirect), security headers (HSTS, CSP, cookies, version disclosure), and connect-scans for risky internet-exposed ports (databases, caches, admin/Docker/Kubelet APIs), plus an offline static audit of the reverse-proxy and container config (Caddy, nginx, docker-compose, Dockerfile) — and ships a hardened Caddy/nginx/firewall reference setup. Findings map to a severity and fail the build; active scanning is authorization-gated. Use to secure or harden a deployment, pentest/scan your own server or site, set up HTTPS/TLS properly, pick a reverse proxy (Caddy), find open ports or exposed services, add security headers, or gate deployment security in CI. Triggers: "secure deployment", "pentest my server", "harden", "HTTPS/TLS setup", "Caddy", "reverse proxy", "open ports", "exposed database", "security headers", "HSTS".

  • React bootstrap

    jaballer/react-claude-skills/react-bootstrap Skill

    0★ repo

    Project scaffolding for the first 5 minutes of a React interview build — Vite + React + TypeScript + Tailwind as the primary scaffold, Next.js App Router as alternate, "they gave me a starter repo" path (most likely Netlify scenario), file structure recommendations, useful dependencies (clsx + tailwind-merge + zod), App.tsx skeleton with brief-restate header, README starter, Tailwind config, what NOT to set up. Use at the start of any interview build to skip 5–10 minutes of setup decisions. Triggers on "scaffold", "bootstrap", "project setup", "first 5 minutes", "vite", "create vite", "package.json", "tailwind config", "App.tsx", "start a project", "new project", "set up", "initial setup", "starter repo".

  • React onboarding docs

    jaballer/react-claude-skills/react-onboarding-docs Skill

    0★ repo

    React patterns for product onboarding flows and documentation sites — multi-step flows, progress indicators, empty states, contextual hints, code-block components, TOC sidebars, on-this-page nav, callouts, copy-buttons, search, syntax highlighting. Use when building onboarding UI, product tours, documentation pages, knowledge bases, or developer-facing reference sites. Triggers on "onboarding", "tour", "walkthrough", "empty state", "tooltip", "documentation", "docs site", "code block", "TOC", "table of contents", "callout".

  • React testing

    jaballer/react-claude-skills/react-testing Skill

    0★ repo

    Testing strategy for React apps — when to reach for Playwright (E2E) vs Vitest (unit/component) vs both, the senior testing pyramid for an SPA, Playwright setup with config + webServer + per-spec project structure, Vitest setup with jsdom + Testing Library, a11y-first locators (getByRole, getByLabel, toBeFocused, toHaveAttribute), assertion patterns for aria-pressed/aria-current/role=alert/focus-on-route-change, @axe-core/playwright for automated a11y audits, running against localhost vs deployed URL via env var, what NOT to test, common flakiness sources and fixes. Use whenever the project needs tests added — interview "would you add tests?" question, real production CI, or post-build polish layer. Triggers on "test", "testing", "playwright", "vitest", "jest", "e2e", "end-to-end", "unit test", "component test", "@playwright/test", "@axe-core/playwright", "getByRole", "testing library", "rtl", "smoke test", "ci tests", "test runner".

  • Project md

    0jg/skills/project-md Skill

    no license0★ repo

    Generates a project-specific CLAUDE.md file at project initialisation time. Use this skill whenever starting a new project, forking a repo, or when the user asks to set up Claude Code for a project. Always invoke this skill as part of the research-project-init workflow — do not write CLAUDE.md from memory. The generated file encodes project type, physics context, toolchain rules, directory conventions, agent configuration, and skill triggers so that all context persists across sessions and survives context compaction.

  • Research project init

    0jg/skills/research-project-init Skill

    no license0★ repo

    Scaffolds a new Python or Rust research project with the full standard toolchain. Also bootstraps Claude Code infrastructure (hooks, agents, settings) on existing or forked repos that lack it. Use this skill whenever the user wants to start a new project, create a new repo, initialise a codebase, set up a package, or bootstrap a forked repo. Triggers on phrases like "new project", "set up a repo", "initialise a project", "scaffold", "start a codebase", or "set up hooks on this repo". Always use this skill — do not scaffold projects from memory, as the toolchain and structure are precisely specified here.

  • Presentation story architecture

    samulee003/agentic-ppt-skills/skills/presentation-story-architecture Skill

    0★ repo

    Turns an approved brief and supported claims into a thesis, audience journey, chapter roles, transitions, and slide-by-slide jobs for the main talk and backup. Use when the story-architecture gate is current for a presentation project or when a router asks for the story and storyboard.

  • Brainstorming

    roedyrustam/claudevibeskills/src/brainstorming Skill

    no license0★ repo

    Advanced brainstorming protocol with 2026 Modern Web Guidance. Use this skill whenever the user wants to ideate, plan, architect, or design a new feature, product, or system — especially for web applications. Trigger on phrases like "brainstorm", "let's plan", "how should I approach", "help me design", "what's the best way to build", "I want to create", "give me ideas for", "design document", "technical spec", or "architecture for". Also trigger when the user is starting a new project and needs a structured Design Document (DD) output. Covers RSC, PPR, Server Actions, AI integration, Passkeys, and structured output templates.

  • Prd architect

    roedyrustam/claudevibeskills/src/prd-architect Skill

    no license0★ repo

    Initial guardrail skill that enforces creating a comprehensive Product Requirements Document (PRD) before generating code. Use whenever the user starts a new project or feature and jumps straight to "build me X" without defined requirements. Trigger on phrases like "build me an app that...", "create a system for...", "I want to build...", or any greenfield request lacking clear scope. Also trigger when the user explicitly asks for a PRD or requirements document.

  • Scalability clean code

    roedyrustam/claudevibeskills/src/scalability-clean-code Skill

    no license0★ repo

    Guidelines for maintaining code readability (Clean Code, SOLID, DRY) and system scalability (Clean Architecture, loose coupling, horizontal scaling, caching). Use whenever the user is reviewing code quality, refactoring, designing system architecture for scale, or asking about best practices for maintainability. Trigger on mentions of clean code, SOLID principles, DRY, technical debt, code smells, refactoring, horizontal scaling, or system architecture review.

  • Senior fullstack

    roedyrustam/claudevibeskills/src/senior-fullstack Skill

    no license0★ repo

    Expert fullstack architecture skill covering advanced backend patterns, infrastructure, testing, and system design. Use this skill whenever the user is working on fullstack architecture decisions, API design, background job queues, caching strategies, database connection pooling, CI/CD pipelines, Docker containerization, end-to-end testing with Playwright, WebSocket real-time features, or deployment configurations. Trigger on mentions of Redis, BullMQ, Prisma, Drizzle, PostgreSQL, Docker, GitHub Actions, connection pooling, rate limiting, Playwright, or any backend/infra topic that goes beyond simple CRUD. Also trigger for performance bottlenecks, scalability concerns, or production readiness reviews.

  • Manuscript profile setup

    dinaf2026-web/manuscript-editorial-suite-plugin/skills/manuscript-profile-setup Skill

    0★ repo

    Sets up (or edits) a book project's editorial profile for the Manuscript Editorial Suite. Every other pass auto-detects this profile from the working folder; this skill is what creates it. Use when there is no profile yet, when a pass reports "no profile found", or when the author says "set up my book", "create a profile", "edit my profile", "change my genre/shelf/comps", "onboard this manuscript", or "configure the editorial suite". It writes `<project>/.manuscript/profile.md` and seeds an empty canon ledger. It does not critique, score, or audit — it only configures.

    The same file is in 1 other repository

  • Nav2009 development

    whobat/AI-Agent-skills/skills/nav-2009/nav2009-development Skill

    0★ repo

    Develop, review, and architect C/AL code and objects for Microsoft Dynamics NAV 2009 (Navision) — Classic client and RoleTailored Client (RTC). Covers C/AL coding patterns and performance idioms (FINDSET/FINDFIRST/ISEMPTY, SETCURRENTKEY, locking, COMMIT discipline), key/SIFT design, code-review checklist, customization architecture (hooks, setup tables, number series), reports (Classic sections and RDLC), integrations (XMLports, Dataports, NAS, web services, MSMQ/COM), and upgrade-friendly patterns toward Business Central. Use for any NAV 2009 / Navision / C/AL task — writing or reviewing code, designing a customization, building a report or integration, or preparing for a BC migration.

  • Secrets hygiene

    SkillMedev/security-compliance-hardening/skills/secrets-hygiene Skill

    0★ repo

    Guides 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

  • Refactor skills

    usrrname/agent-skills/skills/refactor-skills Skill

    no license0★ repo

    Reviews the markdown and template files changed in the current session and tightens them for agent performance — sharper trigger descriptions, progressive disclosure, imperative voice, one-claim-per-bullet, fewer redundant rules — while preserving every workflow step, constraint, and trigger condition. Use when the user has just edited one or more skill or prompt files (`SKILL.md`, `references/*.md`, `recipes/*.md`, agent templates, slash-command prompts) and wants a tightening pass before committing, or invokes "/refactor-skills", "refactor this skill", "tighten the skill", "polish SKILL.md", "make this skill leaner". Behaviour-preserving only — never use this to add features, expand scope, or remove rules.

  • Refactor

    usrrname/agent-skills/skills/refactor Skill

    no license0★ repo

    Refactors existing code by identifying language and applying best practices. Use when the user asks to refactor, improve, optimize, or clean up code.

  • Mobile perf profiler

    SkillMedev/mobile-app-engineering/skills/mobile-perf-profiler Skill

    0★ repo

    Diagnoses 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

  • React native pro

    SkillMedev/mobile-app-engineering/skills/react-native-pro Skill

    0★ repo

    Builds 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

  • Api design

    muxammadmamajonov/dot-claude/.claude/skills/api-design Skill

    0★ repo

    Design versioned, secure API contracts (REST, GraphQL, RPC, events, SDK surface) from requirements and data model. Use before implementing endpoints or for a breaking contract change.

  • Architecture

    muxammadmamajonov/dot-claude/.claude/skills/architecture Skill

    0★ repo

    Design and document system architecture and trade-offs after requirements and stack selection, before build — or when a structural change (new service, scaling redesign) needs a record.

  • Ordito init

    karuhi/ordito/.claude/skills/ordito-init Skill

    0★ repo

    Scaffold Ordito into a repository — create ordito.config.json, the docs IR directory, a starter page, a collection (nav), and a GitHub Pages deploy workflow (.github/workflows/docs.yml). Use this once when setting Ordito up in a new repo for internal developer docs (after the .claude/skills + bundled engine have been copied in, e.g. via scripts/install-into.sh). Idempotent: existing files are left untouched unless force:true. Does NOT generate HTML (run ordito-generate after) and does NOT ask for confirmation; the calling agent owns that.

  • Pmo architect

    cody-hutson/pmo-platform/release/skills/pmo-architect Skill

    no license0★ repo

    System-scope Architect Specialist — cross-component, middleware, and data architecture; integration design and blast-radius assessment; system-level ADR authorship. Composes pmo-principal-engineer (within-component solution depth) and pmo-technical-analyst (technical review) — invokes each, re-implements neither. Modes: System-Design · Integration-Review. Use for system design across components, integration design, blast-radius assessment, cross-component architecture, or to write a system ADR. Triggers: "architecture review", "system design", "integration design", "blast-radius assessment", "cross-component design", "write a system ADR". Distinct from the solution-scope Principal Engineer (within-component depth).

  • Obsidian maintenance

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-maintenance Skill

    0★ repo

    Specialist skill for keeping an Obsidian vault healthy over time — deduplicating overlapping notes, merging, refactoring outdated documentation, fixing structural mess, and updating docs after code changes. Normally invoked by the obsidian-documentation orchestrator. Use for "clean up the vault", "these notes overlap", "the docs are outdated", "refactor the documentation", or when any skill notices duplication or rot.

  • Backend onboard

    vipincode/exr-agent-skills/.claude/skills/backend-onboard Skill

    no license0★ repo

    Make any project ready for the backend toolkit (backend-feature-planner, backend-module-builder, backend-test-writer) by establishing its contract files. Use this as the entry point whenever the user points the toolkit at a directory — "set up my existing API for this", "onboard this repo", "I want to use these skills on my current project", "get this project ready", or starting work in a folder that has no ARCHITECTURE.md / MODULE_REGISTRY.md yet. For an EXISTING codebase it scans the repo and generates a DESCRIPTIVE ARCHITECTURE.md plus a MODULE_REGISTRY.md seeded with all existing reusable code, so feature work reuses what's there instead of duplicating it (DRY). For an EMPTY directory it hands off to express-ts-bootstrap. It is non-destructive — it never refactors existing code, only writes the contract files. After onboarding, plan/build/test happen through the dedicated skills.

  • Express ts bootstrap

    vipincode/exr-agent-skills/.claude/skills/express-ts-bootstrap Skill

    no license0★ repo

    Scaffold a new production-grade Express.js + TypeScript + Mongoose + JOSE backend from scratch. Use this whenever the user wants to start a new Node/Express API project, bootstrap a backend, set up an Express + TypeScript starter, or initialize a server-side project — even if they only say "new API", "Express starter", "backend boilerplate", or name the stack loosely. This skill scaffolds the infrastructure ONCE per project and generates the two source-of-truth files (ARCHITECTURE.md and MODULE_REGISTRY.md) that the backend-feature-planner, backend-module-builder, and backend-test-writer skills depend on. Do NOT use this to add a feature to an existing project (that is backend-feature-planner + backend-module-builder) or to write tests (backend-test-writer). This scaffolds an Express/Node + TypeScript backend specifically — do NOT use it to bootstrap projects in other stacks or languages (Django/Python, Rails, Spring, Go, Next.js, etc.); those are out of scope.