pyramidheadshark/.claude/skills/design-doc-creator
.claude/skills/design-doc-creator/SKILL.md
# Design Doc Creator ## When to Load This Skill Load when: starting a new project, creating or updating `design-doc.md`, translating client requirements into structured documentation, filling in the design document template. ## Purpose This skill guides the creation of a complete design document. It is always the first deliverable of any project — before environment setup, before tests, before code. ## Document Structure (10 Sections) The template lives at `templates/design-doc.md` in `cla
$ install --global
skillsauthnpx skillsauth add pyramidheadshark/ml-claude-infra .claude/skills/design-doc-creatorInstall 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 15, 2026, 8:06 AM84.0s2 files scanned
SKILL.md
Design Doc Creator
When to Load This Skill
Load when: starting a new project, creating or updating design-doc.md, translating client requirements into structured documentation, filling in the design document template.
Purpose
This skill guides the creation of a complete design document. It is always the first deliverable of any project — before environment setup, before tests, before code.
Document Structure (10 Sections)
The template lives at templates/design-doc.md in claude-scaffold.
| Section | Owner | When | |---|---|---| | 0. Quick Summary | Agent (from inputs) | Intake | | 1. Business Context | Human + Agent | Intake → Iteration | | 2. Users and Roles | Human + Agent | Intake → Iteration | | 3. Input Data | Human | Intake | | 4. Use Cases / Scenarios | Human + Agent | Iteration | | 5. Non-Functional Requirements | Human + Agent | Iteration | | 6. Technical Architecture | Agent | After 1–5 approved | | 7. Test Plan | Agent | After 6 drafted | | 8. Deployment Plan | Agent | After 6 drafted | | 9. Open Technical Questions | Agent | Ongoing | | 10. Changelog | Agent | Every update |
Sections 1–5 must be fully resolved before agent writes sections 6–9.
Intake Phase Workflow
Step 1: Collect all available inputs
Sources may include:
- Voice transcript / written description from human
- Client Excel checklist (use
multimodal-routerskill if needed) - Existing partial documentation
- Uploaded PDF / Word files
Step 2: Populate template
Fill every section. Mark unknown values as TBD — never leave blanks.
Mark resolved items as Agreed.
Step 3: Generate open questions
Categorise as:
- Business — client/stakeholder must answer
- Technical — developer decides or researches
Keep questions specific and answerable. Not "what are the requirements?" but "What is the maximum acceptable response latency for the chat endpoint — 2s, 5s, or unconstrained?"
Step 4: Iterate
Re-run steps 2–3 with each batch of answers. Stop when all Business questions in section 1.5 are resolved. Technical questions may remain open during early development.
Step 5: Finalize
- Change status header from
DRAFT→REVIEW - Create
dev/status.mdusing the template - Set active phase to "Phase 1: Design Document"
- Seed backlog with first 5 tasks from the design doc
Quality Checklist Before Approval
- [ ] Every scenario in section 4 maps to a
.featurefile path - [ ] Every NFR in section 5 has a measurable value or explicit
TBD - [ ] No vague requirements ("system should be responsive", "easy to use")
- [ ] Input data in section 3 has format, volume, and acquisition status
- [ ] Load numbers in section 2 have concrete estimates or
TBD - [ ] Stack choices in section 6 have rationale, not just names
- [ ] All known secrets are listed in section 6.5
Updating an Existing Design Doc
When requirements change:
- Update affected sections
- Log the change in section 10 (Changelog)
- Bump the version (patch for clarifications, minor for new scenarios, major for scope changes)
- Update
dev/status.mdwith the architectural decision if significant
Never delete old content — mark it as [DEPRECATED] with a date and replacement reference.
Related Skills
pyramidheadshark/tests/fixtures/project-with-status/.claude/skills/design-doc-creator
testing
VerifiedTrustedCommunity
# Design Doc Creator ## When to Load This Skill Load when: design documents, requirements, new project start. Short fixture skill for testing (optional/meta skill).
4SKILL.mdUpdated Apr 17, 2026
pyramidheadshark/.claude/skills/windows-developer
development
VerifiedTrustedCommunity
# Windows Developer Guide ## When to Load Automatically loaded on Windows (`platform_trigger: "win32"`). Applies to: `.py`, `.ps1`, `.bat`, `.cmd` files and any Windows-specific workflow. ## Python on Windows ### Encoding (CRITICAL) Windows defaults to `cp1251` / `cp1252` for file I/O. Always specify UTF-8 explicitly: ```python with open("file.txt", "r", encoding="utf-8") as f: content = f.read() Path("file.txt").read_text(encoding="utf-8") Path("file.txt").write_text(content, encodin
4SKILL.mdUpdated Apr 15, 2026
pyramidheadshark/.claude/skills/test-first-patterns
development
VerifiedTrustedCommunity
# Test-First Patterns ## When to Load This Skill Load when writing tests, creating `.feature` files, setting up conftest, discussing test strategy, or reviewing coverage. ## Philosophy Tests are written BEFORE code. Always. No exceptions. The order is: Design Doc → BDD Scenarios → Unit Tests → Implementation. BDD scenarios come from the design document's use cases section — they are a direct translation of business requirements into executable specifications. This makes tests the living do
4SKILL.mdUpdated Apr 15, 2026
pyramidheadshark/.claude/skills/supply-chain-auditor
testing
VerifiedTrustedCommunity
# Skill: Supply Chain Auditor ## When to Load Auto-load when: adding dependencies, reviewing packages, updating versions, or discussing `requirements.txt`, `pyproject.toml`, `package.json`. Triggers on `dependency`, `install`, `package`, `CVE`, `audit`, `vulnerable` (≥2 keywords). ## Core Rules Every new dependency addition must pass this checklist before merging: 1. **Pinned** — exact version in production (`==1.2.3` for pip, `"1.2.3"` for npm, not `^` or `~`). 2. **Maintained** — last com
4SKILL.mdUpdated Apr 15, 2026