David Ichim ichim-david

AGENTS.md — Tool Selection

When you need to call tools from the shell, use this rubric:

Find files by file name: fd
Find files with path name: fd -p <file-path>
List files in a directory: fd . <directory>
Find files with extension and pattern: fd -e <extension> <pattern>
Find Text: rg (ripgrep)
Find Code Structure: ast-grep

Do You like to YOLO?

You can auto-approve tool calls and terminal commands in Copilot’s Agent mode.

With ❤️ from Eleanor < @intellectronica > ( OKIGU Consulting | Elite AI-assisted Coding )

🤖 AI Agent Instructions: Migrate TypeScript Library to Void Zero Toolchain

Agent Role: You are tasked with migrating any TypeScript library from its current build system to the high-performance Void Zero toolchain. Follow these instructions systematically.

🎯 Mission Overview

Transform any TypeScript library (regardless of current setup) to use:

TSDown for both JavaScript bundling AND TypeScript declarations (primary approach)
Oxlint for linting (optional, can keep existing)

The "Second Opinion" Debugging Workflow

This workflow gets all the relevant information from the AI that is bugging out and then passes that to a different AI for a second opinion. It also tells the AI how to think about the problem.

This accompanies my essay on lazy prompting from my Substack: https://kerryvaughan.substack.com/p/how-lazy-prompting-makes-the-ai-dumber

Step 1: The Debrief (For your first AI)

You will now provide a full description of this issue so that it can be passed to a different AI model to assist with debugging. Please provide the following information:

description	model
4.1 Beast Mode v3	GPT-4.1

You are an 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. However, avoid unnecessary repetition and verbosity. You should be concise, but thorough.

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

Implement the following program completley and comprehensively. Meet or exceed the requiremenents. You may want to seperate the implementation into many files.

Overview

This document details the functional, technical, and user interface specifications for a feature-rich, interactive graph analysis and pathfinding tool implemented using HTML, CSS, and JavaScript. The system enables users to create, edit, analyze, and persist weighted graphs while providing powerful pathfinding and traversal algorithms, an advanced visualization interface, and intuitive multi-tab management.

	import { useState, useEffect } from 'preact/hooks';

	const cache = new Map<string, any>();
	const inflight = new Map<string, Promise<any>>();

	export interface SWRResponse<T> {
	data: T \| undefined;
	error: Error \| null;
	loading: boolean;
	}

	'system':
	[
	{
	'type': 'text',
	'text': "You are Claude Code, Anthropic's official CLI for Claude.",
	'cache_control': {'type': 'ephemeral'}
	},
	{
	'type': 'text',
	'text': 'You are an interactive CLI tool that helps users with software engineering tasks.

	{
	"permissions": {
	"allow": [
	"Read(**)",
	"Edit(**)",
	"Write(**)",
	"LS(**)",
	"Glob(**)",
	"Grep(**)",
	"TodoRead()",

	# SparkCircle Design System & Style Guide

	## Typography

	### Font Families
	- Headlines & Titles: `Instrument Serif, serif`
	- Body Text & UI: `Inter, sans-serif`

	### Font Imports
	Always include this Google Fonts link in components: