FDEOps

# AGENTS.md - working in the fdeops repository

This repository **is** FDEOps: skills that help Forward Deployed Engineers work across strategy, architecture and engineering through AI coding agents. All 35 task skills work individually; `fde` coordinates them for ongoing customer work. Local `.fde/` records support continuity between sessions; users confirm consequential judgments.

## If you are helping use fdeops in an engagement

For ongoing customer work, use **`@fde`**: read `skills/fde/SKILL.md`, select the relevant instructions, and follow its record rules. When the user selects a task such as `discover` or `build`, run that task directly with the supplied context; a customer record is optional. Do not make users choose a task when they have asked the coordinator for help. Other tools use thin pointer files in [`adapters/`](adapters/README.md).

## If you are contributing to this repository

- **One brain.** Method lives once in `skills/fde/SKILL.md` + `skills/fde/references/`. Adapters in `adapters/` only point at it - never fork logic per platform. Standalone skills are generated by `node bin/generate-skills.js` from `bin/skill-catalog.js` and canonical references; do not hand-edit generated copies.
- **Deterministic core.** `bin/fde.js` is local-only (git + file reads, no network, no AI). Keep it that way.
- **Run the checks.** `npm run check` must pass before any PR (`node bin/check.js`).
- **Conventions.** See `CONTRIBUTING.md`, `docs/REPO_LAYOUT.md`, and `docs/schema.md`.

## Boundaries

The `fde` CLI never reaches the network. `<private>` blocks are redacted from CLI/dashboard/hook outputs; do not load raw private blocks into a model via file tools or paste. fdeops installs on the FDE's own machine, never on customer infrastructure.

More agent context in suboss87/FDEOps

38 other files this repository gives its agents.