agentleFS
expoexpo/exact/.claude/skills/llp-orient/SKILL.md

llp-orient

Skill4.3k starsChanged 3 days agoMITView on GitHub

Before editing a subsystem, file, or starting a task, assemble the governing LLP context — read the root LLP, follow the @ref annotations on the code in scope, and find the LLPs covering the relevant systems. Produces a compact context pack of the constraints a change must respect. Read-only.

2 other projects use a version of this, 1 of them edited.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 19 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the expo/exact repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about expo/exact

The biggest 5 of 19 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 19

Talked about on GitHub, Bluesky and Hacker News (19 times).

On GitHub · 11

6 more on GitHub

On Bluesky · 6

1 more on Bluesky

On Hacker News · 2

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. expo/expo-device-hub★ 285100% same

    Edited · 1

    1. peterpme/skills★ 2893% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start of a coding task that touches an area with documented design.

    line 18
  2. Distinctive:

    MUST be read-only: never edit code or LLP documents.

    line 22
  3. Distinctive:

    MUST scope to the task: pull the constraints that bind this change, not a corpus summary.

    line 23
  4. Very specific:

    MUST cite, not restate: reference policy as LLP NNNN#anchor rather than paraphrasing sections.

    line 24
  5. Distinctive:

    MUST NOT invent constraints.

    line 25
  6. Very specific:

    MUST NOT guess the rationale behind a broken @ref — report it and hand off to llp-maintain.

    line 26
  7. Distinctive:

    Likely doc updates: if the change lands

    line 41
  8. Very specific:

    No corpus (llp/ missing or stub) → llp-adopt.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

llp-orient

<!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0008-distributed-agent-skills.rfc.md#the-skills--core-five-plus-flags — skill contract --><!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0000-linked-literate-programming.explainer.md#2-reference-syntax — the grammar this reads -->

Load the design rationale governing the area you're about to touch, before touching it. This is the consumption side of LLP — orienting first is what turns @ref from a possibility into a habit.

Invoke as /llp-orient <path-or-task> (file, directory, subsystem, or task description). With no argument, use the current change scope (git diff --name-only).

Trigger

Start of a coding task that touches an area with documented design. The orient-first rule lives in the repo's always-loaded AGENTS.md; this skill is the detailed form that rule routes to for non-trivial work — don't rely on ambient description-match alone.

Invariants

  • MUST be read-only: never edit code or LLP documents.
  • MUST scope to the task: pull the constraints that bind this change, not a corpus summary.
  • MUST cite, not restate: reference policy as LLP NNNN#anchor rather than paraphrasing sections.
  • MUST NOT invent constraints. If something isn't documented, say so.
  • MUST NOT guess the rationale behind a broken @ref — report it and hand off to llp-maintain.

Workflow

Recipe (advisory) — read llp/foundation/ first (the kernel; the root LLP is there once Active — on a fresh adoption it is still Draft and sits in current/), then skim llp/current/ (the declared working set); both hold relative links — symlinks, or small files containing the relative path — so ls answers and either form resolves. Then the root LLP's systems vocabulary. Grep '@ref' over the files in scope and Read each target — these are the highest-signal context. Grep the **Systems:** headers across llp/ for LLPs governing the subsystems touched; read the governing ones (Spec, Decision, Principles, relevant RFCs). Follow Related: and nearby @ref targets one hop out; stop there unless something is clearly load-bearing. Stale-pin nudge (skip offline): read the installed tag from the skills receipt (or a source: pin), compare git ls-remote --tags <origin> — if upstream is newer, say so in one line ("skills at v0.3.0, upstream v0.5.2 — run /llp-adopt update") and move on; never update from here.

Artifact

A context pack with these sections, faster to read than the documents it points at:

  • Scope — files / subsystems queried
  • Governing LLPs — numbered list, one-line gloss each; mark which are in foundation/ and which are in current/ (in-flight — its guidance may still move)
  • Active constraints — bullets, each citing LLP NNNN#anchor
  • Relevant rationale — the why, same citation form
  • Open questions / risks for this area
  • Likely doc updates if the change lands
  • Hand-off — one of none | llp-adopt | llp-create | llp-review | llp-maintain

Hand-offs

  • No corpus (llp/ missing or stub) → llp-adopt.
  • The task needs a decision no LLP covers → llp-create (or llp-review if proposal-shaped).
  • An @ref target or anchor doesn't resolve → llp-maintain.

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.