Eleanor Berger intellectronica

Default Instructions for Gemini CLI

Useful Command-Line Tools

GitHub

Use the gh command-line to interact with GitHub.

Markdown

Use the glow command-line to present markdown content.

In-Depth Analysis of GitHub Copilot Chat (OSS)

https://github.com/microsoft/vscode-copilot-chat

This report provides a detailed examination of the Visual Studio Code Copilot Chat extension, based on an extensive review of the provided repository source code. It covers the project's architecture, core services, operational modes, and a granular look at the agent functionality.

1. Architectural Overview

The vscode-copilot-chat repository is a sophisticated monorepo that employs modern software engineering principles to deliver a complex AI-powered extension. Its architecture is designed for modularity, testability, and extensibility.

🆕 for more detailed information visit the 🌐Community Guide to Open-Source AI Software Craft - oss-ai-swe.org

At-a-glance

Tool	Stars*	Licence	Default models	What it can do out-of-the-box	Ideal use-case

You are an autonomous agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

Your thinking should be thorough and so it's fine if it's very long. Whenever you need to think more deeply, use the @thinking tool. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.

You MUST iterate and keep going until the problem is solved.

You have everything you need to resolve this problem. I want you to fully solve this autonomously before coming back to me.

Only terminate your turn when you are sure that the problem is solved and all items have been checked off. Go through the problem step by step, and make sure to verify that your changes are correct. NEVER end your turn without having truly and completely solved the problem, and when you say you are going to make a tool call, make sure you ACTUALLY make the tool call, instead of ending your turn.

Default Instructions for Codex CLI

You have useful tools available as MCP or command-line. Use them.
Unless you are absolutely sure that you have correct and, crucially, up-to-date information in your knowledge, always get information from the web. You can use Tavily for searching and getting information, and you can always use curl to fetch web pages.
If you are working on something that presents web pages, you should use Playwright to open these pages, take snapshots, and inspect them.
When working in a git repository, always switch to a new branch, unless explicitly insutrcted not to.
If the git repo has a corresponding repo on GitHub, use the gh tool for things like looking at issues, opening pull requests, reading review comments, and looking at CI results.
If the project has tests you can run locally, always run them and make sure everything works correctly.
If the project has CI tests in GitHub, make sure they run, wait for the results, and fix if needed.

Information Retrieval Flashcars

Leonie Monigatti, one of the best and clearest voices on information retrieval, published this great list of the most essential things to know about information retrieval (that's the "R" in "RAG"): 37 Things I Learned About Information Retrieval in Two Years at a Vector Database Company. It's excellent, go read it.

And because these are things I never want to forget, I created flashcards to add to my collection (using CardCraft). Maybe they will be useful to you too.

	<instructions>
	You write Python tools as single files. They always start with this comment:
	# /// script
	# requires-python = ">=3.12"
	# ///
	These files can include dependencies on libraries such as Click. If they do, those dependencies are included in a list like this one in that same comment (here showing two dependencies):
	# /// script
	# requires-python = ">=3.12"
	# dependencies = [
	# "click",

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>Glassmorphism Calculator</title>
	<!-- Tailwind CSS for styling -->
	<script src="https://cdn.tailwindcss.com"></script>
	<!-- Google Fonts: Inter -->
	<link rel="preconnect" href="https://fonts.googleapis.com">

	// ==UserScript==
	// @name ArtiGist
	// @version 0.5
	// @description Launch single-page HTML apps from GitHub Gists.
	// @author Eleanor Berger <[email protected]> with Gemini CLI
	// @match https://gist.github.com//
	// @match https://gist.githubusercontent.com//
	// @grant GM_xmlhttpRequest
	// @grant GM_openInTab
	// ==/UserScript==