home/categories/architecture-patterns
category focus

Architecture

Design patterns and architectural blueprints.

4113 skillsall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
architecture-patterns
56

personalization-logic

Use when defining dynamic content rules, tokens, and conditional offers inside nurture programs.

gtmagents
gtmagents
development
open
architecture-patterns
56

experience-system-blueprint

Documentation pattern for translating brand platforms into modular experience systems.

gtmagents
gtmagents
development
open
architecture-patterns
56

pursuit-governance

Use to set cadences, decision logs, and escalation paths for enterprise pursuits.

gtmagents
gtmagents
development
open
architecture-patterns
56

community-engagement

Use when planning programs, rituals, and response frameworks for owned or partner communities.

gtmagents
gtmagents
development
open
architecture-patterns
56

co-branding

Use to enforce visual, messaging, and legal standards across partner campaigns.

gtmagents
gtmagents
development
open
architecture-patterns
56

advocacy-programs

Use when designing and scaling reference, story, advisory, or community programs.

gtmagents
gtmagents
development
open
architecture-patterns
56

decision-trees

Use when designing branching logic, eligibility rules, and fallback paths.

gtmagents
gtmagents
development
open
architecture-patterns
56

escalation-framework

Use to govern executive involvement, cross-functional response, and risk resolution for at-risk renewals.

gtmagents
gtmagents
development
open
architecture-patterns
56

cohort-analysis

Standard method for slicing bookings, pipeline, and retention cohorts for diagnostics.

gtmagents
gtmagents
development
open
architecture-patterns
55

discover-distributed-systems

Automatically discover distributed systems skills when working with consensus, CRDTs, replication, partitioning, and distributed algorithms

rand
rand
development
open
architecture-patterns
55

typed-holes-refactor

Refactor codebases using Design by Typed Holes methodology - iterative, test-driven refactoring with formal hole resolution, constraint propagation, and continuous validation. Use when refactoring existing code, optimizing architecture, or consolidating technical debt through systematic hole-driven development.

rand
rand
development
open
architecture-patterns
55

atris-backend

Backend architecture policy. Use when building APIs, services, data access, or any backend work. Prevents over-engineering.

atrislabs
atrislabs
development
open
architecture-patterns
47

context7-usage

Patterns for using Context7 MCP for library documentation (v2.25)

alfredolopez80
alfredolopez80
development
open
architecture-patterns
47

typescript

TypeScript strict patterns and best practices. Trigger: When writing TypeScript code - types, interfaces, generics.

yacosta738
yacosta738
development
open
architecture-patterns
47

sandi-metz-rules

This skill should be used when users request code review, refactoring, or code quality improvements for Ruby codebases. Apply Sandi Metz's four rules for writing maintainable object-oriented code - classes under 100 lines, methods under 5 lines, no more than 4 parameters, and controllers instantiate only one object. Use when users mention "Sandi Metz", "code quality", "refactoring", or when reviewing Ruby code for maintainability.

nateberkopec
nateberkopec
development
open
architecture-patterns
46

scalability-advisor

Guidance for scaling systems from startup to enterprise scale. Use when planning for growth, diagnosing bottlenecks, or designing systems that need to handle 10x-1000x current load.

alirezarezvani
alirezarezvani
development
open
architecture-patterns
45

spring-boot-best-practices

Generate Spring Boot components following modern Java best practices and team conventions

kousen
kousen
development
open
architecture-patterns
44

moai-foundation-context

Enterprise context and session management with token budget optimization and state persistence

modu-ai
modu-ai
development
open
architecture-patterns
44

implement-feature

Guide for implementing features following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to a Swift app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers

tddworks
tddworks
development
open
Previous
Page 64 / 172
Next