Clatter LabsHelp Center

How do I write good requests for Line CLI?

How-toUpdated

Say what you want, where, and how to check it's done. Line works best with a clear goal and a way to verify it.

A good request has#

  1. The goal: "Add a dark mode toggle to the settings page."
  2. Where: "The page is in src/settings/." You can attach files by typing @ and a file name.
  3. Limits: "Don't add new dependencies."
  4. The check: "Run npm test and make sure it passes."

For bigger jobs#

  • Use /plan <task> first. Line researches without editing and ends with a plan you approve.
  • Write lasting rules in LINE.md (/init creates one) so you don't repeat them.
  • Choose a deeper effort with /effort max or /effort heavy for hard bugs.

Things to avoid#

  • Very vague requests ("make it better").
  • Pasting secrets into the chat. Line redacts many secrets from tool output, but don't rely on it for what you type.

Related articles

Still need help?

Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.

Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyz
For deleting your whole account or the data of one service.