rakovi4/design-preview
.claude/skills/design-preview/SKILL.md
Preview the planned design for a scenario before writing tests. Shows domain model changes, usecase patterns, and key design choices. Use before red-usecase to get user approval on the implementation approach. If the user rejects the design, offers to discuss inline or escalate to /architecture for a full ADR.
$ install --global
skillsauthnpx skillsauth add rakovi4/continue-example design-previewInstall 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: Apr 17, 2026, 1:19 AM6.9s1 file scanned
SKILL.md
- name:
- design-preview
- description:
- Preview the planned design for a scenario before writing tests. Shows domain model changes, usecase patterns, and key design choices. Use before red-usecase to get user approval on the implementation approach. If the user rejects the design, offers to discuss inline or escalate to /architecture for a full ADR.
/design-preview - Scenario Design Preview
Usage
/design-preview 10 "Filter by date range" # Story 10, named scenario
/design-preview 10 9 # Story 10, scenario 9
/design-preview # Detect from progress.md
Purpose
Before writing any test code, present the planned implementation design to the user for approval. This catches design disagreements early — before red-usecase locks in the approach.
Workflow
1. Gather Context
- Read the story spec — full story document for business context, requirements, constraints, business rules
- Read the scenario from
tests/01_API_Tests.md - Read
ProductSpecification/ExpectedLoad.txt— for scale assumptions (use real numbers, never guess) - Read existing code — domain entities, usecases, ports, request/response DTOs
- Read ADRs — check
decisions/*-decision.mdfiles in the story directory that may constrain the design - Read the acceptance test (if
red-acceptanceis done) — understand expected API behavior
2. Analyze and Design
Think through: domain changes needed, ports needed, multiple viable approaches and recommendation.
3. Present the Design
Simple scenarios (validation, error handling, single CRUD): brief text summary (3-5 lines).
Complex scenarios (new domain concepts, filtering, multi-step workflows): text summary plus method signatures/pseudocode, domain model changes, pipeline/sequence diagrams, port changes.
4. Get Approval
Ask with AskUserQuestion: Approve / Approve and ADR / Needs changes / Reject — need /architecture.
5. Completion
- Approve: mark
designstep as[x]. No files created. - Approve and ADR: mark
designstep as[x], then write an ADR using.claude/templates/spec/adr-format.mdto the story'sdecisions/subfolder. Commit includes the ADR file. - Reject →
/architecture: mark after ADR is decided.
Rules
- Never write code — this is a design step
- Never create files — design lives in the conversation (unless escalated to
/architecture) - Keep it concise — the goal is alignment, not a design document
- If trivially similar to a previous scenario, say so and ask to approve
- Scope of progress.md changes: design-preview may ONLY mark the
designcheckbox as[x]. It must NOT modify, skip, or rewrite any other steps (usecase, adapter, green-acceptance). Skip recommendations go in the design output text only —/continueapplies approved skips to progress.md after the design work unit completes, validating each skip against the "zero production files modified" rule in tdd-rules.md.
Related Skills
rakovi4/test-usecase
testing
VerifiedTrustedCommunity
Run use-case module tests quickly. Use when user wants to run use-case tests or mentions /test-usecase command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-spec
development
VerifiedTrustedCommunity
Generate BDD test specifications for story in 6 categories (API, UI, Load, Infrastructure, Security, Integration). Use when user wants to create test cases or mentions /test-spec command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-review
testing
VerifiedTrustedCommunity
Review tests to replace loose validation (contains, isNotNull, isNotEmpty) with strict validation (isEqualTo on parsed fields). Use when user wants to improve test assertions or mentions /test-review command.
2SKILL.mdUpdated Apr 16, 2026
rakovi4/test-frontend
development
VerifiedTrustedCommunity
Run frontend tests. Use when user wants to run frontend unit tests or mentions /test-frontend command.
2SKILL.mdUpdated Apr 16, 2026