omg

Use when writing or editing .omg.md files - the human-first DSL for API specification that compiles to OpenAPI 3.1

Use when building CLI tools with Commander.js - commands, options, arguments, and help text for Node.js command-line applications

Use when parsing or generating Markdown following the CommonMark specification - AST structure, block/inline elements, and extensions

Use when creating GitHub Actions workflows for CI/CD - testing, building, publishing npm packages, and automating repository tasks

Use when working with JSON Schema for validation, OpenAPI schemas, type definitions, and data structure specification

Use when implementing Language Server Protocol features - diagnostics, completions, hover, go-to-definition, and editor integration

Use when managing npm workspaces monorepos - package dependencies, build ordering, cross-package development, and publishing workflows

Use when writing PEG grammars with Peggy (formerly PEG.js) - parsing expression grammars, parser generation, and syntax definition

Use when creating or editing TextMate grammar files for VS Code syntax highlighting - patterns, scopes, and language tokenization

Use when writing or configuring Vitest tests - assertions, mocking, coverage, and workspace-aware testing for TypeScript projects

Use when creating Docusaurus plugins (remark, rehype, theme, content, lifecycle) to extend markdown, modify HTML, or add custom functionality

Use when writing Vague (.vague) files that need realistic test data using faker generators for names, emails, addresses, dates, and more

Use when writing Vague (.vague) files - a declarative language for generating realistic test data with superposition, constraints, and cross-references

Use when working with OpenAPI Specification files to validate, create/modify paths and schemas, check references, and enforce best practices