Jun 18, 2026, 12:01 PM

This commit is contained in:
Paweł Domański
2026-06-18 10:01:11 +00:00
parent 8190368188
commit 33fa2cf18a
27 changed files with 214 additions and 196 deletions
+2 -1
View File
@@ -9,7 +9,7 @@ Coding style, naming, and structural conventions for the Knowledge Base.
## Formatting & Link Style
- **WikiLinks**: Prefer double brackets `[[knowledge/path/to/page]]` or standard relative link `[[page]]` for connections in the synthesis layer (`knowledge/`).
- **Knowledge BaseLinks**: Prefer double brackets `[[knowledge/path/to/page]]` or standard relative link `[[page]]` for connections in the synthesis layer (`knowledge/`).
- **YAML Frontmatter**: When requested or appropriate, include metadata (tags, dates, source counts) at the top of markdown files.
- **Kebab Case**: File names in `knowledge/concepts/` and `knowledge/entities/` must be kebab-case (e.g., `human-in-the-loop.md`, `sql-server.md`).
@@ -24,3 +24,4 @@ Coding style, naming, and structural conventions for the Knowledge Base.
## Feynman Problems Alignment
- **Central Alignment**: Every newly ingested raw file must be tested against the 12 Feynman Problems documented in `knowledge/feynman_problems.md`. If the content addresses or helps answer any of those questions, update the respective section in `knowledge/feynman_problems.md` with a direct link and concise insight.
+2 -1
View File
@@ -4,7 +4,7 @@ Project and shell commands for development, utility, and maintenance tasks.
## Maintenance Scripts (Windows PowerShell)
- **Knowledge-base Terms Replacer**: Refactors old "wiki" references to "knowledge" across files and renames files containing "wiki":
- **Knowledge-base Terms Replacer**: Refactors old "knowledge" references to "knowledge" across files and renames files containing "knowledge":
```powershell
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\replace_knowledge.ps1
```
@@ -34,3 +34,4 @@ Project and shell commands for development, utility, and maintenance tasks.
```powershell
git log -n 3
```
+2 -1
View File
@@ -4,7 +4,7 @@ Steps and commands to execute when validating code changes or knowledge-base upd
## Verification Checklist
1. **Broken Link Check**: Ensure all newly added `[[WikiLinks]]` are accurate and point to existing files.
1. **Broken Link Check**: Ensure all newly added `[[Knowledge BaseLinks]]` are accurate and point to existing files.
2. **Kebab-Case Naming**: Verify all created concept or entity files are named in kebab-case.
3. **UTF-8 Encoding**: Ensure modified and created markdown files are written in UTF-8 format.
4. **Consistency Script**: Run the text replacement script if naming or file paths were updated:
@@ -16,3 +16,4 @@ Steps and commands to execute when validating code changes or knowledge-base upd
serena memories check
```
6. **Git Cleanliness**: Run `git status` to ensure only intended changes are modified and no unintended files are staged.
+2 -1
View File
@@ -18,4 +18,5 @@ Technical details and tools used in the LLM Knowledge Base repository.
- No compilers, compilers pins, or heavy framework dependencies.
- Git is used for version control of the markdown files, allowing revision history and branching.
- Local custom script: `replace_knowledge.ps1` handles codebase-wide text replacements (specifically migrating old "wiki" terminology to "knowledge").
- Local custom script: `replace_knowledge.ps1` handles codebase-wide text replacements (specifically migrating old "knowledge" terminology to "knowledge").