adr AI Agent Skills
Browse 512 skills related to adr
architecture-decision-records
wshobsonWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
hqq-quantization
davila7Half-Quadratic Quantization for LLMs without calibration data. Use when quantizing models to 4/3/2-bit precision without needing calibration datasets, for fast quantization workflows, or when deploying with vLLM or HuggingFace Transformers.
cto-advisor
davila7Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.
architecture
davila7Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
architecture-decision-records
sickn33Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...
V3 Memory Unification
ruvnetUnify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).
V3 Deep Integration
ruvnetDeep agentic-flow@alpha integration implementing ADR-001. Eliminates 10,000+ duplicate lines by building claude-flow as specialized extension rather than parallel implementation.
V3 Swarm Coordination
ruvnet15-agent hierarchical mesh coordination for v3 implementation. Orchestrates parallel execution across security, core, and integration domains following 10 ADRs with 14-week timeline.
senior-architect
alirezarezvaniThis skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan for scalability", "make technical decisions", or "review system design". Use for architecture decision records (ADRs), tech stack evaluation, system design reviews, dependency analysis, and generating architecture diagrams in Mermaid, PlantUML, or ASCII format.
decisions
recyclarrUse when creating or editing ADRs or PDRs in docs/decisions/
swiss-geo
openclawSchweizer Geodaten, POIs und Tourismus. Orte/Adressen suchen, Höhen abfragen, städtische POIs finden (Restaurants, Cafés, Sehenswürdigkeiten via OpenStreetMap), ÖV-Fahrplan, Kartenlinks. Nutze bei Fragen zu Schweizer Orten, Attraktionen, Ausflügen oder Koordinaten.
architecture-designer
openclawUse when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
roadrunner
openclawBeeper Desktop CLI for chats, messages, search, and reminders.
adr-gen
openclawGenerate Architecture Decision Records with AI. Use when documenting technical decisions.
adr-writer
openclawGenerate Architecture Decision Records with AI. Use when documenting technical decisions.
adr-generator
Adr Generator - Auto-activating skill for Technical Documentation. Triggers on: adr generator, adr generator Part of the Technical Documentation skill category.
line-area-chart
Build LineChart and AreaChart components. Use for time series, trends, and continuous data visualization.
nuxt-module
Using nuxt-charts module in Nuxt applications. Use when building charts in Nuxt projects.
common-patterns
Common patterns and best practices for vue-chrts. Use for general guidance on data formatting, styling, and chart configuration.
maps
Build map visualizations with TopoJSONMap and DottedMap. Use for geographical data, choropleth maps, and location-based visualizations.
bar-chart
Build BarChart components. Use for categorical comparisons, grouped bars, and stacked bars.
bubble-chart
Build BubbleChart components. Use for scatter plots with size encoding, showing relationships between three variables.
donut-chart
Build DonutChart components. Use for part-to-whole relationships and percentage breakdowns.
gantt-chart
Build GanttChart (timeline) components. Use for project timelines, schedules, and temporal data visualization.
dagre-graph
Build DagreGraph components for hierarchical diagrams. Use for org charts, dependency graphs, flowcharts, and decision trees.
vue-chrts-overview
Overview of vue-chrts and nuxt-charts libraries. Use when the user asks about available charts, installation, or general library capabilities.
dual-chart
Build DualChart components combining bars and lines. Use for showing relationships between two different metrics on the same visualization.
sankey-chart
Build SankeyChart components. Use for visualizing flows, conversions, and resource distribution between stages.
ui-design-nuxt-ui
When adding or editing UI, always use Nuxt UI components by default. Check the Nuxt UI MCP for available components and their APIs."
qubo-formulator
a5c-aiQUBO (Quadratic Unconstrained Binary Optimization) formulation skill for optimization problems
adr-generator
a5c-aiSpecialized skill for generating and managing Architecture Decision Records (ADRs). Supports Nygard, MADR, and custom templates with auto-numbering, linking, and status management.
generating-documentation
ancolemanGenerate comprehensive technical documentation including API docs (OpenAPI/Swagger), code documentation (TypeDoc/Sphinx), documentation sites (Docusaurus/MkDocs), Architecture Decision Records (ADRs), and diagrams (Mermaid/PlantUML). Use when documenting APIs, libraries, systems architecture, or building developer-facing documentation sites.
adr-documentation
MadAppGangArchitecture Decision Records (ADR) documentation practice. Use when documenting architectural decisions, recording technical trade-offs, creating decision logs, or establishing architectural patterns. Trigger keywords - "ADR", "architecture decision", "decision record", "trade-offs", "architectural decision", "decision log".
V3 Deep Integration
proffesor-for-testingDeep agentic-flow@alpha integration implementing ADR-001. Eliminates 10,000+ duplicate lines by building claude-flow as specialized extension rather than parallel implementation.
V3 Swarm Coordination
proffesor-for-testing15-agent hierarchical mesh coordination for v3 implementation. Orchestrates parallel execution across security, core, and integration domains following 10 ADRs with 14-week timeline.
V3 Memory Unification
proffesor-for-testingUnify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).
architecture-patterns
groupzer0Common software architecture patterns, ADR templates, and anti-pattern detection. Supports architectural review, design decisions, and system documentation.
technical-writing
rsmdtCreate architectural decision records (ADRs), system documentation, API documentation, and operational runbooks. Use when capturing design decisions, documenting system architecture, creating API references, or writing operational procedures.
architecture-paradigms
atholaInteractive selector and router for architecture paradigms. Use when selecting architecture patterns for new systems, comparing paradigm trade-offs, creating architecture decision records, evaluating architecture fit for team size and domain complexity, planning implementation roadmaps. Do not use when implementing a specific known paradigm - use the specific architecture-paradigm-* skill (hexagonal, layered, microservices, etc.) instead. reviewing existing architecture - use architecture-review instead. Use this skill BEFORE making architecture decisions. Check even if unsure about needs.
documentation-criteria
shinprGuides PRD, ADR, Design Doc, and Work Plan creation with templates and decision matrix.
canonical-format-checker
panaversityThis skill should be used when content teaches patterns (skills, subagents, ADRs, PHRs, specifications) that have canonical sources elsewhere. Prevents format drift by ensuring content references and follows the authoritative format from canonical sources. Use before implementing lessons that teach platform patterns, or when reviewing content for format consistency.
ln-002-best-practices-researcher
levnikolaevichResearch best practices via MCP Ref/Context7/WebSearch and create documentation (guide/manual/ADR/research). Single research, multiple output types.
ln-120-reference-docs-creator
levnikolaevichCreates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices). L2 Worker in ln-100-documents-pipeline.
typescript-docs
giuseppe-trisciuoglioGenerates comprehensive TypeScript documentation using JSDoc, TypeDoc, and multi-layered documentation patterns for different audiences. Use when creating API documentation, architectural decision records (ADRs), code examples, and framework-specific patterns for NestJS, Express, React, Angular, and Vue.
architecture-decision-record
yonatangrossUse this skill when documenting significant architectural decisions. Provides ADR templates following the Nygard format with sections for context, decision, consequences, and alternatives. Use when writing ADRs, recording decisions, or evaluating options.
tech-evaluator
HaaaiawdEvaluate technology stack options using a weighted decision matrix and the ATAM methodology to produce Architecture Decision Records (ADR).
project-planner
adrianpuiuComprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
lead-architect
kienhaminhUse for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
