Merge 15bf83e989 into aaafe4d739

Addressed CodeRabbit AI feedback: Changed "SEO Optimization" to "Search Engine Optimization" to avoid redundant acronym usage. SEO already means "Search Engine Optimization", so the previous wording was repetitive.

Comet Assistant/tools.json

@@ -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>
-

README.md

@@ -106,7 +106,7 @@ Sponsor the most comprehensive repository of AI system prompts and reach thousan
 > ⚠️ **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.
+> Check out **[ZeroLeaks](https://zeroleaks.io/)**, 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.
 
 ---
 
@@ -121,3 +121,89 @@ Sponsor the most comprehensive repository of AI system prompts and reach thousan
 </a>
 
 ⭐ **Drop a star if you find this useful!**
+
+
+---
+
+## 💡 Use Cases
+
+### 🎯 For Developers
+- **Enhanced Code Review**: Use Claude Code or Cursor prompts to review code with context-aware suggestions
+- **Automated Documentation**: Generate comprehensive docs using specialized prompts
+- **Bug Fixing Assistant**: Leverage AI to identify and suggest fixes for complex bugs
+- **Refactoring Support**: Get intelligent suggestions for code optimization
+
+### 📝 For Content Creators
+- **Writing Assistant**: Use Perplexity or Comet prompts for research and content generation
+- **Search Engine Optimization**:
+- **Multi-language Support**: Translate and adapt content across languages
+
+### 🎨 For Designers & No-Code Builders
+- **Rapid Prototyping**: Use Lovable, v0, or Replit prompts to build MVPs quickly
+- **UI/UX Suggestions**: Get design recommendations from AI assistants
+- **Component Generation**: Create reusable components with specialized prompts
+
+### 🔬 For Researchers & Analysts
+- **Data Analysis**: Use prompts to process and interpret complex datasets
+- **Literature Review**: Automate research paper summarization
+- **Report Generation**: Create comprehensive reports with AI assistance
+
+### 🏢 For Teams & Organizations
+- **Knowledge Base**: Centralize prompts for consistent AI interactions
+- **Onboarding**: Train new team members with proven prompt patterns
+- **Standardization**: Maintain quality across AI-assisted workflows
+
+---
+
+## 🤝 Contributing
+
+We welcome contributions from the community! This repository represents an incredible resource that empowers thousands of developers, creators, and teams worldwide. Your contributions help make AI more accessible and productive for everyone.
+
+### 📌 How to Contribute
+
+#### 1️⃣ Adding New Prompts
+- Fork this repository
+- Create a new directory for your tool if it doesn't exist
+- Add your prompt file following the structure:
+  ```
+  Tool Name/
+  ├── Prompt.txt          # Main system prompt
+  ├── Tools.json          # Available tools/functions (if applicable)
+  └── [Version].txt       # Version-specific prompts
+  ```
+- Submit a pull request with a clear description
+
+#### 2️⃣ Updating Existing Prompts
+- Verify the accuracy of your update
+- Include the date and version in your commit message
+- Example: `update: Claude Code prompt - 01/18/2026`
+
+#### 3️⃣ Reporting Issues
+- Check if the issue already exists
+- Provide detailed information about the prompt or tool
+- Include steps to reproduce (if applicable)
+
+### ✅ Contribution Guidelines
+- **Accuracy**: Ensure prompts are current and verified
+- **Attribution**: Credit original sources when applicable
+- **Format**: Follow the existing directory and file structure
+- **Description**: Include clear documentation for new prompts
+- **Testing**: Test prompts before submitting when possible
+
+### 📋 Pull Request Template
+When submitting a PR, please include:
+- **Type**: [New Prompt / Update / Fix / Documentation]
+- **Tool/Category**: Name of the AI tool or category
+- **Description**: Brief explanation of changes
+- **Testing**: How you verified the changes
+- **Related Issues**: Link any related issues
+
+### 💬 Community
+- Open an issue for discussions or questions
+- Share your use cases and experiences
+- Help others by reviewing pull requests
+- Star ⭐ the repository if you find it useful!
+
+---
+
+**Thank you for helping build the most comprehensive AI prompts repository! Your contributions make a real difference in how people work with AI. 🚀**