Is your feature request related to a problem? Please describe.
Developers work locally in VS Code and would benefit from the same validation without needing to open browser.
Describe the solution you'd like
Create a VS Code extension that reuses Guardon's rule engine for local YAML validation.
[ ] Create VS Code extension scaffolding
[ ] Extract rule engine into shared NPM package
[ ] Implement YAML validation as VS Code diagnostic provider
[ ] Add command palette integration for manual validation
[ ] Support custom rules import/export compatible with browser extension
[ ] Add quick fixes for common violations
[ ] Implement settings sync between VS Code and browser extensions
[ ] Publish to VS Code marketplace
Additional context
Files to modify: New VS Code extension project, extract src/utils/rulesEngine.js to shared package
Technical considerations
Use VS Code language server protocol
Share rule definitions between browser and VS Code versions
Consider using the same rule format and storage structure
Is your feature request related to a problem? Please describe.
Developers work locally in VS Code and would benefit from the same validation without needing to open browser.
Describe the solution you'd like
Create a VS Code extension that reuses Guardon's rule engine for local YAML validation.
[ ] Create VS Code extension scaffolding
[ ] Extract rule engine into shared NPM package
[ ] Implement YAML validation as VS Code diagnostic provider
[ ] Add command palette integration for manual validation
[ ] Support custom rules import/export compatible with browser extension
[ ] Add quick fixes for common violations
[ ] Implement settings sync between VS Code and browser extensions
[ ] Publish to VS Code marketplace
Additional context
Files to modify: New VS Code extension project, extract src/utils/rulesEngine.js to shared package
Technical considerations
Use VS Code language server protocol
Share rule definitions between browser and VS Code versions
Consider using the same rule format and storage structure