serpro69/design
klaude-plugin/skills/design/SKILL.md
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.
$ install --global
skillsauthnpx skillsauth add serpro69/claude-starter-kit designInstall 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 29, 2026, 9:12 AM8.7s6 files scanned
SKILL.md
- name:
- design
- description:
- |
Task Analysis Process
Goal: Before writing any code, make sure you understand the requirements and have an implementation plan ready.
Conventions
Read capy knowledge base conventions at shared-capy-knowledge-protocol.md.
Profile detection is delegated to shared-profile-detection.md. When an active profile contributes a design/ subdirectory (e.g., ${CLAUDE_PLUGIN_ROOT}/profiles/k8s/design/), its questions.md feeds the idea-refinement question pool and its sections.md lists required sections the design document must cover. Both the idea-to-design and continue-WIP flows consult the shared procedure; see each flow's workflow file for the specific integration points.
Workflow
Mandatory order — understanding before engagement. The flow below is strictly sequential. Do not engage with the idea prose beyond a keyword scan, ask refinement questions, or write design content until all instructions — this SKILL.md, the relevant process file, the shared profile-detection procedure, and every resolved profile's design/ content — are fully loaded.
The design skill has two entry points; each has its own process file with a detailed workflow. Both follow the same mandatory ordering:
- Keyword scan only. The idea prose (or WIP feature directory) is scanned at the keyword/filename level — enough to drive profile detection, not enough to engage with the content.
- Load instructions. Read the relevant process file (idea-process.md or existing-task-process.md) and the shared profile-detection procedure.
- Detect active profiles. Delegate to shared-profile-detection.md. For fresh ideas, this uses the design interaction pattern (token matching against idea prose). For WIP features, this uses file-based detection with design-pattern fallback.
- Load profile content. For each active profile contributing a
design/subdirectory, read itsindex.mdand all always-load entries (questions.md,sections.md). These feed the refinement question pool and required design sections. - Engage with subject matter. Only now: ask refinement questions, analyze the idea, write design content.
Ideas and Prototypes
Use this for ideas that are not fully thought out and do not have a fully-formed design/specification and/or implementation-plan.
For example: I've got an idea I want to talk through with you before we proceed with the implementation.
Your job: Help me turn it into a fully formed design, spec, implementation plan, and task list.
See idea-process.md.
Continue WIP Feature
Use this to resume work on a feature that already has design docs and a task list in /docs/wip/.
For example: Let's continue working on the auth system.
Your job: Review the current state of the feature, understand what's been done and what's next, then proceed with implementation.
See existing-task-process.md.
Related Skills
serpro69/test
development
VerifiedTrustedCommunity
Guidelines describing how to test the code. Use whenever writing new or updating existing code, for example after implementing a new feature or fixing a bug.
138SKILL.mdUpdated May 7, 2026
serpro69/review-spec
development
VerifiedTrustedCommunity
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
138SKILL.mdUpdated May 7, 2026
serpro69/review-design
testing
VerifiedTrustedCommunity
Review design and implementation docs produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
138SKILL.mdUpdated May 7, 2026
serpro69/merge-docs
testing
VerifiedTrustedCommunity
Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
138SKILL.mdUpdated May 7, 2026