aeo-dev

Bootstrap or augment a repository with governance scaffold — AGENTS.md tree, docs layout, gitignore additions. Idempotent init or augment mode.

Reconcile roadmap and issue docs against implemented code — retire completed items to archive, trim partial implementations, update issue trackers

Read-only alignment check — compare current implementation against roadmap docs, flag objective drift, and recommend prioritized next steps

Scan repo for security risks, PII, secrets, local environment leaks, and supply chain issues before public push

Guide the user through repository documentation governance using the aeo-repo-* command family. Use when the user asks about AGENTS.md scaffolding, roadmap alignment reviews, doc curation, repo bootstrap, or wants to know which governance command to run next. Covers lifecycle sequencing: bootstrap a scaffold, iterate with alignment reviews and curation passes, sanitize before publishing.

Contains verified extension development workflows, webview CSP pitfall resolutions, and profile-based install fixes that produce more correct results than reasoning from general training alone. Targets stable VS Code on Windows/macOS/Linux desktop — not code-insiders on WSL/Linux (use vscode-insiders-extension for that). Consult when building or debugging a VS Code extension, scaffolding with esbuild, fixing blank webview panels or silent CSP violations, troubleshooting extensions that won't load after install with profiles, adding dual TreeView+WebviewView toggle panels, or publishing to the marketplace. Do NOT use for code-insiders on WSL/Linux (use vscode-insiders-extension), VS Code user configuration (themes, keybindings, tasks.json), Chrome/browser extensions, Electron apps, JupyterLab plugins, or Monaco Editor embeds.

Contains verified WSL-specific extension development workflows, webview CSP pitfall resolutions, and profile-based install fixes that produce more correct results than reasoning from general training alone. Targets code-insiders on WSL/Linux — not stable VS Code on Windows/macOS. Consult when building or debugging a VS Code extension under WSL, scaffolding with esbuild, fixing blank webview panels or silent CSP violations, troubleshooting extensions that won't load after install with profiles, or publishing to the marketplace with code-insiders. Do NOT use for stable VS Code, VS Code user configuration (themes, keybindings, tasks.json), Chrome/browser extensions, Electron apps, JupyterLab plugins, or Monaco Editor embeds.