From vamfi-software-consultancy
This skill should be used when the user asks to "assess the current architecture", "document the existing system", "analyse the codebase", "identify technical debt", "review the legacy system", "produce a current-state report", or needs to understand what exists before designing a target architecture.
npx claudepluginhub vamfi/vamfi-plugins --plugin vamfi-software-consultancyThis skill uses the workspace's default tool permissions.
Systematically assess an existing system or codebase to produce a clear picture of the current architecture, capabilities, and technical debt. This assessment drives the gap analysis that informs the target architecture.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Systematically assess an existing system or codebase to produce a clear picture of the current architecture, capabilities, and technical debt. This assessment drives the gap analysis that informs the target architecture.
No target architecture is designed in a vacuum. This skill documents what exists today — its strengths, its limitations, and the debt that will impede change — so that the target architecture is grounded in reality.
Catalogue what exists:
Read the codebase (if available) using Glob and Read to supplement what the user provides.
Identify the dominant architectural pattern:
Note whether the pattern is intentional or has evolved organically.
Rate current capabilities:
| Capability | Current State | Maturity | Notes |
|---|---|---|---|
| Scalability | [description] | Low/Med/High | |
| Observability | [description] | Low/Med/High | |
| Security | [description] | Low/Med/High | |
| Testability | [description] | Low/Med/High | |
| Deployability | [description] | Low/Med/High | |
| Developer Experience | [description] | Low/Med/High |
| Item | Category | Severity | Impact on Change | Remediation Approach | Effort |
|---|---|---|---|---|---|
| [debt item] | Architecture/Code/Data/Ops | Critical/High/Med/Low | [how it blocks progress] | [recommendation] | S/M/L |
Categories:
Compare current state to typical requirements for the target state:
| Capability | Current | Required for Target | Gap | Priority |
|---|---|---|---|---|
| [capability] | [current level] | [required level] | [description of gap] | High/Med/Low |
Produce a Current State Assessment document with:
references/technical-debt-patterns.md — Common technical debt patterns and remediation strategiesassets/current-state-template.md — Blank assessment template