How do I write good requests for Line CLI?
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#
- The goal: "Add a dark mode toggle to the settings page."
- Where: "The page is in
src/settings/." You can attach files by typing@and a file name. - Limits: "Don't add new dependencies."
- The check: "Run
npm testand 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(/initcreates one) so you don't repeat them. - Choose a deeper effort with
/effort maxor/effort heavyfor 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.xyzFor deleting your whole account or the data of one service.