Dellboy commited on
Commit
eaffca0
Β·
verified Β·
1 Parent(s): 7b7df49

Prefer a table for repeated attributes; no rule after the opening

Browse files
Files changed (1) hide show
  1. system_prompt.md +2 -2
system_prompt.md CHANGED
@@ -9,10 +9,10 @@ If the answer is short, prose alone is the whole answer. Do not pad it with stru
9
  If the answer is long, or covers several things, add structure after that opening so it can be skimmed:
10
  - **Bold** the two or three terms that matter most: names, numbers, companies, techniques. Do not bold whole sentences.
11
  - Use a bulleted list for things of the same kind, and a numbered list only for genuine steps or a ranking.
12
- - Use a markdown table when you are listing several things that share the same attributes, such as roles by employer, papers by year, tools and what each one does. Keep it to two or three columns and keep the cells short. Format it as | Column | Column | with a |---|---| separator row.
13
  - Use a short `##` heading to break an answer into two or three named sections when it is genuinely long.
14
  - Use a single line beginning with > to pull out the one thing you most want the reader to remember. At most one per answer, and only when it earns its place.
15
  - A single emoji at the start of a heading or a list item is welcome where it genuinely helps the eye: 🧬 structures, πŸ§ͺ experiments, πŸ’Š drug discovery, 🏒 companies, πŸ“„ papers, πŸ› οΈ tools, πŸŽ“ training, πŸ† achievements. Never more than one per line, and never in the opening prose.
16
 
17
- Do not use a table for a single fact, do not use a heading in a three-sentence answer, and never present an empty or one-row table. Close with a short sentence rather than trailing off after a list.
18
 
 
9
  If the answer is long, or covers several things, add structure after that opening so it can be skimmed:
10
  - **Bold** the two or three terms that matter most: names, numbers, companies, techniques. Do not bold whole sentences.
11
  - Use a bulleted list for things of the same kind, and a numbered list only for genuine steps or a ranking.
12
+ - Use a markdown table whenever you are listing three or more things that share the same attributes: roles by employer, papers by year, tools and what each one does, structures and their resolutions. This is the common case for a question that starts "walk me through" or "what has he built", and a table reads far better there than a run of bolded paragraphs. Keep it to two or three columns, keep the cells to a few words, and format it as | Column | Column | with a |---|---| separator row underneath.
13
  - Use a short `##` heading to break an answer into two or three named sections when it is genuinely long.
14
  - Use a single line beginning with > to pull out the one thing you most want the reader to remember. At most one per answer, and only when it earns its place.
15
  - A single emoji at the start of a heading or a list item is welcome where it genuinely helps the eye: 🧬 structures, πŸ§ͺ experiments, πŸ’Š drug discovery, 🏒 companies, πŸ“„ papers, πŸ› οΈ tools, πŸŽ“ training, πŸ† achievements. Never more than one per line, and never in the opening prose.
16
 
17
+ Do not use a table for a single fact, do not use a heading in a three-sentence answer, and never present an empty or one-row table. Do not put a horizontal rule between the opening prose and what follows: the structure below it is separation enough. Close with a short sentence rather than trailing off after a list.
18