GSoC: Writing the spec document without knowing the specification
summary
A prototype called Lucas chatbot generates AsyncAPI specs by asking a handful of questions and outputting JSON/YAML; demo shows it validating version and URL formats, accepting JSON Schema payloads, creating channels/messages, and warning when a referenced message or channel is missing. Built as a web UI tied to the AsyncAPI initiative, it works interactively in the demo (with some network lag) and plans include ingesting existing specs, answering spec questions, and editing specs on command for contributors.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:04API specs problems and solution
- 2:48Demo: Lucas chatbot spec
- 8:17Future features and community
- 10:50Call to action
related talks
19mGenerating & Using AsyncAPI Specs from Real-World API Data
28mHow AsyncAPI Docs Got a Facelift: GSoD 2022 Contributions
21mLet there be docs!
22mI Spoke to My API — Before It Was Even Built
31mUnifying OpenAPI & AsyncAPI : Designing JSON Schemas+Examples.
08mMy Journey from Contributor to a TSC Member at AsyncAPI
56mIs Spec Kit the future for software development
30mLeveraging Prompt Engineering for Effective OpenAPI Descriptions of APIs