skills/design-an-interface/SKILL.md
Applies "Design It Twice" from APOSD: generates two radically different interface designs for the same problem, then compares them on information hiding, complexity, and cohesion before recommending one. Use when designing a new API, module boundary, or class interface, or asked to "design the interface", "apply design it twice", or "compare interface designs". Ported from https://github.com/mattpocock/skills (Matt Pocock).
npx skillsauth add michaelalber/ai-toolkit design-an-interfaceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Apply the "Design It Twice" principle from A Philosophy of Software Design (Ousterhout).
1. Clarify the problem
Confirm:
2. Generate Design A — narrow and deep:
3. Generate Design B — different decomposition:
4. Compare on these dimensions:
| Dimension | Design A | Design B | |-----------|----------|----------| | Information hiding (1–5, higher=better) | | | | Method count (lower=simpler) | | | | Conceptual complexity (1–5, lower=better) | | | | Cohesion (1–5, higher=better) | | | | Error surface (1–5, lower=better) | | | | Total | | |
See references/aposd-principles.md for scoring guidance on each dimension.
5. Recommend — state which design is better and why, citing specific APOSD principles. If scores are close, propose a hybrid that takes the best of each.
6. Validate — ask: "Any constraint or use case I missed that would change this?"
development
Interviews the user relentlessly about a plan, decision, or idea — one question at a time, each with a recommended answer. Shared engine behind "grill-me" and "grill-with-docs". Use on any "grill" trigger phrase or to stress-test thinking. Do NOT use to build the plan; it ends at shared understanding, not implementation.
testing
Runs a relentless interview to sharpen a plan or design, capturing the decisions as ADRs and a glossary along the way. Use when the user wants to be grilled AND wants the session to leave durable domain documentation behind. Do NOT use for a throwaway stress-test with no artifacts; use grill-me instead.
tools
OWASP-based security review of Vue/TypeScript front-ends. Detects framework (Vite/Vue CLI/Nuxt), entry points, and data flows; scans the OWASP Top 10 (2025) mapped to Vue client-side risks (raw-HTML XSS via v-html, URL/protocol injection, bundled secrets, insecure token storage, dependency CVEs, missing CSP, open redirects, router guard bypass); emits an exec summary plus graded findings. Use to audit Vue for vulnerabilities. Not for architecture grading (vue-architecture-checklist).
tools
Analyzes legacy Vue codebases and produces actionable modernization plans. Primary migration paths include Options API to Composition API, Vue 2 to Vue 3, Vue CLI to Vite, JavaScript to TypeScript, Vue Test Utils/Karma/Mocha to Vitest + Vue Testing Library, legacy Vuex to Pinia, and removed-in-Vue-3 pattern cleanup (filters, event bus, `$listeners`). Does NOT perform the migration — assesses, quantifies risk, and plans.