TachiBot/Docs
HomeGitHubnpm
IntroductionInstallationQuick StartExamplesTools OverviewPlannerPrompt TechniquesWorkflowsPingPongTool ProfilesTools ConfigThemesUsage StatsAPI KeysWhat's NewTerms & ConditionsCookie Policy
Products
TachiBot MCPdokorotachi-agent
Getting started
  • Introduction
  • Installation
  • Quick Start
  • Examples
Core features
  • Tools Overview
  • Planner
  • Prompt Techniques
  • Workflows
  • PingPong
Configuration
  • Tool Profiles
  • Tools Config
  • Themes
  • Usage Stats
  • API Keys
Resources
  • What's New
Legal
  • Terms & Conditions
  • Cookie Policy

Loading documentation...

← Previous
Planner
Next →
Workflows
Edit this page on GitHub
Docs/Core features

Ask the same question, better.

Research-backed prompt techniques that rewrite your query into a structured prompt for any TachiBot tool. You always see the enhanced prompt before it runs.

techniques
88
categories
18
core, shown by default
20
tools to use them
3

Your question in. A structured prompt out.

A technique is a reusable pattern that rewrites your question before a model sees it. Pick one below and read the exact prompt the engine sends: nothing is hidden, and the highlighted text is your query.

You ask

“How should we design caching for 1M concurrent users?”

preview_prompt_technique({
technique: "first_principles",
tool: "grok_reason",
query: "…"
})
Use it when

The obvious solution is 'how everyone does it' and nobody asked why.

first_principles→ the model receives
Reason about "How should we design caching for 1M concurrent users?" from first principles: 1) what is definitely, verifiably true here? 2) what is merely assumed or inherited convention? 3) strip the problem to its irreducible pieces, 4) rebuild an answer from those pieces alone — not from how it is usually done.
your query, substituted into the technique’s template

Discover, preview, execute.

01find one
list_prompt_techniques

Core techniques by default. Pass all=true for every one, or filter by category.

list_prompt_techniques({
filter: "reasoning" })
02read before it runs
preview_prompt_technique

Returns the enhanced prompt and a token valid for 15 minutes. Nothing is executed yet.

preview_prompt_technique({
technique: "first_principles",
tool: "grok_reason", … })
03run it
execute_prompt_technique

Run the previewed prompt with "last", or skip preview and pass technique, tool and query directly.

execute_prompt_technique({
execution_token: "last" })
✓
Not sure which technique?
Pass technique="auto" to preview_prompt_technique and it recommends one, with reasons. Or use refine_prompt to turn a raw query into a goal-first brief.

What are you trying to do?

All 88 techniques

Tier
Category
88 of 88
Retrieval & RAGCorealso accepts note_taking

chain_of_note

Write a short note on each fetched source — is it relevant, and what does it actually say — before you answer.

Reach for it whenEvery search call you make.
What it preventsStops 'according to [source]' when the source never said that. This is where fabricated citations come from.
The prompt the engine sendsarXiv:2311.09210
Answer "{your query}" from the retrieved sources, but take notes before you answer. For EACH source, write one note:RELEVANT / PARTIALLY RELEVANT / NOT RELEVANTWhat it actually says on this question — in its own terms, not your paraphrase of what you hoped it said.Anything it explicitly does NOT establish. Then answer using only the relevant notes. If the notes don't support an answer, say thesources are insufficient and state what's missing — do not fill the gap from memory andattribute it to a source.
preview_prompt_technique({ technique: "chain_of_note", query: "…" })