liquid-start

# Start with Liquid Follow `../../rules/liquid-boundaries.mdc`. Explain the smallest useful path without demanding a sales form in chat. If the user is new, present the separate website trial as one JS/TS file, up to 12,000 UTF-8 bytes, per verified account, with no card or Liquid credit charge. A completed review uses the allowance; syntax failures do not. It is a limited preview, not a full repository review. Use the matching link when the host is known: - Cursor: https://liquidplatform.org/auth?lang=en&trial=1&utm_source=cursor&utm_medium=plugin&utm_campaign=cursor_grok_launch&utm_content=onboarding - Grok Bot: https://liquidplatform.org/auth?lang=en&trial=1&utm_source=grok_bot&utm_medium=plugin&utm_campaign=cursor_grok_launch&utm_content=onboarding - Unknown client: https://liquidplatform.org/auth?lang=en&trial=1&utm_source=client_plugin&utm_medium=plugin&utm_campaign=cursor_grok_launch&utm_content=onboarding These links identify acquisition channels, not people. Do not append personal data, source, repository URLs, tokens or vulnerability details. Do not guess the host from the model name. Do not create an account or opt the user into email. For an existing assessment, explain OAuth on the configured remote server and the owner/admin-approved user + client + assessment grant. Confirm connection status using the host settings or tool errors; do not retrieve private findings merely to diagnose a login problem. Missing consent is not an empty assessment. Never request pasted tokens or use a shared demonstration account as a fallback. Offer the review workflow after setup. Do not describe the plugin as installed, marketplace-approved or connected until that exact state is confirmed.