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

  • Starter rules

    oleg-koval/agent-skills/packages/software-development/starter-rules/adapters/claude/skills/starter-rules Skill

    4★ repo

    Load and enforce the hard rules every oleg-koval/* starter must obey. Use when starting or auditing work in saas-init, ts-npm-starter, go-starter, py-starter, or any future oleg-koval template repo. Covers functional style, 300-line file cap, E2E > unit tests, pre-commit hooks, no-comment policy, KISS/DRY/SOLID, and Vertical Slice as default architecture for SaaS/app starters.

  • Starter rules

    oleg-koval/agent-skills/packages/software-development/starter-rules/adapters/cursor/skills/starter-rules Skill

    4★ repo

    Load and enforce the hard rules every oleg-koval/* starter must obey. Use when starting or auditing work in saas-init, ts-npm-starter, go-starter, py-starter, or any future oleg-koval template repo. Covers functional style, 300-line file cap, E2E > unit tests, pre-commit hooks, no-comment policy, KISS/DRY/SOLID, and Vertical Slice as default architecture for SaaS/app starters.

  • Starter rules

    oleg-koval/agent-skills/packages/software-development/starter-rules/adapters/grok/skills/starter-rules Skill

    4★ repo

    Load and enforce the hard rules every oleg-koval/* starter must obey. Use when starting or auditing work in saas-init, ts-npm-starter, go-starter, py-starter, or any future oleg-koval template repo. Covers functional style, 300-line file cap, E2E > unit tests, pre-commit hooks, no-comment policy, KISS/DRY/SOLID, and Vertical Slice as default architecture for SaaS/app starters.

  • Fable design options

    rhein1/fable5-codex/plugins/fable5-codex/skills/fable-design-options Skill

    4★ repo

    Evidence-grounded design option generation for technical architecture, migrations, APIs, data models, safety controls, operational changes, and implementation plans. Use when the user asks for options, tradeoffs, design review, migration strategy, or a decision memo grounded in the current codebase.

  • Fable understand

    rhein1/fable5-codex/plugins/fable5-codex/skills/fable-understand Skill

    4★ repo

    Source-grounded codebase understanding for behavior, architecture, boot flow, data flow, integration wiring, or "how does this work" questions. Use when the user asks Codex to explain a system, trace a path, map a subsystem, or answer behavior questions with citations and unknowns.

  • Api contract design

    05-deepak-patidar/claude-skills/api-contract-design Skill

    4★ repo

    Designing HTTP/REST APIs, request/response shapes, error formats, versioning, pagination, idempotency, and webhooks. Use when adding or changing endpoints, integrating a frontend with a backend, designing public or partner APIs, or when the user says "API design", "endpoint", "REST", "contract", "breaking change", or "webhook".

  • Architecture design

    05-deepak-patidar/claude-skills/architecture-design Skill

    4★ repo

    Designing module, service, and layer boundaries for applications. Use when starting a new project or feature area, restructuring code, deciding monolith vs services, defining layers (API/service/data), or when the user says "architecture", "structure", "refactor the design", "how should I organize", or "design this system's components".

  • Code quality

    05-deepak-patidar/claude-skills/code-quality Skill

    4★ repo

    Writing and reviewing maintainable, correct code in any language. Use when writing new modules, reviewing code, refactoring, naming things, handling errors, or when the user says "clean this up", "code quality", "review this", "refactor", "is this good code", or "best practices".

  • Legacy code changes

    05-deepak-patidar/claude-skills/legacy-code-changes Skill

    4★ repo

    Making safe changes in unfamiliar, undertested, or legacy codebases — comprehension before modification, characterization tests, seams, and incremental replacement. Use when working in a codebase you didn't write, inheriting a project, touching code with no tests, planning a refactor of old code, or when the user says "legacy", "inherited this code", "old codebase", "nobody knows how this works", or "should we rewrite".

  • System design

    05-deepak-patidar/claude-skills/system-design Skill

    4★ repo

    End-to-end system design — scale, caching, queues, async work, consistency, resilience, capacity. Use when designing how a whole product fits together, handling load or growth, adding background jobs/queues/caches/webhooks/real-time features, or when the user says "system design", "scale", "handle more users", "cache", "queue", "async", or "high availability".

  • Init hooks

    Songhonglei/better-agent-skills/skills/init-hooks Skill

    4★ repo

    管理 OpenClaw 容器启动时自动执行的脚本钩子。gateway 重启、pod 重启、pod 重建均不丢失(数据持久化在 workspace/.init-hooks/)。 支持 inline 命令、本地脚本(shell/python)、CDN URL(zip/tar.gz 自动下载解压)三种钩子类型。 用于:新增/查看/修改/禁用/删除启动钩子、立即测试运行、查看执行日志。 触发词:init-hooks、启动钩子、startup hook、重启初始化、pod重启执行、开机自启。 安装触发词:帮我安装 init-hooks、初始化 init-hooks、设置 init-hooks、执行 init-hooks 安装。 配置变更触发词:修改 openclaw.json、改 gateway 配置、改配置文件 → 执行后自动调用 sync_openclaw_config.py。

  • Subagent timeout config

    Songhonglei/better-agent-skills/skills/subagent-timeout-config Skill

    4★ repo

    One-click subagent timeout configurator for OpenClaw. Configures the three related fields (agents.defaults.timeoutSeconds + subagents.runTimeoutSeconds + acp.runtime.ttlMinutes) atomically with built-in TTL constraint validation (ttlMinutes * 60 ≥ runTimeoutSeconds). Three preset profiles — quick (60s/1h/1h, fast feedback), normal (3min/2h/2h, everyday dev), patient (5min/3h/3h, long-running tasks) — plus --custom for arbitrary values. Auto-backup before write, optional gateway auto-restart, --dry-run preview. Triggers: "set subagent timeout", "subagent 超时", "配置 timeout", "调整超时", "subagent timeout config", "openclaw timeout", "tool call timeout".

  • Workspace git setup

    Songhonglei/better-agent-skills/skills/workspace-git-setup Skill

    4★ repo

    One-command Git tracking setup for any working directory, with a security-focused .gitignore (credentials, TLS/SSH private keys, tokens, runtime caches & PIDs, node_modules, Python caches, build artifacts, editor temp files), a large-file guard (>10MB), and a read-only --audit mode that detects tracked secrets, untracked files, and core.autocrlf misconfiguration. Three modes: (1) init — git init + safe .gitignore + first commit; (2) --audit — read-only health check (no mutations); (3) --dry-run — preview every change without applying. Reads Git identity from GIT_AUTHOR_NAME/GIT_AUTHOR_EMAIL env vars > existing git config > interactive prompt; falls back to the email prefix when only the email is provided. Workspace path resolution: CLI arg > WORKSPACE_DIR env var > current directory. Default branch is main; sets core.autocrlf=input to avoid CRLF false diffs. Trigger this skill when the user says any of: 'add git to my project', 'init git', 'git init', 'track my changes', 'version history', 'back up my workspace', 'is my repo healthy', 'audit my git repo', 'any secrets in git', 'find untracked files', 'fix git config', 'workspace git setup', 'workspace-git-setup' — or 「给项目加 git」「初始化 git」「记录我的改动」「追踪变更历史」「保存历史版本」「项目怎么做版本管理」「我改了很多东西怕丢,帮我备份」「检查 git 有没有问题」「巡检 git」「有没有敏感文件进 git」「检测漏跟踪的文件」「.gitignore 规则过期了」「修复 git 配置」 — or any other phrasing that expresses the intent to add version tracking, audit a repo's health, or guard against accidental secret leaks.

  • Pastiche init

    retz8/pastiche/dist/claude-code/skills/pastiche-init Skill

    4★ repo

    Use when bootstrapping pastiche in a frontend repo for the first time — scaffolds `pastiche/{config.yaml, FACT.md, KNOWLEDGE.md, WISDOM.md}` and extracts FACT. Single-use; refuses to overwrite. Curation happens later via `/pastiche-setup`.

  • Pastiche setup

    retz8/pastiche/dist/claude-code/skills/pastiche-setup Skill

    4★ repo

    Use when bootstrapping pastiche for first-time adoption (post-`/pastiche-init`) — fills `KNOWLEDGE.md` and seeds `[GENERAL]` `WISDOM.md` rules section by section. Resumable across sessions; re-invoke to continue.

  • Bun init

    DaleSeo/bun-skills/skills/bun-init Skill

    4★ repo

    Initialize a new Bun project with TypeScript and optimal configuration. Use when starting a new Bun project or converting a directory to a Bun project.

    The same file is in 9 other repositories

  • Auto setup

    marek-kujda/ad-copy-skill-pack/.claude/skills/auto-setup Skill

    no license4★ repo

    Bootstrap brand voice, ICP, and landing pages from your website URLs. Use when setting up the skill pack for the first time, or when onboarding a new client. Analyzes your website and pre-fills context skills automatically.

  • Yocto kernel bsp

    prashantdivate/awesome-yocto-ai-agent-skills/yocto-kernel-bsp Skill

    4★ repo

    Official-doc-first Yocto kernel and BSP workflow support for AI coding agents. Use when working on Linux kernel recipes, linux-yocto, vendor kernel integration, defconfig, kernel config fragments, device tree files, KERNEL_DEVICETREE, MACHINE configuration, BSP layers, bootloader/kernel handoff issues, COMPATIBLE_MACHINE, kernel modules, or board bring-up problems in Yocto Project and OpenEmbedded workspaces.

  • Yocto project

    prashantdivate/awesome-yocto-ai-agent-skills/yocto-project Skill

    4★ repo

    Official-doc-first Yocto Project workflow support for AI coding agents. Use when working with Yocto Project, OpenEmbedded, or Poky repositories; creating or modifying layers, recipes, images, SDKs, BSPs, machine or distro configuration, packagegroups, kernel integration, devtool workflows, builds, troubleshooting, release migration, layer compatibility, or files such as bblayers.conf, local.conf, layer.conf, image recipes, packagegroup recipes, machine .conf files, distro .conf files, kas configs, and oe-init-build-env based workspaces.

  • Community ops onboarding

    ShiroRyu9/community-ops-kit/skills/community-ops-onboarding Skill

    4★ repo

    Use when designing, auditing, or improving community newcomer journeys, onboarding questions, welcome flows, first-action prompts, start-here pages, role/access routing, activation checklists, or early retention paths across Discord, forums, Slack, product/customer communities, creator communities, or private groups.

  • Scripted command execution

    matt-bat/agent-command-center/skills/scripted-command-execution Skill

    no license4★ repo

    Use for deterministic shell automation and setup tasks (for example environment bootstrap, service orchestration, batch file operations, and repeatable local command pipelines with explicit validation).

  • Syncfusion blazor data form

    syncfusion/blazor-ui-components-skills/skills/syncfusion-blazor-data-form Skill

    no license4★ repo

    Implement Syncfusion Blazor DataForm component for creating dynamic, data-bound forms with validation and field management. Use this when building forms in Blazor with Syncfusion components, handling form validation, binding models, creating editable fields, or managing form events. This skill covers form layout customization, data binding, FormItems configuration, FormAutoGenerateItems setup, templates, events, and data annotation validation.

  • Syncfusion blazor diagram

    syncfusion/blazor-ui-components-skills/skills/syncfusion-blazor-diagram Skill

    no license4★ repo

    Build and troubleshoot Syncfusion Blazor diagrams using SfDiagramComponent. Trigger for flowcharts, org charts, mind maps, BPMN, UML sequence, swimlanes, symbol palettes, nodes/connectors/ports/annotations, layouts, data binding, serialization (load/save), export/print, and collaborative editing questions. Provide Blazor + Syncfusion setup steps, configuration patterns, and sample snippets.

  • Syncfusion blazor smart paste

    syncfusion/blazor-ui-components-skills/skills/syncfusion-blazor-smart-paste Skill

    no license4★ repo

    Set up and use the Syncfusion Blazor Smart Paste Button — AI-powered clipboard-to-form filling with OpenAI, Azure OpenAI, Ollama, or custom AI backends. Covers NuGet setup, service configuration, field annotations, button customization, and troubleshooting.

  • Syncfusion blazor treemap

    syncfusion/blazor-ui-components-skills/skills/syncfusion-blazor-treemap Skill

    no license4★ repo

    Implement and configure the Syncfusion Blazor TreeMap component (SfTreeMap) for hierarchical data visualization. Use this when working with treemaps, area-proportional visualizations, or heat-map-like block displays. This skill covers TreeMap setup, layout configuration, data binding, color mapping, drill-down navigation, and accessibility features.

  • Rest api architect

    vivek-viswanat/dev-arsenal/skills/rest-api-architect Skill

    4★ repo

    Expert in designing resource-oriented REST APIs using OpenAPI 3.1 specifications.

  • Refactor engineer

    Kshitijpalsinghtomar/depth-skills/skills/refactor-engineer Skill

    4★ repo

    Enforces characterize-before-change discipline with continuous green tests, separating structural changes from behavioral ones.

  • System architect

    Kshitijpalsinghtomar/depth-skills/skills/system-architect Skill

    4★ repo

    Forces data-model-first thinking before service boundaries or code, treating the schema as the geological layer everything else sits on.

  • Init

    rvdbreemen/adr-kit/codex/skills/init Skill

    4★ repo

    Drop-in ADR toolkit for AI coding agents (Claude Code, Cursor, Copilot, Codex). Skill + agent + instructions + template. MIT.

  • Setup

    rvdbreemen/adr-kit/codex/skills/setup Skill

    4★ repo

    Register ADR Kit in a project with a managed client instruction block and versioned local guide. Idempotent.

  • Init

    rvdbreemen/adr-kit/copilot/skills/init Skill

    4★ repo

    Drop-in ADR toolkit for AI coding agents (Claude Code, Cursor, Copilot, Codex). Skill + agent + instructions + template. MIT.

  • Setup

    rvdbreemen/adr-kit/copilot/skills/setup Skill

    4★ repo

    Register ADR Kit in a project with a managed client instruction block and versioned local guide. Idempotent.

  • Init

    rvdbreemen/adr-kit/skills/init Skill

    4★ repo

    Initialize ADR Kit in a project. Use for adr-kit init, first-time ADR setup, architecture audit, managed guidance, and the pre-commit gate.

  • Setup

    rvdbreemen/adr-kit/skills/setup Skill

    4★ repo

    The one entry point for installing ADR Kit in a project (R19). Modes: register (default), adopt (audit + propose ADRs, /adr-kit:init), hooks (/adr-kit:install-hooks), upgrade (/adr-kit:upgrade).

  • Intlayer config

    aymericzip/intlayer-skills/skills/intlayer-config Skill

    4★ repo

    Configures Intlayer project settings and environment variables. Use when the user asks to "setup intlayer.config", "configure locales", or "customize Intlayer settings".

  • Xpoz setup

    XPOZpublic/xpoz-clawhub-skills/xpoz-setup Skill

    no license4★ repo

    Set up and authenticate the Xpoz MCP server for social media intelligence. Required by all Xpoz skills. Handles server configuration, OAuth login, and connection verification with minimal user interaction.

  • Coss ui

    lukedj78/dev-flow/coss-ui Skill

    4★ repo

    Set up or extend a Next.js web app with Coss/UI — the official Cal.com design system, built on Base UI + Tailwind CSS v4, installed through the shadcn CLI via the namespaced `@coss/*` registry (copy-paste-and-own source). Two modes: Init (scaffold a new/empty project with `shadcn init @coss/style` — components, neutral tokens, sidebar vars, Inter/Geist fonts) and Add (pull primitives `@coss/ui`, single components `@coss/<name>`, or particles into an already-scaffolded project). Because Coss tokens are the SAME CSS variables as shadcn/ui, DESIGN.md tokens override them directly in globals.css. Integrates with the dev-flow contract: sets `meta.json#stack.ui = "coss"` (+ `ui_base = "base"`). Triggers: "usa Coss/UI", "coss.com/ui", "Cal.com design system", "aggiungi un componente Coss", "init @coss/style", "scaffold con Coss UI", or dev-flow routing when `stack.ui = "coss"`. Not for: writing the DESIGN.md (use figma-to-design-md / image-to-design-md), the generic Next.js scaffold internals (design-md-to-app owns those), backend modules (module-add), or React Native (RN uses NativeWind, not Coss). Caveats: requires Tailwind CSS v4 and carries a mixed MIT/AGPLv3 license — see references/deps-and-license.md.

  • Design md to app

    lukedj78/dev-flow/design-md-to-app Skill

    4★ repo

    Generate or customize a frontend application from a DESIGN.md (Google design.md spec). Reads the YAML tokens + markdown rationale and produces a working React app whose theme, typography, spacing, radii, and components are pre-styled to match. **Canonical target: Next.js 16 + App Router** (Pages Router or pre-16 explicitly refused). Supports four UI libraries: shadcn/ui (Tailwind + copy-pasted source), Base UI (Tailwind + headless library, no CLI overhead), MUI (runtime themed, Material-flavored), and Coss/UI (Cal.com design system on Base UI via the `@coss/*` shadcn registry, hands off to the `coss-ui` skill). Supports two form libraries: **TanStack Form + Zod (default, recommended)** or react-hook-form (opt-in). Integrates with the dev-flow contract: when a `.workflow/` exists, reads `meta.json#stack`, writes the app at the project root (alongside `.workflow/`), and bumps phase to `scaffolded`. Use whenever the user has a DESIGN.md and wants to scaffold an app, set up a theme, customize shadcn/Base UI/MUI from these tokens, or "use this DESIGN.md to start an app". Trigger on "DESIGN.md → app", "scaffold from design.md", "applica il DESIGN.md a shadcn / Base UI / MUI", "crea l'app dal DESIGN.md", "init shadcn con questo DESIGN.md". Always ask shadcn vs Base UI vs MUI (with a suggestion) before generating, unless `meta.json#stack.ui` already specifies one. Always defaults to Next.js 16 + App Router for the framework. Not for: scaffolding mobile apps (use rn-bootstrap for Expo + RN), writing PRDs (use prd-from-idea), or generating individual pages after the scaffold exists (use screenshot-to-page).

  • Eve agent

    lukedj78/dev-flow/eve-agent Skill

    4★ repo

    Scaffold and manage an eve agent (Vercel's filesystem-first agent framework) inside a monorepo, as the engine behind a Next.js app. Use this skill whenever the user wants to create, set up, or initialize an eve agent; add a tool, skill, channel, connection, schedule, subagent, or hook to an eve agent; wire a Next.js (or any) frontend to consume an eve agent; or evolve the `apps/agent` part of a project. Trigger this for ANY mention of "eve", "the agent engine", "agent tools", "agent backend", or building the agentic core of an app — even if the user does not say the word "skill". This is the eve counterpart to dev-flow's Next.js skills (design-md-to-app / module-add); use it for the agent the same way you'd use those for the web app. Not for: building the Next.js app itself or its pages/forms (use design-md-to-app / screenshot-to-page / module-add), scaffolding the monorepo (use monorepo-bootstrap), or React Native (eve is a server-side engine, not an RN concern).

  • Eve registry porting

    lukedj78/dev-flow/eve-registry-porting Skill

    4★ repo

    Port a component (tool, connection, or skill) from a public eve/Flue agent registry — atomeve.dev, evex.sh, agentcn, eveagents.dev, the "shadcn for agents" registries — into a multi-tenant eve app WITHOUT adopting the registry's standalone-agent runtime model. Use when the user wants to "install / use / borrow an agent from atomeve (or evex / agentcn / eveagents)", "add a Stripe/PostHog/Sentry/GitHub tool or connection from a registry", "reuse a skill from a shadcn-for-agents registry", or asks whether a registry agent is usable and how to adapt it. The skill's core is the conformance checklist that makes third-party eve code safe in a multi-tenant app: tenant from the verified session (never model input), companyId in every query, per-tenant encrypted secrets (never global env keys), verified npm deps only, sensitive actions behind tool-grants/approval. For AgentOS specifically it defers to docs/eve-registries.md. Not for: scaffolding a fresh tool/connection/skill slot from scratch (use `eve-agent` for the boilerplate), building the Next.js app or its pages (use design-md-to-app / screenshot-to-page / module-add), or wiring the monorepo (monorepo-bootstrap). This skill governs "what to port from a registry and how to make it tenant-safe", not "how to write an eve primitive".

  • Module add

    lukedj78/dev-flow/module-add Skill

    4★ repo

    Wire a backend or infrastructure module (auth, database, payments, email, file storage, deploy config) into an already-scaffolded app. Reads `.workflow/meta.json#stack` for the chosen tech (better-auth, drizzle+neon, stripe, resend, vercel, etc.) and modifies the codebase at the project root to install + configure the module end-to-end. Always idempotent — running twice does not duplicate config. Use when the user says "add auth", "wire up the database", "set up Stripe", "add file uploads", "configure deploy", "module aggiungi auth", or the orchestrator routes here from phase `scaffolded` / `page_generated`. Not for: scaffolding the app (`design-md-to-app`) or building UI (`screenshot-to-page`).

  • Monorepo add shared package

    lukedj78/dev-flow/monorepo-add-shared-package Skill

    4★ repo

    Extract logic from apps/web/ or apps/mobile/ into a new or existing shared package under packages/ in a turborepo monorepo, OR create a fresh empty shared package skeleton. Reads .workflow/meta.json with stack.framework="monorepo". Adds the package to pnpm-workspace.yaml (already covered by the wildcard), updates tsconfig.base.json path aliases, registers as workspace:* in both apps. Use to "estrai questa logica in shared", "spostala in packages/shared", "create a shared @<slug>/foo package", "factor X out of the apps". Not for: scaffolding the whole monorepo (use monorepo-bootstrap), backend modules (use module-add or rn-module-add — they install into packages/api/ automatically), generating types from a backend schema (use monorepo-sync-types).

  • Monorepo bootstrap

    lukedj78/dev-flow/monorepo-bootstrap Skill

    4★ repo

    Scaffold a turborepo monorepo, with shared packages (types, design tokens or shared UI, backend client). Uses pnpm workspaces + turborepo. Reads .workflow/meta.json with stack.framework="monorepo" and phase in {prd_drafted, design_extracted}. Supports three topologies, detected/asked in Step 1: web+mobile (Next.js web app AND an Expo + RN mobile app — the classic case), web+agent (Next.js web app + an eve agent in apps/agent, no mobile), or web-only (just the turborepo/shared-package tooling around one web app). Produces: root package.json + pnpm-workspace.yaml + turbo.json + packages/typescript-config + packages/eslint-config; apps/web/ scaffolded via design-md-to-app; apps/mobile/ scaffolded via rn-bootstrap ONLY for the web+mobile topology; packages/shared/ + packages/api/ skeletons, plus packages/design/ (web+mobile) or packages/ui/ (web-only / web+agent, shadcn monorepo layout). Always idempotent. Use when dev-flow routes here from prd_drafted+monorepo, or the user says "scaffolda il monorepo", "create a turborepo with web + mobile", "bootstrap il monorepo da PRD + DESIGN.md", "scaffolda un turborepo per web + agent eve". Not for: scaffolding only web with no monorepo tooling (use design-md-to-app), scaffolding only mobile (use rn-bootstrap), adding modules after scaffold (use module-add or rn-module-add).

  • Monorepo sync types

    lukedj78/dev-flow/monorepo-sync-types Skill

    4★ repo

    Regenerate backend types and re-export them via packages/shared/types/ in a turborepo monorepo so both apps/web/ and apps/mobile/ consume a single typed surface. Supports Supabase (via supabase gen types typescript), neon-drizzle (via drizzle-kit introspect/pull + InferSelectModel/InferInsertModel re-exports — the default DB stack), tRPC (via inference from the server router import), and custom REST (via a manual or zod-derived schema). Reads .workflow/meta.json with stack.framework="monorepo" and stack.{auth,db} populated. Use when "rigenera i tipi da Supabase", "sync DB schema to packages/shared/types", "il backend è cambiato, aggiorna i tipi", "sync types from tRPC", "sync Drizzle types after a schema change". Not for: creating shared packages from scratch (use monorepo-add-shared-package), wiring the backend client itself (use module-add or rn-module-add).

  • Promote component

    lukedj78/dev-flow/promote-component Skill

    4★ repo

    Use to refactor a React/RN component up the colocation hierarchy (L0 → L1 → L2) when its usage spreads across pages. Two modes: (1) "scan candidates" — analyzes the entire codebase, counts usages of every component under app/**/_components/ (web) or components/<feature>/ (mobile — Expo Router has no app/_components/ convention), and reports a table of promotion candidates with the Rule of Three; (2) "promote <Component>" — moves the file to the right level, updates all imports across the codebase, runs tsc --noEmit to verify, and commits atomically. Reads .workflow/meta.json#stack.framework to honor next / expo-rn / monorepo conventions, each with its own target paths. Triggers on: "promote PostCard", "scan promotion candidates", "this component is used everywhere, lift it up", "questo componente è usato in più pagine, promuovilo", "refactor components/shared/". Not for: creating new components (use design-md-to-app or screenshot-to-page or rn-add-screen), splitting compound components into a folder (that's a separate manual refactor), or moving files across different concerns (this skill is purely vertical promotion within the colocation hierarchy).

  • Rn add screen

    lukedj78/dev-flow/rn-add-screen Skill

    4★ repo

    Use to add a new screen to an existing Expo + RN app: from a description, a wireframe, or a screenshot, generate the route file in app/ (Expo Router file-based), wire up data fetching via TanStack Query if needed, apply NativeWind classes from the project DESIGN.md tokens, and respect the scaffolded folder layout. Reads .workflow/meta.json with stack.framework="expo-rn" and phase ≥ "scaffolded". Use when dev-flow routes here from scaffolded+expo-rn, or the user says "add a login screen", "create a profile screen from this screenshot", "aggiungi una schermata X". Not for: scaffolding the app (rn-bootstrap), adding backend modules (rn-module-add Wave 3), pure styling changes to an existing screen (rn-styling).

  • Rn bootstrap

    lukedj78/dev-flow/rn-bootstrap Skill

    4★ repo

    Scaffold a new Expo + React Native app from a PROJECT.md + PRD.md + DESIGN.md using the opinionated stack (Expo Router, TypeScript, NativeWind v4, Zustand, TanStack Query, Reanimated, expo-image, FlashList). Reads .workflow/meta.json with stack.framework="expo-rn" and phase in {prd_drafted, design_extracted}. Produces a running Expo app at the project root, sets phase to "scaffolded". Always idempotent: re-running detects existing files and skips. Use when dev-flow routes here from prd_drafted+expo-rn, or the user says "scaffolda app expo from PRD", "create RN app from this PRD/DESIGN", "bootstrap expo app". Not for: adding screens (rn-add-screen, Wave 2), modules (rn-module-add, Wave 3), Next.js scaffolding (design-md-to-app — different stack).

  • Rn eas build submit update

    lukedj78/dev-flow/rn-eas-build-submit-update Skill

    4★ repo

    Use for cloud builds and OTA updates of an Expo + RN app via EAS: configuring eas.json profiles (development/preview/production), managing credentials (APNs key, Android keystore) without committing them to git, submitting builds to App Store Connect / Google Play via EAS Submit, shipping JS-only fixes via EAS Update with channels/branches, EAS Workflows for CI. Triggers on: "set up EAS Build", "OTA update", "EAS Submit", "configure eas.json", "deploy to Play Store / TestFlight". Not for: store metadata/screenshots/IAP (rn-publishing-payments), scaffolding (rn-bootstrap), or the end-to-end deploy orchestration (rn-eas-deploy).

  • Rn module add

    lukedj78/dev-flow/rn-module-add Skill

    4★ repo

    Use to wire a backend/infra module (auth, db, storage, realtime, push, payments) into a scaffolded Expo + RN app. Reads .workflow/meta.json with stack.framework="expo-rn" and the user-chosen provider for each module (Supabase, Firebase, custom REST, tRPC, RevenueCat). Installs deps, generates the wiring code (lib/auth.ts, lib/supabase.ts, etc.), updates meta.json#stack to record the choice. Always idempotent. Triggers on: "add auth", "wire up db", "set up Supabase", "set up Firebase", "add payments", "add push" (the server-side part), "aggiungi modulo X". Not for: building UI for the module (rn-add-screen does the login screen, etc.), client-side knowledge only (rn-backend, rn-push-notifications), scaffolding (rn-bootstrap).

  • Rn upgrade

    lukedj78/dev-flow/rn-upgrade Skill

    4★ repo

    Use to upgrade an existing Expo + RN project to a newer Expo SDK: bump `expo` and run `npx expo install --fix` to align every dependency, run `npx expo-doctor` for diagnostics, clear `node_modules`/`.expo`/Watchman caches, and native-rebuild (`expo prebuild --clean` + `pod install` + `gradlew clean`) only for bare-workflow projects — skip entirely for CNG (Continuous Native Generation) projects. Walks a breaking-changes checklist (removed APIs, moved imports, deprecated native modules like `expo-av` → `expo-audio` + `expo-video`) and supports beta/preview SDK upgrades via the `@next` tag. Reads `.workflow/meta.json` with `stack.framework="expo-rn"`; does NOT bump `phase` (this is a maintenance operation, not a pipeline step) but appends to `history`. Triggers on: "upgrade Expo SDK", "upgrade to Expo SDK 54", "bump expo version", "npx expo-doctor is failing", "upgrade React Native", "aggiorna Expo", "aggiorna il progetto RN", "expo install --fix". Not for: scaffolding a new app (`rn-bootstrap`), adding a new screen (`rn-add-screen`), adding a backend/infra module (`rn-module-add`), or building/submitting to stores (`rn-eas-deploy`, `rn-eas-build-submit-update`).

  • Write tests

    lukedj78/dev-flow/write-tests Skill

    4★ repo

    Write Vitest unit/integration tests OR Playwright e2e tests for an existing source file (server action, page, component, query). Reads the project's wired test framework from `.workflow/meta.json#stack.test`, follows the mocking patterns already present in `vitest.setup.ts` and any sibling test files. Use when the user says "scrivi i test per X", "test per la server action Y", "e2e per /clienti", "unit test per il componente Z", "add tests for <file>", or after `screenshot-to-page` / `module-add` runs and the user wants coverage. Not for: scaffolding the test infrastructure (`module-add test`), running QA on a deployed site (`qa`), or methodology guidance (`superpowers:test-driven-development`).

  • Architecture review

    ntaffzii/Skill-Agents/skills/engineering/architecture-review Skill

    4★ repo

    Architecture review skill for evaluating codebase design, module boundaries, coupling, test seams, domain language, and simplification opportunities. Use when the user asks to improve architecture, zoom out, reduce complexity, untangle code, or review a design.

  • Project discovery

    ntaffzii/Skill-Agents/skills/research/project-discovery Skill

    4★ repo

    Explore and summarize an unfamiliar or existing project before planning, editing, onboarding, architecture review, migration, stack choice, or implementation. Use when the user asks to understand a repo, inspect architecture, map a codebase, discover project conventions, or prepare a project overview.

  • Employee onboarding designer

    Adri3l-R3nan/cognify-skills/.github/skills/employee-onboarding-designer Skill

    no license4★ repo

    Designs structured employee onboarding programs that reduce time-to-productivity and improve retention. Creates day-by-day onboarding plans, training checklists, milestone assessments, and 30/60/90 day success criteria tailored to the role type.

  • Color

    Dragoon0x/dragoon-skills/skills/color Skill

    4★ repo

    Generate a color palette token file (CSS variables, tailwind config, or JS module) from the palette detected by /scan. Uses inferred role names (foreground, background, accent, danger, etc.) where possible, numeric fallback otherwise. Use when the user wants to formalize color tokens, extract a palette from existing code, or scaffold a color system. Defaults to dry-run preview; pass --apply to write. Run as `node ~/.claude/skills/dragoon/skills/color/scripts/color.js`.

  • Map

    Dragoon0x/dragoon-skills/skills/map Skill

    4★ repo

    Architecture overview of the codebase. Reports total file/line/byte counts, top hot files (most imported), largest files by line count, orphan files (imported by nobody), and most-used external dependencies. Pure regex on import statements, no AST. Use to understand a new codebase, find dead code, or audit dependency surface. Run as `node ~/.claude/skills/dragoon/skills/map/scripts/map.js [root]`.

  • Storybook

    Dragoon0x/dragoon-skills/skills/storybook Skill

    4★ repo

    Scaffold storybook config (.storybook/main.ts, preview.ts) plus auto-generated *.stories.tsx files for every PascalCase component in the codebase that has a matching named export. Caps at 50 components per run. dragoon does NOT install storybook - run `npx storybook init` after. Use to bootstrap stories quickly across an existing component library. Run as `node ~/.claude/skills/dragoon/skills/storybook/scripts/storybook.js`.

  • Typography

    Dragoon0x/dragoon-skills/skills/typography Skill

    4★ repo

    Generate a type scale token file (CSS variables, tailwind config, or JS module) anchored on the type ratio detected by /scan. Use when the user wants to formalize their typography system, extract a scale from existing code, or scaffold typography tokens. Defaults to dry-run preview; pass --apply to write. Auto-picks format based on stack: tailwind for tailwind projects, JS module for JS-heavy stacks, CSS variables otherwise. Run as `node ~/.claude/skills/dragoon/skills/typography/scripts/typography.js`.

  • Google play setup

    Ampli-Group/agentic-mobile-blueprint/.agents/skills/google-play-setup Skill

    4★ repo

    Set up Google Play Console, create an Android app listing, configure EAS credentials for Android builds, and set up the service account for CI/CD submissions. Use when publishing a new Android app, setting up Play Store automation, or troubleshooting AAB uploads.

  • Social auth setup

    Ampli-Group/agentic-mobile-blueprint/.agents/skills/social-auth-setup Skill

    4★ repo

    Configure Sign in with Apple and Sign in with Google for Supabase Auth. Use when adding social login, troubleshooting OAuth redirects, setting up Apple Services ID, Google OAuth credentials, or linking Google Play Console to Google Cloud.