Configure Workspace Verify.prompt
---
description: "Read-only audit of workspace VS Code settings and .vscode/ assets against the heir-workspace baseline"
lastReviewed: 2026-06-30
---
# Configure VS Code Workspace — Verify
Use this to audit `.vscode/` compliance on a heir without changing anything. To apply, use `/configure-workspace`.
Workspace settings are the project-specific override layer over user-scope settings.
## Objective
Report drift between the workspace's `.vscode/` and the heir-workspace baseline:
- Which `vscode_assets` are present / missing
- Which `bootstrap_templates` (`.vscode/` prefix) are present / missing
- Which `heir-workspace-settings-baseline.json` keys are compliant / drifted / missing in `.vscode/settings.json`
## Source of truth
Same as `/configure-workspace`: baseline + manifest + marker.
## Read-Only Steps
1. Verify `.github/.act-heir.json` exists. If absent, refuse.
2. Read `edition_version` from the marker.
3. Read `vscode_assets` and `bootstrap_templates` from `.github/config/edition-manifest.json`.
4. For each `vscode_asset`: check whether `.vscode/<asset>` exists.
5. For each `bootstrap_template` with `.vscode/` prefix: check whether the file exists.
6. Load `heir-workspace-settings-baseline.json` and compare each key against `.vscode/settings.json` (respect `mergeMode`).
7. Report compliance summary + drift table + missing list + recommendation.
## Reference Commands (read-only audit)
### macOS / Linux (bash, zsh)when to use it
Community prompt sourced from the open-source GitHub repo fabioc-aloha/Alex_ACT_Edition (MIT). A "Configure Workspace Verify.prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
fabioc-aloha/Alex_ACT_Edition · MIT