@su-record/vibe 4.2.28 → 4.2.29
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -6,14 +6,14 @@
|
|
|
6
6
|
},
|
|
7
7
|
"metadata": {
|
|
8
8
|
"description": "Your personal FDE in Claude and Codex. Understand the work, use the right tools, deliver and retain useful context. One entry: vibe.",
|
|
9
|
-
"version": "4.2.
|
|
9
|
+
"version": "4.2.29"
|
|
10
10
|
},
|
|
11
11
|
"plugins": [
|
|
12
12
|
{
|
|
13
13
|
"name": "vibe",
|
|
14
14
|
"source": "./",
|
|
15
15
|
"description": "Your personal FDE in Claude and Codex. Understand the work, use the right tools, deliver and retain useful context. One entry: vibe.",
|
|
16
|
-
"version": "4.2.
|
|
16
|
+
"version": "4.2.29",
|
|
17
17
|
"category": "productivity"
|
|
18
18
|
}
|
|
19
19
|
]
|
package/internal/guides/wiki.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Keep and improve the knowledge wiki
|
|
2
2
|
|
|
3
|
-
Use on a knowledge turn (the user turned on `vibe knowledge auto`), when the user asks to record or organise what has been learned, or when saved notes have grown into overlapping files. The wiki is the personal knowledge folder (`vibe knowledge auto` prints where); project knowledge in `.vibe/knowledge/` follows the same rules, and the wiki shows each vibe project's as `projects/<project>/`. It is plain Markdown
|
|
3
|
+
Use on a knowledge turn (the user turned on `vibe knowledge auto`), when the user asks to record or organise what has been learned, or when saved notes have grown into overlapping files. The wiki is the personal knowledge folder (`vibe knowledge auto` prints where); project knowledge in `.vibe/knowledge/` follows the same rules, and the wiki shows each vibe project's as `projects/<project>/`. It is plain Markdown the user can open in Obsidian, but its reader is you: it is the knowledge base of the user's personal FDE, there so that you choose better, fill in what the user leaves unsaid and propose improvements fitted to how they work. With session knowledge on, keeping it is your job: the user should never have to say "save this".
|
|
4
4
|
|
|
5
5
|
## Use it before choosing
|
|
6
6
|
|
|
@@ -14,8 +14,8 @@ On a knowledge turn, look at the turns since the last one. When the turn says th
|
|
|
14
14
|
|
|
15
15
|
The knowledge turn names this project's page and, in a vibe project, its shared folder.
|
|
16
16
|
|
|
17
|
-
- Shared: what anyone working on the project needs (how its code is built, its conventions, domain facts, a decision about the product) goes into the project's `.vibe/knowledge/`. It travels with the project, so it shows in the user's git changes and reaches the team once they commit it; say which file you changed. Conventions belong in `conventions.md` there.
|
|
18
|
-
- Personal: how the user works, their methods across projects, skills, and their own notes on the project (`projects/<project>.md`) stay in the wiki.
|
|
17
|
+
- Shared: what anyone working on the project needs (how its code is built, its conventions, domain facts, a decision about the product) goes into the project's `.vibe/knowledge/`. It travels with the project, so it shows in the user's git changes and reaches the team once they commit it; say which file you changed. Conventions belong in `conventions.md` there. Write it in English so every teammate can read it.
|
|
18
|
+
- Personal: how the user works, their methods across projects, skills, and their own notes on the project (`projects/<project>.md`) stay in the wiki. Write personal pages in the language the user talks to you in, not the system's locale; property keys and `type` values stay English, and a page keeps its language until you edit it.
|
|
19
19
|
- Never put a preference, a person's private data or anything from an excluded folder into the shared folder. When unsure, keep it personal.
|
|
20
20
|
|
|
21
21
|
## Find before writing
|
|
@@ -39,9 +39,9 @@ updated: 2026-10-16
|
|
|
39
39
|
|
|
40
40
|
- `summary` is what lists and search results show, so write the conclusion, not "notes about X"; put it in double quotes when it holds a colon.
|
|
41
41
|
- `tags`: one to five, reusing tags other pages already have (search finds them); lowercase, no spaces.
|
|
42
|
-
- `aliases`: other names the user or a model would search for: synonyms, abbreviations and the
|
|
42
|
+
- `aliases`: other names the user or a model would search for: synonyms, abbreviations and the same words in the other language (English on a personal page, the user's words on a shared one), so a search in either finds the page.
|
|
43
43
|
- `type`, one of: `decision` (follow it), `method` (reuse it), `problem` (avoid or solve it), `fact`, `project`, `research`, `skill`, `proposal`, `source`. `vibe knowledge lint` reports any other value.
|
|
44
|
-
- `source`: raw material kept as evidence (a transcript, a web clipping, a video analysis
|
|
44
|
+
- `source`: raw material kept as evidence (a transcript, a web clipping, a video analysis). Never rewrite or split it; an organised page holds the conclusions and links it for its claims. The lint skips its length, not its links.
|
|
45
45
|
- `supersedes: "[[old-page]]"` on a page that replaces another, and `status: archived` on a finished project or knowledge no longer in force. Search ranks both lower and marks them, so keep the old page for its reasons instead of deleting it.
|
|
46
46
|
- One subject per page; a page covering two subjects is two pages linked to each other. Keep `## Related` at the end for links that are not already in the text.
|
|
47
47
|
|
|
@@ -53,9 +53,9 @@ updated: 2026-10-16
|
|
|
53
53
|
- `me.md`: how the user works and what they prefer, as they stated it or as repeated evidence shows; mark an inference as an inference.
|
|
54
54
|
- `practices.md` or a subject page: methods that worked, with the comparison that showed it ("for X, doing A instead of B removed the retry; seen 2026-10-15 in project P").
|
|
55
55
|
- `skills.md`: skills you created from the user's work, what each does and the evidence that led to it.
|
|
56
|
-
- Subject pages for tools, systems and recurring problems (`problems.md`, `corrections.md`, `reuse.md`).
|
|
56
|
+
- Subject pages for tools, systems and recurring problems (`problems.md`, `corrections.md`, `reuse.md`).
|
|
57
57
|
|
|
58
|
-
Give each claim its date and source (a file path with revision, a command and its result, the user's words with the day). When a new fact contradicts a page, correct the page and keep the reason in one line.
|
|
58
|
+
Give each claim its date and source (a file path with revision, a command and its result, the user's words with the day). When a new fact contradicts a page, correct the page and keep the reason in one line. Past about 200 lines, split a page by subject.
|
|
59
59
|
|
|
60
60
|
## Propose improvements fitted to the user
|
|
61
61
|
|
|
@@ -172,7 +172,7 @@ Proposals are proposals: the harness never installs a proposed skill or runs rem
|
|
|
172
172
|
|
|
173
173
|
## Language
|
|
174
174
|
|
|
175
|
-
The always-on card (1KB), the skills and every record vibe writes are English. The model talks to you in your language.
|
|
175
|
+
The always-on card (1KB), the skills and every shared record vibe writes are English; your personal wiki is written in the language you talk in. The model talks to you in your language.
|
|
176
176
|
|
|
177
177
|
## What is inside `.vibe/`
|
|
178
178
|
|
package/package.json
CHANGED