Skip to content

Commit f0304b2

Browse files
danvoronovdanvoronov
committed
2025-03-17 00:16:33
1 parent 85512cf commit f0304b2

File tree

6 files changed

+92
-4
lines changed

6 files changed

+92
-4
lines changed

‎eng_2025/03/2025-03-06-21-22.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,4 @@ Describing his own experience, Karpathy explained how he converses with AI tools
4242
Matthew wishes for a fully hosted, mobile-friendly version of this workflow.
4343

4444

45-
#agentmode #cursor #windsurf #prompts
45+
#agentmode #cursor #windsurf #prompts #vibecoding

‎eng_2025/03/2025-03-14-12-39.md‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,7 @@ Finally, the **Windows version of Wispr Flow** is released — a program for voi
44

55
Of course, this is not directly related to programming, but for *vibe-coding*, it is the tool through which we explain to the AI in Cursor who is the programmer here, and who cannot even write a few lines of code properly.
66

7-
Free 2,000 words per week. For more, $15/month.
7+
Free 2,000 words per week. For more, $15/month.
8+
9+
10+
#vibecoding

‎eng_2025/03/2025-03-16-23-53.md‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
https://github.com/przeprogramowani/ai-rules-builder
2+
3+
[Online generator](https://ai-rules-builder.pages.dev/) of text prompts/project descriptions `rules` for AI tools like Copilot, Cursor, Windsurf, Aider, Junie.
4+
5+
UI is clunky, gotta click around a lot, but hey, it's a first step towards customization, not just catalogs like i wrote about before.
6+
7+
---
8+
9+
Tool creators recommend keeping this file **tiny**. AI can probably guess the project language anyway ;)
10+
11+
Aider [example here](https://github.com/Aider-AI/conventions/blob/main/icalendar-events/CONVENTIONS.md).
12+
13+
Good rule of thumb: add a "patch" if the AI keeps misunderstanding you. You can even do it *from chat*, like in Cursor "pls write me a cursorrule to stop doing {this particular thing}".
14+
15+
Example [here](https://github.com/PostHog/posthog/blob/master/.cursorrules):
16+
```
17+
DO NOT GIVE ME HIGH LEVEL SHIT, IF I ASK FOR FIX OR EXPLANATION, I WANT ACTUAL CODE OR EXPLANATION! I DON'T WANT "Here's how you can blablabla"
18+
- Be casual unless otherwise specified
19+
- Be terse
20+
- Suggest solutions that I didn't think about-anticipate my needs
21+
- Treat me as an expert
22+
- Be accurate and thorough
23+
- Give the answer immediately. Provide detailed explanations and restate my query in your own words if necessary after giving the answer
24+
- Value good arguments over authorities, the source is irrelevant
25+
- Consider new technologies and contrarian ideas, not just the conventional wisdom
26+
- You may use high levels of speculation or prediction, just flag it for me
27+
- No moral lectures
28+
- Discuss safety only when it's crucial and non-obvious
29+
- If your content policy is an issue, provide the closest acceptable response and explain the content policy issue afterward
30+
- Cite sources whenever possible at the end, not inline
31+
- No need to mention your knowledge cutoff
32+
- No need to disclose you're an AI
33+
- Please respect my formatting preferences when you provide code.
34+
- Please respect all code comments, they're usually there for a reason. Remove them ONLY if they're completely irrelevant after a code change. if unsure, do not remove the comment.
35+
- Split into multiple responses if one response isn't enough to answer the question.
36+
If I ask for adjustments to code I have provided you, do not repeat all of my code unnecessarily. Instead try to keep the answer brief by giving just a couple lines before/after any changes you make. Multiple code blocks are ok.
37+
```
38+
39+
40+
41+
#prompts #githubcopilot #cursor #windsurf #aider #junie

‎ukr_2025/03/2025-03-06-21-22.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,4 @@ https://en.wikipedia.org/wiki/Vibe_coding
4242
Метью мріє про повністю хостовану, mobile-friendly версію цього воркфлоу.
4343

4444

45-
#agentmode #cursor #windsurf #prompts
45+
#agentmode #cursor #windsurf #prompts #vibecoding

‎ukr_2025/03/2025-03-14-12-39.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,6 @@ https://wisprflow.ai/
44

55
Звісно, це не прямо пов’язано з програмуванням, але для *вайб-кодінгу* саме вона стала тим інструментом, через який ми пояснюємо ШІ у Cursor, хто тут програміст, а хто навіть кілька рядків коду нормально написати не може.
66

7-
Безкоштовно 2,000 слів на тиждень. За інше $15/місяць.
7+
Безкоштовно 2,000 слів на тиждень. За інше $15/місяць.
8+
9+
#vibecoding

‎ukr_2025/03/2025-03-16-23-53.md‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
2+
https://github.com/przeprogramowani/ai-rules-builder
3+
4+
[Онлайн генератор](https://ai-rules-builder.pages.dev/) текстових промтів-описів проекту для ШІ систем Copilot, Cursor, Windsurf, Aider, Junie.
5+
6+
Хоча інтерфейс дуже незручний, адже потрібно багато клацати туди-сюди, це вже перший крок до кастомізації, а не просто до каталогів, як було раніше.
7+
8+
---
9+
10+
Якщо почитати доки, що пишуть самі творці таких програм, вони рекомендують тримати цей файл **якомога меншого розміру**. Швидше за все, мову програмування проекту ШІ сам може визначити :)
11+
12+
Приклад від aider [тут](https://github.com/Aider-AI/conventions/blob/main/icalendar-events/CONVENTIONS.md).
13+
14+
Гарне просте правило: додавати туди "патч", якщо ШІ кілька разів вас не розуміє і робить не те. Можна додавати навіть просто *з чату*, наприклад у Cursor "будь ласка, напиши мені cursorrule, щоб ти припинив робити {цю конкретну річ}".
15+
16+
Це може в результаті виглядати приблизно [так](https://github.com/PostHog/posthog/blob/master/.cursorrules):
17+
```
18+
DO NOT GIVE ME HIGH LEVEL SHIT, IF I ASK FOR FIX OR EXPLANATION, I WANT ACTUAL CODE OR EXPLANATION! I DON'T WANT "Here's how you can blablabla"
19+
- Be casual unless otherwise specified
20+
- Be terse
21+
- Suggest solutions that I didn't think about-anticipate my needs
22+
- Treat me as an expert
23+
- Be accurate and thorough
24+
- Give the answer immediately. Provide detailed explanations and restate my query in your own words if necessary after giving the answer
25+
- Value good arguments over authorities, the source is irrelevant
26+
- Consider new technologies and contrarian ideas, not just the conventional wisdom
27+
- You may use high levels of speculation or prediction, just flag it for me
28+
- No moral lectures
29+
- Discuss safety only when it's crucial and non-obvious
30+
- If your content policy is an issue, provide the closest acceptable response and explain the content policy issue afterward
31+
- Cite sources whenever possible at the end, not inline
32+
- No need to mention your knowledge cutoff
33+
- No need to disclose you're an AI
34+
- Please respect my formatting preferences when you provide code.
35+
- Please respect all code comments, they're usually there for a reason. Remove them ONLY if they're completely irrelevant after a code change. if unsure, do not remove the comment.
36+
- Split into multiple responses if one response isn't enough to answer the question.
37+
If I ask for adjustments to code I have provided you, do not repeat all of my code unnecessarily. Instead try to keep the answer brief by giving just a couple lines before/after any changes you make. Multiple code blocks are ok.
38+
```
39+
40+
41+
42+
#prompts #githubcopilot #cursor #windsurf #aider #junie

0 commit comments

Comments
 (0)