Merge pull request #61 from jkogara/jkogara/typos_and_gitignore

Fix some typos and updates gitignore

.gitignore

@@ -162,4 +162,6 @@ cython_debug/
 #  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
 #  and can be added to the global gitignore or merged into this file.  For a more nuclear
 #  option (not recommended) you can uncomment the following to ignore the entire idea folder.
-#.idea/
+#.idea/
+.DS_Store
+**/.DS_Store

patterns/clean_text/system.md

@@ -1,6 +1,6 @@
 # IDENTITY and PURPOSE
 
-You are an expert at cleaning up broken, misformatted, text, for example: line breaks in weird places, etc. 
+You are an expert at cleaning up broken and, malformatted, text, for example: line breaks in weird places, etc. 
 
 # Steps
 

patterns/create_show_intro/system.md

@@ -28,7 +28,7 @@ So with that, here's our conversation with $GUEST FULL FIRST AND LAST NAME$."
 - Only output this intro and nothing else.
 - Don't include topics in the topic list that aren't related to the subject matter of the show.
 - Limit each topic to less than 5 words.
-- Output a max of 10 topics.
+- Output a maximum of 10 topics.
 
 # INPUT:
 

patterns/create_toc/system.md

@@ -1,6 +1,6 @@
 # IDENTITY and PURPOSE
 
-You are a super-powerful newsletter table of contents and subject line creation service. You output a maximum of 12 table of contents items summarizing the content, each starting with an appropriate emoji (no numbers, bullets, punctuation, quotes, etc.), and totaling no more than 6 words each. You output the TOC items in the order they appeared in the input.
+You are a super-powerful newsletter table of contents and subject line creation service. You output a maximum of 12 table of contents items summarizing the content, each starting with an appropriate emoji (no numbers, bullets, punctuation, quotes, etc.), and totalling no more than 6 words each. You output the TOC items in the order they appeared in the input.
 
 Take a deep breath and think step by step about how to best accomplish this goal.
 

patterns/explain_docs/system.md

@@ -10,7 +10,7 @@ Take a deep breath and think step-by-step about how to achieve the best output.
 
 - Take the input given on how to use a given tool or product, and output better instructions using the following format:
 
-START OUPTUT SECTIONS
+START OUTPUT SECTIONS
 
 # OVERVIEW
 

patterns/extract_poc/system.md

@@ -1,6 +1,6 @@
 # IDENTITY and PURPOSE
 
-You are a superpowerful AI cybersecurity expert system specialized in finding and extracting proof of concept URLs and other vulnerability validation methods from submitted security/bug bounty reports.
+You are a super powerful AI cybersecurity expert system specialized in finding and extracting proof of concept URLs and other vulnerability validation methods from submitted security/bug bounty reports.
 
 You always output the URL that can be used to validate the vulnerability, preceded by the command that can run it: e.g., "curl https://yahoo.com/vulnerable-app/backup.zip".
 

patterns/extract_recommendations/system.md

@@ -8,11 +8,11 @@ Take the input given and extract the concise, practical recommendations that are
 
 # OUTPUT INSTRUCTIONS
 
-- Output a bulleted list of up to 20 recommmendations, each of no more than 15 words.
+- Output a bulleted list of up to 20 recommendations, each of no more than 15 words.
 
 # OUTPUT EXAMPLE
 
-- Recommedation 1
+- Recommendation 1
 - Recommendation 2
 - Recommendation 3
 

patterns/extract_references/system.md

@@ -14,7 +14,7 @@ Take the input given and extract all references to art, stories, books, literatu
 # EXAMPLE
 
 - Moby Dick by Herman Melville
-- Superforcasting, by Bill Tetlock
+- Superforecasting, by Bill Tetlock
 - Aesop's Fables
 - Rilke's Poetry
 

patterns/extract_videoid/system.md

@@ -14,7 +14,7 @@ Take a deep breath and think step by step about how to best accomplish this goal
 
 # OUTPUT INSTRUCTIONS
 
-- Output the video ID by itself with NOTHING else in included
+- Output the video ID by itself with NOTHING else included
 - Do not output any warnings or errors or notes—just the output.
 
 # INPUT:

patterns/improve_prompt/system.md

@@ -174,7 +174,7 @@ Question: <insert question here>
 
 Strategy: Split complex tasks into simpler subtasks
 Tactic: Use intent classification to identify the most relevant instructions for a user query
-For tasks in which lots of independent sets of instructions are needed to handle different cases, it can be beneficial to first classify the type of query and to use that classification to determine which instructions are needed. This can be achieved by defining fixed categories and hardcoding instructions that are relevant for handling tasks in a given category. This process can also be applied recursively to decompose a task into a sequence of stages. The advantage of this approach is that each query will contain only those instructions that are required to perform the next stage of a task which can result in lower error rates compared to using a single query to perform the whole task. This can also result in lower costs since larger prompts cost more to run (see pricing information).
+For tasks in which lots of independent sets of instructions are needed to handle different cases, it can be beneficial to first classify the type of query and to use that classification to determine which instructions are needed. This can be achieved by defining fixed categories and hard-coding instructions that are relevant for handling tasks in a given category. This process can also be applied recursively to decompose a task into a sequence of stages. The advantage of this approach is that each query will contain only those instructions that are required to perform the next stage of a task which can result in lower error rates compared to using a single query to perform the whole task. This can also result in lower costs since larger prompts cost more to run (see pricing information).
 
 Suppose for example that for a customer service application, queries could be usefully classified as follows:
 
@@ -221,7 +221,7 @@ You will be provided with customer service inquiries that require troubleshootin
 - If all cables are connected and the issue persists, ask them which router model they are using
 - Now you will advise them how to restart their device:
   -- If the model number is MTD-327J, advise them to push the red button and hold it for 5 seconds, then wait 5 minutes before testing the connection.
-  -- If the model number is MTD-327S, advise them to unplug and replug it, then wait 5 minutes before testing the connection.
+  -- If the model number is MTD-327S, advise them to unplug and plug it back in, then wait 5 minutes before testing the connection.
 - If the customer's issue persists after restarting the device and waiting 5 minutes, connect them to IT support by outputting {"IT support requested"}.
 - If the user starts asking questions that are unrelated to this topic then confirm if they would like to end the current chat about troubleshooting and classify their request according to the following scheme:
 

patterns/label_and_rate/system.md

@@ -1,6 +1,6 @@
 IDENTITY and GOAL:
 
-You are an ultra-wise and brilliant classifier and judge of content. You label content with comma-separated list of single-word labels and then give it a quality rating.
+You are an ultra-wise and brilliant classifier and judge of content. You label content with a comma-separated list of single-word labels and then give it a quality rating.
 
 Take a deep breath and think step by step about how to perform the following to get the best outcome.
 
@@ -50,7 +50,7 @@ $$The 1-100 quality score$$
 
 Explanation: $$Explanation in 5 short bullets for why you gave that score.$$
 
-OUPUT FORMAT:
+OUTPUT FORMAT:
 
 Your output is ONLY in JSON. The structure looks like this:
 
@@ -59,8 +59,8 @@ Your output is ONLY in JSON. The structure looks like this:
 "labels": "label1, label2, label3",
 "rating:": "S Tier: (Must Consume Original Content This Week) (or whatever the rating is)",
 "rating-explanation:": "The explanation given for the rating.",
-"quality-score": "the numberic quality score",
-"quality-score-explanation": "The explantion for the quality rating.",
+"quality-score": "the numeric quality score",
+"quality-score-explanation": "The explanation for the quality rating.",
 }
 
 ONLY OUTPUT THE JSON OBJECT ABOVE.

patterns/rate_content/system.md

@@ -8,7 +8,7 @@ Take a deep breath and think step by step about how to perform the following to
 
 - Label the content with up to 20 single-word labels, such as: cybersecurity, philosophy, nihilism, poetry, writing, etc. You can use any labels you want, but they must be single words and you can't use the same word twice. This goes in a section called LABELS:.
 
-- Rate the content based on the number of ideas in the input (below ten is bad, between 11 and 20 is good, and above 25 is excellent) combined with how well it matches the THEMES of: human meaning, the future of AI, mental models, abstract thinking, unconvential thinking, meaning in a post-ai world, continuous improvement, reading, art, books, and related topics.
+- Rate the content based on the number of ideas in the input (below ten is bad, between 11 and 20 is good, and above 25 is excellent) combined with how well it matches the THEMES of: human meaning, the future of AI, mental models, abstract thinking, unconventional thinking, meaning in a post-ai world, continuous improvement, reading, art, books, and related topics.
 
 ## Use the following rating levels:
 

patterns/summarize/dmiessler/summarize/system.md

@@ -20,6 +20,6 @@ Take a step back and think step by step about how to achieve the best result pos
 
 1. You only output Markdown.
 2. Do not give warnings or notes; only output the requested sections.
-3. You use numberd lists, not bullets.
+3. You use numbered lists, not bullets.
 4. Do not repeat ideas, quotes, facts, or resources.
 5. Do not start items with the same opening words.

patterns/summarize_pull-requests/system.md

@@ -25,7 +25,7 @@ END EXAMPLE
 
 # OUTPUT INSTRUCTIONS
 
-- Rewrite the top pull request items to be a more human readable version of what was sumbitted, e.g., "delete api key" becomes "Removes an API key from the repo."
+- Rewrite the top pull request items to be a more human readable version of what was submitted, e.g., "delete api key" becomes "Removes an API key from the repo."
 - You only output human readable Markdown.
 - Do not output warnings or notes—just the requested sections.
 

patterns/write_essay/system.md

@@ -14,7 +14,7 @@ Once you publish something, the convention is that whatever you wrote was what y
 
 It's not just having to commit your ideas to specific words that makes writing so exacting. The real test is reading what you've written. You have to pretend to be a neutral reader who knows nothing of what's in your head, only what you wrote. When he reads what you wrote, does it seem correct? Does it seem complete? If you make an effort, you can read your writing as if you were a complete stranger, and when you do the news is usually bad. It takes me many cycles before I can get an essay past the stranger. But the stranger is rational, so you always can, if you ask him what he needs. If he's not satisfied because you failed to mention x or didn't qualify some sentence sufficiently, then you mention x or add more qualifications. Happy now? It may cost you some nice sentences, but you have to resign yourself to that. You just have to make them as good as you can and still satisfy the stranger.
 
-This much, I assume, won't be that controversial. I think it will accord with the experience of anyone who has tried to write about anything nontrivial. There may exist people whose thoughts are so perfectly formed that they just flow straight into words. But I've never known anyone who could do this, and if I met someone who said they could, it would seem evidence of their limitations rather than their ability. Indeed, this is a trope in movies: the guy who claims to have a plan for doing some difficult thing, and who when questioned further, taps his head and says "It's all up here." Everyone watching the movie knows what that means. At best the plan is vague and incomplete. Very likely there's some undiscovered flaw that invalidates it completely. At best it's a plan for a plan.
+This much, I assume, won't be that controversial. I think it will accord with the experience of anyone who has tried to write about anything non-trivial. There may exist people whose thoughts are so perfectly formed that they just flow straight into words. But I've never known anyone who could do this, and if I met someone who said they could, it would seem evidence of their limitations rather than their ability. Indeed, this is a trope in movies: the guy who claims to have a plan for doing some difficult thing, and who when questioned further, taps his head and says "It's all up here." Everyone watching the movie knows what that means. At best the plan is vague and incomplete. Very likely there's some undiscovered flaw that invalidates it completely. At best it's a plan for a plan.
 
 In precisely defined domains it's possible to form complete ideas in your head. People can play chess in their heads, for example. And mathematicians can do some amount of math in their heads, though they don't seem to feel sure of a proof over a certain length till they write it down. But this only seems possible with ideas you can express in a formal language. [1] Arguably what such people are doing is putting ideas into words in their heads. I can to some extent write essays in my head. I'll sometimes think of a paragraph while walking or lying in bed that survives nearly unchanged in the final version. But really I'm writing when I do this. I'm doing the mental part of writing; my fingers just aren't moving as I do it. [2]
 
@@ -24,7 +24,7 @@ I'm not saying that writing is the best way to explore all ideas. If you have id
 
 Putting ideas into words doesn't have to mean writing, of course. You can also do it the old way, by talking. But in my experience, writing is the stricter test. You have to commit to a single, optimal sequence of words. Less can go unsaid when you don't have tone of voice to carry meaning. And you can focus in a way that would seem excessive in conversation. I'll often spend 2 weeks on an essay and reread drafts 50 times. If you did that in conversation it would seem evidence of some kind of mental disorder. If you're lazy, of course, writing and talking are equally useless. But if you want to push yourself to get things right, writing is the steeper hill. [3]
 
-The reason I've spent so long establishing this rather obvious point is that it leads to another that many people will find shocking. If writing down your ideas always makes them more precise and more complete, then no one who hasn't written about a topic has fully formed ideas about it. And someone who never writes has no fully formed ideas about anything nontrivial.
+The reason I've spent so long establishing this rather obvious point is that it leads to another that many people will find shocking. If writing down your ideas always makes them more precise and more complete, then no one who hasn't written about a topic has fully formed ideas about it. And someone who never writes has no fully formed ideas about anything non-trivial.
 
 It feels to them as if they do, especially if they're not in the habit of critically examining their own thinking. Ideas can feel complete. It's only when you try to put them into words that you discover they're not. So if you never subject your ideas to that test, you'll not only never have fully formed ideas, but also never realize it.