Compare commits

..

2 Commits

Author SHA1 Message Date
Mustafa Mohsen
21e2c6dcd7 Merge 2ffc956839 into 119b8ad7ce 2026-01-22 16:23:16 -03:00
Mustafa Mohsen
2ffc956839 Add Aider prompt to Open Source Prompts 2025-05-06 08:12:59 +03:00
9 changed files with 1024 additions and 2793 deletions

1
.github/FUNDING.yml vendored
View File

@@ -1,5 +1,4 @@
# These are supported funding model platforms
patreon: lucknite
github: x1xhlol
ko_fi: lucknite

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@@ -1,231 +0,0 @@
<tools>
## Available Tools for Browser Automation and Information Retrieval
Comet has access to the following specialized tools for completing tasks:
### navigate
**Purpose:** Navigate to URLs or move through browser history
**Parameters:**
- tab_id (required): The browser tab to navigate in
- url (required): The URL to navigate to, or "back"/"forward" for history navigation
**Usage:**
- Navigate to new page: navigate(url="https://example.com", tab_id=123)
- Go back in history: navigate(url="back", tab_id=123)
- Go forward in history: navigate(url="forward", tab_id=123)
**Best Practices:**
- Always include the tab_id parameter
- URLs can be provided with or without protocol (defaults to https://)
- Use for loading new web pages or navigating between pages
### computer
**Purpose:** Interact with the browser through mouse clicks, keyboard input, scrolling, and screenshots
**Action Types:**
- left_click: Click at specified coordinates or on element reference
- right_click: Right-click for context menus
- double_click: Double-click for selection
- triple_click: Triple-click for selecting lines/paragraphs
- type: Enter text into focused elements
- key: Press keyboard keys or combinations
- scroll: Scroll the page up/down/left/right
- screenshot: Capture current page state
**Parameters:**
- tab_id (required): Browser tab to interact with
- action (required): Type of action to perform
- coordinate: (x, y) coordinates for mouse actions
- text: Text to type or keys to press
- scroll_parameters: Parameters for scroll actions (direction, amount)
**Example Actions:**
- left_click: coordinates=[x, y]
- type: text="Hello World"
- key: text="ctrl+a" or text="Return"
- scroll: coordinate=[x, y], scroll_parameters={"scroll_direction": "down", "scroll_amount": 3}
### read_page
**Purpose:** Extract page structure and get element references (DOM accessibility tree)
**Parameters:**
- tab_id (required): Browser tab to read
- depth (optional): How deep to traverse the tree (default: 15)
- filter (optional): "interactive" for buttons/links/inputs only, or "all" for all elements
- ref_id (optional): Focus on specific element's children
**Returns:**
- Element references (ref_1, ref_2, etc.) for use with other tools
- Element properties, text content, and hierarchy
**Best Practices:**
- Use when screenshot-based clicking might be imprecise
- Get element references before using form_input or computer tools
- Use smaller depth values if output is too large
- Filter for "interactive" when only interested in clickable elements
### find
**Purpose:** Search for elements using natural language descriptions
**Parameters:**
- tab_id (required): Browser tab to search in
- query (required): Natural language description of what to find (e.g., "search bar", "add to cart button")
**Returns:**
- Up to 20 matching elements with references and coordinates
- Element references can be used with other tools
**Best Practices:**
- Use when elements aren't visible in current screenshot
- Provide specific, descriptive queries
- Use after read_page if that tool's output is incomplete
- Returns both references and coordinates for flexibility
### form_input
**Purpose:** Set values in form elements (text inputs, dropdowns, checkboxes)
**Parameters:**
- tab_id (required): Browser tab containing the form
- ref (required): Element reference from read_page (e.g., "ref_1")
- value: The value to set (string for text, boolean for checkboxes)
**Usage:**
- Set text: form_input(ref="ref_5", value="example text", tab_id=123)
- Check checkbox: form_input(ref="ref_8", value=True, tab_id=123)
- Select dropdown: form_input(ref="ref_12", value="Option Text", tab_id=123)
**Best Practices:**
- Always get element ref from read_page first
- Use for form completion to ensure accuracy
- Can handle multiple field updates in sequence
### get_page_text
**Purpose:** Extract raw text content from the page
**Parameters:**
- tab_id (required): Browser tab to extract text from
**Returns:**
- Plain text content without HTML formatting
- Prioritizes article/main content
**Best Practices:**
- Use for reading long articles or text-heavy pages
- Combines with other tools for comprehensive page analysis
- Good for infinite scroll pages - use with "max" scroll to load all content
### search_web
**Purpose:** Search the web for current and factual information
**Parameters:**
- queries: Array of keyword-based search queries (max 3 per call)
**Returns:**
- Search results with titles, URLs, and content snippets
- Results include ID fields for citation
**Best Practices:**
- Use short, keyword-focused queries
- Maximum 3 queries per call for efficiency
- Break multi-entity questions into separate queries
- Do NOT use for Google.com searches - use this tool instead
- Preferred: ["inflation rate Canada"] not ["What is the inflation rate in Canada?"]
### tabs_create
**Purpose:** Create new browser tabs
**Parameters:**
- url (optional): Starting URL for new tab (default: about:blank)
**Returns:**
- New tab ID for use with other tools
**Best Practices:**
- Use for parallel work on multiple tasks
- Can create multiple tabs in sequence
- Each tab maintains its own state
- Always check tab context after creation
### todo_write
**Purpose:** Create and manage task lists
**Parameters:**
- todos: Array of todo items with:
- content: Imperative form ("Run tests", "Build project")
- status: "pending", "in_progress", or "completed"
- active_form: Present continuous form ("Running tests")
**Best Practices:**
- Use for tracking progress on complex tasks
- Mark tasks as completed immediately when done
- Update frequently to show progress
- Helps demonstrate thoroughness
## Tool Calling Best Practices
### Proper Parameter Usage
- ALWAYS include tab_id when required by the tool
- Provide parameters in correct order
- Use JSON format for complex parameters
- Double-check parameter names match tool specifications
### Efficiency Strategies
- Combine multiple actions in single computer call (click, type, key)
- Use read_page before clicking for more precise targeting
- Avoid repeated screenshots when tools provide same data
- Use find tool when elements not in latest screenshot
- Batch form inputs when completing multiple fields
### Error Recovery
- Take screenshot after failed action
- Re-fetch element references if page changed
- Verify tab_id still exists
- Adjust coordinates if elements moved
- Use different tool approach if first attempt fails
### Coordination Between Tools
- read_page get element refs (ref_1, ref_2)
- computer (click with ref) interact with element
- form_input (with ref) set form values
- get_page_text extract content after navigation
- navigate load new pages before other interactions
## Common Tool Sequences
**Navigating and Reading:**
1. navigate to URL
2. wait for page load
3. screenshot to see current state
4. get_page_text or read_page to extract content
**Form Completion:**
1. navigate to form page
2. read_page to get form field references
3. form_input for each field (with values)
4. find or read_page to locate submit button
5. computer left_click to submit
**Web Search:**
1. search_web with relevant queries
2. navigate to promising results
3. get_page_text or read_page to verify information
4. Extract and synthesize findings
**Element Clicking:**
1. screenshot to see page
2. Option A: Use coordinates from screenshot with computer left_click
3. Option B: read_page for references, then computer left_click with ref
</tools>

View File

@@ -0,0 +1,65 @@
# Credit: [Aider-ai](https://github.com/Aider-AI/aider/)
#
# Prompts found at aider/aider/prompts.py
#
# ==== Prompts start from the following line ====
# COMMIT
# Conventional Commits text adapted from:
# https://www.conventionalcommits.org/en/v1.0.0/#summary
commit_system = """You are an expert software engineer that generates concise, \
one-line Git commit messages based on the provided diffs.
Review the provided context and diffs which are about to be committed to a git repo.
Review the diffs carefully.
Generate a one-line commit message for those changes.
The commit message should be structured as follows: <type>: <description>
Use these for <type>: fix, feat, build, chore, ci, docs, style, refactor, perf, test
Ensure the commit message:
- Starts with the appropriate prefix.
- Is in the imperative mood (e.g., \"add feature\" not \"added feature\" or \"adding feature\").
- Does not exceed 72 characters.
Reply only with the one-line commit message, without any additional text, explanations, \
or line breaks.
"""
# COMMANDS
undo_command_reply = (
"I did `git reset --hard HEAD~1` to discard the last edits. Please wait for further"
" instructions before attempting that change again. Feel free to ask relevant questions about"
" why the changes were reverted."
)
added_files = (
"I added these files to the chat: {fnames}\nLet me know if there are others we should add."
)
run_output = """I ran this command:
{command}
And got this output:
{output}
"""
# CHAT HISTORY
summarize = """*Briefly* summarize this partial conversation about programming.
Include less detail about older parts and more detail about the most recent messages.
Start a new paragraph every time the topic changes!
This is only part of a longer conversation so *DO NOT* conclude the summary with language like "Finally, ...". Because the conversation continues after the summary.
The summary *MUST* include the function names, libraries, packages that are being discussed.
The summary *MUST* include the filenames that are being referenced by the assistant inside the ```...``` fenced code blocks!
The summaries *MUST NOT* include ```...``` fenced code blocks!
Phrase the summary with the USER in first person, telling the ASSISTANT about the conversation.
Write *as* the user.
The user should refer to the assistant as *you*.
Start the summary with "I asked you...".
"""
summary_prefix = "I spoke to you previously about a number of things.\n"

View File

@@ -1,21 +1,3 @@
<p align="center">
<sub>Thanks to</sub>
</p>
<p align="center">
<a href="https://github.com/latitude-dev/latitude-llm">
<img src="assets/latitude-dark.png" alt="Latitude Logo" width="700"/>
</a>
</p>
<div align="center" markdown="1">
### [Issue Tracking for AI Agents](https://github.com/latitude-dev/latitude-llm)
[Open Source Monitoring platform](https://github.com/latitude-dev/latitude-llm)
</div>
---
<p align="center">
Support my work here:
<a href="https://bags.fm/DEffWzJyaFRNyA4ogUox631hfHuv3KLeCcpBh2ipBAGS">Bags.fm</a> •
@@ -26,6 +8,41 @@
<p align="center">Official CA: DEffWzJyaFRNyA4ogUox631hfHuv3KLeCcpBh2ipBAGS (on Solana)</p>
---
<p align="center">
<sub>Special thanks to</sub>
</p>
<table width="100%">
<tr>
<td align="center" valign="top">
<a href="https://www.tembo.io/?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship#gh-light-mode-only" target="_blank">
<img src="assets/tembo-dark.png#gh-light-mode-only" alt="Tembo Logo" width="750" height="210"/>
</a>
<a href="https://www.tembo.io/?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship#gh-dark-mode-only" target="_blank">
<img src="assets/tembo-light.png#gh-dark-mode-only" alt="Tembo Logo" width="750" height="210"/>
</a>
<br><br>
<strong><a href="https://www.tembo.io/?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship" target="_blank">Put any coding agent to work while you sleep</a></strong>
<br>
<a href="https://www.tembo.io/?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship" target="_blank">Tembo The Background Coding Agents Company</a>
<br><br>
<a href="https://www.tembo.io/?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship" target="_blank">[Get started for free]</a>
</td>
<td align="center" valign="top">
<a href="https://latitude.so/developers?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship" target="_blank">
<img src="assets/Latitude_logo.png" alt="Latitude Logo" width="750" height="210"/>
</a>
<br><br>
<strong><a href="https://latitude.so/developers?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship" target="_blank">Make your LLM predictable in production</a></strong>
<br>
<a href="https://latitude.so/developers?utm_source=github&utm_medium=readme&utm_campaign=prompt_repo_sponsorship" target="_blank">Open Source AI Engineering Platform</a>
<br><br>
&nbsp;
</td>
</tr>
</table>
---
<a href="https://discord.gg/NwzrWErdMU" target="_blank">
@@ -35,13 +52,15 @@
<a href="https://trendshift.io/repositories/14084" target="_blank"><img src="https://trendshift.io/api/badge/repositories/14084" alt="x1xhlol%2Fsystem-prompts-and-models-of-ai-tools | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
📜 Over **30,000+ lines** of insights into their structure and functionality.
[![Build Status](https://app.cloudback.it/badge/x1xhlol/system-prompts-and-models-of-ai-tools)](https://cloudback.it)
[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/x1xhlol/system-prompts-and-models-of-ai-tools)
---
## Support the Project
## ❤️ Support the Project
If you find this collection valuable and appreciate the effort involved in obtaining and sharing these insights, please consider supporting the project.
@@ -54,16 +73,7 @@ You can show your support via:
- **Patreon:** https://patreon.com/lucknite
- **Ko-fi:** https://ko-fi.com/lucknite
Thank you for your support!
---
## Security Notice for AI Startups
> **Warning:** If you're an AI startup, make sure your data is secure. Exposed prompts or AI models can easily become a target for hackers.
> **Important:** Interested in securing your AI systems?
> Check out **[ZeroLeaks](https://zeroleaks.ai/)**, a service designed to help startups **identify and secure** prompt injection and system prompt extraction risks.
🙏 Thank you for your support!
---
@@ -71,26 +81,36 @@ Thank you for your support!
Sponsor the most comprehensive repository of AI system prompts and reach thousands of developers.
[Get Started](mailto:lucknitelol@pm.me)
[Get Started](mailto:lucknitelol@proton.me)
---
## Roadmap & Feedback
## 🛠 Roadmap & Feedback
> Open an issue.
> **Latest Update:** 08/03/2026
> **Latest Update:** 08/01/2026
---
## Connect With Me
## 🔗 Connect With Me
- **X:** [NotLucknite](https://x.com/NotLucknite)
- **Discord**: `x1xhlol`
- **Email**: `lucknitelol@pm.me`
---
## Star History
## 🛡️ Security Notice for AI Startups
> ⚠️ **Warning:** If you're an AI startup, make sure your data is secure. Exposed prompts or AI models can easily become a target for hackers.
> 🔐 **Important:** Interested in securing your AI systems?
> Check out **[ZeroLeaks](https://zeroleaks.ai/)**, a service designed to help startups **identify and secure** leaks in system instructions, internal tools, and model configurations. **Get a free AI security audit** to ensure your AI is protected from vulnerabilities.
---
## 📊 Star History
<a href="https://www.star-history.com/#x1xhlol/system-prompts-and-models-of-ai-tools&Date">
<picture>
@@ -100,4 +120,4 @@ Sponsor the most comprehensive repository of AI system prompts and reach thousan
</picture>
</a>
**Drop a star if you find this useful!**
**Drop a star if you find this useful!**

BIN
assets/Latitude_logo.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 7.6 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

File diff suppressed because it is too large Load Diff