Some of our power users have a weird habit: they make Cline say...
Cline@cline
32 views
Jan 29, 2025
~1 min read
Advertisement
1
Some of our power users have a weird habit: they make Cline say 'YARRR!' before writing any code.
Sounds crazy, but there's genius behind it. Here's what they discovered about getting 10x better output 👇
Sounds crazy, but there's genius behind it. Here's what they discovered about getting 10x better output 👇
0:19
2
1/ Most people treat Cline like a magic box. Paste prompt, get code. But our power users found something wild:
the more you force Cline to think out loud, the better it performs.
the more you force Cline to think out loud, the better it performs.
3
2/ The 'YARRR!' trick is simple but brilliant:
By telling Cline to say "YARRR!" before every tool use at the START of a task, you essentially have created a "flag" to know if/when Cline has lost context from the start of the task.
By telling Cline to say "YARRR!" before every tool use at the START of a task, you essentially have created a "flag" to know if/when Cline has lost context from the start of the task.
4
3/ Our community has other tricks up their sleeves.
They also make Cline rate its confidence (1-10) in solutions when troubleshooting -- if it's not a 10 then Cline needs to dig deeper.
They also make Cline rate its confidence (1-10) in solutions when troubleshooting -- if it's not a 10 then Cline needs to dig deeper.
0:05
5
4/ Another trick: play dumb
"Ask 'stupid' questions like: are you sure this is the best way to implement this?"
Asking "stupid" questions actually forces Cline to search for more context, leading to better output
"Ask 'stupid' questions like: are you sure this is the best way to implement this?"
Asking "stupid" questions actually forces Cline to search for more context, leading to better output
0:07
6
5/ And more elegantly, have Cline create markdown files of the implementation plan before doing any coding:
"Before writing code:
1. Analyze all code files thoroughly
2. Get full context
3. Write .md implementation plan
4. Then implement code"
"Before writing code:
1. Analyze all code files thoroughly
2. Get full context
3. Write .md implementation plan
4. Then implement code"
0:13
7
6/ Our users have come up with a ton of prompting tricks. Learn about how to best code using Cline by reading the whole guide here: docs.cline.bot/improving-your…
8