ailang-parse

End-to-end checklist for adding a new input or output format to AILANG Parse (docparse). Use when the user says 'add support for X format', 'wire up a new parser', 'add .foo format', 'add a parser for .bar', 'support .baz files', 'ship format X', 'can we parse .qux', 'new format rollout', or mentions a file extension that isn't yet supported (e.g. 'what about RTF', 'add Jupyter notebooks'). Covers parser code, ailang.toml exports, WASM demo, vendor-wasm-packages.sh, homepage, workbench, all format-list surfaces across the docs site, SDK READMEs, release tag, registry publish, and the ailang messages send docparse downstream notification. Use even when only part of this is requested — the skill tells you which surfaces you'd otherwise miss.

Create a new AILANG Parse documentation/landing page targeting a specific keyword or topic. Use when user says 'new landing page', 'new page for X', 'create a page about X', 'landing page for keyword X', or wants to add a documentation page to the docs/ site. Also use when the user references long-tail keywords, SEO pages, or competitor comparison pages.

Run OfficeDocBench evaluation and refresh benchmark scores across the AILANG Parse website. Use when the user says 'run benchmarks', 'rerun the benchmark', 'refresh benchmark numbers', 'update bench scores', 'regenerate summary.json', mentions OfficeDocBench, asks to evaluate parsers, asks why scores are out of sync on the docs, or after any change to docparse/services/*.ail or benchmarks/officedocbench/scoring.py — even if they don't explicitly say 'benchmark'. Also use after editing any AILANG parser to verify no regression.

Audit the design_docs/ folder structure against the current project version. Use when user says 'audit design docs', 'check design docs', 'are design docs organized', 'verify design doc placement', 'tidy design docs', or asks about misplaced/stale design documents. Also use when the user asks to reorganize planned vs implemented docs, or after a version bump.

Fix a parser gap identified in the spec coverage audit. Use when user says 'fix a gap', 'implement X parsing', 'improve parser coverage', 'close a gap', 'next P1', or references a specific ECMA-376 spec section like '§17.9'. Also use when the user asks to improve DOCX/XLSX/PPTX parsing quality, add support for a missing Office feature, or mentions numbering, styles, hyperlinks, formatting, fields, merged cells, equations, or speaker notes in the context of parser improvement.

Verify generated Office documents (DOCX, PPTX, XLSX, ODT, ODP, ODS, HTML) are valid and open correctly. Use when: user asks to verify generated files, check document output quality, validate Office files, run the verification loop, test generated documents, check if files open in Keynote/Word/Numbers, or after changing any generator code (docx_generator, pptx_generator, xlsx_generator, odt_generator, odp_generator, ods_generator, html_generator). Also use when user says "verify", "check the files", "do they open", "run verification", or "test the output".