PLATFORM_SPEC.md — Void (VS Code fork)¶

New to gald3r on this platform? Start at Use gald3r with Void for a short overview before the full breakdown below.

Authoring status: create (STUB — generated to end the ghost-platform invisibility; capability cells below were subsequently reconciled with the curated the platform capability matrix / platform_matrix_data.json values). This platform ships an overlay (platforms/void/) and is registered in PLATFORM_REGISTRY.yaml. Hooks/Rules/Skills/Commands/MCP below reflect a curated, human-assessed capability set, not a live docs crawl. Run @g-platform-scan-docs void (crawl https://voideditor.com) then @g-platform-check void to upgrade this spec from curated to verified.

Void (VS Code fork) is registered in the gald3r platform roster. Per the curated capability matrix (platform_matrix_data.json, reconciled here), the five matrix-tracked primitives split: Hooks, Skills, and Commands are assessed ❌ not supported, while Rules and MCP are assessed ✅ supported — Rules specifically via the legacy .cursorrules file (rules_ext: ".cursorrules"), with an MCP (L2) engine-integration tier for the MCP path. This is a human-assessed curation, not the result of a live docs crawl or install test: the three primitives the matrix does not track (folder hierarchy, the AI instruction file, and native agent/subagent support) remain ❓ unknown until a live scan runs. This stub exists so the platform is visible to the monitor tooling and the roster-parity gate instead of being silently dropped.

1. Folder Hierarchy¶

Status: ❓ untested — no verified info. Not a capability the curated matrix tracks either. The platform's config-folder layout has not been crawled/verified. Do not assume a .void/ tree exists until @g-platform-scan-docs void confirms it.

2. AI Instruction File¶

Status: ❓ untested. Not a capability the curated matrix tracks. Whether Void (VS Code fork) auto-reads AGENTS.md / CLAUDE.md or a native instruction file is unverified — separate from the curated .cursorrules Rules signal below, which is a VS Code/Cursor-fork legacy rules file, not necessarily the AI instruction file.

3. Agents Support — ❓ untested¶

Not a matrix-tracked column. No verified info. Pending a live docs crawl.

4. Skills Support — ❌ curated, pending crawl verification¶

platform_matrix_data.json / the platform capability matrix assess Skills as ❌ not supported (human-assessed). Do not assume any g-skl-*/SKILL.md discovery path exists on Void until a live docs crawl either confirms this gap or finds an undocumented mechanism.

5. Commands / Workflows — ❌ curated, pending crawl verification¶

Curated ❌ not supported. No slash-command or workflow-file primitive is assessed as present. Re-check at the next @g-platform-scan-docs void.

6. Hooks System — ❌ curated, pending crawl verification¶

Curated ❌ not supported. No native lifecycle-hook system is assessed as present; do not wire g-hk-*.py files expecting Void to invoke them.

7. Rules / Memory — ✅ curated, pending crawl verification¶

Curated ✅ supported, via the legacy .cursorrules file (platform_matrix_data.json records rules_ext: ".cursorrules"). This is the VS Code/Cursor-fork convention Void inherited; the exact loading behavior (root-only vs. subdirectory, precedence vs. other files) is unverified pending a live docs crawl.

8. MCP Support — ✅ curated, pending crawl verification¶

Curated ✅ supported, with a curated engine-integration tier of MCP (L2). Connection config and transport details are unverified — pending a live docs crawl.

Parity vs. Cursor Reference¶

At the curated level, Void matches the Cursor reference's ✅ row on 2 of 5 matrix-tracked primitives (Rules via .cursorrules, MCP) and diverges on the other 3 (Hooks, Skills, Commands all curated ❌). This is not a verified parity claim: the three primitives outside the matrix (folder hierarchy, instruction file, agents) are still ❓, and none of the five curated cells has been confirmed by an install test. Re-derive a verified parity comparison against g-skl-platform-cursor/PLATFORM_SPEC.md after @g-platform-scan-docs void runs.

Hook System¶

Type: curated ❌ not supported
Config file: n/a (curated — no hooks system assessed)
Events available: n/a
Event payload format: n/a
gald3r hook files: g-hk-*.py portability is curated not supported on Void; unverified by a live docs crawl

Atypical Handling¶

None recorded — no live scan has run. Capture atypical behaviors after the first verified scan.

gald3r Integration Notes¶

Capability cells (Hooks/Rules/Skills/Commands/MCP) are now curated to match the platform capability matrix: Hooks/Skills/Commands curated ❌, Rules curated ✅ via .cursorrules, MCP curated ✅. Do not assume any .claude/ reuse, hook, skill, or command wiring mechanism works on Void until a live docs crawl / install test verifies it — curated only means "assessed as (not) supported," not "implementation confirmed."
For Rules specifically, treat .cursorrules as the best-known curated target file, but do not assume gald3r's .mdc/.md rule files translate without a verified crawl.
Run @g-platform-scan-docs void (crawl https://voideditor.com) then @g-platform-check void.

Capability Summary¶

Hooks	Rules	Skills	Commands	MCP	Docs Fresh
❌	✅	❌	❌	✅	❓

Legend: ✅ verified working · ⚠️ partial / Cursor-generic · ❌ not supported · ❓ untested.

Provenance : the five capability cells above are curated (human-assessed, sourced from platform_matrix_data.json / the platform capability matrix) — they are not live-crawl-verified. Docs Fresh stays ❓ because last_doc_scan: never.

Overall platform status: ❓ (crawl-untested) — capability cells are curated (Hooks/Skills/Commands = ❌, Rules = ✅ via .cursorrules, MCP = ✅) but not yet confirmed** by a live docs crawl or install test. This is the honest state: curated, not verified.

Verification Evidence¶

Capability	How verified
Hooks / Skills / Commands	Curated ❌, not crawled. Sourced from `platform_matrix_data.json` (human-assessed) / the platform capability matrix; reconciled into this spec.
Rules	Curated ✅ via `.cursorrules`, not crawled. Same curated source; `rules_ext: ".cursorrules"`.
MCP	Curated ✅, not crawled. Same curated source; curated engine tier `MCP (L2)`.
Folder hierarchy / AI instruction file / Agents	Not yet verified — no curated or crawled data exists for these three primitives.
(all)	Run `@g-platform-scan-docs void` to replace curated cells with live-crawl-verified ones.

Reference page — canonical source: g-skl-platform-void/PLATFORM_SPEC.md in the engine repo, generated by scripts/generate_platform_support_docs.py. Pages marked curated are hand-assessed and not yet live-verified.