avav25/architecture
plugin/skills/architecture/SKILL.md
Use this skill when the user wants "architecture" work but the scope is ambiguous and you want auto-classification — as the architecture entry-point router that classifies the request as feature design, existing-system analysis, or migration/evolution and then dispatches to `/architecture-design`, `/architecture-analyze`, or `/architecture-evolve`. For a known scope, invoke the specialized command directly instead.
$ install --global
skillsauthnpx skillsauth add avav25/ai-assets architectureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 23, 2026, 4:32 AM98.5s6 files scanned
SKILL.md
- name:
- architecture
- description:
- Use this skill when the user wants "architecture" work but the scope is ambiguous and you want auto-classification — as the architecture entry-point router that classifies the request as feature design, existing-system analysis, or migration/evolution and then dispatches to `/architecture-design`, `/architecture-analyze`, or `/architecture-evolve`. For a known scope, invoke the specialized command directly instead.
- context:
- fork
- argument-hint:
- <feature PRD, analysis request, or migration brief>
/architecture — Scope Router
Thin dispatcher. The bulk of architecture work lives in three specialized skills with focused scopes:
| Skill | Scope | Routes to |
|---|---|---|
| /architecture-design | Feature-level design from a PRD | Agent(solution-architect) (default), Agent(cloud-architect) (--cloud), Agent(devops-architect) (--cicd) |
| /architecture-analyze | Document existing system; gap analysis; tech-debt register | Agent(system-architect) (default), Agent(cloud-architect) (--cloud), Agent(devops-architect) (--cicd) |
| /architecture-evolve | Migration / redesign / cross-tech evolution | Agent(solution-architect) + Agent(system-architect) |
When to use
- Scope is unclear and you want auto-classification
- Quick entry point when you do not remember the specialized command name
For known scope, prefer the specialized command directly — it avoids the dispatch round-trip.
Behavior
- Read the user's input.
- Classify scope via these triggers:
| Trigger phrase | Classified as |
|---|---|
| "PRD", "feature", "design", "new capability", "endpoint", "API" | Feature design |
| "analyze", "document architecture", "audit", "tech debt", "what do we have" | Analysis |
| "migrate", "redesign", "from X to Y", "replace", "evolve", "modernize" | Evolution |
| "cloud", "GCP", "Azure", "AWS", "landing zone", "networking", "VPC" | + --cloud flag |
| "CI/CD", "pipeline", "deployment", "GitHub", "platform engineering" | + --cicd flag |
- Announce the classification and dispatch:
Classified as: <feature design | analysis | evolution> [+ <flag>]
Dispatching to: /architecture-<design | analyze | evolve> [<flag>]
-
If the input contains conflicting signals (e.g. both "PRD for new feature" and "migrate from old system") — present the candidate classifications to the user and ask. Do not pick silently.
-
If the input is too sparse to classify — ask the user one clarifying question (scope: design / analyze / evolve?) before dispatching.
Why this exists
The previous monolithic /architecture skill bundled all three scopes inline and crowded the 12K skill-body limit. Splitting into three focused workflows (per the agentskills.io single-responsibility recommendation) keeps each scope readable, lets each declare scope-specific NFRs and quality gates, and avoids step duplication for users who already know their scope.
Integration
- Dispatches to:
/architecture-design,/architecture-analyze,/architecture-evolve - Templates: shared at
${CLAUDE_PLUGIN_ROOT}/skills/architecture/assets/(adr-template, c4-mermaid-template, nfr-template, gap-analysis-template, tech-debt-register-template) — referenced by all three specialized skills
Related Skills
avav25/knowledge-sync
development
VerifiedTrustedCommunity
Use this skill when running the recurring (daily) knowledge-base rescan for a repo that already has knowledge/.knowledge-sync.yml — the main-thread dispatcher that reads the config, computes the git delta since last_scanned_sha, maps changed paths to affected doc areas, early-exits cheaply when nothing changed, then fans out one Agent(content-writer) per affected area, applies the propose/direct update policy, advances the baseline only on success, and writes an L4 run log — all with the G1 untrusted-content choke-point, secret-scan, deny-list, and budget controls woven in. For first-time setup use /knowledge-sync-init.
1SKILL.mdUpdated May 24, 2026
avav25/knowledge-sync-init
development
VerifiedTrustedCommunity
Use this skill when bootstrapping scheduled knowledge-base sync for a repo that has no knowledge/.knowledge-sync.yml yet — to run one-time setup that detects the knowledge_root from CLAUDE.md/AGENTS.md, maps doc areas to source globs, records opt-in external sources (Linear/Notion/WebFetch, all disabled by default), captures a baseline last_scanned_sha, sets the per-area update policy, generates or seeds knowledge/CONVENTIONS.md, provisions the L4 memory dir, and offers to register the daily routine. Routes ongoing recurring sync operations to /knowledge-sync.
1SKILL.mdUpdated May 24, 2026
avav25/ai-skills-init
tools
VerifiedTrustedCommunity
Use this skill when bootstrapping a target repository to be ai-skills-aware — on the first run of any ai-skills workflow in a fresh repo, when adopting the ai-skills plugin in an existing repo, or after upgrading to a plugin version that adds new memory paths or templates, including when the user does not say "init" but asks to "set up" or "onboard" the repo — to detect codebase type, create CLAUDE.md + AGENTS.md scaffolding, initialize the .ai-skills-memory/ directory tree from L1 templates, and configure .gitignore. Idempotent — safe to re-run. Accepts `--codebase-type <type>` and `--overwrite`. Not for re-initializing only memory — use `/memory-init` instead.
1SKILL.mdUpdated May 18, 2026
avav25/plugin-author
tools
VerifiedTrustedCommunity
Use this skill when extending, repairing, or improving plugin assets, when ingesting a `/feedback` report as a fix-cycle backlog, or when you do not remember which lower-level command is right for the job — the umbrella workflow for ai-skills plugin-asset authoring and maintenance: creating, auditing, fixing, improving, refactoring, and migrating skills, agents, rules, hooks, prompts, schemas, and rubrics inside the plugin. Auto-classifies the request, loads the right knowledge skills (`@prompt-engineering`, `@context-engineering`, `@team-protocols`), and spawns the right subagents (`prompt-engineer`, `system-architect`, `python-engineer`, `software-engineer`, `qa-engineer`, `eval-judge`) via the `Agent` tool.
1SKILL.mdUpdated May 14, 2026