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

  • Official runtime setup guide

    ThanhNguyxnOrg/blendops/skills/official-runtime-setup-guide Skill

    4★ repo

    Establish official runtime prerequisites and setup boundaries before any Blender execution claim.

  • Clean architecture

    tbc-servicos/dataagile-agent-kit/fluig/skills/clean-architecture Skill

    4★ repo

    Aplica os princípios de Clean Architecture (livro de Robert Martin, o Uncle Bob) ao desenvolvimento Fluig — regra de dependência e camadas no widget Angular + PO-UI (component → service de aplicação → domínio puro → adapter HTTP/Dataset), datasets server-side e eventos de workflow como adaptadores finos, SOLID em TypeScript com a DI do Angular. Use quando o dev pedir para "organizar o widget em camadas", "desacoplar regra de negócio do componente", "aplicar clean architecture", "aplicar SOLID", "onde colocar essa regra", "dataset está gigante" ou quando o brainstorm/plan/review precisar de critério estrutural de design.

  • Init project

    tbc-servicos/dataagile-agent-kit/fluig/skills/init-project Skill

    4★ repo

    Inicializa um projeto Fluig — entrevista o desenvolvedor e gera CLAUDE.md com contexto do cliente (URL servidor, prefixos, ambiente, integração Protheus). Invoque explicitamente ao iniciar projeto novo: /fluig:init-project

  • Playwright cli

    tbc-servicos/dataagile-agent-kit/playwright/skills/playwright-cli Skill

    4★ repo

    Setup completo, CLI e test-agents do Playwright. Cobre instalação, playwright.config.ts, todos os comandos npx playwright, fluxo planner/generator/healer com --loop=claude, e autenticação via storageState. Use quando precisar criar, executar ou reparar testes E2E com Playwright CLI.

  • Advpl tlpp sdd

    tbc-servicos/dataagile-agent-kit/protheus/skills/advpl-tlpp-sdd Skill

    4★ repo

    Plan and implement Protheus projects/features with 4 adaptive phases — Specify, Design, Tasks, Execute. Auto-sizes depth based on complexity. Creates atomic tasks with verification criteria, atomic commits, requirement traceability, and persistent memory across sessions. Specific to AdvPL/TLPP + Protheus. Use when: (1) Starting new Protheus projects, (2) Working on existing codebases (map modules, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification and atomic commits, (5) Quick tasks (bug fixes, entry points, config), (6) Tracking decisions/blockers/ideas across sessions, (7) Pausing/resuming work. Triggers on: 'initialize project', 'map codebase', 'specify feature', 'discuss feature', 'design', 'tasks', 'implement', 'validate', 'verify work', 'quick fix', 'pause work', 'resume work'.

  • Clean architecture

    tbc-servicos/dataagile-agent-kit/protheus/skills/clean-architecture Skill

    4★ repo

    Aplica os princípios de Clean Architecture (livro de Robert Martin, o Uncle Bob) ao desenvolvimento ADVPL/TLPP — regra de dependência, separação em camadas (domínio, caso de uso, adaptador, framework Protheus), SOLID em TLPP OO e organização de fontes por domínio. Use quando o dev pedir para "organizar em camadas", "desacoplar regra de negócio", "aplicar clean architecture", "aplicar SOLID", "onde colocar essa regra", "separar SQL da regra", "estruturar um desenvolvimento grande" ou quando o brainstorm/plan/reviewer precisar de critério estrutural de design.

  • Create implementation plan

    tbc-servicos/dataagile-agent-kit/protheus/skills/create-implementation-plan Skill

    4★ repo

    Create machine-readable implementation plan files for features, refactoring, upgrades, design, architecture, or infrastructure. Use when a user says "create implementation plan", "plan this upgrade", "plan this refactor", or needs a structured, phased plan with requirements, constraints, tasks, and validation criteria saved to the /plan/ directory.

  • Init project

    tbc-servicos/dataagile-agent-kit/protheus/skills/init-project Skill

    4★ repo

    Inicializa um projeto Protheus ADVPL — explora o projeto existente, entrevista o desenvolvedor e gera CLAUDE.md com configuração do cliente (AppServer, ambiente, prefixo de tabelas).

  • Refactor method complexity reduce

    tbc-servicos/dataagile-agent-kit/protheus/skills/refactor-method-complexity-reduce Skill

    4★ repo

    Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods. Use when user says 'reduce complexity', 'simplify method', 'cognitive complexity too high'.

  • Refactor

    tbc-servicos/dataagile-agent-kit/protheus/skills/refactor Skill

    4★ 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. Use when user says 'refactor this code', 'extract function', 'reduce complexity', 'code smells'.

  • Lo onboarding orchestrator

    stephenrogan/augmented-csm/skills/pillar-2-lifecycle-orchestration/lo-onboarding-orchestrator Skill

    4★ repo

    Manages the customer onboarding workflow from sales handoff through first-value milestone. Sequences tasks, triggers communications, tracks completion, and flags delays. Use when asked to set up onboarding for a new customer, track onboarding progress, build onboarding workflows, automate onboarding sequences, manage customer go-live, monitor time-to-value, or when any new account needs to be moved through a structured activation process. Also triggers for questions about onboarding playbooks, kickoff coordination, or implementation tracking.

  • Getting started

    celigo/ai/skills/getting-started Skill

    4★ repo

    Orientation for Celigo integrations -- core concepts, build order, account discovery, planning discipline, sandbox awareness, and which skill to use for each task. Start here when the task is unclear or the user is new to Celigo.

  • Genesis seed

    gabrieldabbah/genesis/skills/genesis-seed Skill

    4★ repo

    Manage reusable genesis seeds and one-time machine setup. Use when the user says "/genesis-seed", "save this as a seed", "save my setup", "list seeds", "edit the seed", or "set up my machine for genesis". Writes/loads named, AI-authored configuration seeds (so the user never hand-writes config) and performs the once-per-machine bootstrap (optional rtk detection, global plugin install guidance, ccusage check for usage-guard).

  • Simplify

    kt3k/skills/skills/simplify Skill

    no license4★ repo

    Read source code and find opportunities to simplify, deduplicate, and consolidate. Apply changes after user approval.

  • Refactoring guru

    eXodes/skills-workspace/refactoring-guru Skill

    no license4★ repo

    Code quality and design patterns advisor using Refactoring Guru principles. Trigger when users ask what's structurally wrong with code, mention code smells, ask which design pattern to use, want to refactor messy code, or ask about composition vs. inheritance. Examples: "this code is a mess", "I have to change 10 files every time I add a feature", "what pattern fits this?". Use for structural design questions—not runtime debugging, testing, or language features.

  • Refactoring ui

    eXodes/skills-workspace/refactoring-ui Skill

    no license4★ repo

    Expert advisor for UI and visual design using Refactoring UI principles. Use this skill when the user shares a UI design for review, asks about color, typography, spacing, layout, shadows, contrast, or visual hierarchy, wants to build a design system or color palette, or asks casual questions like "my design looks boring", "this layout feels cramped", "how do I pick colors", "what shadow should I use", "how do I make my UI more professional", or "something feels off". Do NOT use for frontend framework implementation, JavaScript logic, CSS debugging, animations, or API design.

  • Build right preflight

    pax-k/build-right/skills/build-right-preflight Skill

    4★ repo

    Agent-agnostic skills that turn a fuzzy app idea into evidence-backed AI execution.

  • Specgate project setup

    thanhtung2693/specgate/app/doc-registry/internal/agentpackages/plugins/skills/specgate-project-setup Skill

    4★ repo

    Use when SpecGate is being initialized or configured for a repository, its workspace binding is missing, IDE plugins need installation or refresh, or setup diagnostics fail.

  • Specgate project setup

    thanhtung2693/specgate/plugins/skills/specgate-project-setup Skill

    4★ repo

    Use when SpecGate is being initialized or configured for a repository, its workspace binding is missing, IDE plugins need installation or refresh, or setup diagnostics fail.

  • Scaffold

    BytesFromToby/plumbline/skills/scaffold Skill

    3★ repo

    Bootstrap a greenfield project — git init, the full convention folder skeleton, and a CLAUDE.md contract. Lays structure only and makes no design decisions; the stack and commands are left as pending fields for architect to fill. Run once at the start.

  • Langchain architecture

    carlopezzuto/agents/.claude/skills/langchain-architecture Skill

    3★ repo

    Design LLM applications using the LangChain framework with agents, memory, and tool integration patterns. Use when building LangChain applications, implementing AI agents, or creating complex LLM workflows.

  • Monorepo management

    carlopezzuto/agents/.claude/skills/monorepo-management Skill

    3★ 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.

  • Prometheus configuration

    carlopezzuto/agents/.claude/skills/prometheus-configuration Skill

    3★ 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.

  • Shellcheck configuration

    carlopezzuto/agents/.claude/skills/shellcheck-configuration Skill

    3★ repo

    Master ShellCheck static analysis configuration and usage for shell script quality. Use when setting up linting infrastructure, fixing code issues, or ensuring script portability.

  • Plantuml architect

    smartbrainactivity/visual-diagramming-export/plantuml-architect Skill

    3★ repo

    Utiliza este skill cuando se solicite crear diagramas UML formales, casos de uso complejos, secuencias, diagramas de clases, grafos abstractos o arquitecturas de software estrictas. Genera código PlantUML y lo compila localmente de forma agnóstica a una URL de SVG estático (Kroki API) para entregar directamente la imagen final.

  • Cf init

    QBall-Inc/clear/skills/cf-init Skill

    3★ repo

    Initialize the CLEAR framework in the current project. Use when a user wants to set up CLEAR for the first time, reinitialize an existing project (destructive), or refresh meta files (CLAUDE.md + rules.md) from the latest CLEAR templates (non-destructive).

  • Configure

    lantisprime/claude-sdlc/skills/configure Skill

    3★ repo

    Use this skill when the user runs /configure, /configure --needs, or /configure --check. Also auto-invoked by env-detect.sh on fresh install (Layer 0) and by skills that find required config missing at runtime (Layer 2). Guides setup of config/tools.json and config/tools.local.json through a question bank; handles public/local split, diff-before-write, and resume semantics for interrupted commands.

  • Design

    lantisprime/claude-sdlc/skills/design Skill

    3★ repo

    Use this skill after Phase 2 Analyze to produce the design artifacts a build depends on — application architecture, data/platform/infrastructure/security architecture, test architecture, test cases, technical specifications, and DevOps pipeline design. Validates existing architecture artifacts against current requirements before writing new ones. Trigger after requirements have been approved, or when the user asks to "design", "architect", "create specs", or "plan the tests". This is the densest phase — consider delegating architecture validation and test-case generation to subagents when available.

  • Tekton

    broomva/skills/skills/design/tekton Skill

    3★ repo

    Tekton — the shared architecture-intent substrate for co-designing systems with the agent. One typed graph across six tiers (system / journey / data / infra / decisions / qualities); views are queries, not separate diagrams. The canonical artifact is a diff-friendly YAML model both human and agent read and write; it renders to Mermaid (agent-legible, GitHub-native) and a self-contained tabbed HTML viewer (human-visual). Cross-tier traceability (`tekton query <from> <to>`) answers "which infra does this user-journey step touch?" as a path query. USE WHEN: designing or thinking deeply about architecture, a system, a data model, user journeys/flows, or a technical plan WITH the agent; when a Category-C HTML doc isn't enough because you need to see AND edit AND traverse the design across tiers; "let's design X", "architect this", "model the system", "draw the flow", "how does this fit together", "diagram this", "/tekton". NOT FOR: a one-off throwaway diagram (use Mermaid inline); prose-only ADRs (write the ADR); implementation itself. Triggers on: design architecture, model the system, user journey, data model, tekton.

  • Architecture design principles

    broomva/skills/skills/governance/architecture-design-principles Skill

    3★ repo

    Distilled architecture & design principles for building self-service developer platforms, control-plane / data-plane separation, and edge-centralized cross-cutting concerns — drawn from a senior platform engineer's 8-year retrospective on building Atlassian's Envoy-based load-balancing platform (Open Service Broker + Sovereign xDS control plane + AWS infra + sidecar model). Covers the three IaC layers (image / infra / runtime), the template+context pattern for dynamic proxy configuration, forced-migration as an adoption tool, long-term maintenance discipline (churn as a smell, build vs maintain as distinct skills), and the non-technical engineering skills (diplomacy, mentoring vs teaching). Use when: (1) designing a self-service internal developer platform, (2) deciding between native proxy features vs sidecars, (3) introducing or migrating to Envoy / xDS / service mesh, (4) implementing the Open Service Broker spec or any resource-provisioning API, (5) abstracting cloud complexity (AWS CloudFormation, Packer, SaltStack/Ansible/Puppet) behind a developer-friendly API, (6) centralizing cross-cutting concerns (auth, authz, rate limiting, DDoS, access logs) at the edge, (7) planning a fleet-wide migration to new infrastructure, (8) auditing a long-lived codebase for churn / coupling / maintenance burden, (9) onboarding engineers to an existing platform, (10) deciding when to mentor vs train, (11) user says "platform engineering", "control plane", "data plane", "xDS", "Envoy", "service broker", "edge compute", "sidecar", "cross-cutting concerns", "self-service", "internal developer platform", "IDP", "platform migration", "code churn", "long-term maintenance", "mentoring vs teaching".

  • Make spec

    broomva/skills/skills/tooling/make-spec Skill

    3★ repo

    Scaffold a substantive human-readable design doc (spec / plan / ADR / report / PR explainer) as native HTML using the workspace's canonical Broomva dark theme. Implements P18 (Format-Follows-Audience) for Category-C native artifacts — distinct from `bookkeeping render`, which projects Category-B markdown canonicals to HTML. Use when: (1) drafting a substantive design doc a human will actually read (>100 lines OR contains tables/diagrams/decision matrices), (2) writing an ADR (architectural decision record), (3) producing a plan a non-agent stakeholder will review, (4) writing a PR explainer for a substantive PR, (5) producing a report that synthesizes prior research. The skill ships theme.css + the spec HTML template, and generates the plan / adr / report / pr-explainer variants from that same theme + the prose skeletons below — so the agent doesn't rebuild the 70-line :root + h1-h4 + table + callout boilerplate every time. Triggers on "spec", "plan", "ADR", "decision record", "design doc", "explainer", "report", "html spec", "html doc", "Broomva html", "dark theme spec".

  • Architecture and contracts

    aneja5/forge-skills/skills/architecture-and-contracts Skill

    3★ repo

    Use when .forge/prd.md exists and the system needs a structural design before task breakdown, when modules will be implemented in parallel and need interface contracts to prevent integration failures, or when non-obvious technical decisions need to be recorded for future reference.

  • Refactoring and tech debt

    aneja5/forge-skills/skills/refactoring-and-tech-debt Skill

    3★ repo

    Use when tracking tech debt across a codebase, when planning a refactor, when deciding whether to rewrite vs incrementally improve, when a workaround has appeared in three places, or when a refactor PR is about to be combined with feature work.

  • Design tokens

    TimboGP/timbogp-marketplace/plugin/ux-design/skills/design-tokens Skill

    3★ repo

    This skill should be used when a user wants to scaffold or refactor a design token system — e.g. "set up design tokens", "create a design system foundation", "extract these hardcoded colors into tokens", "add a type scale", "theming setup", or "dark mode tokens". It produces a single source of truth for color, type, spacing, radius, shadow, motion, and z-index, emitted in the format the detected stack expects.

  • Ux foundations

    TimboGP/timbogp-marketplace/plugin/ux-design/skills/ux-foundations Skill

    3★ repo

    This skill should be used when the user wants to bootstrap or set up a UX baseline in a project — e.g. "bootstrap UX best practices", "set up our UX foundations", "scaffold a design system starting point", "establish UX standards for this repo", or runs /ux-bootstrap. It detects the project's stack and lays down design tokens, accessible base primitives, a11y linting, lightweight metrics, and a UX-CHECKLIST. It is the orchestrator that other implement skills (design-tokens, accessible-components, interaction-feedback) build on.

  • Ux onboarding

    TimboGP/timbogp-marketplace/plugin/ux-design/skills/ux-onboarding Skill

    3★ repo

    This skill should be used when someone wants to get familiar with an existing project's UX/design choices and patterns — e.g. "walk me through how this app does UX", "onboard me onto the design system", "explain this project's UI patterns", "I'm new to this codebase, show me the design layer", or runs /ux-onboarding. It builds a working mental model by surveying the design layer, teaching it part by part (explaining, sending the user to read the real code, and checking comprehension with questions), then having the user reimplement a small recent UX change picked from history. Familiarization — not scaffolding (ux-foundations) or scoring (ux-audit).

  • Design pattern

    ProjAnvil/MindForge/skills/en/design-pattern Skill

    3★ repo

    Expert knowledge in software design patterns covering GoF patterns, architectural patterns, and modern design principles. Apply appropriate patterns to improve code maintainability, scalability, and extensibility. Use this skill when designing new software components, refactoring existing code, reviewing code for design quality, resolving complex design problems, or need guidance on applying SOLID principles and identifying code smells.

    The same file is in 1 other repository

  • System architecture

    ProjAnvil/MindForge/skills/en/system-architecture Skill

    3★ repo

    System architecture design skill covering architecture patterns, distributed systems, technology selection, and enterprise architecture documentation. Use this skill when designing system architectures, evaluating technology stacks, planning distributed systems, or creating architecture decision records and documentation.

  • Api design

    ProjAnvil/MindForge/skills/zh-cn/api-design Skill

    3★ repo

    专业的 API 设计技能,涵盖 RESTful API、GraphQL、API 版本控制、身份认证、幂等性和 API 文档最佳实践。使用此技能设计 RESTful API、GraphQL schema、API 版本策略,或需要 API 文档和认证授权指导时使用。

  • Design pattern

    ProjAnvil/MindForge/skills/zh-cn/design-pattern Skill

    3★ repo

    精通软件设计模式,包括 GoF 模式、架构模式和现代设计原则。应用适当的模式提高代码的可维护性、可扩展性和可伸缩性。使用此技能设计新软件组件、重构现有代码、审查代码设计质量、解决复杂设计问题,或需要 SOLID 原则和代码异味识别指导时使用。

  • System architecture

    ProjAnvil/MindForge/skills/zh-cn/system-architecture Skill

    3★ repo

    系统架构设计技能,涵盖架构模式、分布式系统、技术选型和企业架构文档编写。使用此技能设计系统架构、评估技术栈、规划分布式系统,或创建架构决策记录和文档时使用。

  • Low complexity

    mryll/skills/skills/low-complexity Skill

    3★ repo

    Enforce low Cognitive Complexity (SonarSource) and low Cyclomatic Complexity in ALL code written or modified, in any programming language, framework, or platform. This skill MUST activate automatically whenever code is being written, generated, modified, or refactored — no explicit trigger needed. Triggers include writing any function, method, class, module, script, handler, endpoint, test, or code block. Also triggers on "low complexity", "cognitive complexity", "cyclomatic complexity", "reduce complexity", "simplify code", "too complex", "refactor for readability", "clean code", "implement", "fix bug", "add feature", "generate test", "optimize", "rewrite", "scaffold".

  • Vertical slice architecture

    mryll/skills/skills/vertical-slice-architecture Skill

    3★ repo

    Enforce Vertical Slice Architecture (VSA) when building applications in any language (Go, .NET/C#, Java, Kotlin, TypeScript, Python, etc.) and any type (web API, mobile backend, CLI, event-driven). Organize code by feature/use-case instead of technical layers. Each feature is a self-contained vertical slice with a single entry point that receives the router/framework handle and its dependencies. Use when the user says "vertical slice architecture", "VSA", "organize by feature", "feature-based architecture", "slice architecture", or when building a new app or feature and the project already follows VSA conventions. Also use when reviewing or refactoring code to align with VSA principles.

  • Kanso refactor

    blakecyze/kanso/skills/kanso-refactor Skill

    3★ repo

    Use when the user asks to clean up, tighten, simplify, de-bloat, de-slop, or refactor code. Also use when acting on findings from /kanso-audit or /kanso-nuclear. Behaviour-preserving only.

  • Templateclaw refactor

    jeromwolf/templateclaw/skills/templateclaw-refactor Skill

    3★ repo

    Generate refactoring checklists — performance optimization, security audit, and database migration guides. Actionable step-by-step guides with verification commands.

  • Templateclaw setup

    jeromwolf/templateclaw/skills/templateclaw-setup Skill

    3★ repo

    Generate project setup files — README.md, CLAUDE.md, AGENTS.md, .env template, Docker Compose. Best practices for modern development teams and AI-assisted coding.

  • Templateclaw

    jeromwolf/templateclaw/skills/templateclaw Skill

    3★ repo

    Scaffold a complete project with production-ready templates. Generates landing pages, dashboards, UI components, project setup files, and dev methodology guides. Use when starting a new project or adding features.

  • Ios scaffold

    edfenton/claude-skills/ios/ios-scaffold Skill

    3★ repo

    Scaffold a SwiftUI iOS app (iPhone + iPad) with offline-first persistence, push notifications plumbing, SwiftFormat + SwiftLint, CI, and optional GitHub repo creation.

  • Mern scaffold

    edfenton/claude-skills/mern/mern-scaffold Skill

    3★ repo

    Scaffold a pnpm + Turborepo MERN monorepo with Next.js, tooling, tests, CI, and optional GitHub repo creation.

  • Mern stack

    edfenton/claude-skills/mern/mern-stack Skill

    3★ repo

    Stack decisions for MERN apps (Next.js, pnpm monorepo). Reference before scaffolding or architecture work.

  • Nean scaffold

    edfenton/claude-skills/nean/nean-scaffold Skill

    3★ repo

    Scaffold an Nx monorepo with NestJS API, Angular frontend, and shared libraries.

  • Nean stack

    edfenton/claude-skills/nean/nean-stack Skill

    3★ repo

    Stack decisions for NEAN apps (NestJS, Angular, Nx monorepo). Reference before scaffolding or architecture work.

  • Python scaffold

    edfenton/claude-skills/shared/python-scaffold Skill

    3★ repo

    Add Python VS Code workspace config to a project. Composable — works standalone or merges into existing .vscode/ from a prior kit scaffold.

  • Api design

    CODE-SAURABH/OpenSkills/api-design Skill

    3★ repo

    Design production-grade APIs — REST, GraphQL, gRPC, and WebSocket — with a focus on consistency, versioning, error standards, and developer experience. Use when the user asks to design an API, define endpoints, choose between REST and GraphQL, structure request/response schemas, handle API versioning, design pagination, or produce an OpenAPI/Swagger spec.

  • Database architect

    CODE-SAURABH/OpenSkills/database-architect Skill

    3★ repo

    Expert database architecture and design guidance — schema/data modeling, ER diagrams, indexing, query optimization, partitioning, replication and high availability, transactions and locking, connection pooling, migrations, and multi-tenancy patterns across PostgreSQL, MySQL, MongoDB, and Redis. Use this whenever the user asks about designing a schema, a slow or N+1 query, choosing between SQL and NoSQL, sharding, read replicas, a database migration, or says something like "why is this query slow" or "how should I structure this table" — even without the word "database" in the request.

  • System design

    CODE-SAURABH/OpenSkills/system-design Skill

    3★ repo

    Expert system design guidance for architects and senior engineers. Use when the user asks about microservices, monolith design, event-driven architecture, scalability, reliability, caching strategies, queue design, load balancers, or API gateways.

  • Scaffold

    TNT-Likely/honeycomb/plugins/flutter-riverpod-drift/skills/scaffold Skill

    3★ repo

    当用户要起一个 Flutter app 项目,采用 Riverpod 状态管理 + Drift 本地数据库 + 可选云同步的成熟架构时使用。脱胎于 BeeCount(蜜蜂记账)生产实践,包含 Design Token 系统、Repository 多端切换、缓存→Stream 切流、严格 Drift 迁移纪律、PrimaryHeader/SectionCard 统一页面骨架等模式。触发关键词:"scaffold Flutter Riverpod 项目"、"新建一个 Flutter app"、"起一个 BeeCount 风格的 Flutter 项目"、"flutter app with riverpod and drift"、"create flutter mobile app starter"、"按 flutter-riverpod-drift 模板建项目"。不适用于纯 Flutter web、用 BLoC/GetX 的项目、demo 级 app。

  • Code scaffolding

    VersoXBT/claude-recommended-skills/code-scaffolding Skill

    3★ repo

    Generate project boilerplate, component templates, and framework scaffolding that follows existing codebase conventions. Use when the user says 'scaffold', 'generate boilerplate', 'create a new component', 'set up a new service', 'bootstrap', 'new module', 'add a new route', 'create a new endpoint', 'template for', 'stub out', or 'create a new page'. Also triggers on 'scaffolding', 'boilerplate', 'code generation', 'new feature skeleton', 'project setup', 'starter template', or 'generate files for'.

  • Architecture

    soden46/syarif-laravel-ai-skills/skills/architecture Skill

    3★ repo

    Apply Laravel-native architecture decisions without forcing unnecessary repositories, interfaces, DTOs, or custom layers.

  • Bird troubleshooting

    bird-chinese-community/BIRD.skills/bird-troubleshooting Skill

    3★ repo

    Diagnose complex BIRD routing-daemon problems that cross configuration, source-code, and tooling boundaries. Use when the daemon fails to start, crashes at runtime, logs a confusing error, or behaves differently from the documented semantics after lint passes. For simple config syntax or formatting issues, use bird-agent; for source-level questions, use bird-source-explorer.