steipete

• Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
• Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
• NEVER edit .env or any environment variable files—only the user may change them.
• Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
• Moving/renaming and restoring files is allowed.
• ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

faabian

"""
Quick and dirty replication of
"Winning Gold at IMO 2025 with a Model-Agnostic Verification-and-Refinement Pipeline" (https://arxiv.org/abs/2507.15855)
using LangGraph.

Export GOOGLE_API_KEY to run.
Change the model, question and constants directly in the code (no CLI).
"""

import asyncio

dctmfoo

AGENTS.md - Essential Briefing for AI Agents

For human contributors: See README.md for getting started guide.

---

🤖 THE 3-ENTITY WORKFLOW (CORE CONCEPT)

This project uses a 3-entity collaboration pattern between Human, Droid Assistant, and Droid Exec.

chandika

Executive Summary

This guide documents how to use Factory's Droid CLI with your Claude Code Max subscription (OAuth authentication) instead of pay-per-token API keys. The solution leverages CLIProxyAPI as a transparent authentication proxy that converts API key requests from Factory CLI into OAuth-authenticated requests for Anthropic's API.

Architecture Overview

Factory CLI → [Anthropic Format + API Key] → CLIProxyAPI → [Anthropic Format + OAuth] → Anthropic API
                                                  ↓
 (Auth Header Swap)

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