prompt-architecture
Skill9 starsChanged 19 days agoApache-2.0View on GitHub
How ShipIt stores and composes LLM prompts: prompt text as .md data files loaded at module top level, composition in TypeScript, the byte-stability prompt-cache contract, and how to test prompts (composition and caching, never literal wording). Load when editing agent system instructions, voice cleanup, session naming, or any prompt-composing code.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- roronoazoroshao369/vibe-coding-ostheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- roronoazoroshao369/vibe-coding-os★ 1same name
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 repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-endpointSkill
- android-buildSkill
- client-architectureSkill
- deployment-architectureSkill
- design-languageSkill
- docs-navigatorSkill
- dogfooding-shipitSkill
- frontend-design:frontend-designSkill
- git-architectureSkill
- server-architectureSkill
- session-containersSkill
- session-lifecycleSkill
- session-processesSkill
- testing-and-qualitySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
Every (agentId, mode) variant renders once at module load into PRECOMPUTED_INSTRUCTIONS, a module-level ReadonlyMap (typed as read-only.
≈ “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
Prompt architecture
LLM prompts — agent system instructions, voice cleanup, session naming — are content, not logic. Keep the two separated.
Prompt text is data: it lives in .md files
Co-locate the .md with the code that composes it. Prose reviews as prose, diffs cleanly, and needs no backtick or ${} escaping.
Load it with loadPrompt(import.meta.url, "./x.md") (orchestrator/load-prompt.ts), at module top level — once at init, never per call. A missing file then throws at boot rather than mid-turn.
Not a bundler ?raw import: production runs TS via tsx with no bundler, so fs.readFileSync(new URL(...)) is what actually works.
Examples: agents/<id>/system-prompt.md, voice/cleanup-prompt.md, orchestrator/prompts/*.md.
A per-call hole is still data. session-namer.ts loads session-naming-prompt.md at module level and fills its {{MESSAGE}} per call through buildSessionNamePrompt. The file read happens once; only the substitution is per call, which is composition and belongs in TypeScript. A prompt whose text varies per request is not a reason to inline it.
Prompt composition is code
Axis branching and fragment selection stay in TypeScript. In agent-instructions.ts, renderInstructions fills {{TOKEN}} holes in prompts/skeleton.md via fillPromptTokens, which throws on an unfilled token — that's the guard ensuring no literal {{FOO}} ever reaches the model.
There are two axes: agentId (Parallel-sessions wording) and the session mode, which has three values — std, ops (docs/128), and sandbox (docs/211). isOps and isSandbox are mutually exclusive, and ops wins if both are passed. Every (agentId, mode) pair is precomputed, so don't write code or tests that assume a single isOps boolean.
The prompt-cache contract is load-bearing
Every (agentId, mode) variant renders once at module load into PRECOMPUTED_INSTRUCTIONS, a module-level ReadonlyMap (typed as read-only; not runtime-frozen). The per-turn path is a pure lookup, which keeps the CLI string byte-stable so the Anthropic prompt cache stays warm.
Never move composition or the .md reads onto a per-call path. Doing so silently destroys cache hits on every turn.
Testing prompts
Test composition and caching, never literal wording. A pure prompts/*.md copy-edit should require no test changes.
Do assert:
- Fragment selection per
agentId/isOps - Variant distinctness, and non-ops byte-identity
- Byte-identity of the precomputed constants across repeated lookups. Note the limit: the rendered instructions are strings, and JS strings are primitives, so
toBe/Object.ispasses for two independently assembled equal strings. Such a test pins the value, not the absence of per-call reassembly — don't claim it proves caching. To actually pin that, assert on the map identity or spy on the compose path. - Call-site threading
- The cheap load guard: every variant non-empty, no leftover
{{TOKEN}} - Presence/absence keyed off a structural anchor — a
##header, a command token — not a sentence
Don't assert specific prose phrases. They churn on copy-edits, and were deliberately removed from agent-instructions.test.ts for that reason.
Provider and integration tests reference the imported constant (toContain(CLEANUP_INSTRUCTIONS)), never a pasted copy.
See voice/cleanup.test.ts and integration_tests/system-prompt.test.ts.
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.

