# llm-tools

> **A phonebook for AI agents.** This repository exists so that Codex, Claude, Cursor, and any other LLM-based tool can orient themselves quickly in Jacob Mathison's development environment — without having to ask, guess, or explore blindly.

---

## What Is This?

When an AI agent starts working in this codebase, it often needs to answer basic questions:

- Where is the git server?
- What AWS account am I working in, and what's deployed?
- How do I authenticate?
- What other machines and services exist on the network?
- What projects are active?

This repo answers all of those questions. Think of it as a rolodex — structured reference docs, one per surface, that any LLM can read and immediately act on.

---

## Files

| File | What it covers |
|------|---------------|
| [`llm.txt`](./llm.txt) | Plain-text overview of this repo and the environment |
| [`manifest.json`](./manifest.json) | Machine-readable index: repos, CI, machines, conventions |
| [`gitea.llm.md`](./gitea.llm.md) | Local Gitea instance — clone URLs, PAT auth, API examples |
| [`aws-cli.llm.md`](./aws-cli.llm.md) | AWS account — profiles, S3, Amplify, CloudFront, Lambda |

---

## Quick Start for an AI Agent

**1. Check your network access**
```bash
curl -s http://100.79.253.19:3000/api/v1/version   # Gitea — expect {"version":"1.26.2"}
aws sts get-caller-identity                         # AWS — expect account 567637986724
```

**2. Clone something**
```bash
# Any repo on the local Gitea (Tailscale required):
git clone http://100.79.253.19:3000/jacob-mathison/<repo>.git

# This repo itself:
git clone http://100.79.253.19:3000/jacob-mathison/llm-tools.git
```

**3. Read the guide for whatever surface you need**

Working with source control → [`gitea.llm.md`](./gitea.llm.md)
Working with AWS → [`aws-cli.llm.md`](./aws-cli.llm.md)

---

## Environment at a Glance

| Surface | Detail |
|---------|--------|
| **AWS Account** | `567637986724` — IAM user `jacob_mathison` (AdministratorAccess) |
| **AWS Default Region** | `us-east-1` |
| **AWS Profiles** | `default`, `mp-mac-tabitha` |
| **Gitea** | `http://100.79.253.19:3000` (Tailscale) |
| **CI Runner** | `orson-runner` — act_runner v0.6.1, host mode, Node 24 on Orson |
| **Primary dev machine** | `Tabitha` (MacBook Pro arm64, `100.76.192.116`) |
| **Gitea host** | `Orson` (Mac mini, `100.79.253.19`) |

---

## Conventions

- **Commits:** [Conventional Commits](https://www.conventionalcommits.org/) — `feat:`, `fix:`, `ci:`, `docs:`, `chore:`
- **Default branch:** `main`
- **Node (CI):** 20.x LTS
- **Package manager:** `npm`
- **IaC:** AWS Amplify Gen 2 for most frontend projects

---

## Keeping This Up to Date

When you (a human or an AI agent) add a new service, machine, or repo, update the relevant file and push. The `manifest.json` especially should reflect the live state of the Gitea repo list.

```bash
cd /Volumes/Hagia/workspaces/workspace_Father/llm-tools
# edit the file(s)
git add .
git commit -m "docs: update <file> with <change>"
git push
```

---

*Maintained by [Jacob Mathison](mailto:jacob@mathisonprojects.com) · [Mathison Projects Inc](https://www.mathisonprojectsinc.com)*