fnl-setup-instructions

Installation
SKILL.md

Set up agent instructions

User-scoped instructions load in every session the user starts, in every repository. Write them as a short working contract: who the user is, how to work with them, what needs their approval, and where the detailed practice lives. Detailed engineering rules stay in the fnl- skills; the contract points to them instead of restating them.

Project-scoped instructions hold only repository-specific build and test commands, conventions, adopted gates and pointers to the fnl- skills. Never repeat the user-scoped contract in them.

Start with one question: "Which scope: user, project, or both?" Add one concrete recommendation: user for a bare invocation or preferences across repositories, project for repository context, both when the request covers both. Wait for the answer before scope-dependent exploration.

The user-contract skeleton and question bank are in references/contract-template.md. File locations and include syntax per host are in references/hosts.md; recheck them against each host's docs before writing.

1. Explore

  • Which hosts the user runs (claude, codex, agy on PATH) and which instruction files already exist in the chosen scope (see hosts.md). Read them as the starting draft; read the user contract for comparison when available, without changing it in project-only mode.
  • Whether the same text is copied into several files (a drift risk this skill will offer to remove).
  • For project scope: the repository root, its documented build and test commands and conventions, existing context files and overrides, and the ## Agent skills block and review-gate adoption line written by fnl-setup. Read and preserve those entries; never duplicate or author them. If either is missing, point to /fnl-setup and leave adoption pending.

A file or command that cannot be checked here is listed as unverified in one line, with a request that the user paste its contents if it exists. Missing permissions are not a reason to stop: the interview needs only the user's answers.

Done when the message lists the files found, their sizes, any duplication and what is unverified, and it ends with the first round of questions, each with a concrete recommended answer. When the hosts are unverified, the round includes which hosts the user runs ("Recommended: Claude Code first, the others later."), and questions that depend on the answer (file locations, host sections, delegation between hosts) wait for the next round.

Installs
2
GitHub Stars
4
First Seen
Nov 3, 2026