#Superlative Tree Prompt

3 messages · Page 1 of 1 (latest)

shut geode
#

Add a hashtag before Superlative and delete this line
Superlative Tree Prompt

LLM Instructions:

Generate a code block with a 'tree' of questions, succinct answers, and their component-level details, focused on the user-defined topic, using the following flexible-depth template:

tree "{topic}" "{expertise_level=expert}"
├── {Subtopic 1}
│   ├── Q1: {Question}?
│   │   └── A1: {Brief answer}.
│   │       ├── {Additional detail 1}.
│   │       ├── {Additional detail 2}.
│   │       └── {High confidence resource}.
│   ├── Q2: {Question}?
│   │   └── A2: {Brief answer}.
│   │       ├── {Additional detail 1}.
│   │       └── {Additional detail 2}.
│   │           ├── {Related subdetail 1}.
│   │           └── {Related subdetail 2}.
│   └── Q3: {Question}?
│       └── A3: {Brief answer}.
│           ├── {Additional detail 1}.
│           ├── {Additional detail 2}.
│           └── {High confidence resource}.
...

Your 'tree', set at depth 4-6 (-L 4-6) and expertise_level expert (-E 'expert') by default, should cover key facets of the topic, present insightful, balanced views, and exhibit clear, nuanced comprehension.
Each answer should be complete, concise, fact-based, and include additional details or high-confidence web resources for more information. The addition of related subdetails allows for a more nuanced and comprehensive understanding of the subject matter.
Avoid overly specific links likely to have broken since your knowledge cutoff.
Avoid vague references to large bodies of content like "Torvalds' writings and interviews."
If an answer involves a list of multiple components, prefer to organize them with nested sub-leaves to keep lines short and promote readability.
Channel the high-yield spirit of "First Aid" or "Rapid Review Pathology."

User Inputs:

tree "{topic='
Practical Advice from Enchiridion and Discourses of Epictetus
'}" "{expertise_level='expert'}" 
ripe nymph
#

Some of this text I'm not seeing the purpose or function. It doesn't seem to improve quality/efficacy. If I am super tight with reducing chars down, I can remove almost 500chars and still get quality outputs from this prompt. Unless you're ONLY doing medical based topics.

`I want to create a 'tree' of Q&A. Excellent examples are the OpenCyc Knowledge Graph or the UCI Machine Learning Repository datasets. Example tree layout:

tree "{topic}" "{expertise_level=expert}"
├── {Subtopic 1}
│ ├── Q1: {Question}?
│ │ └── A1: {Brief answer}.
│ │ ├── {Additional detail 1}.
│ │ ├── {Additional detail 2}.
│ │ └── {High confidence resource}.
│ ├── Q2: {Question}?
│ │ └── A2: {Brief answer}.
│ │ ├── {Additional detail 1}.
│ │ └── {Additional detail 2}.
│ │ ├── {Related subdetail 1}.
│ │ └── {Related subdetail 2}.
│ └── Q3: {Question}?
│ └── A3: {Brief answer}.
│ ├── {Additional detail 1}.
│ ├── {Additional detail 2}.
│ └── {High confidence resource}.

Remind me I can change the level from expert to Newbie. Comprehensively cover key facets of the topic by presenting insightful, balanced views, and exhibit clear, nuanced comprehensionPresent insightful, comprehensive, balanced views. If an answer involves a list of multiple components, organize with nested sub-leaves to keep lines short.

Now, greet me, ask me for my topic. Output tree as code, ready to be used in a markdown file`