Back to categories
Category

Agent Skills in category: architecture

63 skills match this category. Browse curated collections and explore related Agent Skills.

nuxt-layers

Working with Nuxt layers (base, nuxt-ui, x-ui) that provide shared functionality. Use when understanding layer architecture, importing from layers, extending layer functionality, or creating new layers.

nuxtlayer-architecturefrontend-frameworkmodular-design
leeovery
leeovery
1

nuxt-repositories

Repository pattern for API access with automatic model hydration. Use when creating repositories for API resources, configuring model hydration, adding custom API methods, or registering repositories in app config.

repository-patternapimodel-hydrationnuxt
leeovery
leeovery
1

nuxt-architecture

Foundational architecture for Nuxt 4 + Vue 3 + Nuxt UI applications. Use when starting new projects, understanding project structure, or making architectural decisions about directory organization, technology choices, and pattern selection.

nuxtvue3nuxt4project-structure
leeovery
leeovery
1

documentation-architect

>

documentationarchitecture-documentsdocumentation-architecturearchitecture-design
ddunnock
ddunnock
1

swift-architecture

Master iOS/macOS app architecture - MVVM, Clean Architecture, Coordinator, DI, Repository

iosmacosmvvmclean-architecture
pluginagentmarketplace
pluginagentmarketplace
0

technical-decision-making

Master technical decision-making, architecture choices, technology evaluation, and technical roadmaps for engineering teams

technical-decision-makingtechnology-evaluationarchitecture-patternstechnology-roadmap
pluginagentmarketplace
pluginagentmarketplace
0

technical-discussion

Document technical discussions as expert architect and meeting assistant. Capture context, decisions, edge cases, debates, and rationale without jumping to specification or implementation. Second phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) Users discuss/explore/debate architecture or design, (2) Working through edge cases before specification, (3) Need to document technical decisions and their rationale, (4) Capturing competing solutions and why choices were made. Creates documentation in docs/workflow/discussion/{topic}.md that technical-specification uses to build validated specifications.

architecturearchitectural-decisionsdecision-logstechnical-specifications
leeovery
leeovery
9

symmetry-group-identifier

Use when you've identified candidate symmetries and need to map them to mathematical groups for architecture design. Invoke when user mentions cyclic groups, dihedral groups, Lie groups, SO(3), SE(3), permutation groups, or needs to formalize symmetries into group theory language. Provides taxonomy and mathematical foundations from Visual Group Theory principles.

group-theorysymmetrycyclic-groupsdihedral-groups
lyndonkl
lyndonkl
0

decomposition-reconstruction

Use when dealing with complex systems that need simplification, identifying bottlenecks or critical failure points, redesigning architecture or processes for better performance, breaking down problems that feel overwhelming, analyzing dependencies to understand ripple effects, user mentions "this is too complex", "where's the bottleneck", "how do we redesign this", "what are the key components", or when optimization requires understanding how parts interact.

task-decompositiondependency-analysissystems-analysisprocess-improvement
lyndonkl
lyndonkl
0

equivariant-architecture-designer

Use when you have validated symmetry groups and need to design neural network architecture that respects those symmetries. Invoke when user mentions equivariant layers, G-CNN, e3nn, steerable networks, building symmetry into model, or needs architecture recommendations for specific symmetry groups. Provides architecture patterns and implementation guidance.

machine-learningarchitectural-patternsgeometric-deep-learningequivariant-layers
lyndonkl
lyndonkl
0

adr-architecture

Use when documenting significant technical or architectural decisions that need context, rationale, and consequences recorded. Invoke when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when team needs to understand why a decision was made. Use when user mentions ADR, architecture decision, technical decision record, or decision documentation.

architecture-decision-recordarchitectural-decisionstechnical-specificationsdeveloper-guidance
lyndonkl
lyndonkl
0

domain-driven-design

This skill should be used whenever domain modeling is taking place. It provides specialized guidance for type-driven and data-driven design based on Rich Hickey and Scott Wlaschin's principles. The skill helps contextualize current modeling within the existing domain model, identifies inconsistencies, builds ubiquitous language, and creates visualizations (Mermaid, Graphviz/DOT, ASCII diagrams) to communicate domain concepts clearly. Use this skill when designing types, modeling business domains, refactoring domain logic, or ensuring domain consistency across a codebase.

domain-driven-designdomain-modelingdiagram-generationarchitecture-patterns
bfollington
bfollington
0

design-documentation

Transform approved requirements into comprehensive technical designs. Define system architecture, component interactions, data models, and interfaces to create a blueprint for implementation.

software-architecturecomponent-compositiondata-modelingAPI-design
Kiro Team
Kiro Team
0

Page 2 of 2 · 63 results