llp-adopt
Skill4.3k starsChanged 3 days agoMITView on GitHub
Bring LLP to a repository and keep its installed skills current — the single entry point for "set up LLP here" and "update the LLP skills". Scaffold mode (fresh structure), retrofit mode (survey the codebase, draft a provenance-tagged root LLP, propose an adoption plan), install step (copy skills from a tagged release with a receipt), and update mode (verified, diff-approved skill updates).
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★ 2895% 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-createSkill
- llp-maintainSkill
- llp-orientSkill
- llp-reviewSkill
- llp-super-refineSkill
- orchestrateSkill
- panelSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
- Very specific: line 21
MUST extend an existing llp/ tree if one exists — never start a second setup layer.
- Distinctive: line 22
MUST write only new files and clearly-marked managed blocks.
- Very specific: line 23
MUST keep every generated document Draft and provenance-tagged: claims are [observed] (say where), [confirmed] (named human + date), or …
- Very specific: line 24
MUST propose @ref annotations and apply them only after approval — no mass annotation, and none on volatile early code.
- Distinctive: line 25
MUST NOT create a batch of speculative LLPs in either mode.
- Distinctive: line 26
When a tool expects CLAUDE.md, symlink it to AGENTS.md when safe rather than maintaining divergent copies.
- Distinctive: line 31
MUST confirm before writing user/global skill directories (they affect every repo for that user).
- Distinctive: line 33
Update MUST present the full changeset for the installed profile *as defined at the target tag* as one diff, revalidate the approved state …
- Distinctive: line 34
If upstream is unreachable, a tag moved or vanished, or content can't be verified against the resolved commit: report exactly that and …
≈ “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-adopt
<!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0001-adopting-llp.guide.md — the workflow this automates --><!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0010.000-skill-installation-and-updates.spec.md — install/update design, receipts, trust model --><!-- @ref https://github.com/ccheever/llp/blob/v0.5.2/llp/0000-linked-literate-programming.explainer.md#provenance-for-generated-rationale — tagging rules for generated docs -->One entry point for "add LLP to this project" and "update the LLP skills". Invoke as /llp-adopt (auto-detect scaffold/retrofit), --mode scaffold / --mode retrofit, or /llp-adopt update.
Trigger
"Set up / bring LLP to this repo," for any repository state; "update the LLP skills," in any repo with installed skills.
Invariants — adoption
- MUST extend an existing
llp/tree if one exists — never start a second setup layer. - MUST write only new files and clearly-marked managed blocks; existing user prose is never overwritten without showing a diff and asking. Reruns MUST be idempotent (no duplicate files or blocks).
- MUST keep every generated document
Draftand provenance-tagged: claims are[observed](say where),[confirmed](named human + date), or[inferred]— and[inferred]claims never survive into a document proposed for promotion. - MUST propose
@refannotations and apply them only after approval — no mass annotation, and none on volatile early code. - MUST NOT create a batch of speculative LLPs in either mode; establish orientation and the loop, then hand off.
- When a tool expects
CLAUDE.md, symlink it toAGENTS.mdwhen safe rather than maintaining divergent copies.
Invariants — install and update (LLP 0010.000)
- MUST install only from a tagged release (the tag's tree is the release), as copies never symlinks, and write a receipt beside the installation: origin, tag, resolved commit, profile flags (core;
review-plus;delivery, which also records the repo's delivery policy in repo-local config), and a per-file content hash. The receipt — notsource:frontmatter — is the trust root for updates. - MUST confirm before writing user/global skill directories (they affect every repo for that user); project-local may proceed more freely.
- Update MUST three-way-check each file against the receipt hash. Any mismatch is a local fork: abort the coupled update, never clobber, and offer discard (restore managed copy) or detach (file leaves the managed set permanently; receipt records it; later updates ignore it and note upstream changes without applying).
- Update MUST present the full changeset for the installed profile as defined at the target tag as one diff, revalidate the approved state immediately before mutation, and be recoverable to either endpoint (the receipt write is the commit point). Runs are single-flight per installation.
- If upstream is unreachable, a tag moved or vanished, or content can't be verified against the resolved commit: report exactly that and write nothing. Cannot-verify never degrades to guess.
Workflow
Recipe (advisory) — Adoption: inspect first (existing
llp/? agent files? how much code?): little to mine → scaffold; substantial history → retrofit. Both share the spine:llp/with itscurrent/andfoundation/overlay directories, root LLP 0000 (Explainer,**Role:** Root,Draft— linked intocurrent/; it entersfoundation/when the author makes itActive), theAGENTS.mdmanaged block. Retrofit adds: survey, draft root LLP, propose 2–5 subsystem LLPs, layered annotation plan (LLP 0001). Install: offer after the managed blocks; default profile core, flags opt-in. Update: fetch the tag's tree (shallow clone or archive; git required), diff, approve, apply as a staged set with prior bytes retained until the receipt lands; rollback isgit revertwhere the installation is committed, the backups otherwise. Releasing (this repo): bumpsource:pins and pinned URLs → commit → tag → push tag — a skill-file change is not installable until tagged.
Artifact
Scaffold: llp/ with current/ (holding the link to the new root) and an empty foundation/, an LLP 0000 skeleton, the managed blocks. Retrofit: those plus a survey summary, Draft provenance-tagged document(s), and a proposed adoption plan. Install/update: pinned skill copies, the receipt, and (with the delivery flag) the repo policy file.
Hand-offs
- Corpus exists → daily work starts with
llp-orient; author follow-on docs withllp-create. - Ratify generated drafts with
llp-reviewwhere stakes warrant; keep healthy withllp-maintain— whose audit notes stale pins and hands back to/llp-adopt update.
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.

