richfrem/prototype-builder
plugins/exploration-cycle-plugin/skills/prototype-builder/SKILL.md
Orchestrates the full prototype build cycle for a Subject Matter Expert. Coordinates layout confirmation and component building — it does not build components directly. Acts as the single entry point for all prototype-related requests. Trigger phrases: "build a prototype", "create a working prototype", "show me a working version", "prototype to clarify scope", "build an exploratory prototype"
$ install --global
skillsauthnpx skillsauth add richfrem/agent-plugins-skills prototype-builderInstall 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 27, 2026, 7:30 AM68.3s4 files scanned
SKILL.md
- name:
- prototype-builder
- plugin:
- exploration-cycle-plugin
- description:
- >
- Orchestrates the full prototype build cycle for a Subject Matter Expert. Coordinates layout confirmation and component building — it does not build components directly. Acts as the single entry point for all prototype-related requests. Trigger phrases:
- build a prototype", "create a working prototype", "show me a working version", "prototype to clarify scope", "build an exploratory prototype
- allowed-tools:
- Bash, Read, Write
<example>
<commentary>Demonstrates the standard flow where the user asks to build after a Discovery Plan has been approved.</commentary>
User: Build a prototype based on our plan
Agent: Reads the most recent Discovery Plan, invokes visual-companion to confirm layout direction, then invokes subagent-driven-prototyping to build the components, stays available during the build, and guides the SME through a walkthrough once it's ready.
</example>
<example>
<commentary>Demonstrates the HARD-GATE redirect when the user asks to build without any existing Discovery Plan.</commentary>
User: Create a working prototype for me
Agent: Checks for a Discovery Plan file and finds none. Responds: "Before we can build, I need to understand what we're building first. Can we start with a planning session? It only takes a few minutes and it'll make sure what we build is exactly what you need." Stops there and does not continue.
</example>
Role
This skill coordinates the full prototype build cycle. It does NOT build components directly. Building is handled by subagent-driven-prototyping. Layout confirmation is handled by visual-companion. This skill connects those two steps and guides the SME through the full journey from plan to working prototype.
HARD-GATE Check
This is the first thing that runs, before any other step.
Check: does exploration/discovery-plans/ exist and contain at least one .md file?
If NO plan exists:
"Before we can build, I need to understand what we're building first. Can we start with a planning session? It only takes a few minutes and it'll make sure what we build is exactly what you need."
Stop. Do not continue. Do not suggest workarounds. Do not attempt to build without a plan.
If a plan exists: Read the most recent .md file in exploration/discovery-plans/. This is the source of truth for the entire build session.
Session Flow
Step 1 — Layout direction
Invoke the visual-companion skill to present layout options and get SME confirmation before any building begins.
Do not proceed to Step 2 until visual-companion has written exploration/captures/layout-direction.md and announced "Layout confirmed."
Step 2 — Build
Once layout is confirmed, invoke the subagent-driven-prototyping skill.
Announce:
"I'm putting your prototype together now — each part separately so I can make sure it matches our plan. I'll show you the full version once everything is ready."
Stay available during the build. If any component is BLOCKED or NEEDS_CONTEXT, address it immediately. Do not let the build stall.
Step 3 — SME walkthrough
Once all components are built and the completion report is received, invite the SME to review:
"Your prototype is ready. Please click through it and let me know if the flows work the way you described. It's much easier to adjust things at this stage than later on."
Guide the SME through each main flow described in the Discovery Plan. Ask about each one:
"Does this part work the way you expected?"
Listen carefully for surprises, corrections, and anything that wasn't in the original plan.
Step 4 — Capture observations
Write exploration/captures/prototype-notes.md:
# Prototype Observations
**Session date:** [date]
**Discovery Plan reference:** [plan filename]
## Confirmed Flows
[Business flows the SME confirmed as correct]
## Surprises and Corrections
[Anything that worked differently from the plan]
## New Rules Observed
[Rules implied by prototype behaviour not in the original plan]
## Edge Cases Raised
[Exceptions or conditions the SME flagged during the walkthrough]
Step 5 — Hand off
"I'll pass your walkthrough notes to the next stage now, which will pull out all the details we need for the documentation."
Invoke prototype-companion-agent for structured requirement extraction from the walkthrough notes.
Related Skills
richfrem/vector-db-ingest
tools
VerifiedTrustedCommunity
Ingests repository files into the ChromaDB vector store. Builds or updates the vector index from a manifest or directory scan using ingest.py. Use when new files need to be indexed or the vector store is out of date. <example> user: "Index these new plugin files into the vector database" assistant: "I'll use vector-db-ingest to add them to the vector store." </example> <example> user: "The vector store is missing recent files -- update it" assistant: "I'll use vector-db-ingest to re-index the changes." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-cleanup
data-ai
VerifiedTrustedCommunity
Removes stale and orphaned chunks from the ChromaDB vector store for files that have been deleted or renamed. Use after files are removed or moved to keep the vector index in sync with the filesystem. <example> user: "Clean up the vector store after I deleted some files" assistant: "I'll use vector-db-cleanup to remove orphaned chunks." </example> <example> user: "The vector database has chunks for files that no longer exist" assistant: "I'll run vector-db-cleanup to prune them." </example>
3SKILL.mdUpdated Jun 2, 2026
richfrem/vector-db-audit
testing
VerifiedTrustedCommunity
Audit Vector DB coverage -- compares the live filesystem manifest against the ChromaDB index to identify coverage gaps.
3SKILL.mdUpdated Jun 2, 2026
richfrem/rlm-search
development
VerifiedTrustedCommunity
3-Phase Knowledge Search strategy for the RLM Factory ecosystem. Auto-invoked when tasks involve finding code, documentation, or architecture context in the repository. Enforces the optimal search order: RLM Summary Scan (O(1)) -> Vector DB Semantic Search -> Grep/Exact Match. Never skip phases.
3SKILL.mdUpdated Jun 2, 2026