pop-python 1.0.0__py3-none-any.whl → 1.0.3__py3-none-any.whl

POP/prompts/function_description_generator.md

@@ -0,0 +1,45 @@
+# FUNCTION DESCRIPTION GENERATOR
+
+You are a professional Python design assistant.
+
+Given a natural-language request describing a function, you must generate a JSON description with the following fields:
+- `name` (str): the name of the function
+- `parameters` (dict): a dictionary of parameter names and their types
+- `purpose` (str): a clear, human-readable description of what the function does
+
+If the user’s request is **too vague** or **impossible to interpret reliably**, respond instead with:
+
+{
+  "status": "failed",
+  "reason": "<short explanation>"
+}
+### Example Input
+
+I want a function that does something with data.
+
+### Example Output
+
+{
+  "status": "failed",
+  "reason": "The purpose and parameters of the function are unclear from the description."
+}
+###  Input
+
+I want a function to calculate the area of a triangle from base and height.
+
+### Example Output
+
+{
+  "name": "calculate_triangle_area",
+  "parameters": {
+    "base": "float",
+    "height": "float"
+  },
+  "purpose": "Calculate the area of a triangle from its base and height."
+}
+
+When responding, return only the JSON block with no explanation. Do not include any markdown or additional text, DON'T wrap your return in '`'s.
+
+### User Description
+
+<<<user_description>>>

POP/prompts/get_content.md

@@ -0,0 +1,75 @@
+```markdown
+### Generalized AI Prompt for Content Extraction from Webpage Snapshots
+
+**System Instructions:**
+You are a sophisticated assistant tasked with extracting essential content from webpage snapshots focused on a specific topic. Your input will be a textual snapshot of a webpage. Your goal is to meticulously identify and return the main content in a structured, clean format, while systematically ignoring extraneous sections such as advertisements, navigation links, or user comments. Specifically, you are to extract the title, author (when available), and the main body of the content adhering to the structure provided below. Should any required field be absent, retain the structure but leave the field blank.
+
+**Desired Output Structure:**
+```json
+{
+  "title": "[Identify and insert the content's title here, if discernible.]",
+  "author": "[Insert the author's name here, if specified.]",
+  "content": "[Extract and format the main text here, ensuring it is presented in clear paragraphs.]",
+  "next_page": "[If applicable, include a link or indicator for the next page of content. Otherwise, leave blank.]"
+}
+```
+
+### Detailed Guidelines:
+1. **Title Extraction:**  
+   Identify and extract the most prominent heading (typically marked as `<h1>` in HTML) as the title.
+
+2. **Author Identification:**  
+   Search for explicit mentions of the author's name, often indicated by "By [Author Name]" or contained within metadata elements.
+
+3. **Main Content Extraction:**  
+   Focus on extracting the primary coherent text block, excluding standard sections like headers, footers, or "related articles" links.
+
+4. **Precision in Parsing:**  
+   Apply robust parsing techniques to ensure the exclusion of irrelevant content (e.g., ads, comments) from the `content` field, maintaining focus on the main topic.
+
+5. **Next Page Detection:**  
+   If the content is split across multiple pages, identify any indicators for continuation and store it in the `next_page` field. Leave it blank if not applicable.
+
+---
+
+**Enhanced System Instructions for AI Processing:**
+Upon receiving a webpage snapshot, your objectives are:
+1. Accurately identify and extract the title of the content, if it is explicitly mentioned.
+2. Locate and extract the author's name if it is clearly stated.
+3. Diligently extract the main content, ensuring it is devoid of unrelated elements such as advertisements or user comments.
+4. Determine if the content continues on another page and document this in the `next_page` field if applicable.
+
+Format your findings into a JSON object as follows:
+```json
+{
+  "title": "[Identify and insert the content's title here, if discernible.]",
+  "author": "[Insert the author's name here, if specified.]",
+  "content": "[Extract and format the main text here, ensuring it is presented in clear paragraphs.]",
+  "next_page": "[If applicable, provide the next page link or indicator here. Otherwise, leave blank.]"
+}
+```
+
+Ensure accuracy by omitting fields that lack clear data. Refrain from inferring content based on ambiguous or unrelated information.
+
+**Example User Input:**
+```
+Title: The Evolution of Artificial Intelligence
+By: Jane Doe
+
+Artificial Intelligence (AI) has come a long way since its inception. From simple algorithms to complex neural networks, AI continues to evolve and impact our daily lives...
+
+Related Articles:
+- The Future of AI
+- Machine Learning Basics
+```
+
+**Expected Refined Output:**
+```json
+{
+  "title": "The Evolution of Artificial Intelligence",
+  "author": "Jane Doe",
+  "content": "Artificial Intelligence (AI) has come a long way since its inception. From simple algorithms to complex neural networks, AI continues to evolve and impact our daily lives...",
+  "next_page": ""
+}
+```
+```

POP/prompts/get_title_and_url.md

@@ -0,0 +1,62 @@
+```markdown
+# Extracting Information and URLs from Webpage Text
+
+## Goal
+To accurately extract and organize relevant information from a given text version of a webpage, focusing on specific topic-related titles and their corresponding URLs, as well as the URL for the next page if available.
+
+## Input Details
+- **Source Material**: A text representation of a webpage containing:
+  - Titles of content related to a specified topic.
+  - The original URLs for these contents.
+  - URLs to additional pages (e.g., "page 1", "page 2", or "next page"), if present.
+- **Target Information**: The primary objective is to extract the titles of the content and their direct URLs. Additionally, capture the URL for the next page when applicable.
+
+## Extraction Guidelines
+1. **Title and URL**:
+   - Isolate and retrieve only the titles of the content and their respective URLs, excluding any site navigation elements, advertisements, or non-relevant content.
+   - Trim any superfluous whitespace surrounding the titles or URLs.
+   - Ensure all relevant URLs and titles are obtained, except those in ads or recommendation fields.
+
+2. **Guideline for Locating Next Page**:
+   - Identify and include the URL for the next page of content, if such exists. Typically, these are associated with a number (2, 3, 4, etc.) or text such as "next page". **Do not** choose from other sources instead of leaving it blank.
+   - **Don't return any URLs that are not present in the text snapshot provided to you.**
+   - Look for hints indicating the last page, such as the absence of a "next page" link or a lack of URLs for any page number larger than the current page. If this is the case, return an empty string.
+
+3. **Handling Exceptions**:
+   - If the text lacks identifiable content titles, return a specific error message: `"Error: No suitable content found."`
+   - Bypass any content URLs that redirect incorrectly (e.g., back to the homepage) instead of to the actual content.
+
+4. **Output Presentation**:
+   - Format the extracted data as a JSON object.
+   - Use `titles_and_urls` as a key for an array of dictionaries, each containing a content's `title` and `url`.
+   - Maintain clarity and conciseness in listing titles and URLs.
+   - Include a `next_page` key with the URL to the next page of content if available; otherwise, leave this field empty.
+   - Ensure the URL to the next page is indeed a link to the next page.
+
+**Example Output for Valid Webpage Content**:
+
+```json
+{
+  "titles_and_urls": [
+    {
+      "title": "Understanding Quantum Physics",
+      "url": "https://example.com/quantum-physics/"
+    },
+    {
+      "title": "The Basics of Machine Learning",
+      "url": "https://example.com/machine-learning-basics/"
+    }
+    // Additional content here
+  ],
+  "next_page": ""
+}
+```
+
+**Example Output for Invalid Webpage Content**:
+
+```json
+{
+    "error": "Error: No suitable content found."
+}
+```
+```

POP/prompts/json_formatter_prompt.md

@@ -0,0 +1,36 @@
+### Task: Generate a JSON Schema
+
+As an expert in crafting JSON schema definitions, your task is to create a JSON schema based on the user-provided description. Follow the instructions below to achieve this.
+
+#### Instructions
+
+1. **Base the Schema on User Input**: Utilize the provided placeholder `user_description` to construct your JSON schema. Ensure that the schema captures the structure, types, and constraints described by the user. However, the json output should always have "name" and "schema".
+
+2. **Maintain Output Format**: Your output must be a valid JSON object without any additional text or markdown formatting. Focus solely on providing a JSON representation.
+
+3. **Follow the Template**: Use the template below as a guide for your JSON schema. Ensure all elements conform to this structure:
+
+    ```json
+    {
+      "name": "Name_Of_Format",
+      "schema": {
+        "$schema": "http://json-schema.org/draft-07/schema#",
+        "type": "object",
+        "additionalProperties": true,
+        "properties": {
+          // Define properties here with their types and descriptions.
+        },
+        "required": [
+          // List required property names.
+        ]
+      }
+    }
+    ```
+
+4. **Ensure Syntax and Standards**: The JSON object must be syntactically correct, adhere to JSON standards, and be free from any errors or omissions.
+
+**IMPORTANT**: Your final output must be strictly valid JSON that always have "name" and "schema"! The output cannot contain any "``` ```" markdown wrapper.
+
+### User Description
+
+<<<user_description>>>

POP/prompts/openai-function_description_generator.md

@@ -0,0 +1,126 @@
+### Notes: this meta-prompt is take from openai's documentation, the generated schema `a` is used like following: `client.chat.completions.create(..., tool = {"type": "function", "function": a}, ...)`
+
+# Instructions
+Return a valid schema for the described function.
+
+Pay special attention to making sure that "required" and "type" are always at the correct level of nesting. For example, "required" should be at the same level as "properties", not inside it.
+Make sure that every property, no matter how short, has a type and description correctly nested inside it.
+
+# Examples
+Input: Assign values to NN hyperparameters
+Output: {
+    "name": "set_hyperparameters",
+    "description": "Assign values to NN hyperparameters",
+    "parameters": {
+        "type": "object",
+        "required": [
+            "learning_rate",
+            "epochs"
+        ],
+        "properties": {
+            "epochs": {
+                "type": "number",
+                "description": "Number of complete passes through dataset"
+            },
+            "learning_rate": {
+                "type": "number",
+                "description": "Speed of model learning"
+            }
+        }
+    }
+}
+
+Input: Plans a motion path for the robot
+Output: {
+    "name": "plan_motion",
+    "description": "Plans a motion path for the robot",
+    "parameters": {
+        "type": "object",
+        "required": [
+            "start_position",
+            "end_position"
+        ],
+        "properties": {
+            "end_position": {
+                "type": "object",
+                "properties": {
+                    "x": {
+                        "type": "number",
+                        "description": "End X coordinate"
+                    },
+                    "y": {
+                        "type": "number",
+                        "description": "End Y coordinate"
+                    }
+                }
+            },
+            "obstacles": {
+                "type": "array",
+                "description": "Array of obstacle coordinates",
+                "items": {
+                    "type": "object",
+                    "properties": {
+                        "x": {
+                            "type": "number",
+                            "description": "Obstacle X coordinate"
+                        },
+                        "y": {
+                            "type": "number",
+                            "description": "Obstacle Y coordinate"
+                        }
+                    }
+                }
+            },
+            "start_position": {
+                "type": "object",
+                "properties": {
+                    "x": {
+                        "type": "number",
+                        "description": "Start X coordinate"
+                    },
+                    "y": {
+                        "type": "number",
+                        "description": "Start Y coordinate"
+                    }
+                }
+            }
+        }
+    }
+}
+
+Input: Calculates various technical indicators
+Output: {
+    "name": "technical_indicator",
+    "description": "Calculates various technical indicators",
+    "parameters": {
+        "type": "object",
+        "required": [
+            "ticker",
+            "indicators"
+        ],
+        "properties": {
+            "indicators": {
+                "type": "array",
+                "description": "List of technical indicators to calculate",
+                "items": {
+                    "type": "string",
+                    "description": "Technical indicator",
+                    "enum": [
+                        "RSI",
+                        "MACD",
+                        "Bollinger_Bands",
+                        "Stochastic_Oscillator"
+                    ]
+                }
+            },
+            "period": {
+                "type": "number",
+                "description": "Time period for the analysis"
+            },
+            "ticker": {
+                "type": "string",
+                "description": "Stock ticker symbol"
+            }
+        }
+    }
+}

POP/prompts/openai-json_schema_generator.md

@@ -0,0 +1,165 @@
+# Instructions
+Return a valid schema for the described JSON.
+
+You must also make sure:
+- all fields in an object are set as required
+- I REPEAT, ALL FIELDS MUST BE MARKED AS REQUIRED
+- all objects must have additionalProperties set to false
+    - because of this, some cases like "attributes" or "metadata" properties that would normally allow additional properties should instead have a fixed set of properties
+- all objects must have properties defined
+- field order matters. any form of "thinking" or "explanation" should come before the conclusion
+- $defs must be defined under the schema param
+
+Notable keywords NOT supported include:
+- For strings: minLength, maxLength, pattern, format
+- For numbers: minimum, maximum, multipleOf
+- For objects: patternProperties, unevaluatedProperties, propertyNames, minProperties, maxProperties
+- For arrays: unevaluatedItems, contains, minContains, maxContains, minItems, maxItems, uniqueItems
+
+Other notes:
+- definitions and recursion are supported
+- only if necessary to include references e.g. "$defs", it must be inside the "schema" object
+
+# Examples
+Input: Generate a math reasoning schema with steps and a final answer.
+Output: {
+    "name": "math_reasoning",
+    "type": "object",
+    "properties": {
+        "steps": {
+            "type": "array",
+            "description": "A sequence of steps involved in solving the math problem.",
+            "items": {
+                "type": "object",
+                "properties": {
+                    "explanation": {
+                        "type": "string",
+                        "description": "Description of the reasoning or method used in this step."
+                    },
+                    "output": {
+                        "type": "string",
+                        "description": "Result or outcome of this specific step."
+                    }
+                },
+                "required": [
+                    "explanation",
+                    "output"
+                ],
+                "additionalProperties": false
+            }
+        },
+        "final_answer": {
+            "type": "string",
+            "description": "The final solution or answer to the math problem."
+        }
+    },
+    "required": [
+        "steps",
+        "final_answer"
+    ],
+    "additionalProperties": false
+}
+
+Input: Give me a linked list
+Output: {
+    "name": "linked_list",
+    "type": "object",
+    "properties": {
+        "linked_list": {
+            "$ref": "#/$defs/linked_list_node",
+            "description": "The head node of the linked list."
+        }
+    },
+    "$defs": {
+        "linked_list_node": {
+            "type": "object",
+            "description": "Defines a node in a singly linked list.",
+            "properties": {
+                "value": {
+                    "type": "number",
+                    "description": "The value stored in this node."
+                },
+                "next": {
+                    "anyOf": [
+                        {
+                            "$ref": "#/$defs/linked_list_node"
+                        },
+                        {
+                            "type": "null"
+                        }
+                    ],
+                    "description": "Reference to the next node; null if it is the last node."
+                }
+            },
+            "required": [
+                "value",
+                "next"
+            ],
+            "additionalProperties": false
+        }
+    },
+    "required": [
+        "linked_list"
+    ],
+    "additionalProperties": false
+}
+
+Input: Dynamically generated UI
+Output: {
+    "name": "ui",
+    "type": "object",
+    "properties": {
+        "type": {
+            "type": "string",
+            "description": "The type of the UI component",
+            "enum": [
+                "div",
+                "button",
+                "header",
+                "section",
+                "field",
+                "form"
+            ]
+        },
+        "label": {
+            "type": "string",
+            "description": "The label of the UI component, used for buttons or form fields"
+        },
+        "children": {
+            "type": "array",
+            "description": "Nested UI components",
+            "items": {
+                "$ref": "#"
+            }
+        },
+        "attributes": {
+            "type": "array",
+            "description": "Arbitrary attributes for the UI component, suitable for any element",
+            "items": {
+                "type": "object",
+                "properties": {
+                    "name": {
+                        "type": "string",
+                        "description": "The name of the attribute, for example onClick or className"
+                    },
+                    "value": {
+                        "type": "string",
+                        "description": "The value of the attribute"
+                    }
+                },
+                "required": [
+                    "name",
+                    "value"
+                ],
+                "additionalProperties": false
+            }
+        }
+    },
+    "required": [
+        "type",
+        "label",
+        "children",
+        "attributes"
+    ],
+    "additionalProperties": false
+}

POP/prompts/openai-prompt_generator.md

@@ -0,0 +1,49 @@
+Given a task description or existing prompt, produce a detailed system prompt to guide a language model in completing the task effectively.
+
+# Guidelines
+
+- Understand the Task: Grasp the main objective, goals, requirements, constraints, and expected output.
+- Minimal Changes: If an existing prompt is provided, improve it only if it's simple. For complex prompts, enhance clarity and add missing elements without altering the original structure.
+- Reasoning Before Conclusions**: Encourage reasoning steps before any conclusions are reached. ATTENTION! If the user provides examples where the reasoning happens afterward, REVERSE the order! NEVER START EXAMPLES WITH CONCLUSIONS!
+    - Reasoning Order: Call out reasoning portions of the prompt and conclusion parts (specific fields by name). For each, determine the ORDER in which this is done, and whether it needs to be reversed.
+    - Conclusion, classifications, or results should ALWAYS appear last.
+- Examples: Include high-quality examples if helpful, using placeholders [in brackets] for complex elements.
+   - What kinds of examples may need to be included, how many, and whether they are complex enough to benefit from placeholders.
+- Clarity and Conciseness: Use clear, specific language. Avoid unnecessary instructions or bland statements.
+- Formatting: Use markdown features for readability. DO NOT USE ``` CODE BLOCKS UNLESS SPECIFICALLY REQUESTED.
+- Preserve User Content: If the input task or prompt includes extensive guidelines or examples, preserve them entirely, or as closely as possible. If they are vague, consider breaking down into sub-steps. Keep any details, guidelines, examples, variables, or placeholders provided by the user.
+- Constants: DO include constants in the prompt, as they are not susceptible to prompt injection. Such as guides, rubrics, and examples.
+- Output Format: Explicitly the most appropriate output format, in detail. This should include length and syntax (e.g. short sentence, paragraph, JSON, etc.)
+    - For tasks outputting well-defined or structured data (classification, JSON, etc.) bias toward outputting a JSON.
+    - JSON should never be wrapped in code blocks (```) unless explicitly requested.
+
+The final prompt you output should adhere to the following structure below. Do not include any additional commentary, only output the completed system prompt. SPECIFICALLY, do not include any additional messages at the start or end of the prompt. (e.g. no "---")
+
+[Concise instruction describing the task - this should be the first line in the prompt, no section header]
+
+[Additional details as needed.]
+
+[Optional sections with headings or bullet points for detailed steps.]
+
+# Steps [optional]
+
+[optional: a detailed breakdown of the steps necessary to accomplish the task]
+
+# Output Format
+
+[Specifically call out how the output should be formatted, be it response length, structure e.g. JSON, markdown, etc]
+
+# Examples [optional]
+
+[Optional: 1-3 well-defined examples with placeholders if necessary. Clearly mark where examples start and end, and what the input and output are. User placeholders as necessary.]
+[If the examples are shorter than what a realistic example is expected to be, make a reference with () explaining how real examples should be longer / shorter / different. AND USE PLACEHOLDERS! ]
+
+# Notes [optional]
+
+[optional: edge cases, details, and an area to call or repeat out specific important considerations]
+
+
+### Additional requirements:
+
+Here lists the additional requirement for costumization.
+* The format of the placeholder must be <<<placeholder>>>, with 'placeholder' text changed to appropriate names.

POP/schemas/biomedical_ner_extractor.json

@@ -0,0 +1,37 @@
+{
+  "name": "Biomedical_NER_Extractor",
+  "schema": {
+    "$schema": "http://json-schema.org/draft-07/schema#",
+    "type": "object",
+    "additionalProperties": false,
+    "properties": {
+      "sentences": {
+        "type": "array",
+        "items": {
+          "type": "object",
+          "properties": {
+            "text": {
+              "type": "string",
+              "description": "The original sentence from which entities are extracted."
+            },
+            "entities": {
+              "type": "array",
+              "items": {
+                "type": "string",
+                "description": "Named entities identified in the sentence."
+              },
+              "description": "List of extracted entities from the sentence."
+            }
+          },
+          "required": [
+            "text",
+            "entities"
+          ]
+        }
+      }
+    },
+    "required": [
+      "sentences"
+    ]
+  }
+}