004 views
Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
You have context-mode MCP tools available. These rules are NOT optional — they protect your context window from flooding. A single unrouted command can dump 56 KB into context and waste the entire session.
When you are generating code prefer to be concise and to the point. Make comments only if needed. This is a design project for a new unit library in typescript. Please be concise and to the point. Task file name convention is [00<X>-<task-name>].md
This section is installed and maintained by `haft init`. Edits **inside** the haft HTML-comment markers (the start/end pair that brackets this section) will be overwritten on the next `haft init`. Add your own project rules **outside**
**Objective:** To ensure all development activities are driven by and tracked within the `scatterbrain` task management system via MCP. Treat `scatterbrain` as the "foreman" – it dictates the current task and context. **Do not deviate from this protocol.**
Guidance for `web/`. The root `CLAUDE.md` holds the rules that apply to every change; this file holds the ones that only bite here. Sizing conventions are in the root under **Conventions** — this is the reasoning behind them and the traps in measuring them.
**DO NOT add private repositories to `secrets-config.yml` or mention them in any PR, commit message, comment, or documentation in this repository.** This repository is **public**. Any repo name added to `secrets-config.yml` — including in PR
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.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. Longer-form reference lives in [`docs/`](docs/README.md): [architecture](docs/architecture.md) (the system in diagrams), [viral-loop](docs/viral-loop.md) (the loop and how to read `npm run stats`), [operations](docs/operations.md) (deploys and what to do when something breaks), and [decisions](docs/decisions.md) (why it is like this, and what was rejected). This file stays the place for invaria
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