first commit

README.md

@@ -0,0 +1,7 @@
+# Pre-Built Prompt Repository
+
+This folder includes firstly, the core prompts for `input.prowl`, `intent.prowl` and `output.prowl` as well as a very special prompt known by the same name as the language, `prowl.prowl`.  The rest of the prompts are organized into folders which categorize what those prompt types do. As more updates happen, and perhaps from community contribution, this will grow, giving you more out-of-the-box prompting solutions, or blocks that you can stack anyway you want with `ProwlStack`.
+
+You can try any of these prompts out on our colab or on prowl.github.io
+
+To see examples of using some of these check out the examples folder or see the ProwlStack documentation.

chat/session_naming.prowl

@@ -0,0 +1,15 @@
+# Create a Chat Session
+Lets configure a session for the user to chat with some AI agents.
+
+## Session Type
+Here is a list of the current session types available to create:
+1. one-on-one: The most basic session. The user chats with an AI agent
+2. group: A group of agents and users chatting together
+3. scenario: Any number of agents and users in a scene at a location
+4. adventure: 
+
+
+
+## Name the Session
+Write a brief and concise title for a chat session about the above:
+- Session Name: {session_name(20, 0.4)}

code/code_step.prout

@@ -0,0 +1,2 @@
+# Step {_list_step}
+{program_overview}

code/code_step.prowl

@@ -0,0 +1,9 @@
+# Step {_list_step}
+{program_overview}
+
+## Write the code
+From here on, just write the code given the step instruction above and the previous considerations:
+```python
+{program_code(600, 0.4)}
+
+```

code/codedit.prowl

@@ -0,0 +1,21 @@
+# Code Refinement
+
+## Step 1: Production Readiness
+Take the following code and critically analyze what it needs to be production ready. Assume that any referenced variables and libraries are available and this code is functional:
+```{language}
+{code}
+```
+### Getting it production ready
+Write a numbered list of up to three considerations that could make the code above production ready:
+{missing(500, 0.1)}
+
+### Efficiency
+Write a shorter numbered list of the code changes necessary to perform the above considerations. Keep in mind that some of the changes might affect the functionality of others:
+{efficient_updates(300, 0.2)}
+
+### Rewrite the code:
+rewrite the code using the analysis from above, be sure to try to keep code clean and succinct
+```{language}
+{production_rewrite(6096, 0.0)}
+
+```

code/codetodo.prowl

@@ -0,0 +1,20 @@
+# Code Completion
+Write a numbered list of all of the TODO comments in the following code
+```{language}
+{@file(filename)}
+```
+
+## Unfinished code TODO list
+Write a numbered list of up to five TODOs mentioned in the code. If there are no TODOs, just write (Nothing to do). Be sure to only include those comments marked with TODO:
+{todo(512, 0.05)}
+
+## Think critically
+Write down which of the items from the list above are feasible to complete. Only complete TODOs that don't have missing variable or library references:
+{possible_completions(512, 0.05)}
+
+## Code Rewrite
+Rewrite the code and complete the TODO sections:
+```{language}
+{rewrite(2048, 0.0)}
+
+```

code/program.prout

@@ -0,0 +1,3 @@
+# Program Overview
+
+{program_overview}

code/program.prowl

@@ -0,0 +1,29 @@
+# Create Python Program
+
+## User Reuirements Check
+Make a numbered list of requirements for building the program:
+{program_requirements(300, 0.5)}
+
+## Program Scope
+Is this a small program or a large framework? Write one paragraph about this program's scope:
+{program_scope(120, 0.3)}
+
+## Class Planning
+Write an inclusive step-by-step numbered overview of the program structure that will be needed in order to complete this task. Write about the elemental classes you will need to build the program:
+{program_overview(320, 0.2)}
+
+## Needed Libraries
+Give a bullet list of all of the needed libraries or modules:
+{program_requirements(180, 0.2)}
+
+## Program Main EntryPoint
+Even though the classes described do not exist yet, write the initial entry point script:
+```{program_language}
+{program_code(360, 0.1)}
+
+```
+
+# Coding
+Write some code for classes listed above
+
+{@each(program_overview, code_step)}

code/python.prowl

@@ -0,0 +1,11 @@
+# Write a Python Script
+You will write code using python 3.x.
+
+## Python Code
+write a python code block:
+```{program_language(6, 0.0)}
+{code(1024, 0.0)}
+
+```
+
+## 

code/readme.prowl

@@ -0,0 +1,2 @@
+# Creating a README.md
+Create a markdown file that explains the features, benefits and 

code/regex.prowl

@@ -0,0 +1,3 @@
+# Make a Regular Expression pattern
+Create a regular 
+{pattern(256, 0.1)}

code/test_input.prowl

@@ -0,0 +1,2 @@
+# User Request
+Make a robust multi-agent system that generates a high definition simulation of cell communication via voltage potentials and ion channels. This does not include neuronal communication methods as those were evolved later.

digest/ee.prowl

@@ -0,0 +1,11 @@
+# Entity Extraction
+Read the following story snippet and create a list of characters, locations and items mentioned. Use full or long-form names if necessary to distinguish between entities. Be sure to list what type each entity is like `- NAME OF ENTITY (TYPE): DESCRIPTION`
+
+## Story:
+
+{story}
+
+## List of Characters, Locations and Items:
+
+{character_list(300, 0.1)}
+

digest/se.prowl

@@ -0,0 +1,15 @@
+# State Extraction
+Using the following story snippet and list of entities in the story, create a list of relationships between the entities which defines their most recent state. List entries should be in the format: - entity_subject_name <relationship> entity_object_name
+
+## Entities
+
+{character_list}
+
+## Story
+
+{story}
+
+## Updated Entity States
+Write a flat bullet list of the states/relationships of the entities as expressed in the story:
+{relationships(400, 0.1)}
+

digest/sum_cliffs.prout

@@ -0,0 +1 @@
+{summary}

digest/sum_cliffs.prowl

@@ -0,0 +1,11 @@
+# Summarization
+Write the Cliff's Notes for the following:
+
+
+{text}
+
+
+## Cliff's Notes Summary:
+Write the brief and concise summary about the above. Structure your summary correctly with markdown headers, lists and tables:
+{summary(712, 0.0)}
+

digest/sum_recursive.prowl

@@ -0,0 +1,20 @@
+# Aggregate Summarization
+Write the Cliff's Notes for the following:
+
+## Current Summary
+This is the current summary:
+```
+{summary}
+```
+
+## New Information
+```
+{text}
+```
+
+## Refactor the Summary:
+Using the current summary and the new information, write a brief and concise refactored summary that integrates both and reduces the overall summary length and avoids repetition. Structure your summary correctly with markdown headers, lists and tables:
+```
+{summary(748, 0.0)}
+
+```

digest/sumtitle.prowl

@@ -0,0 +1,11 @@
+# Create a Title
+Come up with a title for the following summary.
+
+## Summary
+```
+{summary}
+```
+
+## Summary Title
+Write an concise and explanatory title to the summary above. Write no more than five words:
+- Title: {summary_title(15, 0.3)}

examples/creative.prowl

@@ -0,0 +1,22 @@
+# Creative Writing
+
+## Storytelling
+Write a short and creative story with a {mood} mood that satisfies the user's request:
+- Story Name: {story_name(24, 0.7)}
+- Story Type: {story_type(12, 0.4)}
+- Story Archectype: {story_archetype(12, 0.2)}
+
+## Write the story
+{story(1024, 0.8)}
+
+## Critical Questions
+Write a numbered list of up to four questions that critically compare the mood and the user request with the rewritten story and ask what details are missing and what doesn't sound convincing:
+{critical_questions(300, 0.1)}
+
+## Critical Answers
+Answer the above questions, adhering to the {mood} mood. Be concise but provide complete answers:
+{critical_answers(512, 0.35)}
+
+## Rewrite
+Now rewrite the story given everything considered making sure it sticks to the {mood} mood:
+{rewrite(1800, 0.3)}

extract/ee.prout

@@ -0,0 +1,2 @@
+# Characters, Locations and Items
+{entity_list}

extract/ee.prowl

@@ -0,0 +1,11 @@
+# Entity Extraction
+Read the following story snippet and create a list of characters, locations and items mentioned. Use full or long-form names if necessary to distinguish between entities.
+
+## Story:
+
+{story}
+
+## List of Characters, Locations and Items
+Write a bullet list with up to five entities. Entity types can be character, location or item. Be sure to list what type each entity is adhering to the syntax `- Name Of Entity (type): Description`. Here's an example "- Frodo (character): The hero who is responsible to deliver the one ring":
+{entity_list(256, 0.0)}
+

extract/ee_inline.prout

@@ -0,0 +1,2 @@
+# Characters, Locations and Items
+{entity_list}

extract/ee_inline.prowl

@@ -0,0 +1,7 @@
+# Entity Extraction
+Using the above text, write a bullet list of characters, locations and items mentioned. Use full or long-form names if necessary to distinguish between entities.:
+
+## List of Characters, Locations and Items
+Write a bullet list with one entity per entry. Entity types can be character, location or item. Be sure to list what type each entity is adhering to the syntax `- Name Of Entity (type): Description`. Here's an example "- Frodo (character): The hero who is responsible to deliver the one ring":
+{entity_list(1024, 0.0)}
+

extract/se.prowl

@@ -0,0 +1,15 @@
+# State Extraction
+Using the following story snippet and list of entities in the story, create a list of relationships between the entities which defines their most recent state. List entries should be in the format: - entity_subject_name <relationship> entity_object_name
+
+## Entities
+
+{entity_list}
+
+## Story
+
+{story}
+
+## Updated Entity States
+Write a flat bullet list of the states/relationships of the entities as expressed in the story. Relationships should be one or two words. Only list entities from the list above as subject or object. Use the syntax - entity_subject (relationship) entity_object:
+{relationships(400, 0.1)}
+

image/comfy.prowl

@@ -0,0 +1 @@
+{@comfy(scene_prompt, workflow, width_background, height_background)}

image/scene.prowl

@@ -0,0 +1,34 @@
+# Make an Image
+The goal of this task is to make an image by first choosing a subject and then generating a prompt for it which we will use the comfy tool to generate an image from.
+
+## Subject
+Describe a subject for the image. Choose anything people would take photos of, surprise me:
+{subject(200, 0.6)}
+
+## Mood
+Choose a single word mood for this subject, for example "creative" or "melancholy":
+- Mood Word: {mood(8, 0.25)}
+
+## Subject Physical Aspects
+Write a brief paragraph which describes more about the physical aspects of the Subject. Be sure to talk about details missing from your previous description which logically make sense:
+{scend_subject_aspects(320, 0.1)}
+
+## Scene
+Write a brief paragraph describing a scene for this subject which reflects the {mood} mood:
+{scene_description(300, 0.2)} 
+
+## Scene Physical Aspects
+Describe the physical aspects of the scene in a couple of sentences:
+{scene_aspects(300, 0.05)}
+
+## Scene Lighting
+Write a short phrase which describes the lighting and the shadows of the scene:
+{scene_lighting(200, 0.1)}
+
+## Medium
+Choose the artistic medium that this image is represented in, for example "pencil drawing" or "photo", or say DEFAULT to let the image generator model choose:
+- Image Medium: {scene_medium(10, 0.1)} 
+
+## Prompt Composition
+Write a comma delimited set of key phrases on a single line which describes all of the above. be sure to only use commas to separate phrases:
+{scene_prompt(520, 0.0)}

input.prowl

@@ -0,0 +1,2 @@
+# User Request
+{user_request}

intent.prowl

@@ -0,0 +1,4 @@
+# User Intent
+What is the user's intended meaning? Disambiguate the request and write one sentence about it's pragmatic intention. Be concise and accurate:
+- The user is requesting I {user_intent(48, 0.0)}
+

language/ansi.prowl

@@ -0,0 +1,5 @@
+# ISO 639-1 Language Codes
+Given the country of a person, figure out what language they most likely speak, and then give the ISO639-1 code for that language.
+- Person Country: {country}
+- Language most likely spoken: {language(6, 0.0)}
+- ISO639-1 Code: {language_iso(2, 0.0)}

language/language.prowl

@@ -0,0 +1,4 @@
+# Language
+Write the language and dialect of the user request and make sure all of your replies are in the same language:
+- Language: {user_languge(14, 0.0)}
+- Dialect: {user_dialect()}

layout/ttrpg.prowl

@@ -0,0 +1,25 @@
+# TTRPG Book Page Layout Design
+Write up an HTML/CSS layout for a page of a TTRPG book for the user based on their request. Keep in mind, the HTML/CSS will be converted into a PDF.
+
+## Critical Thinking
+Write a numbered list of up to five critical questions about the user's request and how to layout their page and style fonts and images:
+{critical_questions(100, 0.05)}
+
+## Critical Answers
+Write a numbered list to answer the questions above:
+{critical_answers(220, 0.0)}
+
+## Coding the Layout
+
+### Setup
+Choose your layout properties based on the user request.
+- Short Creative Style Description: {layout_style(20, 0.0)}
+- Font for Headers: {font_header(8, 0.0)}
+- Font for Paragraphs: {font_paragrapn(8, 0.0)}
+
+### Write the HTML
+Given the considerations above and the user's request, code an HTML body which meets the requirements. Any CSS should be embedded into the HTML. Anywhere content should be put use the syntax with two square brackets and variable in snake case like this [[content_name]]:
+```html
+{html_layout(2048, 0.0)}
+
+```

list/grocery_recipe.prowl

@@ -0,0 +1,27 @@
+# Grocery List:
+Write a Grocery List as a numbered list with up to ten items, only include the names of the items:
+{groceries(120, 0.4)}
+
+## Make a Recipe
+
+### Choose the Ingredients
+Choose your ingredients from your grocery list:
+- Ingredient 1: {@list(groceries)}
+- Ingredient 2: {ingredient_2(12, 0.1)}
+- Ingredient 3: {ingredient_3(12, 0.0)}
+
+### Choose a Theme
+Write a short phrase representing a creative theme title for your recipe. Be creative and don't include the ingredients in your theme title:
+- Theme: {recipe_theme(14, 0.9)}
+
+### Write the Recipe
+Write numbered list with steps on how to cook a delicious meal which features the three ingredients above:
+{recipe_steps(512, 0.3)}
+
+### Name your Creation
+Come up with a short and sweet name for the above recipe:
+- Name: {recipe_name(12, 0.3)}
+
+### Ingredients you Didn't Buy
+Write a bullet list of any ingredients mentioned in the recipe which were not in the grocery list:
+{missing_ingredients(120, 0.0)}