Agent Skills: architecture-decision
Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.
ID: jwynia/agent-skills/architecture-decision
Install this agent skill to your local
Skill Files
The files that make up architecture-decision.
More agent skills
- maven-plugin-configurationUse when configuring Maven plugins, setting up common plugins like compiler, surefire, jar, or creating custom plugin executions.
- power-flow-dataPower system network data formats and topology. Use when parsing bus, generator, and branch data for power flow analysis.
- ux-compareCompare UX patterns across multiple reference apps using pattern libraries produced by ux-extract. Reads 2+ pattern-library.md files, walks them category by category, identifies where apps converge (strong signal), where they diverge (genuine design choice), what's unique to one app, and what's absent across the set. Produces an opinionated comparison document with recommendations for a new build. No browser needed — pure markdown analysis. Trigger with 'compare UX patterns', 'how do top apps handle X', 'ux comparison', 'pattern comparison across reference apps'.
- copilot-usage-metricsRetrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.
- azure-resource-health-diagnoseAnalyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.
- cloudbase-cliCloudBase CLI (tcb, 云开发CLI, Tencent CloudBase命令行) resource management skill. Use when deploying cloud functions, CloudRun, storage, NoSQL/MySQL, static hosting, permissions, CORS/domains via tcb; for CI/CD and batch ops; when the user prefers CLI; or as the first-session fallback when CloudBase MCP tools are not loaded yet (after install/config, before IDE restart). Covers tcb login (device code for Tencent Cloud accounts; --cloudbase-api-key -e for environment API Key without an account; --apiKeyId/--apiKey for CI) and domain commands (fn/hosting/cloudrun/…) as MCP auth/manage parity — do not default to tcb deploy.