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
Most recently taken up by
- peterpme/skillsedited, first seen Nov 15, 2026
- expo/expo-device-hubword for word, first seen Nov 8, 2026
Who's talking about expo/exact
- A Hacker News story“Exact – a new cross platform UI framework”Hacker News · Nov 9, 2026 · 137 points
- A Hacker News story“Exact by Expo: A Rust-based cross-platform native app runtime”Hacker News · Nov 9, 2026 · 5 points
- @keith.bsky.social“Or make something new! github.com/expo/exact”Bluesky · Nov 12, 2026 · 2 likes
- @ccheever.com“Still a work in progress but I think it's ready for others to try it out. Here's the repo: …”Bluesky · Nov 9, 2026 · 2 likes
- soundor/soundor“Rewrite Soundor in Rust 🦀 (JS is no longer hype)”GitHub · Nov 11, 2026 · 1 reactions
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
- Nov 11, 2026Rewrite Soundor in Rust 🦀 (JS is no longer hype) — soundor/soundor1 reaction · 2 comments
- Nov 10, 2026Add Exact Contract v0.1.0 — zed-industries/extensions1 reaction · 4 comments
- Nov 14, 2026Exact: offload builds of apps that declare native modules — appandflow/stim0 reactions · 1 comment
- Nov 13, 2026Agent-first UI authoring: compact vocabulary, UI checks, and a run/verify loop — PathlandDev/Pathland0 reactions
- Nov 13, 2026vendor-radar: daily scan 2026-11-13 — ultrametricai/ultrametric0 reactions · 3 comments
6 more on GitHub
- Nov 12, 2026Daily 2026-11-12: Nod, aws-emulator, agent_skills, exact, blender-ai-mcp-addon — yash-nandvana/ai-tools0 reactions · 2 comments
- Nov 11, 2026Docs: plan for rebuilding the frontend on Exact — odonckers/berean0 reactions
- Nov 11, 2026Trending candidates 2026-11-11-00 — tayyabimam1/awesome-ai-agent-stack0 reactions · 1 comment
- Nov 11, 2026expo 'exact' — 한 번 쓰면 웹·macOS·iOS·Linux에 네이티브로 돌고, AI 에이전트가 직접 만들고 테스트하는 앱 런타임 (11/11, GitHub) — roomedia/ax-trend0 reactions
- Nov 10, 20267am AI 2026-11-10: Anthropic's Fable 5.2 is better at coding and cheaper to use — Repzei/7amai0 reactions
- Nov 10, 2026fix(css): flex alignment follows Chrome on overflow — nuxieai/nuxie-runtime0 reactions
On Bluesky · 6
- Nov 12, 2026Or make something new! github.com/expo/exact — @keith.bsky.social2 likes and reposts
- Nov 9, 2026Still a work in progress but I think it's ready for others to try it out. Here's the repo: https://github.com/expo/exact — @ccheever.com2 likes and reposts · 1 reply
- Nov 10, 2026ウェブやネイティブ環境で高速に動くExpoの新しいクロスプラットフォームUIフレームワークっぽい マルチプラットフォーム対応のアプリ開発で試したい yug1224 starred expo/exact https://github.com/expo/exact — @yug1224.com1 likes and repost
- Nov 10, 2026I cant keep up man github.com/expo/exact — @dw.whey.party1 likes and repost
- Nov 10, 2026expo/exact https://realtime.jser.info/2026/11/10/expo-exact/ https://github.com/expo/exact Web/macOS/iOS/Linux向けのクロスプラットフォームアプリケーションランタイム。… — @jser.info1 likes and repost
1 more on Bluesky
- Nov 10, 2026Web/macOS/iOS/Linux向けのクロスプラットフォームアプリケーションランタイム。 宣言的なContract言語でUIを定義し、TypeScriptまたはRustでデータ処理を記述する。… — @azu.bsky.social1 likes and repost
On Hacker News · 2
- Nov 9, 2026Exact – a new cross platform UI framework137 points · 109 comments
- Nov 9, 2026Exact by Expo: A Rust-based cross-platform native app runtime5 points
Other versions2 projects use a version of this.
Word for word · 1
- expo/expo-device-hub★ 285100% same
Edited · 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llp-adoptSkill
- llp-createSkill
- llp-maintainSkill
- llp-reviewSkill
- llp-super-refineSkill
- orchestrateSkill
- panelSkill
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
- Distinctive: line 18
Start of a coding task that touches an area with documented design.
- Distinctive: line 22
MUST be read-only: never edit code or LLP documents.
- Distinctive: line 23
MUST scope to the task: pull the constraints that bind this change, not a corpus summary.
- Very specific: line 24
MUST cite, not restate: reference policy as LLP NNNN#anchor rather than paraphrasing sections.
- Distinctive: line 25
MUST NOT invent constraints.
- Very specific: line 26
MUST NOT guess the rationale behind a broken @ref — report it and hand off to llp-maintain.
- Distinctive: line 41
Likely doc updates: if the change lands
- Very specific: line 46
No corpus (llp/ missing or stub) → llp-adopt.
≈ “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.
Files
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#anchorrather 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 tollp-maintain.
Workflow
Recipe (advisory) — read
llp/foundation/first (the kernel; the root LLP is there onceActive— on a fresh adoption it is stillDraftand sits incurrent/), then skimllp/current/(the declared working set); both hold relative links — symlinks, or small files containing the relative path — solsanswers and either form resolves. Then the root LLP's systems vocabulary.Grep '@ref'over the files in scope andReadeach target — these are the highest-signal context.Grepthe**Systems:**headers acrossllp/for LLPs governing the subsystems touched; read the governing ones (Spec, Decision, Principles, relevant RFCs). FollowRelated:and nearby@reftargets 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 asource:pin), comparegit 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 incurrent/(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(orllp-reviewif proposal-shaped). - An
@reftarget or anchor doesn't resolve →llp-maintain.
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
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.

