agentleFS
Sign inStart free
jdiejimjdiejim/chiltepin/.github/copilot-instructions.md

chiltepin

Copilot instructions4 starsChanged 49 days agoMITView on GitHub

This project uses Chiltepin: documentation-as-code where a doc is Markdown with typed, fenced YAML blocks, and the files on disk are the single source of truth. When creating or changing any document under docs/*/.md, follow the authoring skill at skills/chiltepin/SKILL.md. It defines the block grammar and the doc#id reference scheme; run node packages/cli/dist/bin.js block <type> for any block's fields and an example. In short: - Prose is plain Markdown; structure goes in typed blocks (e.g. sequence, erd, table, callout, c4,…

We split this copilot-instructions.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When creating or changing any document under docs//*.md, follow the authoring skill at skills/chiltepin/SKILL.md.

    line 8
  2. Distinctive:

    Use only the documented block types and their documented fields — the schemas are strict, so an unknown block or field fails validation.

    line 16
  3. Very specific:

    Run chiltepin check and fix all diagnostics before finishing.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md
<!-- Repo location: .github/copilot-instructions.md — GitHub Copilot reads this automatically. -->

Chiltepin — authoring guide

This project uses Chiltepin: documentation-as-code where a doc is Markdown with typed, fenced YAML blocks, and the files on disk are the single source of truth.

When creating or changing any document under docs/**/*.md, follow the authoring skill at skills/chiltepin/SKILL.md. It defines the block grammar and the doc#id reference scheme; run node packages/cli/dist/bin.js block <type> for any block's fields and an example. In short:

  • Prose is plain Markdown; structure goes in typed blocks (e.g. sequence, erd, table, callout, c4, flow, timeline, userstory). Never paste raw HTML or inline SVG.
  • Use only the documented block types and their documented fields — the schemas are strict, so an unknown block or field fails validation. Bodies are YAML.
  • Give a block an id: when it needs to be referenced; reference it as doc#id.
  • Edit the specific block surgically — don't regenerate whole files.
  • Run chiltepin check and fix all diagnostics before finishing. A change isn't done until it passes.

Download now (ZIP)

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository3 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free