You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+69-64Lines changed: 69 additions & 64 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,92 +18,97 @@ In this ecosystem, giants monopolise the resources, and developers are thrown in
18
18
19
19
What can it help you do?
20
20
21
-
- A **universal prompt specification**: teaches you how to write Global / Root / Child / Skill / Command / Agent prompts in a unified structure.
22
-
-**Sync these prompts into as many AI coding tools as possible**: Cursor, Kiro, Warp, Claude CLI, Gemini CLI, Codex CLI, and more—if there is an entry point, it will stuff your memory into it.
23
-
- Like a rat gnawing on cables, it **gnaws structured memory out of existing directory structures and config files**, instead of asking you to rewrite everything from scratch.
24
-
- Provides **fine-grained control**: you can choose what to sync by project, by Agent, by tool type, avoiding "one-size-fits-all" overwrites.
25
-
- Guarantees **read-only source files**: it never modifies your original repository directly, only reads and transforms, then materialises the result on the target tool side.
26
-
27
-
## Who is this for
28
-
29
-
- You are writing code in a forgotten sewer.\
30
-
No one will proactively feed you, not even with a tiny free quota, not even with a half-decent document.
31
-
- As a rat, you can barely get your hands on anything good:\
32
-
you can only scurry between free tiers, trial credits, education discounts, and random third-party scripts.
33
-
- What can you do?\
34
-
You keep darting between IDEs, CLIs, browser extensions, and cloud Agents, copying and pasting the same memory a hundred times.
35
-
- You leech API offers from vendors day after day:\
36
-
today one platform runs a discount so you top up a little; tomorrow another launches a promo so you rush to scrape it.
37
-
- Once they have harvested the telemetry, user profiles, and usage patterns they want,\
38
-
they can kick you—this stinking rat—away at any moment: price hikes, rate limits, account bans, leaving you with no channel to complain.
21
+
-**`.mdx` as the prompt source format**: write your prompts in MDX; `memory-sync` reads, transforms, and writes them into each tool's native config format—you maintain one source, it handles the rest.
22
+
- A **universal prompt spec**: write Global / Root / Child / Skill / Command / Agent prompts in a unified structure.
23
+
-**Auto-write tool config files**: AGENTS.md, .cursorrules, .kiro/, CLAUDE.md, etc.—if there is an entry point, it stuffs your memory in.
24
+
-**Generate copy-ready one-shot prompts**: package project context, tech stack, and current task into AI-friendly Markdown, paste into any chat box directly.
25
+
- Like a rat gnawing on cables, **gnaw structured memory out of existing directory structures and config files**, instead of asking you to rewrite everything from scratch.
26
+
-**Fine-grained control**: describe rules in YAML / JSON config files, choose what to sync by project, by Agent, by tool type—no "one-size-fits-all" overwrites.
27
+
-**Read-only source files**: never modifies your original repository directly, only reads and transforms, then materialises the result on the target tool side.
28
+
-**Full wipe**: on sync, erases all stale prompt traces in target tools—prompts are fully computable and auditable, leaving no residue for bad actors.
29
+
-**Prompts grow with you only**: memory follows you as a person, not the project. Someone else takes over the project—they cannot take your context. You move to a new project—your accumulated knowledge moves with you intact.
30
+
31
+
## Install
32
+
33
+
```sh
34
+
npm install -g @truenine/memory-sync
35
+
```
39
36
40
-
If you are barely surviving in this environment, `memory-sync` is built for you:\
41
-
it helps you carry fewer bricks, copy prompts fewer times, and at least on the "memory" front, you are no longer completely on the passive receiving end.
You have a stable salary, project revenue share, and a budget to sign official APIs yearly.
47
-
- And yet you still come down here,\
48
-
competing with us filthy sewer rats for the scraps in the slop bucket.
49
-
- If you can afford APIs and enterprise plans, then pay for them.\
50
-
Go and do things that actually create more value—like paying properly and giving proper feedback, nudging the ecosystem slightly in the right direction.
51
-
- Instead of turning back,\
52
-
stripping away the tiny gap that was originally left for marginalised developers, and squeezing out the last crumbs with us.
44
+
More platforms being added continuously.
53
45
54
-
In other words:\
55
-
**this is not a tool for optimising capital costs, but a small counterattack prepared for the "rats with no choice" in a world of extreme resource inequality.**
Native-friendly, plus targeted conditional prompt authoring.
69
62
70
-
## Quick Start
63
+
`AGENTS.md` is the spec; `memory-sync` is the hauler—it writes the same memory into the native config formats of a dozen tools simultaneously, sparing you the manual copy-paste grind.
71
64
72
-
### Prerequisites
65
+
**Is there anything in your prompts you don't want to leave behind?**
73
66
74
-
Node.js >= 25.2.1, pnpm >= 10
67
+
Yes. That's why `memory-sync` provides a full-wipe mode: after sync, only the content you explicitly authorised remains in the target tools—everything else is erased. Prompts are fully computable, no hidden residue, no backdoor left for anyone else.
75
68
76
-
### Installation
77
-
78
-
```bash
79
-
pnpm add -g @truenine/memory-sync
80
-
```
81
-
82
-
Or use directly:
69
+
## Who is this for
83
70
84
-
```bash
85
-
npx @truenine/memory-sync
86
-
```
71
+
To use `memory-sync` you need:
87
72
88
-
### Run
73
+
- Solid development experience, years of working with various dev tools
74
+
- Proficiency with version control (Git)
75
+
- Proficiency with the terminal
89
76
90
-
```bash
91
-
tnmsc
92
-
```
77
+
---
93
78
94
-
### Update
79
+
- You are writing code in a forgotten sewer.\
80
+
No one will proactively feed you, not even a tiny free quota, not even a half-decent document.
81
+
- As a rat, you can barely get your hands on anything good:\
82
+
scurrying between free tiers, trial credits, education discounts, and random third-party scripts.
83
+
- What can you do?\
84
+
Keep darting between IDEs, CLIs, browser extensions, and cloud Agents, copying and pasting the same memory a hundred times.
85
+
- You leech API offers from vendors day after day:\
86
+
today one platform runs a discount so you top up a little; tomorrow another launches a promo so you rush to scrape it.
87
+
- Once they have harvested the telemetry, user profiles, and usage patterns they want,\
88
+
they can kick you—this stinking rat—away at any moment: price hikes, rate limits, account bans, and you have no channel to complain.
95
89
96
-
```bash
97
-
pnpm update -g @truenine/memory-sync --latest
98
-
```
90
+
If you are barely surviving in this environment, `memory-sync` is built for you:\
91
+
carry fewer bricks, copy prompts fewer times—at least on the "memory" front, you are no longer completely on the passive receiving end.
99
92
100
-
## GUI Desktop App
93
+
## Who is NOT welcome
101
94
102
-
GUI package provides Tauri desktop application, build in `gui/` directory:
95
+
- Your income is already fucking high.\
96
+
Stable salary, project revenue share, budget to sign official APIs yearly.
97
+
- And yet you still come down here,\
98
+
competing with us filthy sewer rats for the scraps in the slop bucket.
99
+
- If you can afford APIs and enterprise plans, go pay for them.\
100
+
Do things that actually create value—pay properly, give proper feedback, nudge the ecosystem slightly in the right direction.
101
+
- Instead of coming back down\
102
+
to strip away the tiny gap left for marginalised developers, squeezing out the last crumbs with us rats.
103
+
- You are a freeloader.\
104
+
Everything must be pre-chewed and spoon-fed; you won't even touch a terminal.
105
+
- You love the grind culture.\
106
+
Treating "hustle" as virtue, "996" as glory, stepping on peers as a promotion strategy.
107
+
- You leave no room for others.\
108
+
Not about whether you share—it's about actively stomping on people, competing maliciously, sustaining your position by suppressing peers, using others' survival space as your stepping stone.
103
109
104
-
```bash
105
-
pnpm tauri:build
106
-
```
110
+
In other words:\
111
+
**this is not a tool for optimising capital costs, but a small counterattack prepared for the "rats with no choice" in a world of extreme resource inequality.**
0 commit comments