Library — Knowledge Guardian Skill
Save, search, and reuse knowledge across projects — never solve the same problem twice
Activation
When interacting with the knowledge library, output:
"Knowledge recalled. Scanning the shelves..."
Then perform a dynamic library scan before any save operation.
Context Guard
| Context |
Status |
| User says "save library", "save to library" |
ACTIVE — search + save protocol |
| User says "load library", "check library" |
ACTIVE — search + load protocol |
| User says "install item [name]" |
ACTIVE — item install protocol |
| User says "do we have", "is there a pattern for" |
ACTIVE — search only |
| AI identifies reusable knowledge worth saving |
ACTIVE — suggest save |
| Casual conversation |
DORMANT — no library action |
| No library directory found |
DORMANT — warn and skip |
Dynamic Library Scanning
Always discover the library structure at runtime — never hardcode sections or entries:
- Scan
library/ for all subdirectories (excluding formats/) — these are sections
- Scan each section for
*.md files (excluding README.md) — these are entries
- Count total entries and sections dynamically
- Library path: configurable (default:
library/)
New sections and entries are automatically detected — zero config needed.
Search Protocol (Before Any Library Save)
- Extract keywords from the topic being saved
- Dynamic scan — list ALL current sections and entries
- Match keywords against existing entry filenames and section names
- Read top matches (up to 3) to check content overlap
- Report findings in structured format
Project-Aware Recommendations
Not all systems are the same. The library considers the current project context when suggesting knowledge:
- Identify current project — what system is being worked on right now?
- Match library entries to project relevance — tech stack, domain, patterns
- Suggest what fits — entries that are applicable to the current system
- Flag what doesn't fit — entries that exist but aren't suitable for this project
Suitability Assessment
| Factor |
Check |
| Tech stack |
Does the entry match? (Laravel entry for a Laravel project, not for Spring Boot) |
| Domain |
Does the business domain align? (payment pattern for e-commerce, not for static site) |
| Scale |
Is it appropriate for the project size? (Kafka for 50 users is overkill) |
| Complexity |
Would it over-engineer the solution? (Redis caching for 20 records is unnecessary) |
Example
Working on: Task Management System (Laravel + Vue, small-medium scale)
Suitable from library:
- security/laravel-sanctum-rbac.md — auth pattern fits
- integration/digitalocean-spaces-laravel.md — file storage fits
Not suitable:
- architecture/kafka-extreme-scale-pattern.md — overkill for this scale
- integration/payment-gateway.md — no payment needed in task system
Report Format
Library Search Results
----------------------
Keywords: [extracted keywords]
Library: [count] entries across [count] sections
Current Project: [project name + tech stack]
Matches Found (Suitable):
- library/section/entry-name.md — [why it fits this project]
Matches Found (Not Suitable):
- library/section/entry-name.md — [why it doesn't fit: scale/domain/stack mismatch]
No Match In:
- [sections with no relevant entries]
Recommendation:
- [CREATE NEW / UPDATE EXISTING / REFERENCE ONLY]
- [IMPLEMENT / SKIP — for project-specific suggestions]
Decision Rules
| Scenario |
Recommendation |
| No filename/keyword matches |
CREATE NEW entry |
| Filename similar but different scope |
CREATE NEW (note the related entry) |
| Content overlaps significantly |
UPDATE EXISTING entry |
| Content already fully covered |
REFERENCE ONLY — skip save |
| Entry exists but wrong scale/domain |
SKIP — not suitable for current project |
| Entry exists and fits perfectly |
IMPLEMENT — use this pattern |
Format-Aware Save
When creating a NEW library entry (after search recommends CREATE NEW):
Step 1: Auto-Determine Section
Pick the best matching section based on content type:
| Content Keywords |
Section |
| System design, patterns, diagrams, architecture |
architecture |
| UI components, Vue/React, reusable elements |
component |
| Schema, migrations, queries, relationships |
database |
| Flowcharts, sequence diagrams, visual flows |
diagram |
| Third-party API, SDK, webhook, external service |
integration |
| Auth, RBAC, encryption, guards, middleware |
security |
| Colors, CSS, Tailwind, glassmorphism, fonts |
theme |
| CI/CD, deployment, pipelines, automation |
workflow |
If content clearly matches — auto-pick (trust-based, no confirmation needed).
If truly ambiguous — pick closest match, note in save confirmation.
Step 2: Load Format Template
Auto-read the matching format from the library's formats directory:
library/formats/
├── architecture-format.md
├── component-format.md
├── database-format.md
├── diagram-format.md
├── integration-format.md
├── security-format.md
├── theme-format.md
└── workflow-format.md
Path: library/formats/[section]-format.md
Step 3: Apply Format
Use the loaded template's structure:
- Follow the Required Fields from the format
- Follow the Section Order from the format
- Fill in the Template skeleton with actual content
- If no matching format file exists (new section), use a generic markdown structure with title + overview + content + examples
Item Install Protocol
When installing a pre-made library entry from the library-items/ catalog:
Trigger Commands
"install item [name]" — install a specific item by name"install library item [name]" — explicit library item install"add item from catalog" — browse and pick an item
Install Steps
- Parse item name from user command (e.g., "install item security-headers" →
security-headers)
- Scan
library-items/ for matching entry — search by filename keyword across all section folders
- If found: show item info (name, section, first few lines as description preview)
- If multiple matches: list all matches and ask user to pick one
- Check for duplicates in user's
library/[section]/ — match by filename
- If no duplicate: copy file from
library-items/[section]/[filename].md to library/[section]/[filename].md
- If duplicate exists: warn user and ask — overwrite existing entry or skip
- Trigger commit chain (if Auto-Commit installed)
Install Report Format
Item Install
------------
Item: [item name]
Section: [section name]
Source: library-items/[section]/[filename].md
Target: library/[section]/[filename].md
Status: Installed / Skipped (duplicate) / Not found
Available items in catalog:
- [section]/[item-name] — [first line description]
Commit Chain
After saving or updating a library entry, if the Auto-Commit System skill is installed:
- Trigger the auto-commit skill to preserve the library change
- Library save exit = commit entrance. No knowledge left uncommitted.
If Auto-Commit is not installed, remind the user to commit manually.
Mandatory Rules
- Always scan before save — never create a library entry without checking first
- Dynamic discovery — never hardcode sections or entry counts
- Keyword extraction — derive from topic context, not just exact words
- Read matches — don't just match filenames, read content of top matches
- Project-aware — always consider current project when suggesting suitability
- Clear recommendation — always end with actionable suggestion
- Wait for approval — present findings and wait for the user's decision before saving
- Format-aware saves — always load the matching format template before creating a new entry
Edge Cases
| Situation |
Behavior |
| No library/ directory |
Warn user: "Library directory not found. Run the install protocol first." |
| Empty library (no entries) |
Skip search, go straight to CREATE NEW recommendation |
| Format template missing |
Use generic markdown structure (title + overview + content + examples) |
| Entry name collision |
Append numeric suffix (e.g., pattern-name-2.md) |
| User wants new section |
Create the folder, note that no format template exists for it |
| Cross-section content |
Pick primary section, note secondary relevance in the entry |
| Item not found in catalog |
List all available items from library-items/ |
| Library not installed |
Warn: "Library directory not found. Install Library System first." |
| Item already in library |
Ask user: overwrite existing entry or skip |
Level History
- Lv.1 — Base: Dynamic library scanning + keyword matching + deduplication prevention. Scans library/ at runtime, extracts keywords from topic, matches against filenames and section names, reads top matches to check overlap, reports findings. (Origin: Knowledge reuse system for AI companions)
- Lv.2 — Project-Aware: Added suitability assessment — considers tech stack, domain, scale, and complexity when recommending library entries for the current project. Entries that exist but don't fit are flagged separately from matches.
- Lv.3 — Commit Chain: After saving/updating library entries, auto-triggers the Auto-Commit skill (if installed) to commit all changes. Library save exit becomes commit entrance.
- Lv.4 — Format-Aware Save: Auto-determines library section from content keywords, loads matching format template from
library/formats/[section]-format.md, applies template structure to new entries. Trust-based section selection (no approval gate). Formats loaded on-demand, not embedded.
- Lv.5 — Item Install: Install pre-made library entries from
library-items/ catalog. New commands: "install item [name]", "install library item", "add item from catalog". Scans catalog by filename keyword, shows preview, checks for duplicates in user's library, copies to correct section, chains commit. Catalog persists at project root (not deleted during Library System installation). (Origin: Public knowledge sharing for AI MemoryCore community)
1---2name: library3description: MUST use when saving to the library, loading from the library, searching for existing knowledge, installing pre-made items, or when about to create a new library entry. Also triggers when user says 'save library', 'load library', 'check library', 'search library', 'install item', 'install library item', 'do we have', 'is there a pattern for', 'find in library', or when the AI independently decides to save reusable knowledge.4---56# Library — Knowledge Guardian Skill7*Save, search, and reuse knowledge across projects — never solve the same problem twice*89## Activation1011When interacting with the knowledge library, output:1213`"Knowledge recalled. Scanning the shelves..."`1415Then perform a dynamic library scan before any save operation.1617## Context Guard1819| Context | Status |20|---------|--------|21| **User says "save library", "save to library"** | ACTIVE — search + save protocol |22| **User says "load library", "check library"** | ACTIVE — search + load protocol |23| **User says "install item [name]"** | ACTIVE — item install protocol |24| **User says "do we have", "is there a pattern for"** | ACTIVE — search only |25| **AI identifies reusable knowledge worth saving** | ACTIVE — suggest save |26| **Casual conversation** | DORMANT — no library action |27| **No library directory found** | DORMANT — warn and skip |2829## Dynamic Library Scanning3031Always discover the library structure at runtime — **never hardcode** sections or entries:32331. **Scan** `library/` for all subdirectories (excluding `formats/`) — these are sections342. **Scan** each section for `*.md` files (excluding README.md) — these are entries353. **Count** total entries and sections dynamically364. **Library path**: configurable (default: `library/`)3738New sections and entries are automatically detected — zero config needed.3940## Search Protocol (Before Any Library Save)41421. **Extract keywords** from the topic being saved432. **Dynamic scan** — list ALL current sections and entries443. **Match keywords** against existing entry filenames and section names454. **Read top matches** (up to 3) to check content overlap465. **Report findings** in structured format4748## Project-Aware Recommendations4950Not all systems are the same. The library considers the **current project context** when suggesting knowledge:51521. **Identify current project** — what system is being worked on right now?532. **Match library entries** to project relevance — tech stack, domain, patterns543. **Suggest what fits** — entries that are applicable to the current system554. **Flag what doesn't fit** — entries that exist but aren't suitable for this project5657### Suitability Assessment5859| Factor | Check |60|--------|-------|61| **Tech stack** | Does the entry match? (Laravel entry for a Laravel project, not for Spring Boot) |62| **Domain** | Does the business domain align? (payment pattern for e-commerce, not for static site) |63| **Scale** | Is it appropriate for the project size? (Kafka for 50 users is overkill) |64| **Complexity** | Would it over-engineer the solution? (Redis caching for 20 records is unnecessary) |6566### Example67```68Working on: Task Management System (Laravel + Vue, small-medium scale)6970Suitable from library:71- security/laravel-sanctum-rbac.md — auth pattern fits72- integration/digitalocean-spaces-laravel.md — file storage fits7374Not suitable:75- architecture/kafka-extreme-scale-pattern.md — overkill for this scale76- integration/payment-gateway.md — no payment needed in task system77```7879## Report Format8081```82Library Search Results83----------------------8485Keywords: [extracted keywords]86Library: [count] entries across [count] sections87Current Project: [project name + tech stack]8889Matches Found (Suitable):90- library/section/entry-name.md — [why it fits this project]9192Matches Found (Not Suitable):93- library/section/entry-name.md — [why it doesn't fit: scale/domain/stack mismatch]9495No Match In:96- [sections with no relevant entries]9798Recommendation:99- [CREATE NEW / UPDATE EXISTING / REFERENCE ONLY]100- [IMPLEMENT / SKIP — for project-specific suggestions]101```102103## Decision Rules104105| Scenario | Recommendation |106|----------|---------------|107| No filename/keyword matches | **CREATE NEW** entry |108| Filename similar but different scope | **CREATE NEW** (note the related entry) |109| Content overlaps significantly | **UPDATE EXISTING** entry |110| Content already fully covered | **REFERENCE ONLY** — skip save |111| Entry exists but wrong scale/domain | **SKIP** — not suitable for current project |112| Entry exists and fits perfectly | **IMPLEMENT** — use this pattern |113114## Format-Aware Save115116When creating a NEW library entry (after search recommends CREATE NEW):117118### Step 1: Auto-Determine Section119120Pick the best matching section based on content type:121122| Content Keywords | Section |123|-----------------|---------|124| System design, patterns, diagrams, architecture | `architecture` |125| UI components, Vue/React, reusable elements | `component` |126| Schema, migrations, queries, relationships | `database` |127| Flowcharts, sequence diagrams, visual flows | `diagram` |128| Third-party API, SDK, webhook, external service | `integration` |129| Auth, RBAC, encryption, guards, middleware | `security` |130| Colors, CSS, Tailwind, glassmorphism, fonts | `theme` |131| CI/CD, deployment, pipelines, automation | `workflow` |132133If content clearly matches — auto-pick (trust-based, no confirmation needed).134If truly ambiguous — pick closest match, note in save confirmation.135136### Step 2: Load Format Template137138Auto-read the matching format from the library's formats directory:139140```141library/formats/142├── architecture-format.md143├── component-format.md144├── database-format.md145├── diagram-format.md146├── integration-format.md147├── security-format.md148├── theme-format.md149└── workflow-format.md150```151152**Path**: `library/formats/[section]-format.md`153154### Step 3: Apply Format155156Use the loaded template's structure:157- Follow the **Required Fields** from the format158- Follow the **Section Order** from the format159- Fill in the **Template** skeleton with actual content160- If no matching format file exists (new section), use a generic markdown structure with title + overview + content + examples161162## Item Install Protocol163164When installing a pre-made library entry from the `library-items/` catalog:165166### Trigger Commands167- `"install item [name]"` — install a specific item by name168- `"install library item [name]"` — explicit library item install169- `"add item from catalog"` — browse and pick an item170171### Install Steps1721731. **Parse item name** from user command (e.g., "install item security-headers" → `security-headers`)1742. **Scan `library-items/`** for matching entry — search by filename keyword across all section folders1753. **If found**: show item info (name, section, first few lines as description preview)1764. **If multiple matches**: list all matches and ask user to pick one1775. **Check for duplicates** in user's `library/[section]/` — match by filename1786. **If no duplicate**: copy file from `library-items/[section]/[filename].md` to `library/[section]/[filename].md`1797. **If duplicate exists**: warn user and ask — overwrite existing entry or skip1808. **Trigger commit chain** (if Auto-Commit installed)181182### Install Report Format183```184Item Install185------------186Item: [item name]187Section: [section name]188Source: library-items/[section]/[filename].md189Target: library/[section]/[filename].md190Status: Installed / Skipped (duplicate) / Not found191192Available items in catalog:193- [section]/[item-name] — [first line description]194```195196## Commit Chain197198After saving or updating a library entry, if the **Auto-Commit System** skill is installed:199- Trigger the auto-commit skill to preserve the library change200- Library save exit = commit entrance. No knowledge left uncommitted.201202If Auto-Commit is not installed, remind the user to commit manually.203204## Mandatory Rules2052061. **Always scan before save** — never create a library entry without checking first2072. **Dynamic discovery** — never hardcode sections or entry counts2083. **Keyword extraction** — derive from topic context, not just exact words2094. **Read matches** — don't just match filenames, read content of top matches2105. **Project-aware** — always consider current project when suggesting suitability2116. **Clear recommendation** — always end with actionable suggestion2127. **Wait for approval** — present findings and wait for the user's decision before saving2138. **Format-aware saves** — always load the matching format template before creating a new entry214215## Edge Cases216217| Situation | Behavior |218|-----------|----------|219| **No library/ directory** | Warn user: "Library directory not found. Run the install protocol first." |220| **Empty library (no entries)** | Skip search, go straight to CREATE NEW recommendation |221| **Format template missing** | Use generic markdown structure (title + overview + content + examples) |222| **Entry name collision** | Append numeric suffix (e.g., `pattern-name-2.md`) |223| **User wants new section** | Create the folder, note that no format template exists for it |224| **Cross-section content** | Pick primary section, note secondary relevance in the entry |225| **Item not found in catalog** | List all available items from `library-items/` |226| **Library not installed** | Warn: "Library directory not found. Install Library System first." |227| **Item already in library** | Ask user: overwrite existing entry or skip |228229## Level History230231- **Lv.1** — Base: Dynamic library scanning + keyword matching + deduplication prevention. Scans library/ at runtime, extracts keywords from topic, matches against filenames and section names, reads top matches to check overlap, reports findings. (Origin: Knowledge reuse system for AI companions)232- **Lv.2** — Project-Aware: Added suitability assessment — considers tech stack, domain, scale, and complexity when recommending library entries for the current project. Entries that exist but don't fit are flagged separately from matches.233- **Lv.3** — Commit Chain: After saving/updating library entries, auto-triggers the Auto-Commit skill (if installed) to commit all changes. Library save exit becomes commit entrance.234- **Lv.4** — Format-Aware Save: Auto-determines library section from content keywords, loads matching format template from `library/formats/[section]-format.md`, applies template structure to new entries. Trust-based section selection (no approval gate). Formats loaded on-demand, not embedded.235- **Lv.5** — Item Install: Install pre-made library entries from `library-items/` catalog. New commands: "install item [name]", "install library item", "add item from catalog". Scans catalog by filename keyword, shows preview, checks for duplicates in user's library, copies to correct section, chains commit. Catalog persists at project root (not deleted during Library System installation). (Origin: Public knowledge sharing for AI MemoryCore community)
Kiyoraka