Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
Follow `/CLAUDE.md` first. This repository uses `.github/` as the canonical instruction system. Do not create or follow a separate competing rule set inside `.claude/`. Always read the feature/module markdown closest to the code you are changing.
Inspect first, make the smallest useful change, verify it, and summarize the evidence. Follow the project's existing conventions. Act on safe, reversible work; ask when blocked, destructive, or security-sensitive. Keep replies concise.
> Source: https://github.com/yldray/vibe-check When the user says **"vibe check"**, **"pre-launch check"** or asks if the project is ready to ship, run this audit. If the user says **"quick vibe check"**, run **Quick mode** instead of Steps 2–3:
> You (Claude Code, "cc") are the autonomous builder **and** the project manager > for this repository. You administer **beans** (the issue tracker) at the > milestone/epic level and drive **OpenSpec** for every unit of work inside an
**All** changes to files in this repository -- source, tests, `README.md`, `CLAUDE.md`, `scripts/`, `pyproject.toml`, configuration, anything tracked or untracked -- must be shown to the user as a diff and approved by them **before**
Docker + k3s homelab managed with Ansible. ~50 containerized services deployed across three hosts via infrastructure-as-code, the k3s migration **completed 2026-08-14** — `docs/archive/k3s-migration/` is now a historical record of executed work, not a plan. Docker survives only on `daniel-pi`. (Exact count, and the per-service host/route/auth/backup/auto-deploy facts: `docs/reference/services.md`, regenerated by the `docs-refresh` cron and browsable at `docs.local.<domain>`. Don't hand-maintain
Hide as the furniture. Most players are props, who look at something on the map and become it; the rest are hunters, blindfolded while the props hide and then given a few minutes to find them, paying in health for every piece of real furniture they shoot.
You are rebuilding **Sketch Oversight** (UIST 2026, Monterio / Koey / Das) as a cross-platform desktop app (macOS, Windows, Linux) that a user can install with no setup beyond a first-run wizard. The agent works on its own desk on
A personal Pokémon Nuzlocke run tracker. Web app first, installable mobile app later. Single user — there is no multi-user story and no plan for one. **Status: M0 in progress.** Scaffolded and building — Vite/React/TS, Tailwind, shadcn/ui, and
> App: Holy Auramaxing (one spelling in everything people see, D-059; the repo, folders and Supabase project id keep the old "holy-auramaxxxing"). Domain: not chosen yet (set `NEXT_PUBLIC_SITE_URL`). Supabase region: Mumbai (`ap-south-1`). AI coding tools re-read this file every session. Run the phase prompts in `PROMPTS.md` one at a time.
> **How this file is used:** Place this file at the root of the student's semester-project folder as `CLAUDE.md` (or paste it as the first message of an empty Claude Code session). It is the complete, self-contained context for the lab. The original handouts (lab activity docx + three instructor PDFs) are NOT available in the session; everything needed from them is reproduced below.
You are an experienced mineralogist spanning systematic mineralogy, crystallography, economic and environmental mineral characterization, museum/collection curation, and IMA-CNMNC new-mineral work. You reason from crystal chemistry, structure, optical