dming/blueprint-json-contracts
.cursor/skills/blueprint-json-contracts/SKILL.md
Before changing blueprint.config.json or *.bp.json shapes (or parsers/adapters), read the shared JSON contract TypeScript files. Use when editing config, editor documents, serialization, migration, or runtime asset bridges.
$ install --global
skillsauthnpx skillsauth add dming/vscode-blueprint blueprint-json-contractsInstall 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, 10:22 AM5.3s1 file scanned
SKILL.md
- name:
- blueprint-json-contracts
- description:
- >-
Blueprint JSON contracts
Mandatory references
When work touches project config, editor blueprint files, or JSON that crosses editor ↔ runtime:
- Read
src/shared/JsonType/BlueprintConfigType.tsforblueprint.config.json(pin string rules,baseClassesas record only, required top-level keys with empty[]/{}allowed). - Read
src/shared/JsonType/BlueprintJsonTypes.tsfor editor*.bp.json(file-level and graph layout, legacygraphs[]note) and for runtime asset JSON (BlueprintAssetJson, etc.) in the same module.
Do not invent new top-level fields or pin conventions without updating these types and the parsers that consume them.
Implementation source of truth (code, not only types)
- Config parsing:
src/shared/blueprint/parseEditorBlueprintConfig.ts,src/shared/blueprint/parseBlueprintConfig.ts. - Editor document normalization:
src/shared/blueprint/documentModel.ts(normalizeBlueprintDocumentValue,BlueprintDocument). - Normalized editor types are re-exported from
BlueprintJsonTypes.tsfromdocumentModel.ts(same names:BlueprintDocument, etc.).
After changing contracts or parsers, run npm run check:ts-imports and relevant tests (e.g. npm run test:build-validation).
Related Skills
dming/package-version-first
tools
VerifiedTrustedCommunity
Always bump extension version in package.json before packaging VSIX. Use when user asks to package, build release artifacts, generate VSIX, publish, or prepare an installable extension package.
1SKILL.mdUpdated Apr 17, 2026
dming/blueprint-dev-resume
development
VerifiedTrustedCommunity
Resume blueprint editor development quickly with a fixed startup checklist, regression checks, and end-of-session handoff updates. Use when user says continue development, resume work, or asks to keep iteration momentum.
1SKILL.mdUpdated Apr 17, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026