Software Development
Language Spec Author
Turn a rough idea for a language into a complete, implementable specification — a DSL, query, config/data, template, or protocol language — by interviewing the author dimension by dimension until another developer could build a conforming implementation from the document alone. It grills for the decisions authors skip: lexical rules (whitespace, case, comments, literals), grammar with precedence and ambiguity resolution, a semantic/type model, validation rules with counter-examples, execution algorithms and the error model, the output/serialization format, and RFC 2119 conformance. The completeness bar and formal notation (lexical vs syntactic grammar, function-style algorithms) are distilled from the GraphQL specification. Trigger on \"spec out my language\", \"design a DSL / query language\", \"write a language or grammar spec\", \"formalize this syntax\", or when someone has a language idea that needs to become an implementable spec — even if they only say \"spec\" or \"grammar\".
- Publisher / source
- pproenca/dot-skills (found on skills.sh)
- Upstream record
- pproenca/dot-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
8d8a5c0223579d347fd4069d077a488f8b657ebc856c9d4723c6d10cd3168d88