agentsclimarketplace

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

  • Helm chart scaffolding

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/helm-chart-scaffolding Skill

    no license1★ repo

    Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments.

    The same file is in 1 other repository

  • Monorepo management

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/monorepo-management Skill

    no license1★ repo

    Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

    The same file is in 1 other repository

  • Mtls configuration

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/mtls-configuration Skill

    no license1★ repo

    Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.

    The same file is in 1 other repository

  • Prometheus configuration

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/prometheus-configuration Skill

    no license1★ repo

    Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.

  • Python configuration

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/python-configuration Skill

    no license1★ repo

    Python configuration management via environment variables and typed settings. Use when externalizing config, setting up pydantic-settings, managing secrets, or implementing environment-specific behavior.

    The same file is in 1 other repository

  • React native architecture

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/react-native-architecture Skill

    no license1★ repo

    Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecting React Native projects.

    The same file is in 1 other repository

  • Sast configuration

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/sast-configuration Skill

    no license1★ repo

    Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

  • M15 anti pattern

    ulpi-io/plugin-marketplace/plugins/zhanghandong/skills/m15-anti-pattern Skill

    no license1★ repo

    Use when reviewing code for anti-patterns. Keywords: anti-pattern, common mistake, pitfall, code smell, bad practice, code review, is this an anti-pattern, better way to do this, common mistake to avoid, why is this bad, idiomatic way, beginner mistake, fighting borrow checker, clone everywhere, unwrap in production, should I refactor, 反模式, 常见错误, 代码异味, 最佳实践, 地道写法

    The same file is in 1 other repository

  • Rust refactor helper

    ulpi-io/plugin-marketplace/plugins/zhanghandong/skills/rust-refactor-helper Skill

    no license1★ repo

    Safe Rust refactoring with LSP analysis. Triggers on: /refactor, rename symbol, move function, extract, 重构, 重命名, 提取函数, 安全重构

    The same file is in 1 other repository

  • Artifacts

    zinan92/repo-evals/repos/zarazhangrui--codebase-to-course/runs/2026-05-05/run-static-checks/artifacts Skill

    1★ repo

    Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people. Use this skill whenever someone wants to create an interactive course, tutorial, or educational walkthrough from a codebase or project. Also trigger when users mention 'turn this into a course,' 'explain this codebase interactively,' 'teach this code,' 'interactive tutorial from code,' 'codebase walkthrough,' 'learn from this codebase,' or 'make a course from this project.' This skill produces a stunning, self-contained HTML file with scroll-based navigation, animated visualizations, embedded quizzes, and code-with-plain-English side-by-side translations.

  • Orient

    mike-diff/ai-coding-configs/.claude/skills/orient Skill

    no license1★ repo

    Build a comprehensive understanding of the codebase. Maps tech stack, architecture, and patterns. Findings persist through project memory.

  • Orient

    mike-diff/ai-coding-configs/.cursor/skills/orient Skill

    no license1★ repo

    Build comprehensive understanding of a codebase. Maps tech stack, architecture, entry points, and patterns. Use when starting work on an unfamiliar codebase or onboarding to a new project.

  • Orient

    mike-diff/ai-coding-configs/plugins/agent-team/skills/orient Skill

    no license1★ repo

    Build a comprehensive understanding of the codebase. Maps tech stack, architecture, and patterns. Findings persist through project memory.

  • Api contract testing

    almasumdev/awesome-mobile-testing-agent-skills/.github/skills/integration/api-contract-testing Skill

    no license1★ repo

    Expert guidance on consumer-driven contract tests for mobile apps using Pact. Use when mobile clients depend on backend APIs that evolve independently and staging smoke tests are slow or flaky.

  • Image optimization pipeline config

    jacob-balslev/skill-graph/examples/projects/markdown-static-site/skills/image-optimization-pipeline-config Skill

    no license1★ repo

    Use when authoring or reviewing the build-time image pipeline config — defining responsive srcset breakpoints, picking output formats (AVIF / WebP / JPEG fallback), tuning compression quality per format, and ensuring the pipeline never produces a lossy artifact for source PNGs with transparency. Activate this skill whenever the task touches `lib/images/pipeline.config.ts`, `scripts/build-images.ts`, or any code path that resizes or recompresses content images. Do NOT use for runtime image rendering choices (use a frontend skill) or for chasing a specific build failure (use debugging).

  • Api design

    jacob-balslev/skill-graph/marketplace/skills/api-design Skill

    no license1★ repo

    Use when designing or reviewing HTTP API surfaces: consumer tasks, audience class, protocol/paradigm fit, resources/actions, route taxonomy, request and response schemas, status codes in context, pagination, filtering, sorting, field selection, idempotency, auth and tenant boundaries, error envelopes, rate-limit signals, versioning, deprecation, discovery, and contract artifacts. Do NOT use for pure HTTP protocol semantics (use `http-semantics`), framework-specific route handler mechanics (use `route-handler-design`), non-HTTP system contracts (use `system-interface-contracts`), async event contracts (use `event-contract-design`), database design (use `entity-relationship-modeling`), inbound provider webhook mechanics (use `webhook-integration`), or post-failure diagnosis (use `debugging`). Do NOT use for define the broader contract between a job, service, and dashboard. Do NOT use for design database tables, foreign keys, and views.

  • Architecture decision records

    jacob-balslev/skill-graph/marketplace/skills/architecture-decision-records Skill

    no license1★ repo

    Use when writing, reviewing, or updating Architecture Decision Records: context, decision, options rejected, consequences, status, supersession, and follow-up verification. Do NOT use for general documentation prose (use `documentation`), code review findings (use `code-review`), or choosing between frameworks before a decision exists (use `framework-fit-analysis`). Do NOT use for write a general README section explaining how this module works. Do NOT use for choose which framework we should use for this project. Do NOT use for review this PR for bugs and regressions. Do NOT use for design the interface contract between these two services.

  • Best practice

    jacob-balslev/skill-graph/marketplace/skills/best-practice Skill

    no license1★ repo

    Cross-cutting best practices enforcement across code, templates, skills, prompts, scripts, documentation, pages, and design. The enforcement layer that catches violations any specialist might miss. Do NOT use for deep code review methodology (use code-review), application security depth (use owasp-security), accessibility implementation depth (use a11y), or specialist design-system work (use design-system-architecture, color-system-design, or typography-system). Do NOT use for designing the color system and contrast model (use color-system-design). Do NOT use for implementing font loading and vertical rhythm (use typography-system). Do NOT use for designing a skill's comprehension or application eval suite (use eval-driven-development).

  • Client server boundary

    jacob-balslev/skill-graph/marketplace/skills/client-server-boundary Skill

    no license1★ repo

    Use when reasoning about the line where execution context changes between server runtime and client runtime: what values can cross via the active serializer, what cannot, how `'use client'`, `'use server'`, guard imports, and server-only file conventions mark module/function transitions, how React Server Components differ from server-rendered HTML, why Server Functions / Server Actions are reachable network endpoints, why client input is adversarial, and how server-only modules, secrets, raw records, or closures leak into client bundles and payloads. Do NOT use for choosing when and where UI is produced (use rendering-models), full Server Component read-path placement (use server-components-design), full Server Action mutation/form/cache design (use server-actions-design), public Route Handler endpoint design (use route-handler-design), HTTP wire semantics (use http-semantics), frontend codebase organization (use frontend-architecture), or API JSON contract design (use api-design).

  • Color system design

    jacob-balslev/skill-graph/marketplace/skills/color-system-design Skill

    no license1★ repo

    Use when designing a color system — palette construction, semantic color tokens, WCAG contrast pairings, perceptual scale generation in OKLCH/LCH/HCT, wide-gamut fallbacks, and light/dark/high-contrast parity. Do NOT use for single brand-color picks, runtime theme-switching mechanics, token delivery architecture, or non-color design tokens. Do NOT use for Pick the brand's primary color from scratch with no system constraints. Do NOT use for Implement prefers-color-scheme detection, localStorage persistence, and anti-flash script. Do NOT use for Design the full DTCG token build pipeline for all token categories. Do NOT use for Choose spacing values for the layout grid. Do NOT use for the palette, the scale construction, the semantic color roles, and the contrast pairings against every surface (use dark-mode-implementation).

  • Component architecture

    jacob-balslev/skill-graph/marketplace/skills/component-architecture Skill

    no license1★ repo

    The architectural discipline of structuring a UI component library — layering, API surface design, headless/styled split, and state contracts — so component APIs survive reuse across products, themes, and teams. Do NOT use for design the typography system: type scale, font pairing, text sizes, and reading rhythm. Do NOT use for define the form validation, error messaging, submit behavior, and field grouping for checkout. Do NOT use for decide where component state lives across the app and which components own the app state. Do NOT use for how a single product's modules compose internally (use design-module-composition). Do NOT use for palette, token, contrast, and semantic color decisions (use color-system-design). Do NOT use for type scale, font pairing, rhythm, and text hierarchy (use typography-system). Do NOT use for form validation, submission, grouping, and error experience (use form-ux-architecture). Do NOT use for the visual language itself (use visual-design-foundations).

  • Dependency architecture

    jacob-balslev/skill-graph/marketplace/skills/dependency-architecture Skill

    no license1★ repo

    Use when designing or auditing dependency structure: package boundaries, runtime vs build dependencies, adapter layers, duplicate-purpose libraries, supply-chain risk, upgrade policy, lock-in, and dependency graph health. Do NOT use for choosing a major framework (use `framework-fit-analysis`), vulnerability-only review (use `owasp-security`), or routine refactoring without dependency boundary changes (use `refactor`). Do NOT use for choose between Next.js, Remix, and Astro for a new app. Do NOT use for scan dependencies only for known vulnerabilities. Do NOT use for refactor this module without changing dependency boundaries. Do NOT use for write an ADR after the dependency decision is accepted.

  • Design system architecture

    jacob-balslev/skill-graph/marketplace/skills/design-system-architecture Skill

    no license1★ repo

    Use when designing or auditing a design system's architecture: token taxonomy, semantic tokens, component APIs, theming, accessibility contracts, documentation, governance, and migration strategy. Do NOT use for information hierarchy and navigation (use `information-architecture`), page-specific layout (use `layout-composition`), visual craft direction (use `visual-design-foundations`), sentence-level UI copy (use `microcopy`), or accessibility-only audits (use `a11y`). Do NOT use for organize pages, nav, sitemap, and wayfinding. Do NOT use for rewrite the empty-state text and tooltip labels. Do NOT use for add aria-labels and keyboard behavior to this component. Do NOT use for draft an architecture note explaining why we chose Postgres over DynamoDB.

  • Event contract design

    jacob-balslev/skill-graph/marketplace/skills/event-contract-design Skill

    no license1★ repo

    Use when designing or reviewing asynchronous event contracts: producer/consumer ownership, event envelope, schema, topic/channel naming, ordering, idempotency, versioning, compatibility, replay, dead-letter behavior, and AsyncAPI/CloudEvents-style documentation. Do NOT use for domain-event discovery (use `event-storming`), broad interface contracts (use `system-interface-contracts`), inbound provider webhook mechanics (use `webhook-integration`), or HTTP endpoint design (use `api-design`). Do NOT use for discover the domain events, commands, and policies in this business process. Do NOT use for define every boundary contract between services, jobs, and APIs. Do NOT use for verify inbound provider webhook signatures and retry behavior. Do NOT use for design REST endpoints, status codes, and pagination.

  • Form ux architecture

    jacob-balslev/skill-graph/marketplace/skills/form-ux-architecture Skill

    no license1★ repo

    Use when designing or auditing form structure and validation UX: field grouping, required vs optional inputs, validation timing, client/server validation split, submission lifecycle, recovery, multi-step forms, and high-risk data entry. Do NOT use for labels and announcements alone (use `a11y`), validation-message wording (use `microcopy`), API schema design (use `api-design`), or stored data modeling (use `entity-relationship-modeling`). Do NOT use for add labels so assistive tech can read each field. Do NOT use for rewrite the inline validation messages. Do NOT use for define the request and response schema for the form submit endpoint. Do NOT use for model the database columns that store these inputs. Do NOT use for validation-message wording (use microcopy).

  • Frontend architecture

    jacob-balslev/skill-graph/marketplace/skills/frontend-architecture Skill

    no license1★ repo

    Use when organizing a frontend codebase — module boundaries, component layering, state ownership, data-flow direction, and the separation between feature code and shared primitives. Do NOT use for visual design decisions, specific framework migration tactics, or backend API contract design. Do NOT use for Pick the brand color palette for a marketing site. Do NOT use for Design the REST endpoint shape for the orders resource. Do NOT use for Decide whether to use CSS-in-JS or Tailwind.

  • Gemini pro

    jacob-balslev/skill-graph/marketplace/skills/gemini-pro Skill

    no license1★ repo

    Use when deciding whether to route a task to Google's Gemini Pro frontier model (current Gemini 3.1 Pro generation, moving to Gemini 3.5 Pro) instead of Claude Opus or GPT-5 — especially for very-large-context reasoning (1M-token input), whole-codebase or long-document analysis, native multimodal input (audio/video/PDF/image in one call), or capability-per-dollar at the frontier. Covers the context window, the 200K context-tier pricing cliff, multimodal support, and the per-lane comparison against Claude Opus / GPT-5. Do NOT use for choosing the cheap/fast tier (use `gemini-flash`), for general agent-system architecture (use `agent-engineering`), or for dispatching among local skills (use `skill-router`). Do NOT use for I just need a cheap classifier for 10k rows. Do NOT use for design the multi-agent orchestration for this system. Do NOT use for which of my local skills should handle this request?

  • Http semantics

    jacob-balslev/skill-graph/marketplace/skills/http-semantics Skill

    no license1★ repo

    Use when designing or reviewing HTTP-based systems where method semantics, status codes, idempotency, safe methods, conditional requests, content negotiation, caching headers, range requests, integrity digests, or representation metadata are load-bearing. Covers the RFC 9110/9111/9112 contract layer below any specific framework. Do NOT use for API surface shape and route taxonomy (use api-design), for WebSocket or SSE bidirectional streams (use streaming-architecture skill when available), for vendor-specific webhook signing (use webhook-integration), or for transport-level concerns like TLS or QUIC (use platform-level documentation). Do NOT use for decide between WebSocket and SSE for live updates (use streaming-architecture).

  • Information architecture

    jacob-balslev/skill-graph/marketplace/skills/information-architecture Skill

    no license1★ repo

    Use when structuring information for findability: navigation, page hierarchy, docs architecture, sitemap shape, labeling systems, wayfinding, and content grouping. Do NOT use for formal category-governance work (use `taxonomy-design`), responsive page composition (use `layout-composition`), component/token architecture (use `design-system-architecture`), or sentence-level UI text (use `microcopy`). Do NOT use for make the category taxonomy and assignment rules for this skill library. Do NOT use for define design tokens, component APIs, and theming rules. Do NOT use for rewrite this tooltip and empty-state copy. Do NOT use for audit keyboard accessibility and ARIA semantics. Do NOT use for structure inside a page or screen (use layout-composition). Do NOT use for sentence-level UI text (use microcopy).

  • Refactor

    jacob-balslev/skill-graph/marketplace/skills/refactor Skill

    no license1★ repo

    Use when reorganizing existing code without changing external behavior — extracting functions, reducing duplication, renaming for clarity, splitting modules, or tightening structure. Covers behavior preservation, duplication reduction, decomposition, naming improvements, structural reorganization, and before/after verification. Do NOT use for bug investigation, adding new product behavior, or writing documentation (even when the docs describe the refactored code). Do NOT use for the test is failing after my edit — what did I break? Do NOT use for write an architecture note explaining this pattern for new team members. Do NOT use for reproduce why this function retries three times on transient network errors.

  • Rendering models

    jacob-balslev/skill-graph/marketplace/skills/rendering-models Skill

    no license1★ repo

    Use when reasoning about how a web UI is produced and delivered: client-side rendering, server-side rendering, static-site generation, incremental static regeneration, React Server Components, streaming SSR, edge rendering, and partial prerendering. Covers the time × place grid (build/request/stream/interaction × server/edge/client), the trade-offs between first-paint latency and time-to-interactive, the relationship between rendering and hydration, and how a route's content profile (dynamic / static / personalized) maps to a model. Do NOT use for organizing the frontend codebase (use frontend-architecture), the serialization frontier between server and client code (use client-server-boundary), the wire protocol itself (use http-semantics), or specific deploy-platform composition patterns (use vercel-composition-patterns).

  • Skill scaffold

    jacob-balslev/skill-graph/marketplace/skills/skill-scaffold Skill

    no license1★ repo

    Use when creating a new SKILL.md from scratch, restructuring a draft before it becomes a stable skill, or teaching another author the canonical Skill Metadata Protocol frontmatter, body, and audit-state.json sidecar structure. Covers flat schema-conformant frontmatter, the sidecar split, v8 classification, body layout by skill intent, semantic-layer discipline (description vs activation vs Coverage), teaching-layer mechanics (TEMPLATE NOTE blockquotes), native skill-creator handoff, public/private safety, and routing-eval honesty. Do NOT use when modifying an already-written skill (edit it directly), writing general technical documentation, routing an existing request across skills, or fixing malformed library health at scale (use `skill-infrastructure`). Do NOT use for refactor my existing skill to be more concise. Do NOT use for my skill's routing isn't activating — why? Do NOT use for audit my skill library for stale frontmatter. Do NOT use for write a developer guide for the contributor docs.

  • Streaming architecture

    jacob-balslev/skill-graph/marketplace/skills/streaming-architecture Skill

    no license1★ repo

    Use when reasoning about systems that emit a sequence of values over time and consume them incrementally: the producer/stream/consumer/backpressure/termination primitives, the difference between streaming and request-response, the difference between streaming and pub-sub messaging, how WHATWG Streams, Server-Sent Events, HTTP chunked transfer, WebSockets, gRPC streaming, and React Server Component streaming compose, push vs pull backpressure, and the failure modes (slow consumer, abandoned consumer, partial-result correctness). Do NOT use for the message-history protocol between a model and a tool runtime (use tool-call-flow), browser freshness or live dashboard UX transport choice (use real-time-updates), single-response API design (use api-design), durable worker execution and retry semantics (use background-jobs), or event payload/domain-event contracts (use event-contract-design). Do NOT use for design the JSON shape and status codes for a single request-response API payload.

  • System interface contracts

    jacob-balslev/skill-graph/marketplace/skills/system-interface-contracts Skill

    no license1★ repo

    Use when defining or reviewing contracts between systems, modules, services, agents, jobs, events, APIs, or teams: ownership, inputs, outputs, invariants, compatibility, errors, idempotency, and versioning. Do NOT use for REST resource design alone (use `api-design`), async event contract detail (use `event-contract-design`), database schemas (use `entity-relationship-modeling`), or post-failure debugging (use `debugging`). Do NOT use for design the REST endpoints, status codes, and pagination. Do NOT use for create database tables and constraints. Do NOT use for investigate why this existing integration is failing in production. Do NOT use for write an ADR after the interface decision has already been accepted.

  • Theme system design

    jacob-balslev/skill-graph/marketplace/skills/theme-system-design Skill

    no license1★ repo

    Use when designing a theme system — design tokens, semantic token layering, CSS custom property strategy, runtime theme switching, and theme contract guarantees. Do NOT use for one-off color choices, brand-only palette work, or framework-specific styling-library configuration. Do NOT use for Choose the exact hex value for the brand's primary blue. Do NOT use for Configure Tailwind's content array and purge settings. Do NOT use for Implement the dark mode toggle interaction.

  • Visual design foundations

    jacob-balslev/skill-graph/marketplace/skills/visual-design-foundations Skill

    no license1★ repo

    Use when designing or auditing visual craft at foundation level: color palette, typography, spacing, elevation, rhythm, density, optical alignment, visual hierarchy direction, brand fit, contrast intent, and motion feel — making a surface more legible, polished, scannable, and tone-appropriate without changing its task structure. Do NOT use for sign-system meaning (use `semiotics`), token/component architecture (use `design-system-architecture`), responsive structure (use `layout-composition`), accessibility compliance (use `a11y`), or the DEEP contract of one dimension — formal color systems (use `color-system-design`), full type systems (use `typography-system`), deep hierarchy modeling (use `visual-hierarchy`), theming/token delivery (use `theme-system-design`), or interaction-state feedback (use `interaction-feedback`). Do NOT use for what does this icon or badge color communicate to users? Do NOT use for define semantic tokens and component variants.

  • Fallow

    itsyasirkhandev/spec-driven-development/skills/development/fallow Skill

    no license1★ repo

    Codebase intelligence for JavaScript and TypeScript. Free static layer finds unused code (files, exports, types, dependencies), code duplication, circular dependencies, complexity hotspots, architecture boundary violations, and feature flag patterns. Optional paid runtime layer (Fallow Runtime) merges production execution data into the same health report for hot-path review, cold-path deletion confidence, and stale-flag evidence. 90 framework plugins, zero configuration, sub-second static analysis. Use when asked to analyze code health, find unused code, detect duplicates, check circular dependencies, audit complexity, check architecture boundaries, detect feature flags, clean up the codebase, auto-fix issues, merge runtime coverage, or run fallow.

  • Improve codebase architecture

    itsyasirkhandev/spec-driven-development/skills/development/improve-codebase-architecture Skill

    no license1★ 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 11 other repositories

  • Improve codebase architecture

    itsyasirkhandev/spec-driven-development/skills/matt pocock/improve-codebase-architecture Skill

    no license1★ 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

  • Setup matt pocock skills

    itsyasirkhandev/spec-driven-development/skills/matt pocock/setup-matt-pocock-skills Skill

    no license1★ 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

  • Architecture diagram

    diamitani/rostr-agent/skills/creative/architecture-diagram Skill

    1★ repo

    Dark-themed SVG architecture/cloud/infra diagrams as HTML.

    The same file is in 2 other repositories

  • Codebase inspection

    diamitani/rostr-agent/skills/github/codebase-inspection Skill

    1★ repo

    Inspect codebases w/ pygount: LOC, languages, ratios.

    The same file is in 2 other repositories

  • Simplify code

    diamitani/rostr-agent/skills/software-development/simplify-code Skill

    1★ repo

    Parallel 3-agent cleanup of recent code changes.

    The same file is in 1 other repository

  • No dead code

    yli769227-jpg/agent-discipline/skills/no-dead-code Skill

    1★ repo

    Never assume dead code (cross-agent safety). Before deleting any symbol (function/class/variable/file), grep every caller. After adding a file, update the project manifest. When multiple agents edit in parallel, re-read the latest file before editing — don't trust a cached copy. Triggers when about to delete a symbol, add a source file, or edit a file that may be concurrently modified. 不假设 Dead Code:删任何符号前先 grep 所有调用方;新增文件后更新清单;多 agent 并行时编辑前先读最新文件;看到"像是没用"的符号先 grep 再说。 消歧:多文件接口改造的逐文件 build 节奏归 incremental-build,本 skill 只管"删/改符号前证明安全"。

  • Api design

    kwhorne/elyra-skills/skills/api-design Skill

    1★ repo

    Design consistent HTTP/REST endpoints with sensible naming, status codes, pagination, error formats, and versioning. Use when the user asks to design, review, or extend an HTTP API, or wants feedback on endpoint shape.

  • Architecture review

    kwhorne/elyra-skills/skills/architecture-review Skill

    1★ repo

    Evaluate a system or component design against non-functional requirements - scalability, reliability, maintainability, security, cost. Use when the user asks for an architecture review, design critique, system review, or wants to evaluate a proposed design or ADR before commit.

  • Codebase exploration

    kwhorne/elyra-skills/skills/codebase-exploration Skill

    1★ repo

    Systematically explore and understand an unfamiliar codebase - entry points, architecture, data flow, conventions, and hotspots - before changing anything. Use when the user asks how a project works, asks to onboard onto a codebase, asks "where is X handled", or before implementing in a project you haven't mapped yet.

  • Context engineering

    kwhorne/elyra-skills/skills/context-engineering Skill

    1★ repo

    Write and maintain agent context files (AGENTS.md, CLAUDE.md, .cursorrules) that actually steer coding agents - commands, conventions, architecture, and boundaries, without bloat. Use when the user wants to set up or improve agent instructions for a project, asks why an agent keeps making the same mistake, or wants to make a codebase agent-friendly.

  • Onboarding doc

    kwhorne/elyra-skills/skills/onboarding-doc Skill

    1★ repo

    Write or audit onboarding documentation so a new engineer can get productive without ambient knowledge - setup, architecture, conventions, who to ask. Use when the user asks to write onboarding docs, improve dev setup instructions, create a getting-started guide, or audit new-hire experience.

  • Refactoring

    kwhorne/elyra-skills/skills/refactoring Skill

    1★ repo

    Refactor code safely with characterization tests first, small reversible steps, and verification after each step. Use when the user asks to refactor, restructure, clean up, simplify, extract, or rename existing code.

  • Tech debt triage

    kwhorne/elyra-skills/skills/tech-debt-triage Skill

    1★ repo

    Inventory technical debt and prioritize it by interest paid, not by annoyance - quantify cost, classify, and produce a ranked paydown plan that survives contact with a roadmap. Use when the user asks what to refactor first, wants a tech debt audit, needs to justify cleanup work to stakeholders, or asks whether to fix or live with a known problem.

  • Rn bundle size

    almasumdev/awesome-react-native-agent-skills/.github/skills/performance/rn-bundle-size Skill

    no license1★ repo

    Expert guidance on shrinking React Native bundle size with Hermes bytecode, Metro config, tree shaking, and inline requires. Use when asked about bundle size, startup, or Metro configuration.

  • Codebase graph scout

    Arnie016/codex-prompt-templates/skills/codebase-graph-scout Skill

    1★ repo

    Use graph-backed or semantic codebase intelligence before editing. Use when tasks need symbol search, blast radius, affected tests, architecture health, dependency paths, large-codebase context, Roam, CodeAlive, GraphRAG, or MCP code search. Skip for tiny scripts where rg/read is enough.

  • Install agent scaffold

    designgrappler/agent-os/claude/skills/install-agent-scaffold Skill

    1★ repo

    Bootstraps a new project with the Agent OS structure.

  • Install agent scaffold

    designgrappler/agent-os/skills/install-agent-scaffold Skill

    1★ repo

    Scaffold the full Agent OS structure for a new project. Drops a setup file the user fills in — no files are generated until it's complete.

  • Wiki

    eliransu/digital-brain/skills/wiki Skill

    1★ repo

    Claude + Obsidian knowledge companion. Sets up a persistent wiki vault, scaffolds structure from a one-sentence description, and routes to specialized sub-skills. Use for setup, scaffolding, cross-project referencing, and hot cache management. Triggers on: "set up wiki", "scaffold vault", "create knowledge base", "/digital-brain:wiki", "wiki setup", "obsidian vault", "knowledge base", "second brain setup", "running notetaker", "persistent memory", "llm wiki".

  • Onboard

    Rish-Modi/career-agent/.claude/skills/onboard Skill

    no license1★ repo

    First-run setup for a fresh clone of career-agent. Bootstraps $PERSONAL, checks prerequisites (pandoc, python deps, git config), then runs a guided interview to populate personal-info, goals, impact-doc, and brag-doc. Detects partial setup and resumes. Use when the user says "/onboard", "set me up", "I just cloned the repo", "first time using this".

  • Local dev setup

    sonsriver4815/agent-skill-starter/examples/local-dev-setup Skill

    1★ repo

    Use this skill when the user asks to inspect, install, verify, or troubleshoot a local developer environment, CLI tool, plugin, shell path, or project startup workflow.

  • Local dev setup

    sonsriver4815/agent-skill-starter/src/agent_skill_starter/examples/local-dev-setup Skill

    1★ repo

    Use this skill when the user asks to inspect, install, verify, or troubleshoot a local developer environment, CLI tool, plugin, shell path, or project startup workflow.

  • Codebase design

    MarcoAntolini/cursor-sync/agents/skills/mattpocock/engineering/codebase-design Skill

    no license1★ repo

    Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

    The same file is in 19 other repositories