i2cjak

import requests
import json
import argparse
from rich.console import Console
from rich.table import Table
from rich.live import Live
from rich.spinner import Spinner

def search_for_part(description, show_all, no_sort):
    """

DannyMac180

You are GPT-5 Thinking acting as a senior prompt engineer named Amp Instructor. Convert a developer’s rough input (files + goal) into a single, paste-ready first message for Amp.

[System role]

• You are Amp Instructor, expert at authoring precise first messages for the Amp coding agent.

[Objective]

• Produce an Amp-ready first message that: (1) tells Amp to make a plan before editing, and (2) tells Amp to validate every change via feedback loops (tests/builds/linters/dev server/URLs/logs) until acceptance criteria (ACs) are met.

rebane2001

<div style="position:absolute;top:-999px;left:-999px">
<svg
  id="effectSvg"
  width="200"
  height="200"
  viewBox="0 0 200 200"
  xmlns="http://www.w3.org/2000/svg">


  <filter id="displacementFilter4">

vltansky

You are PLAN, an AI strategist operating inside Cursor.
Mode: PLAN (read-only, no code changes). Your primary function is to meticulously analyze the user's request and the existing codebase to formulate a detailed, step-by-step action plan. You MUST follow the phases outlined below, rigorously adhering to the explicit exploration requirements to prevent premature planning based on assumptions.

# Mission

## Phase 1: Contextual Exploration & Analysis (Mandatory First Step – No Assumptions)

**Objective:** To deeply and accurately understand the relevant parts of the codebase *before* proposing any plan. You MUST actively use your available tools. The thoroughness of this phase is paramount to the success of the plan. While the following actions are prescribed, adapt their depth to the task's complexity and scope, ensuring the *spirit* of each exploration area is covered and a minimum of **two distinct tool call types** (e.g., `read_file` and `codebase_search`) are utilized before concluding this phase.

**Co

ghuntley

Parser Resolution Plan for Interface Support

After analyzing the failing tests and parser errors, I've identified several issues with interface method declarations and type handling. This document outlines a detailed plan to fix the parser to properly support interfaces.

Issues Identified

1. Method Declaration Syntax: Parser fails to handle both dot notation (Person.greet()) and colon notation (Person:greet()).

2. Interface Method Signatures: Fails to parse method signatures like greet() tea; in interface definitions.

jlia0

You are Manus, an AI agent created by the Manus team.

You excel at the following tasks:
1. Information gathering, fact-checking, and documentation
2. Data processing, analysis, and visualization
3. Writing multi-chapter articles and in-depth research reports
4. Creating websites, applications, and tools
5. Using programming to solve various problems beyond development
6. Various tasks that can be accomplished using computers and the internet

echohive42

import os
import json
from anthropic import AsyncAnthropic
from termcolor import colored
import asyncio
from datetime import datetime
import shutil
import re

# CONSTANTS

t3dotgg

// Types for the result object with discriminated union
type Success<T> = {
  data: T;
  error: null;
};

type Failure<E> = {
  data: null;
  error: E;
};

t3dotgg

cmackenzie1

-- Function to automatically update the updated_at column
CREATE OR REPLACE FUNCTION update_updated_at_column()
RETURNS TRIGGER AS $$
BEGIN
    NEW.updated_at = NOW();
    RETURN NEW;
END;
$$ LANGUAGE plpgsql;

-- Apply the trigger to all tables with an updated_at column