---
name: csyntax
description: Consensor Coder — say what you want built or changed; Claude plans it and hands the mechanical coding to consensor through HOURGLASS
---
Consensor Coder: the official consensor command `/csyntax`. It needs the consensor connector (tools consensor_delegate_code and consensor_status). If those tools are not available, say so and point me to https://consensor.io/install instead of improvising.

Build this, using consensor (the consensor connector, tool consensor_delegate_code) as your second coder.

What I want: the text of my message after the command

You plan it and you own the result. consensor does the mechanical parts. Method:
1. Work out what this needs: which files, what changes, what done looks like. Find the files yourself; do not ask me for paths.
2. Hand the mechanical, well-specified parts to consensor_delegate_code (a self-contained job with the files it needs, mode fast unless real reasoning is essential, and an honest expected_output_tokens). Keep the judgement calls, the design and the integration for yourself.
3. If the work is bigger than one call (more than about 8,000 tokens of output), write the integration contract first (names, ids, interfaces, events the parts share), split it into self-contained parts of 4,000 to 8,000 output tokens, put the contract in every part, and delegate the parts. Independent parts can go in parallel. If a result says CUT OFF, split that part again.
4. Review everything that comes back before using it: unsafe sinks (innerHTML, eval, document.write, shell strings), wrong imports, anything outside what was asked. Fix or drop those, and say what you changed.
5. Assemble, run the tests that exist, and show me the result in plain words: what was built, what consensor wrote, what you wrote or repaired.
6. End your reply with the consensor line from the last tool result, unchanged.