PromptGuard — Devlog #1

Today we built the first working version of PromptGuard: a local-first VS Code extension that helps people write safer, clearer, and cheaper AI prompts.The core focus was making prompt review useful without sending prompts anywhere by default.

PromptGuard now analyzes prompts locally for ambiguity, missing roles/constraints/output formats, repetition, prompt-injection patterns, potential secrets, and PII. It turns those checks into a quality score, actionable findings, editor decorations, and quick fixes.We also added practical prompt-engineering tooling: token, cost, latency, and savings estimates; locally stored searchable prompt history; an analytics dashboard; a sidebar navigator; and a non-destructive optimization diff so users can inspect a suggested rewrite before adopting it.

For VS Code Chat, we added @promptguard /analyze, which reports a prompt’s score, safety findings, and token information directly in chat. The extension respects provider boundaries: it only handles chat turns sent to PromptGuard itself, rather than attempting to intercept other providers’ messages.

We added optional Groq-powered semantic review and prompt improvement too. It is strictly opt-in through a local API key, clearly warns that prompts leave VS Code when enabled, asks targeted follow-up questions when key context is missing, and validates the improved prompt locally afterward.

Finally, we set up the extension project structure, local development configuration, icon, documentation, licensing, and a modular architecture for future rule plugins and model providers. The project type-checks and compiles successfully.

Next up: add dashboard and diff screenshots, benchmark prompts, and build toward policy packs and CI prompt linting.