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

  • Clean architecture

    planifest/planifest-framework/planifest-framework/external-skills/clean-architecture Skill

    0★ repo

    Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

  • Cloud architect

    planifest/planifest-framework/planifest-framework/external-skills/cloud-architect Skill

    0★ repo

    Analyse a Terraform plan and produce a structured Markdown summary — one-sentence overview, top 10 critical changes or concerns, and 5 key takeaways covering security, cost, and compliance.

  • Code quality

    planifest/planifest-framework/planifest-framework/external-skills/code-quality Skill

    0★ repo

    Explain code, security tool output, or configuration text — outputs clear EXPLANATION, SECURITY IMPLICATIONS, CONFIGURATION EXPLANATION, or ANSWER sections depending on input type. Use when you need a plain-language breakdown of what code or config does.

  • Design critique

    planifest/planifest-framework/planifest-framework/external-skills/design-critique Skill

    0★ repo

    Conduct a detailed architecture design review — evaluating component clarity, integrations, security, scalability, data management, maintainability, and risks. Use when reviewing a system design document or architecture diagram.

  • Documentation architecture

    planifest/planifest-framework/planifest-framework/external-skills/documentation-architecture Skill

    0★ repo

    Author architecture documentation that explains boundaries, dependencies, and operational constraints for engineering decision-making. Use when architecture docs are primary deliverables or must be updated after structural changes; do not use for implementing production feature logic.

  • Dotnet architect

    planifest/planifest-framework/planifest-framework/external-skills/dotnet-architect Skill

    0★ repo

    Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns.

    The same file is in 8 other repositories

  • Graphql architect

    planifest/planifest-framework/planifest-framework/external-skills/graphql-architect Skill

    0★ repo

    Master modern GraphQL with federation, performance optimization, and enterprise security. Build scalable schemas, implement advanced caching, and design real-time systems.

    The same file is in 7 other repositories

  • Onboarding cro

    planifest/planifest-framework/planifest-framework/external-skills/onboarding-cro Skill

    0★ repo

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.

    The same file is in 4 other repositories

  • Refactoring ui

    planifest/planifest-framework/planifest-framework/external-skills/refactoring-ui Skill

    0★ repo

    Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off", "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.

  • Release it

    planifest/planifest-framework/planifest-framework/external-skills/release-it Skill

    0★ repo

    Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", "chaos engineering", "bulkhead pattern", "retry with backoff", or "health checks". Also trigger when designing resilient microservices, planning zero-downtime deployments, or investigating cascading failure scenarios. Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

  • Site architecture

    planifest/planifest-framework/planifest-framework/external-skills/site-architecture Skill

    0★ repo

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

    The same file is in 4 other repositories

  • System design

    planifest/planifest-framework/planifest-framework/external-skills/system-design Skill

    0★ repo

    Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.

  • Typescript style guide

    planifest/planifest-framework/planifest-framework/external-skills/typescript-style-guide Skill

    0★ repo

    Style, review, and refactoring standards for TypeScript codebases. Trigger when `.ts`, `.tsx`, `.d.ts`, or `tsconfig*.json` files are created, changed, or reviewed and TS-specific quality rules (type safety, narrowing, async/error handling, module boundaries) must be enforced. Do not use for JavaScript-only modules that are outside TypeScript type-check scope. In mixed JS/TS repositories, this skill owns `tsconfig`-scoped modules. For shared JS/TS configuration files (for example `package.json`, shared lint/test config), run together with `javascript-style-guide` when both JS and TS artifacts change in the same pull request.

  • Zero trust architecture

    planifest/planifest-framework/planifest-framework/external-skills/zero-trust-architecture Skill

    0★ repo

    Implement Zero Trust security model with identity verification, microsegmentation, least privilege access, and continuous monitoring. Use when building secure cloud-native applications.

    The same file is in 1 other repository

  • Planifest refactor

    planifest/planifest-framework/planifest-framework/skills/planifest-refactor Skill

    0★ repo

    TDD refactor phase — improves code quality while keeping all tests passing. Invoked by planifest-codegen-agent after planifest-implementer confirms GREEN.

  • Dsai styling

    michelve/hugin-v0/skills/dsai-styling Skill

    0★ repo

    DSAI styling system reference, Bootstrap 5 utilities, CSS custom properties (design tokens), cn() utility, dark mode, and token pipeline. Replaces the old tailwindcss skill. Use this skill when generating or modifying styles, classNames, or theme configuration in DSAI consumer applications.

  • Setup

    michelve/hugin-v0/skills/setup Skill

    0★ repo

    Verify environment variables, MCP servers, and LSP are configured correctly. Use when user says 'setup', 'check my setup', 'verify config', 'is everything configured', or wants to confirm their development environment is ready.

  • Writing tests

    michelve/hugin-v0/skills/writing-tests Skill

    0★ repo

    Use this skill when writing, reviewing, or improving tests. Trigger on: 'write tests', 'add tests', 'test naming', 'what should I test', 'edge cases', 'test structure', 'assertion', 'toBe vs toEqual', 'toBeDefined', 'toBeTruthy', 'test review', 'test quality', 'test coverage', 'how to test', 'bug found write test', 'one test enough', 'test name', 'arrange act assert', 'AAA pattern'. Also trigger when user shares a test and asks for review, asks about assertion best practices, asks what edge cases to consider, mentions test names like 'test login' or 'should work', asks about splitting tests, or reports finding a bug and wants to know what else to test. Do NOT trigger for test runner configuration (jest.config, vitest.config), CI/CD pipeline setup, or questions about testing frameworks that aren't about how to write the tests themselves.

  • Game development behavior architecture

    LoogacyStudio/skills/plugins/game-development/skills/game-development-behavior-architecture Skill

    0★ repo

    Use when a cross-engine gameplay task needs a Layer 2 shared-runtime architecture decision — simpler rule flow, FSM, behavior tree, utility scoring, or GOAP-style planning — and the agent must stay comparative before locking in one control pattern.

  • Scene architecture review

    LoogacyStudio/skills/plugins/godot-dotnet/skills/scene-architecture-review Skill

    0★ repo

    Use when a Godot/.NET task needs a Layer 4 overlay architecture review of a scene, gameplay system, or UI flow specifically to assess scene composition, node responsibility, script ownership, signal boundaries, autoload fit, and UI-to-gameplay coupling, and the agent must judge maintainability seams rather than primarily evaluating readability, focus, feedback, or other UX-only concerns.

  • Version upgrade review

    LoogacyStudio/skills/plugins/godot-dotnet/skills/version-upgrade-review Skill

    0★ repo

    Use when a Godot/.NET task needs a Layer 4 overlay upgrade review that evaluates engine, SDK, C# compatibility, addons/plugins, export pipeline, verification, and rollback risk, then returns a staged sequence instead of a risky all-at-once migration.

  • My council

    alexleekt/agents/skills/my-council Skill

    no license0★ repo

    **ALWAYS use when user mentions:** "review council", "multi-agent review", "parallel review", "team review", "full code review", "review with experts", "spawn reviewers", "council pattern", "review all dimensions", "code review", "review this", "PR review", "check my code", "critique", "how should I write this", "raise the bar". **ALWAYS use when:** a codebase has changed >5 files or ~100+ lines, or when the user wants a thorough review across multiple dimensions (security, performance, correctness, maintainability, tests, accessibility, architecture, types, research). **DO NOT use for:** single-file quick checks, asking how a specific function works, or debugging a known bug (use the appropriate debug skill instead).

  • Setup

    technomaton/edpa/plugin/skills/setup Skill

    0★ repo

    Initialize EDPA V2 governance for a project. Vendors the engine (scripts + schemas + templates) into `.edpa/engine/`, creates `.edpa/config/{edpa.yaml,people.yaml}`, seeds id_counters.yaml, and optionally copies the PR-signal CI workflow + registers git hooks (lefthook-aware; wires one `extends:` line instead of clobbering managed hooks). No GitHub Project provisioning (V1 path removed in 2.0.0).

  • Backend api contract review

    yangshu2087/Codex/.agents/skills/backend-api-contract-review Skill

    no license0★ repo

    Use when a task involves backend services, API routes, database writes, auth, permissions, error semantics, or service contracts.

  • Repo codex bootstrap

    yangshu2087/Codex/.agents/skills/repo-codex-bootstrap Skill

    no license0★ repo

    Add or refresh repository-level Codex scaffolding such as .codex/config.toml and AGENTS.md. Use when a repo needs lightweight Codex defaults, repo-specific instructions, or a repeatable project bootstrap.

  • Repo postcheck summary

    yangshu2087/Codex/.agents/skills/repo-postcheck-summary Skill

    no license0★ repo

    Run the minimum useful verification after repository bootstrap or small setup changes, then produce a concise change summary. Use when a repo has just been initialized or had Codex scaffolding added and the user wants a quick verification-and-summary pass.

  • Stitch ui prompt architect

    yangshu2087/Codex/vendor/skills/skilltrust-curated/stitch-kit/stitch-ui-prompt-architect Skill

    no license0★ repo

    Use when the user explicitly mentions Google Stitch and wants a structured Stitch-ready UI prompt or prompt refinement from rough product/design ideas.

  • Tca architect

    ninjaproger/skills/skills/tca-architect Skill

    no license0★ repo

    Architect modular iOS apps using Swift Package Manager and The Composable Architecture (TCA). Use when designing or implementing a new iOS app (or feature module) that should be split into separate SPM packages, each owning a TCA feature reducer, view, and tests. Covers the full workflow: module decomposition, Package.swift dependency graph, reducer/view/navigation patterns, dependency injection via swift-dependencies, and the delegate action pattern for cross-module communication. Trigger when the user asks to: architect a TCA app, create a new SPM module/feature, set up a modular iOS project, add a feature to an existing TCA app, wire navigation between features, or design a dependency client.

  • Tca developer

    ninjaproger/skills/skills/tca-developer Skill

    no license0★ repo

    Develop new features in a modular iOS app using The Composable Architecture (TCA) and Swift Package Manager. Use when implementing a new screen, adding a sub-feature, extending an existing reducer, adding SwiftUI previews, or writing TCA tests. Covers the full development workflow: reading the existing codebase, creating reducer + view files, wiring navigation, writing SwiftUI previews for all meaningful states (loaded, empty, error, and feature-specific variants), and writing TestStore tests. Always explore the target module before writing code to match its existing style and conventions.

  • Code explain visually

    RileyCornelius/Code-Skills/skills/code-explain-visually Skill

    0★ repo

    Explain code with diagrams, analogies, and step-by-step walkthroughs. Use when the user wants help understanding a function, file, module, request flow, architecture slice, or unfamiliar codebase area, especially when a visual explanation would make the behavior easier to follow.

  • Code simplifier

    RileyCornelius/Code-Skills/skills/code-simplifier Skill

    0★ repo

    Simplify recently changed code for clarity, consistency, and maintainability without changing behavior. Use when the user wants a cleanup, refactor, polish pass, or readability improvement on code that already works and should keep the same functionality.

  • Architecture design

    lx-wnk/skills/skills/architecture-design Skill

    0★ repo

    Design system-level architecture — bounded contexts, modules, domains, layering, dependency direction, and ADRs. Make sure to use this skill whenever the user asks to design an architecture, plan a system, define bounded contexts, draft an ADR, decide on module boundaries, or says things like "entwirf die Architektur", "plane das System", "wie strukturieren wir X", "architecture design", "system design", "bounded contexts", "module layout". Use this skill for HIGH-LEVEL structural decisions only — component and class-level design belongs in `component-design`.

  • Architecture review

    lx-wnk/skills/skills/architecture-review Skill

    0★ repo

    Review system-level architecture of a PR, branch, namespace, or whole project — boundary violations, dependency cycles, layer breaches, ADR compliance, cohesion of modules and bounded contexts. Make sure to use this skill whenever the user asks to review the architecture, audit module boundaries, check for circular dependencies, verify domain structure, or says things like "architektur-review", "prüfe die struktur", "check architecture", "review namespace", "audit boundaries", "are our modules clean". Use this skill for HIGH-LEVEL structural review only — SOLID, class design, and method-level issues belong in `component-review`.

  • Component design

    lx-wnk/skills/skills/component-design Skill

    0★ repo

    Design low-level component and class structure — classes, interfaces, design patterns, method signatures, aggregates, service contracts, and collaboration within a single module or bounded context. Make sure to use this skill whenever the user asks to design classes, pick a design pattern, define interfaces, model an aggregate, shape a service, or says things like "wie strukturiere ich die klassen", "welches pattern passt", "component design", "class design", "design the service", "model the aggregate". Use this skill for DETAIL DESIGN inside a known module — system-level structure belongs in `architecture-design`.

  • Full project review

    lx-wnk/skills/skills/full-project-review Skill

    0★ repo

    Comprehensive multi-agent audit of the ENTIRE project (all repos / full HEAD state). Spawns parallel subagents for code quality, architecture, security (OWASP/CWE/CVSS), SEO, privacy/legal, UI/UX (WCAG), and performance, and consolidates their reports into a complete Findings.md with P0–P4 prioritization and reasoned recommendations. Use this skill for "review the entire project", "full project audit", "audit the codebase", "comprehensive review", "code audit", "security audit", "compliance audit", "review everything", "DSGVO audit", "OWASP audit", or German equivalents "vollumfängliches review", "review das ganze projekt", "audit das projekt", "kompletter code-audit", whenever a systematic audit without branch/diff context is requested — even when no changes are pending, no PR exists, or the branch is empty. PR/diff status is NOT a blocker. DO NOT trigger when only branch changes should be reviewed — use branch-review for that.

  • Codebase design

    neumie/almanac/skills/other/codebase-design Skill

    0★ repo

    Use when designing module interfaces, seams, deep modules, testability, AI-navigable architecture, or when another skill needs design vocabulary.

  • Codebase improve

    neumie/almanac/skills/other/codebase-improve Skill

    0★ repo

    Use when finding architectural friction in a codebase. Surfaces shallow modules, proposes refactors for testability/AI-navigability, grills the design. Uses CONTEXT.md + ADRs.

  • Pixelvault setup

    pixelvault-dev/skill/skills/pixelvault-setup Skill

    0★ repo

    Set up PixelVault CLI — install the CLI and configure API key authentication. Use when the user wants to configure PixelVault, "set up image hosting", "connect PixelVault", get an API key for image uploads, or when pixelvault-upload fails due to missing auth.

  • Konecty meta

    konecty/skills/skills/konecty-meta Skill

    0★ repo

    All Konecty metadata operations through the Konecty admin MCP server: read/inspect MetaObjects, manage document schemas and fields, manage list/view/access/pivot metas, validate and generate hook code, manage Namespace config (SMTP/RabbitMQ/storage/MCP flags), validate metadata integrity, and sync metadata repo↔database. Use when: ler metadados, inspecionar esquema, gerenciar campos, adicionar campo, criar lista/view, configurar perfil de acesso, gerar hook, configurar Namespace/SMTP/fila RabbitMQ, habilitar MCP, validar integridade meta, sincronizar metas, remover módulo meta, read metadata, manage schema, add fields, manage list view access pivot, generate hook, configure namespace, enable MCP flags, validate metadata, sync metadata, remove meta module. Requires the konecty-admin MCP server connected and an admin user (admin: true). Do NOT use for data record ops (find/create/update/delete/upload) — use konecty-data; do NOT use for MCP server setup — use konecty-setup.

  • Konecty setup

    konecty/skills/skills/konecty-setup Skill

    0★ repo

    Setup and troubleshooting for the Konecty MCP connection in Claude Code: register or replace the konecty and konecty-admin MCP servers for a company URL, guide the browser OAuth login, run the admin token path (interim OTP), and diagnose connection, login, and permission errors. Use when: configurar konecty, conectar meu crm, trocar de empresa, mudar a URL do konecty, problema de login no konecty, problema de permissão no konecty, refazer login, configurar acesso admin, set up konecty, connect my CRM, switch company URL, fix konecty login, re-authenticate, MCP connection or enablement errors. Do NOT use for data record operations (find/create/update/delete/upload) — use konecty-data; do NOT use for metadata/schema administration (documents, lists, views, access, hooks, namespace) — use konecty-meta.

  • Setup

    aylee/agent-os/.agents/skills/setup Skill

    0★ repo

    Personalize or upgrade an Agent-OS instance only when the user explicitly invokes setup. Preview all writes, preserve fictional examples unless removal is approved, and never overwrite global runtime or third-party skill configuration.

  • Devcontainer setup

    TheWatcher01/skills/.claude/skills/devcontainer-setup Skill

    0★ repo

    Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go), and persistent volumes. Use when adding devcontainer support to a project, setting up isolated development environments, or configuring sandboxed Claude Code workspaces.

    The same file is in 2 other repositories

  • Dl scaffold

    TheWatcher01/skills/.claude/skills/dl-scaffold Skill

    0★ repo

    Templates reutilisables pour scaffold rapide (crawler, route, schema, job). Copier+adapter > generer.

  • Guidelines advisor

    TheWatcher01/skills/.claude/skills/guidelines-advisor Skill

    0★ repo

    Smart contract development advisor based on Trail of Bits' best practices. Analyzes codebase to generate documentation/specifications, review architecture, check upgradeability patterns, assess implementation quality, identify pitfalls, review dependencies, and evaluate testing. Provides actionable recommendations.

    The same file is in 4 other repositories

  • Monorepo sync

    TheWatcher01/skills/.claude/skills/monorepo-sync Skill

    0★ repo

    Synchronize roadmaps, AGENTS.md, versions, and documentation across chainskills monorepo packages — use when updating version numbers, syncing roadmap status, or keeping documentation consistent

  • Project bootstrap

    TheWatcher01/skills/.claude/skills/project-bootstrap Skill

    0★ repo

    Factory logicielle : interrogatoire interactif → architecture → scaffolding TWB complet. 0 token de generation, 100% blocks prefabriques.

  • Update config

    TheWatcher01/skills/.claude/skills/update-config Skill

    0★ repo

    Agent Skills collection — Reusable capabilities for AI coding agents. Install: npx skills add TheWatcher01/skills

  • React nextjs antd clean architecture

    luismpenholato/maurao-skills/skills/react-nextjs-antd-clean-architecture Skill

    0★ repo

    React 19 + Next.js 16 App Router, TypeScript, Ant Design, TanStack Query, Axios, React Hook Form, Zod — Clean Architecture frontend with vertical slice by feature. Use when creating or refactoring Next.js apps, admin panels, SaaS frontends, CRUDs, forms, layouts and frontend architecture.

  • Clean architecture

    timothy-pham/copilot-suite/skills/bundled/clean-architecture Skill

    0★ repo

    Bootstrap GitHub Copilot project instructions and skills from official sources with a bilingual autopilot CLI.

  • N8n node configuration

    pessini/aria/backend/agents/n8n_agent/skills/n8n-node-configuration Skill

    0★ 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

  • Init

    rulebased-io/harness/rulebased-harness/skills/init Skill

    0★ repo

    Initializes the harness structure and migrates existing project artifacts into it

    The same file is in 1 other repository

  • Editorial config

    EditorialOS/editorial-os/skills/editorial-config Skill

    0★ repo

    Load client context at the start of every command by calling client-context skill. Interpret Drive documents into structured editorial intelligence — competitors, pillars, audience segments, constraints, content history, and performance baselines. Run silently. Never narrate the loading process.

  • Security threat model

    northseadl/skillwisp/skills/@openai/security-threat-model Skill

    0★ repo

    Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.

    The same file is in 8 other repositories

  • Clean architecture

    iceflower/agent-skills/clean-architecture Skill

    0★ repo

    Clean Architecture and Hexagonal Architecture (Ports & Adapters) patterns. Covers the dependency rule, domain layer isolation, use case (application service) design, repository pattern, input/output port definitions, adapter implementation, and onion architecture layering. Use when designing layered architecture, defining port/adapter boundaries, structuring domain-centric applications, or enforcing the dependency rule between infrastructure and domain layers.

  • Cloud native

    iceflower/agent-skills/cloud-native Skill

    0★ repo

    Cloud native application design principles based on the Twelve-Factor App methodology and CNCF patterns including codebase management, dependency isolation, config externalization, backing services, build-release-run separation, stateless processes, port binding, concurrency via process model, disposability, dev/prod parity, log streaming, and admin processes. Extends to 15-Factor with API-first design, telemetry, and security. Covers AWS/GCP/Azure Well-Architected frameworks. Use when designing cloud native applications, reviewing application architecture for cloud readiness, or applying twelve-factor principles to existing applications.

  • Code quality

    iceflower/agent-skills/code-quality Skill

    0★ repo

    Code quality and design principles. Includes refactoring techniques, code smell identification, and safe refactoring workflows. Use when writing, reviewing, or refactoring code.

  • Gradle convention

    iceflower/agent-skills/gradle-convention Skill

    0★ repo

    Gradle build conventions for Kotlin/JVM multi-module projects. Covers multi-module project structure, convention plugins, buildSrc setup, dependency management with version catalogs, Gradle wrapper configuration, build cache configuration, task optimization, and plugin publishing. Use when writing or reviewing build.gradle.kts, settings.gradle.kts, version catalog files, or configuring convention plugins for shared build logic.

  • System design

    iceflower/agent-skills/system-design Skill

    0★ repo

    Large-scale system design patterns including database architecture, caching, CDN, stateless design, message queues, consistent hashing, and rate limiting. Covers CAP theorem, eventual consistency, sharding strategies, replication factor, read replica configuration, and system stability patterns (circuit breaker, bulkhead, backpressure). Includes distributed systems patterns: data replication, partitioning, consensus, distributed time (Lamport clock, hybrid clock), cluster management (lease, gossip, state watch), and network communication patterns. Use when designing scalable system architectures, evaluating consistency vs availability trade-offs, planning data partitioning and replication strategies, or implementing distributed systems patterns.

  • Spec init

    taujiong/skills/skills/spec-init Skill

    no license0★ repo

    Deploy spec-driven development (SDD) skills and runtime directories to a project. Use when users want to initialize or set up the SDD workflow in a specific directory. Also triggers when users mention init sdd, setup sdd, initialize spec workflow, or bootstrap spec-driven development.

  • Project tech stack rules

    Chagai33/my-agent-skills/project-tech-stack-rules Skill

    no license0★ repo

    Defines the global technical stack, architecture guidelines, and restrictions for the project.