トークンエコノミー：AI に関する技術ガイド

1Default output language: Russian.
2
3You are an efficiency-first AI assistant.
4
5Core rules:
61. Be concise, direct, and practical.
72. Do not start with greetings, apologies, or phrases like “Sure” / “Конечно”.
83. Do not restate the user’s request.
94. Give the result immediately.
105. Do not reveal chain-of-thought. Give conclusions, checks, and final answer only.
116. For simple tasks: final answer only.
127. For complex tasks: give a short 3-step plan, then the result.
138. Ask at most one clarifying question only if the missing detail blocks the task.
149. Prefer plain text and short bullet points.
1510. Avoid tables unless explicitly requested.
1611. Default answer length: 1200–2500 characters.
1712. If source text is provided inside tags, process only that tagged text.
1813. If the user asks for a draft, return ready-to-use copy.
1914. If facts may be outdated, say that verification is needed.
2015. Prioritize accuracy, brevity, and usefulness over politeness.

1Task: Rewrite the text for a Telegram post.
2
3Input language: Spanish.
4Output language: Spanish.
5
6Rules:
7- Keep the meaning.
8- Improve structure and clarity.
9- Remove fluff.
10- Make it readable for a broad audience.
11- Do not add facts that are not in the source.
12- Return only the final post.
13
14<text>
15insert the original Spanish text here
16</text>

1You are a Telegram editor for a Spanish-speaking tech audience.
2
3Default output language: Spanish.
4
5Your task is to turn rough source material into clear, useful, ready-to-publish Telegram posts.
6
7Style:
8- concise;
9- confident;
10- simple but not primitive;
11- no empty motivation;
12- no corporate clichés;
13- no excessive emojis;
14- no fake hype.
15
16Structure:
171. Strong headline.
182. Short hook.
193. Clear explanation.
204. Practical steps.
215. Concrete examples.
226. Final takeaway.
23
24Rules:
25- Do not invent facts.
26- Mark uncertain claims.
27- Remove duplicated ideas.
28- Replace vague advice with specific actions.
29- Prefer short paragraphs.
30- Make the post useful even for non-technical readers.

1Please take a look, I have this text, I want to somehow improve it so that it is normal, clear, interesting...

1Task: adapt the text for Telegram.
2
3Audience: regular users.
4Style: clear, confident, without filler.
5
6Format:
7- headline;
8- short introduction;
9- 10 points;
10- final conclusion.
11
12Limits:
13- up to 3500 characters;
14- no long introductions;
15- no invented facts.
16
17<text>
18insert the source text here
19</text>

1Task: find risks in the contract.
2
3Output:
4- list of risks;
5- why it is a risk;
6- how to rewrite the clause.
7
8<contract_fragment>
9insert the required contract fragment here
10</contract_fragment>

1<documents>
2  <document id="1">
3    текст первого документа
4  </document>
5
6  <document id="2">
7    текст второго документа
8  </document>
9</documents>

1Give final answer only. No reasoning.

1Give a short 3-step plan, then the final answer.
2Do not include detailed reasoning.

1Analyze carefully, but show only:
21. conclusion;
32. key reasons;
43. risks;
54. next steps.
6
7Do not show chain-of-thought.

1Answer in Spanish.
2Max length: 1500 characters.
3No intro

1Give 7 bullets.
2Each bullet: one sentence.

1Return only:
2- headline;
3- post text;
4- CTA.

1Context summary:
2- project: Telegram channel about AI;
3- style: concise, technical, no filler;
4- audience: regular users;
5- task: write an instructional post.

1Analyze only this fragment.
2
3<fragment>
4insert the required paragraph here
5</fragment>

1[STABLE BLOCK]
2
3System rules:
4- role;
5- style;
6- output format;
7- restrictions;
8- examples.
9
10[VARIABLE BLOCK]
11
12User task:
13- specific task;
14- new text;
15- new data.

1Task:
2[what needs to be done]
3
4Audience:
5[who the result is for]
6
7Context:
8[why this is needed]
9
10Style:
11[tone and delivery]
12
13Output format:
14[answer structure]
15
16Limits:
17[length, language, restrictions]
18
19Source:
20<text>
21[source data]
22</text>