Frontend Architecture

2.5k

exceptionless

Svelte SPA architecture for Exceptionless. Route groups, lib structure, API client, feature slices, and barrel exports. Keywords: route groups, $lib, feature slices, api-client, barrel exports, index.ts, vertical slices, shared components, generated models, ClientApp structure

multi-tenancy

756

dadbodgeoff

Implement multi-tenant architecture with tenant isolation, data separation, and per-tenant configuration. Supports shared database and schema-per-tenant models.

code-architecture-wrong-abstraction

159

flpbalada

Guides when to abstract vs duplicate code. Use this skill when creating shared utilities, deciding between DRY/WET approaches, or refactoring existing abstractions.

runner-dev

36

lemline

Development guide for the lemline-runner ecosystem. Use when working with the modular runner architecture (lemline-runner-* modules), messaging (commands/events channels), feature modules (waits, retries, parents, schedules, listeners, forks, failures), shared infrastructure (lemline-runner-common), CLI commands, configuration, repositories with Kotlin coroutines, or Flyway migrations. Covers the dual-channel architecture, outbox pattern, and production best practices for the Quarkus/Kotlin runtime.

gemini-workspace-bridge

31

melodic-software

Central authority for Claude–Gemini shared workspace architecture. Defines directory structure, artifact exchange, and file-naming conventions. Use when setting up dual-CLI workflows, deciding where to store AI artifacts, or managing cross-CLI file exchange.

agent-communication

29

omer-metin

Inter-agent communication patterns including message passing, shared memory, blackboard systems, and event-driven architectures for LLM agents. Use when terms such as agent communication, message passing, inter-agent, blackboard, agent events, multi-agent, communication, message-passing, events, coordination are mentioned.

design-systems

29

omer-metin

World-class design systems architecture - tokens, components, documentation, and governance. Design systems create the shared language between design and engineering that makes products feel cohesive at any scale. Use when "design system, component library, design tokens, atomic design, style guide, theme, theming, design scale, component api, variant, figma tokens, style dictionary, design-system, tokens, components, theming, documentation, figma, accessibility, versioning" mentioned.

multi-agent-architecture

27

majesticlabs-dev

Patterns for designing multi-agent systems with Claude Code - job description method, shared folder communication, handbook consolidation, context management. Use when building complex agent orchestrations.

mermaid-gen

23

ajoslin

Generate syntactically correct Mermaid diagrams for technical documentation

platform-infrastructure

22

liqiongyu

Produce a Platform & Infrastructure Improvement Pack (shared capabilities plan, reliability/performance/privacy targets, scaling triggers, analytics + discoverability decisions, execution roadmap). Use for platform engineering, infrastructure planning, scalability, reliability, and architecture foundations.

architecture-analysis

16

front-depiction

Architectural dependency analysis and impact assessment. Use for: (1) Blast radius - who depends on a service, what breaks if I change it; (2) Dependency tree - what does a service depend on (ancestors/upstream); (3) Root cause analysis - find shared dependencies when multiple services fail; (4) Architecture metrics - coupling (density), depth (diameter), connectivity; (5) Domain discovery - identify module boundaries via cut vertices; (6) Hot services - critical infrastructure with many dependents; (7) Impact assessment before changes; (8) Debugging cascading failures; (9) Identifying god services, tight coupling, deep hierarchies. Provides graph-based analysis via CLI commands: analyze, blast-radius, ancestors, common-ancestors, metrics, domains, hot-services. All agents can use this for architectural questions.

swiftui-architecture

14

mintuz

WHEN building SwiftUI views, managing state, setting up shared services, or making architectural decisions; NOT for UIKit or legacy patterns; provides pure SwiftUI data flow without ViewModels using @State, @Binding, @Observable, and @Environment.

learn

12

darkroomengineering

Persistent memory system for storing and recalling learnings across sessions. Supports local (personal) and shared (team) knowledge tiers. AUTO-INVOKE THIS SKILL when you: - Fix a non-obvious bug (store as "bug") - Discover a useful code pattern (store as "pattern") - Encounter a gotcha or edge case (store as "gotcha") - Find a useful tool/library feature (store as "tool") - Make a performance optimization (store as "perf") - Discover configuration that solved a problem (store as "config") - Make an architecture decision with rationale (store as "arch") - Find a useful testing insight (store as "test") Also invoke when user says: "remember this", "store learning", "recall learnings", "what did we learn", "lessons learned"

Monorepo Setup

12

patricio0312rev

Sets up monorepo architecture with Turborepo, pnpm workspaces, shared packages, and optimized build pipelines. Use when users request 'monorepo setup', 'Turborepo', 'pnpm workspaces', 'shared packages', or 'multi-package repository'.

clean-architecture

11

marcioaltoe

Clean Architecture principles for Modular Monolith with bounded contexts and minimal shared kernel. **ALWAYS use when working on backend code, ESPECIALLY when creating files, deciding file locations, or organizing contexts (auth, tax, bi, production).** Use proactively to ensure context isolation and prevent "Core Obesity Syndrome". Examples - "create entity", "add repository", "where should this file go", "modular monolith", "bounded context", "shared kernel", "context isolation", "file location", "layer organization".

architecture-auditor

11

marcioaltoe

Architecture audit and analysis specialist for Modular Monoliths. **ALWAYS use when reviewing codebase architecture, evaluating bounded contexts, assessing shared kernel size, detecting "Core Obesity Syndrome", or comparing implementation against ADR-0001 and anti-patterns guide.** Use proactively when user asks about context isolation, cross-context coupling, or shared kernel growth. Examples - "audit contexts structure", "check shared kernel size", "find cross-context imports", "detect base classes", "review bounded context isolation", "check for Core Obesity".

mermaid-gen

9

vladm3105

Generate syntactically correct Mermaid diagrams for technical documentation

doc-review

9

vladm3105

Review a single file or all files in a folder for data inconsistencies, reference errors, typos, and unclear terminology using parallel sub-agents

code-analyzer

9

petbrains

Comprehensive codebase analysis for building a mental model of project structure, dependencies, and implementation context. Use when needing to: (1) understand project architecture before review or documentation; (2) find dependencies and shared modules; (3) locate implementation markers (AICODE-*); (4) prepare context for review, memory generation, or agent creation. Triggers: analyze code, load code context, scan codebase, understand project structure.

doc-tasks

9

vladm3105

Create Task Breakdown (TASKS) - Layer 11 artifact decomposing SPEC into AI-structured TODO tasks

doc-validator

9

vladm3105

Cross-document validation, traceability gaps, and project-wide consistency checks for SDD framework

context-analyzer

9

vladm3105

Project context analysis engine that scans project structure and surfaces relevant information for documentation creation

trace-check

9

vladm3105

Validate and update bidirectional traceability across SDD artifacts

n8n

9

vladm3105

Develop workflows, custom nodes, and integrations for n8n automation platform

test-automation

9

vladm3105

Create test plans, write tests, validate code quality through testing

project-mngt

9

vladm3105

Product Owner / Project Manager skill for MVP/MMP/MMR implementation planning

charts-flow

9

vladm3105

Create and manage Mermaid architecture diagrams with automatic SVG generation

quality-advisor

9

vladm3105

Proactive quality guidance system that monitors artifact creation and provides real-time feedback on documentation quality

project-init

9

vladm3105

Initialize projects with AI Dev Flow framework using domain-aware setup

saas-architecture-advisor

9

TerminalSkills

Advises on multi-tenant SaaS architecture decisions including tenancy models, data isolation strategies, tenant routing, and scaling patterns. Use when someone is building a SaaS product, converting single-tenant to multi-tenant, or evaluating isolation strategies. Trigger words: multi-tenant, SaaS architecture, tenant isolation, shared database, per-tenant database, row-level security, tenant routing, SaaS patterns.

doc-naming

9

vladm3105

Enforces unified ID naming standards and threshold naming rules for all SDD documentation artifacts

skill-recommender

9

vladm3105

Intelligent skill suggestion engine that analyzes user intent and project context to recommend appropriate documentation skills

doc-ref

9

vladm3105

Create Reference Documents (REF) - supplementary documentation that doesn't participate in formal traceability chain

refactor-flow

9

vladm3105

Improve code quality, reduce technical debt, restructure for maintainability

adr-roadmap

9

vladm3105

Generate phased implementation roadmaps from Architecture Decision Records

workflow-optimizer

9

vladm3105

Workflow navigation assistant that recommends next steps and optimizes documentation sequence through the SDD workflow

analytics-flow

9

vladm3105

Analytics and data analysis workflow skill

contract-tester

9

vladm3105

Test and validate API contracts against specifications

security-audit

9

vladm3105

Security analysis, vulnerability assessment, and security code reviews

devops-flow

9

vladm3105

DevOps, MLOps, DevSecOps practices for cloud environments (GCP, Azure, AWS)

google-adk

9

vladm3105

Develop agentic software and multi-agent systems using Google ADK in Python

doc-ctr

9

vladm3105

Create Data Contracts (CTR) - Optional Layer 8 artifact using dual-file format (.md + .yaml) for API/data contracts

doc-flow

9

vladm3105

AI-Driven Specification-Driven Development (SDD) workflow orchestrator - guides skill selection and general SDD methodology

better-chatbot

9

jackspace

This skill provides project-specific coding conventions, architectural principles, repository structure standards, testing patterns, and contribution guidelines for the better-chatbot project (https://github.com/cgoinglove/better-chatbot). Use this skill when contributing to or working with better-chatbot to understand the design philosophy and ensure code follows established patterns. Includes: API architecture deep-dive, three-tier tool system (MCP/Workflow/Default), component design patterns, database repository patterns, architectural principles (progressive enhancement, defensive programming, streaming-first), practical templates for adding features (tools, routes, repositories). Use when: working in better-chatbot repository, contributing features/fixes, understanding architectural decisions, following server action validators, implementing tools/workflows, setting up Playwright tests, adding API routes, designing database queries, building UI components, handling multi-AI provider integration Keywords: better-chatbot, chatbot contribution, better-chatbot standards, chatbot development, AI chatbot patterns, API architecture, three-tier tool system, repository pattern, progressive enhancement, defensive programming, streaming-first, compound component pattern, Next.js chatbot, Vercel AI SDK chatbot, MCP tools, workflow builder, server action validators, tool abstraction, DAG workflows, shared business logic, safe() wrapper, tool lifecycle

code-review

9

vladm3105

Code review skill for quality, standards compliance, and best practices

domain-driven-design

5

booklib-ai

Design and review software using patterns from Eric Evans' "Domain-Driven Design." Use for DDD tactical patterns (Entities, Value Objects, Aggregates, Repositories, Factories, Domain Services), strategic patterns (Bounded Context, Context Map, Anticorruption Layer, Shared Kernel, Open Host Service), supple design (Intention-Revealing Interfaces, Side-Effect-Free Functions, Closure of Operations), distillation (Core Domain, Segregated Core), large-scale structure (Responsibility Layers, Knowledge Level), and Ubiquitous Language. Trigger on "DDD", "domain-driven design", "bounded context", "aggregate root", "value object", "entity", "repository pattern", "domain service", "anticorruption layer", "context map", "ubiquitous language", "core domain", "specification pattern", "supple design", "layered architecture", or "strategic design."

domain-driven-design

5

ZLStas

Design and review software using patterns from Eric Evans' "Domain-Driven Design." Use for DDD tactical patterns (Entities, Value Objects, Aggregates, Repositories, Factories, Domain Services), strategic patterns (Bounded Context, Context Map, Anticorruption Layer, Shared Kernel, Open Host Service), supple design (Intention-Revealing Interfaces, Side-Effect-Free Functions, Closure of Operations), distillation (Core Domain, Segregated Core), large-scale structure (Responsibility Layers, Knowledge Level), and Ubiquitous Language. Trigger on "DDD", "domain-driven design", "bounded context", "aggregate root", "value object", "entity", "repository pattern", "domain service", "anticorruption layer", "context map", "ubiquitous language", "core domain", "specification pattern", "supple design", "layered architecture", or "strategic design."

Feature-Sliced Design

5

constellos

This skill should be used when the user asks to "implement FSD", "use Feature-Sliced Design", "organize architecture", "structure project folders", "set up FSD layers", "create feature slices", "refactor to FSD", "add FSD structure", or mentions "feature slices", "layered architecture", "FSD methodology", "architectural organization", "views layer", "entities layer", "shared layer", "Next.js with FSD", or "Turborepo FSD structure". Provides comprehensive guidance for implementing Feature-Sliced Design methodology in Next.js applications with custom 'views' layer naming.