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

  • Cold start interview

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

    0★ repo

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

  • Cold start interview

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

    0★ repo

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

  • Cold start interview

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

    0★ repo

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

  • Cold start interview

    Zerif007/Claude_Legal-Bangladesh_Edition/bd-regulatory-compliance/skills/cold-start-interview Skill

    0★ repo

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

  • Cold start interview

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

    0★ repo

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

  • Cold start interview

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

    0★ repo

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

  • Cc clone

    duliangkuan/cc-clone/skill/cc-clone Skill

    0★ repo

    Clone a Claude Code brain — package your own memory/skills/agents/rules into a shareable, secret-redacted pack, or one-click install another developer's brain into your Claude Code (or export it to Codex/Gemini/Cursor/OpenCode). Use when the user says "clone my brain", "package my Claude Code setup", "install someone's brain", "克隆大脑", "打包我的记忆", "移植到 codex/cursor", or wants to distribute or adopt a Claude Code configuration.

  • Architecture

    rabius-sunny/agent-skills/architecture Skill

    no license0★ repo

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    The same file is in 4 other repositories

  • System design

    rabius-sunny/agent-skills/system-design Skill

    no license0★ repo

    Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

    The same file is in 5 other repositories

  • Information architecture

    muzalee/claude-atelier/skills/information-architecture Skill

    no license0★ repo

    Define the structural layer of a product or site before visual design begins. Covers navigation, content hierarchy, page structure, URL patterns, and user flows. Use when user wants to plan site structure, define navigation, map user flows, organize content, or mentions "IA" or "information architecture".

  • Project bootstrap

    muzalee/claude-atelier/skills/project-bootstrap Skill

    no license0★ repo

    Scaffold a new project from scratch — folder, .gitignore, README, LICENSE, git init + first commit, and (if gh is authed) create the GitHub repo with description, topics, and visibility. Use when user says "start a new project", "bootstrap", "new repo", "scaffold X", or asks to set up a fresh codebase.

  • Project setup

    cobuchan/compounding-operator/skills/project-setup Skill

    0★ repo

    Bootstrap new projects with standardized structure, CLAUDE.md, scratchpad, docs directory, and git repo. Use when creating a new project, setting up a repo, or bootstrapping from source material.

  • Grill my architecture

    NasserAlbusaidi/ship-gate/skills/grill-my-architecture Skill

    0★ repo

    Brutal staff-engineer review of system architecture — service/module boundaries, data ownership, communication patterns, failure modes, scaling, security trust boundaries, evolvability, cognitive load, cost. Accepts an architecture doc, a set of ADRs, a system design write-up, a diagram pack, a verbal sketch, OR the codebase itself (the skill reconstructs the de-facto architecture from the code when no doc exists). Distinct from `grill-my-code` (file/function craft), `grill-my-backend` (server-side surface within one service), `grill-my-plan` (a specific planned change before code is written), `improve-codebase-architecture` (constructive refactoring opportunities), and `plan-eng-review` / `plan-ceo-review` (constructive walkthroughs). Use when the unit of critique is the *system shape*, not a file or a feature. Triggers on "grill my architecture", "grill the system design", "grill these ADRs", "is this architecture going to survive", "tear apart this design", "review my system design brutally", "stress-test the architecture".

  • Dead code sweep

    ccpowerpack/claude-code-skills/skills/dead-code-sweep Skill

    0★ repo

    Find and safely remove dead code with call-site evidence — unused functions, unreachable branches, orphaned files, stale feature flags. Use when the user asks to clean up, find unused code, or reduce codebase size.

  • Refactor safe

    ccpowerpack/claude-code-skills/skills/refactor-safe Skill

    0★ repo

    Behavior-preserving refactoring with proof. Pins current behavior in characterization tests BEFORE touching structure, then proves the SAME tests pass unmodified after. Use for "refactor this", "clean up / restructure / extract / rename this without changing behavior", "split this function", "untangle this module", or any change that claims "no behavior change". Halts and re-scopes the moment a refactor turns out to alter behavior.

  • Trip scaffold

    fantasybz/trip-pwa-skills/skills/trip-scaffold Skill

    0★ repo

    Compile a curated, offline-first family-travel PWA from a few prompts. Generates a vanilla static PWA (HTML+CSS+JS+JSON) with a schedule, per-anchor contingency plans, prep refs, an a11y baseline, and GitHub Pages-ready output — owned by the user, installable to the home screen, works offline. Use when scaffolding a new trip ("make a Kyoto family trip app", "build a trip PWA"), seeding a day plan (draft-days), or running pre-publish audits (launch-check). Pairs with food-ingest and refs-ingest for content.

  • Strangler refactor

    manman1414/frontend-refactor-skills/skills/strangler-refactor Skill

    0★ repo

    Replaces legacy frontend modules incrementally using the strangler fig pattern — Vue 2 to Vue 3, Options API to Composition API, class components to hooks, old design system to new — with feature flags, parallel routes, and rollback paths. Use when migrating frameworks, replacing large legacy components, or rewriting modules without a big-bang release.

  • Session bootstrap

    nubasu/Pseudo-Fable-Framework/frameworks/pseudo-fable-retro/.claude/skills/session-bootstrap Skill

    0★ repo

    Session start and end rituals for multi-session projects — boot "where were we" from the state file, delegations ledger, tickets, and git in minutes; verify drift before resuming; end each session with a checkpoint the next session can boot from. Use at the start of any session that continues earlier work, and before ending a work session (or when context is nearly full).

  • Architect

    sumitake/agent-collab/plugins/agent-collab/skills/architect Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Llm architect

    sumitake/agent-collab/plugins/agent-collab/skills/llm-architect Skill

    no license0★ repo

    Unified dynamic-host agent collaboration policy and signed-runtime client

  • Privacy architecture

    fevra-dev/Subrosa/skills/privacy-architecture Skill

    0★ repo

    Selects and applies cryptographic primitives for privacy-by-design — systems where selective disclosure is structural, not procedural. Use when user says "build this with privacy built in", "how do I avoid collecting identity", "zero-knowledge proof for this", "anonymous credential", "can I prove X without revealing Y", "stealth address", "blind signature", "private transaction", "MPC", "homomorphic encryption", "differential privacy for analytics", "TEE", "can I verify without seeing the data", or when designing a new system, protocol, or product and wants privacy to be architectural rather than a policy layer added afterward. The Cypherpunk layer of the privacy suite — implements Eric Hughes' (1993) selective disclosure principle and Timothy May's (1988) anonymous transaction system program using contemporary cryptographic primitives. Distinct from all other privacy skills — those audit and repair; this one builds.

  • Onboarding with earth care network

    Giving-Back-Studio/growth-agent/skills/onboarding-with-earth-care-network Skill

    no license0★ repo

    Guides a business owner through Earth Care Network onboarding end to end over MCP — life context, enterprise creation, the seven Growth Plan modules, signal watchlists, and first leads. Use when someone connects the Earth Care Network connector for the first time, says they are new to ECN, asks to get set up, or wants their Growth Plan built.

  • Alterlab rma thesis architect

    prone-dc302/AlterLab-FC-Skills/skills/rma/alterlab-rma-thesis-architect Skill

    0★ repo

    This skill should be used when the user asks about "thesis structure", "dissertation", "thesis writing", "chapter organization", "research proposal", "thesis outline", "defense preparation", "thesis defense", "committee management", "thesis timeline", "writing productivity", "argument architecture", "thesis introduction", "literature review structure", "methodology chapter", "findings chapter", "discussion chapter", "thesis conclusion", "act as a thesis architect", "thesis architect mode", "dissertation proposal", "thesis pipeline", "academic writing structure", "thesis formatting", "thesis revision", "writing schedule", "thesis advisor", "research proposal writing", "thesis planning", "chapter drafting", "thesis feedback", "defense slides", "viva preparation", or needs expertise in structuring, planning, writing, and defending a thesis or dissertation. Part of the AlterLab FC Skills collection (Research Methods & Academic Writing department).

    The same file is in 1 other repository

  • Refactor

    supermodo/skills/skills/refactor Skill

    0★ repo

    Deep functional refactoring of TypeScript code for purity, testability, and modularity. Use when the user says /refactor, asks to clean up or restructure code, mentions large files, god functions, mixed concerns, poor testability, or when code grew unwieldy after feature iterations. Also triggers on "this file is too big", "split this", "make this more functional", "extract", "decompose", or any mention of code smells like let, try/catch in business logic, for loops, or files over 300 lines. If the user describes messy, tangled, or overgrown code that needs structural improvement, this is the right skill — even without the word "refactor."

  • Caching strategy architect

    tamasbege/staff-engineer-skills/plugins/staff-engineer-skills/skills/caching-strategy-architect Skill

    0★ repo

    Design caching architectures that are fast AND correct - cache placement (in-process, distributed, CDN), pattern selection (cache-aside, read-through, write-through, write-behind), TTL and invalidation strategy, stampede protection, and consistency guarantees. Use when database load is too high, latency needs cutting, the same data is fetched repeatedly, users see stale data after updates, cache and database disagree, a cache expiry causes load spikes (thundering herd), or the user asks where or how to add caching or fix cache invalidation.

  • Event pipeline architect

    tamasbege/staff-engineer-skills/plugins/staff-engineer-skills/skills/event-pipeline-architect Skill

    0★ repo

    Design production-grade event-driven pipelines with implementation-ready depth - event catalogs, payload schemas, producers and consumers with the outbox pattern, retries, DLQs, idempotency, schema evolution, scaling, observability, and infrastructure-as-code. Use when adding async processing between services, decoupling producers from consumers, migrating from synchronous to event-driven communication, designing Kafka / Azure Service Bus / AWS SQS-SNS / RabbitMQ / Pub-Sub topologies, or redesigning retry and failure handling for existing events.

  • Expressive motion architect

    tamasbege/staff-engineer-skills/plugins/staff-engineer-skills/skills/expressive-motion-architect Skill

    0★ repo

    Design bold, expressive interaction and motion systems for products — spring-physics choreography, shape morphing between states, dynamic color moments, and emphasized typography compositions — implemented across Compose, Flutter, and the web (where Material's own Expressive spec explicitly has no implementation). Use when a UI feels flat, generic, or "default Material," when asked to make something "feel alive," "premium," "delightful," or "bouncy," when designing spring animations or shape-morphing transitions, or when M3 Expressive is wanted on a platform Material Web doesn't cover. Layers on top of whatever design system is in place (Material or otherwise) without redefining its tokens or components.

  • Idempotency builder

    tamasbege/staff-engineer-skills/plugins/staff-engineer-skills/skills/idempotency-builder Skill

    0★ repo

    Design and deliver a complete idempotency system so critical actions are safe to retry - key design, request fingerprinting, atomic locking, partial-failure recovery, payment provider coordination (Stripe, Adyen, PayPal), saga idempotency, and monitoring. Use when protecting payments, orders, or webhooks from duplicate execution, handling at-least-once message delivery, double-click or client-retry bugs, duplicate webhook processing, overlapping cron jobs, or when the user asks to make an endpoint idempotent or prevent duplicate charges and records.

  • Gitnexus exploring

    theinterneti/TTA.dev/.claude/skills/gitnexus/gitnexus-exploring Skill

    0★ repo

    Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

    The same file is in 5 other repositories

  • Gitnexus refactoring

    theinterneti/TTA.dev/.claude/skills/gitnexus/gitnexus-refactoring Skill

    0★ repo

    Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

    The same file is in 5 other repositories

  • Llmwiki init

    sergsrgsg/rock-star-skills/skills/llmwiki-init Skill

    0★ repo

    Initialize the LLM Wiki. Creates directory structure, index, log, sets up qmd collection, and runs initial ingest of all existing content from raw/, docs/, and notes/. Run once per project.

  • Vainjs

    vainjs/skills/skills/vainjs Skill

    0★ repo

    Scaffold projects with vainjs conventions for npm packages and Chrome extensions. Make sure to use this skill whenever the user mentions initializing an npm package, creating a new project with Vite or Rollup, setting up a Chrome extension (Manifest V3), scaffolding a library, or running `npm init`, `pnpm create`, or similar scaffold commands — even if they don't explicitly ask for vainjs conventions.

  • Greenfield monorepo

    gabriel-f-santos/coding-agents/skills/greenfield-monorepo Skill

    no license0★ repo

    Bootstrap a brand-new polyglot monorepo from zero — interview for the apps and stacks, then scaffold a runnable hello-world per app with current best-practice harness, lint, tests, pre-commit, Docker Compose dev stack with seed data, dev scripts (up/down/restart/seed), root + per-app AGENTS.md, and CI. Use when the user wants to "start a new project/monorepo", "scaffold a greenfield repo", "set up frontend + backend + mobile", "iniciar um projeto do zero", "criar o monorepo", "montar o esqueleto", "configurar lint/test/pre-commit/docker do projeto novo", or hands over an architecture.md to build from. Ships two pinned stacks (Vite+React→Cloudflare Workers, FastAPI async) and a generic research-and-scaffold path (context7/web) for any other stack (LangGraph, Go realtime, Flutter, …). Do not use to add a feature to an existing app, to write a single Dockerfile/CI file in isolation, or to design product/architecture from scratch (chain to product-brainstorming / tech-discovery for that).

  • Review phase

    gabriel-f-santos/coding-agents/skills/review-phase Skill

    no license0★ repo

    Review a just-implemented phase/feature across functionality, security, and quality by fanning out three reviewers as subagents, scoped to the phase contract. Use after building something — "revisa a fase", "review phase X", "code review da feature", "revisa o que foi implementado", "revisão da phase-NN". Reads docs/phases/phase-NN-<slug>.md (acceptance criteria, deliverables) + the diff, runs review-functionality, review-security and review-quality (parallel subagents when available), de-dupes and prioritizes findings P0/P1/P2, prints a summary to screen and writes the full report to a gitignored artifacts path. Do not use for live UI/runtime smoke (use e2e-test-review) or to apply fixes (use simplify/refactor).

  • Review quality

    gabriel-f-santos/coding-agents/skills/review-quality Skill

    no license0★ repo

    Review changed code for "crap" reduction — reuse, simplification, efficiency, dead code, duplication, naming, and altitude. Use to clean up what was just built — "reduz a gambiarra", "revisa qualidade do código", "tem duplicação/dead code?", "dá pra simplificar essa feature?". Reports findings only (does not apply fixes — use simplify/refactor for that), confidence-based, never security or correctness (those are review-security / review-functionality). Runs standalone or as a subagent of review-phase.

  • Tailscale setup

    gabriel-f-santos/coding-agents/skills/tailscale-setup Skill

    no license0★ repo

    Guia setup completo do Tailscale: conta, cliente na máquina local, ACL policy e geração de auth key para servidor. Invocada pelo /hetzner-vm e /linux-vm-hardening quando ssh_mode=tailscale, ou diretamente para configurar um tailnet do zero. Use quando for usar Tailscale como VPN de acesso SSH a servidores.

  • Tech discovery

    gabriel-f-santos/coding-agents/skills/tech-discovery Skill

    no license0★ repo

    Act as a senior technical architect running technical discovery AFTER product discovery/brainstorming. Use when a problem/product is validated and you need to design the system before building — "discovery técnico", "arquitetura da solução", "como vamos construir isso", "desenho de sistema", "technical discovery", "solution architecture", "definir a arquitetura". Reads the product discovery brief/PRD, explores architecture options with trade-offs, designs boundaries (C4/DDD), the data model, NFRs + cost, and a STRIDE threat model, surfaces the riskiest unknowns as time-boxed spikes, and writes a Tech Discovery Brief that feeds prd-creator and research. Do not use for product/market discovery (use product-discovery), for granular lib/pattern choices per phase (use research), or for the implementation plan (use plan-phase).

  • Software architecture

    karim-bhalwani/agent-skills-collection/skills/software-architecture Skill

    0★ repo

    Guide for quality focused software architecture. Use when designing software systems, reviewing architecture, analyzing code structure, planning refactors, or mentoring on architectural patterns.

  • Interswitch setup

    rexedge/interswitch/skills/interswitch-setup Skill

    no license0★ repo

    Set up the Interswitch API client, environment variables, OAuth 2.0 authentication, and TypeScript helpers for server-side payment integration. Use this skill whenever starting a new Interswitch integration, configuring API keys, creating a reusable fetch wrapper, or setting up the foundation for any Interswitch feature. Also use when you see errors related to missing CLIENT_ID, SECRET_KEY, authentication failures, or need to understand Interswitch's base URLs, passport OAuth flow, response format, currencies, or environment switching (test/live).

  • Syncfusion javascript kanban

    syncfusion/javascript-ui-controls-skills/skills/syncfusion-javascript-kanban Skill

    no license0★ repo

    Implement Syncfusion TypeScript Kanban board for visual task management and workflow tracking. Use this when working with task boards, workflow visualization, or agile project management. This skill covers Kanban board setup, column configuration, card management, swimlanes, drag-and-drop interactions, and WIP limits for TypeScript applications.

  • Syncfusion javascript scheduler

    syncfusion/javascript-ui-controls-skills/skills/syncfusion-javascript-scheduler Skill

    no license0★ repo

    Implement the Syncfusion Essential JS 2 TypeScript Scheduler (Schedule) component for event and appointment management. Use this when working with scheduling interfaces, calendar views, appointment CRUD operations, or resource management. This skill covers scheduler setup, views configuration, appointments handling, recurring events, resource scheduling, timeline views, editor templates, exporting functionality, timezone support, styling, and accessibility features.

  • Architecture

    jovd83/junit5-skill/architecture Skill

    0★ repo

    Use when Codex needs to shape or refactor JUnit 5 suite architecture, test package structure, naming, fixture ownership, reuse patterns, or boundaries between component, integration, and service tests.

  • Tl

    javalenciacai/develop-skills/.agents/skills/tl Skill

    0★ repo

    Technical orchestrator. Tech Lead coordinates Architect (architecture) and Dev (code) for implementation, technical design and code review. Reports to CTO. Use when: (1) Technical decisions or architecture design needed, (2) Code implementation, features or bug fixes required, (3) Code review, refactoring or technical debt management, (4) Technology evaluation or framework selection, (5) Technical documentation like ADRs or design docs, (6) Performance optimization or scalability concerns, (7) Coordinating between architecture design and code implementation.

  • Onboarding plan builder

    stephenrogan/csm-skills/skills/onboarding-plan-builder Skill

    0★ repo

    Creates a structured customer onboarding plan with phased milestones, success criteria, timeline, and responsibility assignments. Adapts by segment and complexity. Use when asked to build an onboarding plan, structure a customer kickoff, create an implementation timeline, design a go-live plan, or when a new customer needs a clear roadmap from contract signing to value realisation. Also triggers for questions about customer onboarding structure, implementation planning, kickoff preparation, time-to-value planning, or how to set up a new customer for success from day one.

  • Migrate to portal

    subsquid-labs/skills/squid-sdk/migrate-to-portal Skill

    no license0★ repo

    Migrate an existing Squid SDK indexer (EVM or Solana) off the v2 gateway and onto the Portal data source. Covers the package swap (`@subsquid/evm-processor` → `@subsquid/evm-stream` + `@subsquid/evm-objects` + `@subsquid/batch-processor` for EVM; `@subsquid/solana-stream@^0.x` → `^1.x` for Solana), the API/type shape changes, and field-selection changes. Use when the user mentions migrating, porting, upgrading, or converting a v2 squid to Portal; references `v2.archive.subsquid.io`, `setGateway`, `setDataSource`, `lookupArchive`, or `SolanaRpcClient`; or hits TS errors on `EvmBatchProcessor`, `evmLog`, or `block.header.slot` after a `@subsquid/*` bump.

  • Ab test setup

    planifest/planifest-framework/planifest-framework/external-skills/ab-test-setup Skill

    0★ repo

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

  • Api contract testing

    planifest/planifest-framework/planifest-framework/external-skills/api-contract-testing Skill

    0★ repo

    Consumer-provider contract testing and release-gate design for compatibility matrices, contract assertions, and CI blocking rules across versions and transports. Trigger when API contract diffs are detected but compatibility evidence is missing or stale (contract test pass, consumer-impact mapping, or compatibility matrix update), or when multiple consumers, versions, or transports must be protected by automated gates. Do not use for first-pass API interface design.

  • Api design graphql

    planifest/planifest-framework/planifest-framework/external-skills/api-design-graphql Skill

    0★ repo

    GraphQL schema and resolver contract design for type boundaries, nullability, authz, and query-cost safety. Trigger when SDL, resolver behavior, field contracts, or query safety controls are added/changed, and their contract impact is not yet explicitly specified. Do not use for REST/OpenAPI endpoint design, API version lifecycle governance, or standalone error taxonomy design.

  • Api design rest

    planifest/planifest-framework/planifest-framework/external-skills/api-design-rest Skill

    0★ repo

    Resource-oriented REST/OpenAPI contract design for URI/method semantics, idempotency, pagination, and HTTP status behavior. Trigger when REST contract diffs are detected in paths, methods, schemas, or status semantics, or when request-response transport choice is still unresolved before implementation. Do not use for GraphQL schema authoring, error-taxonomy-only changes, version lifecycle governance, or consumer-provider contract test implementation.

  • Api design

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

    0★ repo

    Generate secure, composable code changes for an existing project from structured JSON input — use with `code2context` to apply AI-suggested file creates and updates from natural language instructions.

  • Architecture c4 modeling

    planifest/planifest-framework/planifest-framework/external-skills/architecture-c4-modeling Skill

    0★ repo

    C4 architecture modeling workflow for context, container, and component views that make boundaries and responsibilities explicit. Use when teams need a shared structural model before major implementation or refactoring; do not use as a substitute for decision records.

  • Architecture clean architecture

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

    0★ repo

    Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.

  • Architecture ddd

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

    0★ repo

    Domain-driven design workflow for bounded context partitioning, aggregate design, and context mapping in complex domains. Use when domain complexity or organizational scaling requires explicit model boundaries; do not use for small CRUD domains without competing language models.

  • Architecture decision records

    planifest/planifest-framework/planifest-framework/external-skills/architecture-decision-records Skill

    0★ repo

    Architecture Decision Record workflow for capturing technical decisions, alternatives, trade-offs, and revision triggers over time. Use when decisions materially affect system behavior, cost, or team workflow; do not use for trivial implementation choices.

  • Architecture event driven

    planifest/planifest-framework/planifest-framework/external-skills/architecture-event-driven Skill

    0★ repo

    Event-driven architecture workflow for asynchronous integration, decoupled workflows, and failure-tolerant event propagation. Use when temporal decoupling and independent evolution are required; do not use when strict synchronous consistency is mandatory across all steps.

  • Architecture microservices

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

    0★ repo

    Microservices architecture workflow for service boundary design, independent deployability, and distributed operational safety. Use when domain and team structure justify independent service evolution; do not use as a default scaling strategy for all systems.

  • Architecture monolith

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

    0★ repo

    Modular monolith architecture workflow for strong domain boundaries, transactional consistency, and operational simplicity in a single deployable. Use when teams need fast delivery and coherent data consistency with controlled complexity; do not use when independent runtime scaling boundaries are mandatory.

  • Architecture principles

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

    0★ repo

    Define architecture principles and review guardrails before choosing monolith, microservices, serverless, or event-driven options. Use when teams need explicit decision criteria; do not use to record final decisions.

  • Architecture serverless

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

    0★ repo

    Serverless architecture workflow for event-driven and bursty workloads using managed compute and platform services. Use when elasticity and reduced platform operations justify managed-service constraints; do not use when workload shape requires long-lived stateful control loops.

  • Architecture tradeoff analysis

    planifest/planifest-framework/planifest-framework/external-skills/architecture-tradeoff-analysis Skill

    0★ repo

    Architecture trade-off analysis workflow for comparing options with explicit criteria, weighting, and sensitivity under uncertainty. Use when multiple viable architecture choices exist and rationale must be defensible; do not use after architecture direction is already fixed.