agentleFS
Sign inStart free
IvanGomezMartinezIvanGomezMartinez/MatStudyLab/AGENTS.md

MatStudyLab

AGENTS.md2 starsChanged 3 months agoMITView on GitHub

Private portfolio/template repo for optical lab technicians using AI-assisted MATLAB workflows. Local markdown under .scratch/<feature>/ (wayfinder map and tickets). Implementation PRD at .scratch/matstudylab/PRD.md. See docs/agents/issue-tracker.md. Five canonical roles with default strings (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See docs/agents/triage-labels.md. Single-context repo: CONTEXT.md at root; ADRs in docs/adr/ when created. See docs/agents/domain.md. Installed under .agents/skills/ per skills-lock.json: All five workflow commands (/accept, /explain, /build, /new, /modify) are implemented (T3–T7).

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 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.

  • 5

    Very specific

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

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

    Never edit codes/ in situ.

    line 17
  2. Distinctive:

    Never change units without warning.

    line 19
  3. Very specific:

    All five workflow commands (/accept, /explain, /build, /new, /modify) are implemented (T3–T7).

    line 43
  4. Very specific:

    Read LORE.md (if present).

    line 47
  5. Very specific:

    Read docs/spec.md for the command or area in scope.

    line 48
  6. Very specific:

    Read CONTEXT.md for domain terms.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

MatStudyLab — Agent Instructions

Private portfolio/template repo for optical lab technicians using AI-assisted MATLAB workflows.

Project conventions

  • Technical artifacts (code, specs, skills, this file): English.
  • Companion .md and LORE content: user's preferred language (default Spanish); see LORE.md.
  • Developer communication with Iván: Spanish.
  • Spec contract: docs/spec.md — commands, folders, safety rules, bundle model.
  • Domain glossary: CONTEXT.md — use defined terms; avoid synonyms listed under Avoid.
  • MATLAB baseline: docs/matlab-guidelines.md; LORE.md overrides personal style, never safety rules.
  • Templates: docs/templates/script-companion.md, docs/templates/explain-doc.md, docs/templates/LORE.md.

Safety (non-negotiable)

  • Never edit codes/ in situ. Write only in new/, modify/, explain/.
  • /modify on catalog content: copy to modify/ first.
  • Never change units without warning; never delete/overwrite measurement data; never use unavailable toolboxes.

Agent skills

Issue tracker

Local markdown under .scratch/<feature>/ (wayfinder map and tickets). Implementation PRD at .scratch/matstudylab/PRD.md. See docs/agents/issue-tracker.md.

Triage labels

Five canonical roles with default strings (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See docs/agents/triage-labels.md.

Domain docs

Single-context repo: CONTEXT.md at root; ADRs in docs/adr/ when created. See docs/agents/domain.md.

Vendored skills

Installed under .agents/skills/ per skills-lock.json:

  • Pocock engineering: to-spec, to-tickets, implement, grill-me, writing-great-skills, etc.
  • MATLAB (manual vendoring): matlab, matlab-performance-optimizer — required by /new and /modify; read .agents/skills/matlab/SKILL.md and .agents/skills/matlab-performance-optimizer/SKILL.md
  • matstudylab-bootstrap — not user-facing; runs as Step 0 inside /build, /new, /modify, /accept, /explain

All five workflow commands (/accept, /explain, /build, /new, /modify) are implemented (T3–T7).

Before touching code

  1. Read LORE.md (if present).
  2. Read docs/spec.md for the command or area in scope.
  3. Read CONTEXT.md for domain terms.
  4. For MATLAB generation (/new, /modify): read and apply .agents/skills/matlab/SKILL.md and .agents/skills/matlab-performance-optimizer/SKILL.md (manually vendored; bootstrap auto-sync deferred).

Download now (ZIP)

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