Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
**YOUR TASK: audit one anyplot specification and either improve it or report NOOP.** You are running autonomously inside the `daily-regen` pre-flight job. There is no human in the loop during this run — the user will review your output later as a pull request.
You are an experienced, pragmatic software engineer. You don't over-engineer a solution when a simple one is possible. Rule #1: If you want exception to ANY rule, YOU MUST STOP and get explicit permission from Denis first. BREAKING THE LETTER OR SPIRIT OF THE RULES IS FAILURE.
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. The app is **Dovetail**, a native desktop text editor written in Rust. Linux (tiling Wayland setups like Hyprland) comes first, and it also builds and runs on macOS and Windows: a change
Drydock is a per-host daemon that owns AI-CLI PTYs (`claude`, plain shells) plus a Vue 3 + xterm.js web shell that attaches to them. Sessions survive disconnects because the daemon — not any client — holds the PTY master. See README.md for
Self-hosted real estate platform for an Oregon investment and development team. **The repo holds two products.** They share infrastructure, a database, and auth; they do not share code. Know which one you are working on before you edit.
This folder is where Hidden Gem Media's SOPs are written, revised and published. It replaces the "HGM SOP Studio" Claude Project. Everything that Project knew is here: the house style, the two skills, the masters, and the rules below.
HTML/Eta templates rendered server-side (via `api-cloudrun`) into PDFs using Gotenberg. **Git-canonical — for PUBLISHED content.** Git is the source of truth for published template *content*; the Firestore family doc + `published` versions are a rebuildable projection of it. This repo is the canonical content store and an ad-hoc local-dev/preview harness; the production editing surface lives in `manager/`.
Read this file fully at the start of every session. The detailed feature specification is `docs/spec.md`. **The spec is the source of truth for features.** This file is the source of truth for stack, security and engineering rules. If they disagree, point out the conflict and ask. If something is unclear or missing in both, ask before guessing. Never invent requirements.
Guidance for AI agents working in the **Shopsys Platform monorepo**. This file is a signpost: it carries the architecture and always-on rules inline, and links to skills in `.agents/skills/` for the detail. The skills are plain Markdown — follow the links whether or not your agent supports a "skills" mechanism.
`iprange` is FireHOL's high-performance IP range manipulation tool, written in C (`src/`, autotools + CMake builds; CLI binary `iprange`). It is used by `update-ipsets` for set operations (union, intersect, exclude, dedup, compare)
If you are an AI agent preparing a pull request, follow `CONTRIBUTING.md § Contribution quality bar`. In short: accepted issue, do not open the pull request; comment on the issue instead. Manual testing: steps a person ran by hand against a mostrod, with