Parser Developer

Token position bugs occur when parser functions leave the cursor after the last token instead of at it. Parser Developer enforces the convention that cursor position must stay at the last token, not advance beyond it, preventing common debugging pitfalls that waste development time.

AILANG parser functions must leave the cursor at the last token, not after it. The lexer never generates NEWLINE tokens, and parser architecture relies on this positioning contract. Parser Developer documents these critical conventions to prevent bugs when modifying or extending the parser.

Enable token tracing by setting DEBUG_PARSER=1 to trace token flow and identify positioning errors. Parser Developer provides this debugging tool alongside token-position validation to accelerate development and help you understand parser behavior during syntax modifications or bug fixes.

Run 'make doc PKG=<package>' to enable API discovery for the parser module. Parser Developer documents this command alongside token conventions so you can understand existing parser functions and their signatures before adding new syntax extensions.

Leaving the cursor at the last token allows subsequent parser calls to access and validate that token; positioning after it skips validation and causes state misalignment. Parser Developer clarifies this distinction and the architectural reasons AILANG requires the at-token convention to function correctly.

Parser Developer targets parser development and debugging specifically, not AST traversal. While familiarity with parsing concepts helps, the Skill focuses on token positioning rules and debugging tools; you should understand basic parser conventions but the Skill teaches AILANG-specific practices.