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

  • Figma to component

    vipincode/exr-agent-skills/.claude/skills/figma-to-component Skill

    no license0★ repo

    Turn a Figma frame or node (via the Figma MCP) into production-grade Next.js + TypeScript + Tailwind + shadcn/ui components, WITHOUT creating duplicates — it scans MODULE_REGISTRY.md and the shared/feature trees first and reuses or extends what exists, places each new piece correctly (generic/reusable → components/shared, domain-specific → features/<name>/components), styles with Tailwind utilities + theme tokens, animates with Tailwind/CSS or framer-motion, exports assets, and registers new shared components. Use this whenever the user wants to build/implement/convert a Figma design, frame, screen, section, or component into React/Next.js code — phrases like "turn this figma frame into a component", "build this design", "implement this figma node", "code this screen from figma", "figma to react/next", or pasting a figma.com link and asking for components. This is the Figma design-to-code component builder — when the design source is an HTML file/URL use html-to-component, and when it is another existing codebase/repo on disk use project-to-component. It does NOT set up the global theme/colors/fonts (that is font-theme-setup) and does NOT scaffold a project (that is nextjs-bootstrap). Requires the Figma MCP connected, a node-specific Figma URL, and an existing Next.js + shadcn project with the contract files.

  • Font theme setup

    vipincode/exr-agent-skills/.claude/skills/font-theme-setup Skill

    no license0★ repo

    Extract a design system's tokens from a Figma file (via the Figma MCP) and apply them to a Next.js + Tailwind v4 + shadcn/ui project's THEME — rewriting globals.css color tokens in oklch, wiring fonts in layout.tsx (next/font Google + local custom fonts), and setting radius, shadows, spacing, line-heights, gradients, and background images. Use this whenever the user wants to set up or update the theme / design tokens / colors / typography / fonts from a Figma link — phrases like "set up the theme from this figma", "apply these design tokens", "update the colors and fonts from figma", "convert the palette to oklch", "configure the shadcn theme", or "wire up the fonts". This is the frontend theming skill — it edits globals.css + layout.tsx + tailwind theme, it does NOT build pages or components from a frame (that is figma-to-component) and does NOT scaffold the project (that is nextjs-bootstrap). Runs once per project (re-run to refresh tokens). Requires the Figma MCP to be connected and a Figma file/frame URL.

  • Skill snapshot v1

    vipincode/exr-agent-skills/.claude/skills/frontend-feature-planner-workspace/skill-snapshot-v1 Skill

    no license0★ repo

    Plan how an already-designed Next.js/React frontend feature will BIND to a backend API — before any binding code is written. Use this whenever the user has a built (or in-progress) design and wants to wire it to an endpoint: "plan the products API binding", "wire up the orders screen to the API", "bind this design to the auth endpoints", "how do I connect this page to the backend", "make this design functional with the API", or simply names an API/endpoint to hook a frontend feature to. Its signature move: it reads the REAL backend (monorepo source first, then the backend's contract files, then an OpenAPI/Swagger spec, then a user-pasted sample) to learn the actual endpoints, request/response envelope, auth, and validation — so the plan binds to ground truth instead of a guessed contract. It reads the frontend ARCHITECTURE.md + MODULE_REGISTRY.md, maps which existing design components consume which fields, and writes an editable _docs/FEATURE_PLAN_<name>.md (types, Zod schemas, BFF routes, axios api fns, TanStack Query hooks, data-binding map). It does NOT write binding code (that is frontend-module-builder), does NOT build the design/components (that is figma-to-component / html-to-component), does NOT write tests (frontend-test-writer), and is NOT for backend/server planning (that is backend-feature-planner). Frontend / Next.js / React / API-binding scope only.

  • Html to component

    vipincode/exr-agent-skills/.claude/skills/html-to-component Skill

    no license0★ repo

    Turn an HTML file, a pasted HTML section, or a live URL into a production-grade Next.js + TypeScript + Tailwind + shadcn/ui design — in two phases. (1) THEME — extract the design's tokens (colors → oklch, typography, fonts, radius, shadows, spacing, gradients, background images) and apply them to globals.css + wire fonts in layout.tsx. (2) COMPONENTS — turn the markup into components WITHOUT creating duplicates, scanning MODULE_REGISTRY.md and the shared/feature trees first and reusing/extending what exists, placing generic pieces (header, navbar, hero, small-hero, carousel, charts, sidebar, avatar, logo, banner …) in components/shared and domain-specific ones in features/<name>/components, styling with Tailwind utilities + theme tokens, animating with Tailwind/CSS or framer-motion, and registering new shared components. Use this whenever the user wants to convert/implement/build HTML into React/Next.js — phrases like "turn this HTML into a component", "build this html section", "convert design.html to next.js", "code this markup", "html to react/next", or when they point at an .html file (often in _docs/designs/) or paste a chunk of HTML/CSS and want components. Looks for design files in _docs/designs/ by default. Builds INTO an existing Next.js + shadcn project (scaffold first with nextjs-bootstrap; this skill does NOT scaffold). It is the HTML counterpart to figma-to-component (source = Figma) and project-to-component (source = an existing codebase/repo on disk) — reach for those when the source isn't an HTML file/section/URL.

  • Nextjs bootstrap

    vipincode/exr-agent-skills/.claude/skills/nextjs-bootstrap Skill

    no license0★ repo

    Scaffold a new production-grade Next.js (App Router) + TypeScript + Tailwind + shadcn/ui frontend from scratch, wired to a separate API backend (e.g. Express) via a BFF proxy, with axios, Zod, TanStack Query, and React Hook Form. Use this whenever the user wants to start a new Next.js / React frontend, bootstrap a web client/UI, set up a shadcn starter, or initialize a frontend project — even if they only say "new frontend", "Next.js starter", "React app", "admin dashboard UI", or name the stack loosely. It scaffolds the infrastructure ONCE per project and emits the two source-of-truth files (ARCHITECTURE.md and MODULE_REGISTRY.md) that the future frontend-* skills depend on. Do NOT use this to add a feature/page to an existing project (that is frontend-feature-planner + frontend-module-builder) or to write tests. This scaffolds a Next.js + React frontend specifically — do NOT use it to bootstrap a backend/API (that is express-ts-bootstrap) or projects in other frontend stacks (Vite/CRA/Remix/Vue/Svelte/Angular); those are out of scope.

  • Project to component

    vipincode/exr-agent-skills/.claude/skills/project-to-component Skill

    no license0★ repo

    Port a page, screen, or design language from ANY existing codebase into a production-grade Next.js + TypeScript + Tailwind + shadcn/ui page in the current project — the source being another repo/folder on disk (a static design mock, an old app, a legacy frontend — CSS Modules, styled-components, SCSS, plain CSS, Vue, older React/Next, or a Tailwind app with different conventions). Use this whenever the user points at an existing project as the design source — "copy the dashboard from <path/repo>", "port /admin/orders from our old app", "make this route match <project>", "rebuild this screen from <codebase>", "migrate these pages into the new frontend", "make our page look like project X". It reads the source READ-ONLY, derives a reusable translation map (source colors/fonts/spacing → the target's oklch theme tokens; source custom UI → shadcn/ui + shared components), lifts the source theme first when the target still has the stock shadcn theme, then builds dedup-first — scanning ARCHITECTURE.md + MODULE_REGISTRY.md and the shared/feature trees, reusing/extending before creating, placing generic pieces in components/shared and domain-specific ones in features/<name>/components, and registering new shared pieces. It is the codebase counterpart to figma-to-component (source = Figma) and html-to-component (source = a single HTML file/URL) — reach for those when the source isn't a project. Builds INTO an existing Next.js + shadcn project with the contract files; it does NOT scaffold (nextjs-bootstrap) and does NOT bind APIs (frontend-module-builder).

  • Reality check

    scoobydrew83/skills/plugins/coordinated-skills/skills/reality-check Skill

    0★ repo

    Pressure-test an AI-generated technical plan, recommendation set, setup guide, or tool/config list for hallucinations, factual errors, and unnecessary complexity, then verify the surviving claims against live sources before the user acts on them. Use whenever the user pastes recommendations, an implementation plan, a tooling/MCP/package list, install commands, or config and says "validate this", "fact-check this", "is this real/accurate", "did it hallucinate", "sanity-check this", "pressure-test this", "is this overkill", or asks whether a plan is feasible and worth doing. Especially trigger when the content looks AI-generated and is dense with checkable specifics (package names, repo URLs, CLI flags, file paths, versions, env vars, named "best-practice" patterns, time estimates) that could be fabricated. This is for VERIFYING the accuracy and practical value of an EXISTING plan, not for choosing between open options or deciding from scratch (use a decision/council skill for that).

  • System prompt builder

    scoobydrew83/skills/plugins/coordinated-skills/skills/system-prompt-builder Skill

    0★ repo

    Interview-driven builder for enterprise-grade AI system prompts and agent architectures. Use whenever the user wants to design, build, scaffold, or rebuild a system prompt, custom assistant, AI agent, project instructions, custom GPT, multi-agent system, or any reusable LLM instruction set. Trigger on phrases like "build me a prompt system", "design an agent", "write system instructions", "turn this into an agent", "create project instructions", "I want an AI that does X reliably", or any request to architect how an AI should behave across many future interactions — even when the user never says the words "system prompt." Also trigger when the user pastes an existing system prompt and wants it rebuilt, hardened, or extended.

  • Client onboarding os

    search-atlas-group/amm-founding-circle/skills/client-onboarding-os Skill

    0★ repo

    Orchestrate the first 90 days of a new SEO/AEO client engagement — from pre-kickoff access gathering through Day 90 quarterly re-planning. Produces a week-by-week schedule that runs foundational skills (Brand Kit, SERP Intent Decoder) in Weeks 1-2, diagnostic audits (LLM Citation Audit, Entity & Topical Authority Mapper, GBP Competitor Audit or Internal Linking Auditor or Competitor Content Gap depending on business type and engagement scope) in Weeks 3-5, consolidation into the first 90-day plan via AEO/LLM Content Planner in Week 6, and structured execution with Day-30/60/90 checkpoints through the remainder. Routes every actual audit or fix to the specific skill that does the work — this skill is pure sequencing. Use whenever an agency, consultant, or in-house lead is taking on a brand-new client or starting a greenfield AEO/SEO engagement, or whenever someone asks "where do I start with a new client," "what's the onboarding process," "how do I kick off this engagement," "first 90 days for new client," "SEO onboarding checklist," or "AEO consulting onboarding." Chains with every other skill in the pack via sequential invocation; output serves as the engagement's master schedule. When a SearchAtlas MCP is connected, leverages SA tools (rank tracking, brand vault, GBP, OTTO, LLM Visibility) first before falling back to generic web search.

  • Codebase map

    search-atlas-group/amm-founding-circle/skills/codebase-map Skill

    0★ repo

    Generate or refresh a codebase structural map for the current repo. Use proactively when entering a repo that lacks .claude/codebase-map.md, or when the user asks to map/index a codebase.

  • Share your foundation

    search-atlas-group/amm-founding-circle/skills/share-your-foundation Skill

    0★ repo

    Package the rules, skills, and brand you built in Levels 1–3 into one repo a teammate — or your own second machine — clones and runs a single install command against, so everyone runs the exact same agent setup instead of reinventing it. Turns "here's my setup, good luck" into "clone this, run ./install.sh, you're me." Use when you want to onboard a teammate onto your agent stack, when your own setup won't follow you between machines (your CLAUDE.md / skills / brand kit live on one laptop and not the other), when you keep re-sending config over Slack, or when you're on Level 4 and the "share the foundation with your team" step has nothing runnable behind it.

  • Karvey init

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-init Skill

    0★ repo

    Initialize a new Karvey spec. Creates the directory structure, spec.json, and registers the Epic in ClickUp (or PLAN.md if not using ClickUp). Use after karvey-grill or when starting a new feature. Triggers include "karvey init", "iniciar spec", "init spec", "nueva feature", "new feature", "nuevo cambio", "new change", "spec-driven", "SDD", "kiro", "cc-sdd", "gstack", "Garry Tan", "PRD", "iniciar proyecto spec-driven", "start spec-driven project", "nuevo método", "new method", "scaffolding".

  • Configure

    rifatshampod/vibeops/skills/configure Skill

    0★ repo

    Set up or change how a project gets deployed by asking the user simple questions and saving the answers to a config file. Use after assessing a project, or whenever the user wants to choose or change their hosting or deployment setup. Also triggers on: "configure my app", "set up hosting", "change my setup", "pick a platform", "I want to use Railway", "start the setup".

  • Technical spec

    SkillMedev/product-manager-stack/skills/technical-spec Skill

    0★ repo

    Writes 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

  • Remotion setup

    SkillMedev/remotion-video-production/skills/remotion-setup Skill

    0★ repo

    Scaffolds 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

  • Setup browser cookies

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/gstack/setup-browser-cookies Skill

    no license0★ repo

    Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages.

  • N8n node configuration

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/n8n-skills/skills/n8n-node-configuration Skill

    no license0★ repo

    Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type.

    The same file is in 2 other repositories

  • Setup browser cookies

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/setup-browser-cookies Skill

    no license0★ repo

    Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages.

  • Simmer setup

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/simmer-setup Skill

    no license0★ repo

    Setup subskill for simmer. Inspects the artifact or workspace, infers evaluation contracts and search space, proposes a complete assessment to the user, and produces a setup brief after confirmation. Conversational, not form-based — the agent does the work of understanding the problem, then presents what it found. Do not invoke directly — called by simmer orchestrator.

    The same file is in 1 other repository

  • React core

    LaoitdevOpen/laoitdev-skills/skills/frontend/react-core Skill

    0★ repo

    How to implement the src/core folder — app-level infrastructure shared by every feature. Covers folder structure, Axios config with auth interceptors, QueryClient, router config, i18n setup, theme, AuthContext, SnackbarContext, ThemeContext, type-safe storage utility, Zustand layout store, and main.tsx provider composition. Use whenever setting up a new project, adding a new core concern, or modifying any of these foundational files.

  • Salesforce help navigator

    ayanme/salesforce-navigator-suite/skills/salesforce-help-navigator Skill

    0★ repo

    This Navigator researches Salesforce configuration, administration, and setup from official Salesforce documentation. Use when the user asks how to configure, administer, or set up Salesforce: permissions, profiles, sharing rules, licensing, editions, feature availability, Prompt Builder, Agentforce setup, Data Cloud setup, Identity Resolution, Flow, Marketing Cloud Personalization, CRM Analytics configuration, and MuleSoft/Anypoint Platform configuration.

  • Operator help

    mohitkhandelwal242/ai-pm-operator/.claude/skills/operator-help Skill

    no license0★ repo

    Discovery guide for the AI-PM Operator — answers 'what can you do for me?'. Lists every installed skill grouped by PM job-to-be-done and recommends a tailored starter set based on the user's business.json (business type, platforms, revenue model). Use when the user says '/help', 'help', 'what can you do', 'which skill', 'what skills do I have', 'list skills', 'getting started', 'where do I start', or seems unsure what to run.

  • Operator onboarding

    mohitkhandelwal242/ai-pm-operator/.claude/skills/operator-onboarding Skill

    no license0★ repo

    First-run setup for AI-PM Operator. Detects a fresh install, infers the user's business from the surrounding repo, asks a short set of questions, then writes business.json / .env / team.json and tailors every skill to the user's business. Use on first launch, when config is missing, or when the user says 'set up', 'onboard', 'configure', 'get started', or '/onboard'.

  • Manuscript profile setup

    dinaf2026-web/manuscript-editorial-suite/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

  • Systems architect

    bispeklolik/optika/skills/systems-architect Skill

    0★ repo

    Архитектор Системных Связей — аналитическая линза для глубокой деконструкции и СИСТЕМНОГО решения задач: код, геймдизайн и баланс, сценаристика/лор, философия, бизнес-логика. Не латает симптом — вскрывает скрытую систему за ним и перестраивает фундамент так, чтобы проблема стала невозможной by design. Включай, когда пользователь просит: «архитектор», «системный архитектор», «деконструируй», «разбери по слоям», «разложи по слоям», «фасад и движок», «в чём корневая причина», «в чём истинная причина», «системно перестрой», «перепроектируй фундамент», «спроектируй заново», «реши класс проблемы», «сделай проблему невозможной», «убери саму возможность бага», «не лечи симптом», «копни глубже», «почему это ломается на самом деле», «кто выгодоприобретатель», «cui bono»; либо по-английски: systems architect, deconstruct, root cause, root-cause redesign, architecture, system design, refactor the root cause, redesign from first principles, fix the whole class of bugs, facade vs engine, teleology, cui bono. Контексты применения: сложные и повторяющиеся баги и рефакторинг (утечки состояния, гонки данных, сильная связность, нарушение контрактов, порядок инициализации); геймдизайн и экономика баланса (механики, эксплойты, прогрессия, саморегуляция); сценаристика и внутренняя непротиворечивость лора (противоречия, мотивация, надуманный нарратив как заплатка); философия и концептуальные разборы; бизнес-логика, процессы и обратные связи. Не для мелких правок, честно решаемых одной строкой, и не для вопросов «как синтаксис X» — только там, где нужно вскрыть систему за симптомом.

  • Ponytail

    aarshsharma2803-stack/optimusprime/skills/ponytail Skill

    0★ repo

    Code minimalism — no premature abstractions, no speculative features, smallest correct implementation only. Auto-activates when complexity budget is minimal or user asks for simpler/smaller code. Trigger: complexity_budget:minimal, goal contains refactor/simplify/minimize/clean/slim, or user says "keep it simple", "no abstractions", "smaller diff".

  • Design system

    digitaldreams/tuhin/skills/design-system Skill

    0★ repo

    Analyzes the project and generates a custom, opinionated design system with Tailwind CSS CSS-first configuration (@theme), writing tasks/design_system.md from requirements, wireframes, information architecture, and the frozen architecture. Use whenever the user says "design system", "design tokens", or "set up the Tailwind theme".

  • Information architecture

    digitaldreams/tuhin/skills/information-architecture Skill

    0★ repo

    Generates the information architecture — sitemap, page inventory, navigation, access control, URL rules — from tasks/user_journeys.md and tasks/requirements.md, writing tasks/information_architecture.md. Use whenever the user says "information architecture", "IA", "site map", or "navigation structure".

  • System design

    digitaldreams/tuhin/skills/system-design Skill

    0★ repo

    Turns frozen architecture decisions into a behavioral blueprint: component contracts, API design, key flows, data flow, applied patterns, failure handling. Reads tasks/architecture.md and tasks/requirements.md, writes tasks/system_design.md. Use whenever the user says "system design", "create the system design doc", or as the SDLC pipeline step after architecture.

  • Task breakdown

    digitaldreams/tuhin/skills/task-breakdown Skill

    0★ repo

    Breaks analyzed requirements down into Epics and vertically-sliced actionable tasks, writing the tasks/epics.md planning document from requirements, architecture, system design, IA, and journeys. Use whenever the user says "break down the requirements", "epics and tasks", or "create the development task breakdown". Never writes tasks/tasks.md — that board belongs to the task-manager agent, which converts epics into board tasks.

  • Vsa

    digitaldreams/tuhin/skills/vsa Skill

    0★ repo

    Vertical Slice Architecture guardian, two modes. PLACE mode: decide where a new class, event, DTO, or module belongs under VSA rules, or design a new module/slice map from scratch. AUDIT mode: scan for slice-isolation violations (cross-slice imports, cross-module coupling, misplaced events) and prescribe the move that fixes each. Use whenever the user says "VSA", "which slice", "where does this class go", "slice isolation", "organize the slices", "cross-slice import", "should this move to module root", or asks how to structure a feature in a slice-based codebase.

  • System architecture translator

    jpoindexter/design-case-study-skills/skills/system-architecture-translator Skill

    0★ repo

    Translate data flows, services, queues, workflows, storage, consistency, latency, failures, retries, and distributed-system constraints into visible product and UX decisions for a case study. Use for AI agents, desktop tools, data products, scraping engines, background jobs, cloud systems, or any portfolio story where architecture determines telemetry, state management, loading, recovery, permissions, or user control.

  • Bokun setup

    duongxthanh/claude-bokun-skills/skills/bokun-setup Skill

    0★ repo

    One-time setup for the bokun-* skills — discovers your Bokun vendor account through the browser (extranet subdomain, experiences and their IDs, departure type, capacity, currency, sales channels) and writes bokun.config.md that every other bokun skill reads. Use when bokun.config.md is missing, or after adding/changing experiences.

  • Codebase audit

    lankyjo/lankyjo-core-skills/skills/code/codebase-audit Skill

    no license0★ repo

    Audits a software codebase across 29 dimensions — security, privacy, accessibility, sector compliance (HIPAA/PCI/SOC 2/ISO 27001/FedRAMP/COPPA/ FERPA/GLBA/EU AI Act/NIS2/DORA/Quebec Law 25/etc.), architecture, testing, dependencies, code reuse / consolidation, workaround / root-cause detection, performance, speed, DevOps, cost, engineering practice, UX, product gaps, frontend modernization, i18n, SEO, AI/ML, and product-type platform idioms. Produces structured docs under `/docs/audits/` and files real remediation tickets. Use for any audit / review / analysis request, including narrow asks like "security review", "is this accessible", "are we GDPR/HIPAA/PCI/SOC 2 compliant", "is the app slow", "is this ready to ship", "audit our deployment", "find product gaps", "is our SEO any good", "are our deps current", "are we overpaying for infra", "can a new dev onboard". The `/audit` command is the user-facing entry point.

  • Codebase memory

    lankyjo/lankyjo-core-skills/skills/code/codebase-memory Skill

    no license0★ repo

    Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher query examples, edge types, how to use search_graph.

    The same file is in 1 other repository

  • Codebase to course

    lankyjo/lankyjo-core-skills/skills/code/codebase-to-course Skill

    no license0★ 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.

  • Improve codebase architecture

    lankyjo/lankyjo-core-skills/skills/code/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

  • Setup matt pocock skills

    lankyjo/lankyjo-core-skills/skills/code/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

  • Css architecture

    jgamaraalv/delivery-loop/.claude/skills/css-architecture Skill

    0★ repo

    Organize CSS using BEM, SMACSS, and CSS-in-JS patterns. Use when building scalable, maintainable styling systems with proper naming conventions.

  • Refactor

    jgamaraalv/delivery-loop/.claude/skills/refactor Skill

    0★ repo

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

  • System design

    jgamaraalv/delivery-loop/.claude/skills/system-design Skill

    0★ repo

    Design scalable distributed systems — load balancing, caching, database scaling, message queues, capacity estimation. Use for "system design", "scale this", "high availability", "rate limiter", or choosing microservices vs monolith.

  • Vite

    jgamaraalv/delivery-loop/.claude/skills/vite Skill

    0★ repo

    Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.

    The same file is in 8 other repositories

  • Github issues setup

    DazzleML/dazzle-claude-code-config/dotclaude/skills/github-issues-setup Skill

    0★ repo

    Initialize standard GitHub issues (#1 Roadmap, #2 Quick Notes) with the canonical label set for a new project.

  • Repokit setup

    DazzleML/dazzle-claude-code-config/dotclaude/skills/repokit-setup Skill

    0★ repo

    Set up a new project using DazzleTools git-repokit-template and git-repokit-common. Creates repo, adds subtree, initializes standard structure.

  • Client onboarding system

    SkillMedev/agency-operating-system/skills/client-onboarding-system Skill

    0★ repo

    Runs 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

  • Phase project init

    awjackson2/phase-skills/phase-project-init Skill

    0★ repo

    Use to bootstrap a fresh project for the phase-driven workflow. Trigger when the user is starting a brand-new project, says "initialize the project", "set up the project", "bootstrap this repo", "set up the phase workflow here", "phase init", or otherwise wants the scaffolding (git, development directories, phase-log templates) in place before any phase work begins. Sets up git, the development/phase_log/ structure, the plan/log/index templates, and the conventions the phase-tracker and phase-recap skills expect, then hands off to phase-tracker or phase-loop for the first phase.

  • Api contract guardian

    willianbs/skills/api-contract-guardian Skill

    0★ repo

    Guards OpenAPI/proto/GraphQL contracts against breaking changes and drift from implementation. Use on API PRs and releases. Emits CONTRACT_REPORT. Never rubber-stamps breaking changes without a versioning/migration plan.

  • Guardrails configurator

    willianbs/skills/guardrails-configurator Skill

    0★ repo

    Interviews you to configure project engineering guardrails (code, architecture, security, testing, git/PR, ops, AI agent behavior) and writes them to a durable project file. Use for greenfield setup, “set our rules”, or refreshing standards. Emits GUARDRAILS_CONFIG. Never invents team policy as fact, never overwrites an existing guardrails file without confirmation, and never starts feature work.

  • Refactoring advisor

    willianbs/skills/refactoring-advisor Skill

    0★ repo

    Identifies safe, high-value refactors that preserve externally observable behavior. Use for debt, smells, or “clean this up” asks. Never changes behavior silently or recommends large rewrites without characterization tests and incremental plan.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-commercial-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-commercial-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-consumer-product-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-consumer-product-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-corporate-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-corporate-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-criminal-specialty-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-criminal-specialty-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-education-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-education-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-employment-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-employment-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-energy-utilities-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-energy-utilities-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-family-personal-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-family-personal-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-general-statutes/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-general-statutes. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-health-pharma-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-health-pharma-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-insurance-legal/skills/cold-start-interview Skill

    0★ repo

    Mandatory first-run setup interview for bd-insurance-legal. Use when the plugin is freshly installed, when config still shows [PLACEHOLDER], or when the user says "set up", "configure", or "interview". Writes the practice profile that every other skill in this plugin reads before doing substantive work.