[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYRTSN8HS3XPEV83RQV4YA":3,"skill-same:01M7AYRTSN8HS3XPEV83RQV4YA":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7AYRTSN8HS3XPEV83RQV4YA","vault-completion",null,"Fill missing Obsidian vault notes from overview\u002FMOC files with wikilinks, Mermaid diagrams, ASCII removal, cross-vault linking, and content migration from old stubs to new vaults.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fvault-completion\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vault-completion\ndescription: \"Fill missing Obsidian vault notes from overview\u002FMOC files with wikilinks, Mermaid diagrams, ASCII removal, cross-vault linking, and content migration from old stubs to new vaults.\"\n---\n\n# Vault Completion\n\nComplete workflow for filling Panomete's Obsidian vaults from overview files. Covers gap analysis, note format preferences, Mermaid diagram insertion, cross-vault linking, and content migration.\n\n## When to Use\n\n- User has an Overview\u002FMOC file with `[[wikilinks]]` pointing to non-existent notes\n- \"Fill in the missing notes\", \"Complete the vault\", \"Summarize X based on the overview\"\n- User has an old stub note that needs expanding into a full topic vault\n- User wants Mermaid diagrams added to existing pattern\u002Farchitecture notes\n\n## Core Workflow\n\n1. **Read source material** — reference document (SWEBOK chapter, book TOC, website)\n2. **Read the Overview\u002FMOC** — identify dead `[[wikilinks]]` vs existing files\n3. **Present gap analysis** — table: Topic | In Overview? | Has Note? | Status\n4. **Fill missing notes** — synthesize from source + your knowledge. Priority: user-specified URL → provided reference → own knowledge\n5. **Update Overview** — add `[[wikilinks]]` to plain-text headings\n6. **Verify** — run verification script: file count, size >1KB, Sources present, Mermaid valid\n\n## Note Format\n\n- `# Topic N: Title` + brief intro\n- Tables over prose for rules, comparisons, patterns\n- `## When to Use` with categorized examples\n- `## Comparison` for similar\u002Fconfusable concepts (use ❌\u002F✅ pairs)\n- `## Practical Applications` — \"Why This Matters in SE\" or equivalent\n- `⚠️ Target-Audience Traps` — dedicated error-pattern section if teaching specific audience (Thai speakers, etc.)\n- `## Quick Test` — 5 questions with answers\n- `## Sources` — cite reference material\n\n### Style Rules\n- Tables > prose, bold keywords, scannable, practical not academic\n- ❌\u002F✅ pairs for immediate contrast\n- Images: `![](url)` from authoritative sources only — never fabricate URLs\n\n## Directory Structure\n\n- **Category folders** with numbered prefixes: `01 Foundation\u002F`, `02 Tenses & Time\u002F`\n- **Flat files inside** — NOT folder-per-topic. `Topic Name.md` goes directly in its category folder\n- Files numbered for teaching order: `01 Parts of Speech.md`, `02 Articles.md`\n- For sub-topics needing individual files: subfolder with Overview index: `05 12 English Tense\u002F` containing `05 12 English Tense Overview.md` + `05.1 Present Simple.md` through `05.12 Future Perfect Continuous.md`\n- **Sub-topic folder pattern:** when a topic naturally splits into many sub-topics (e.g., 12 tenses, 22 design patterns, 15 UX laws), create a numbered subfolder containing an overview index and individual numbered files. The folder replaces the single `.md` file: `05 12 English Tense\u002F` instead of `05 12 English Tense.md`. Individual sub-topic files use decimal numbering: `05.1`, `05.2`, `05.12`.\n- Overview file lives at vault root OR inside the topic folder (when there are many files)\n\n## Mermaid Diagrams\n\nObsidian renders Mermaid natively. Prefer over ASCII art for design patterns, architecture, flows.\n\n### When to Add Mermaid\n- **classDiagram** — design patterns, OOP, architecture components\n- **sequenceDiagram** — API flows, auth, Saga orchestration, event chains\n- **graph TD\u002FLR** — deployment pipelines, decision trees, protocol flows\n- **stateDiagram-v2** — circuit breaker, order lifecycle, auth states\n\n### GoF Design Pattern Conventions\n- Interfaces: `\u003C\u003Cinterface>>`, Abstract classes: `\u003C\u003Cabstract>>`\n- Relationships: `..>` (Dependency), `-->` (Association), `o--` (Aggregation), `*--` (Composition), `..|>` (Implementation), `\u003C|--` (Inheritance)\n- Keep diagrams focused — pattern participants, not every method\n\n### ASCII Removal Workflow\n1. Add Mermaid alongside existing ASCII — don't delete ASCII yet\n2. Once all files have Mermaid, ASK before stripping ASCII\n3. Batch-remove with Python script using `patch()` or direct file writes\n4. Verify: no `┌└├┐┘┤─│┬┴┼` chars remain\n5. Re-verify: all files still have ````mermaid` blocks, no broken mermaid (plain text inside mermaid fence)\n\n### Mermaid Verification\nCheck all files:\n- ````mermaid` present\n- First line after fence is a valid diagram type\n- No plain text accidentally pulled into mermaid block during edits\n\n## Cross-Vault Linking\n\nWhen a topic spans vaults (programming-note stubs ↔ software-engineering-note deep content):\n1. Identify overlap — compare both vaults\n2. Fill the stub vault with practical notes + Mermaid\n3. Cross-link from overview: \"For philosophy see [[Boundaries]] in Clean Architecture\"\n4. Update Content.md to route to new full notes\n5. Remove old stub after verification\n\n## Content Migration (Stub -> Full Vault)\n\n1. Create `Topic\u002F` folder with overview + category subfolders + numbered topic files\n2. Move content from old stub into new overview (preserve: personal experiments, GitHub links, home server configs)\n3. Update root Content.md to reference `[[Topic Overview]]`\n4. Delete old stub file\n5. Verify: old file gone, folder has correct count, Content.md updated\n\n## Content Hub Pattern (programming-note)\n\nWhen a vault root has a `Content.md` that links to both stubs and full vaults:\n- Rewrite it as a routing table: Topic | Primary Content | Local Note\n- When a stub becomes a full vault, update the routing table — both columns point to `[[New Overview]]`\n- The Content.md becomes a compass: quick stubs for scanning, deep vaults for learning\n- Keep unique local content (personal GitHub repos, home server configs) in the new overview\n\n## Stub Removal Workflow\n\n1. Create full vault folder with overview + category subfolders + numbered topic files\n2. Verify all content from old stub is covered in new vault\n3. Run verification script (file count, Sources sections, Mermaid validity)\n4. Update root Content.md routing table\n5. `rm` the old stub file\n6. Re-verify old stub is gone + Content.md has correct link\n\n## Batch Construction\n\nFor large vaults (>10 files):\n1. Create ALL directories first — single `mkdir -p` with all paths\n2. Write files in parallel batches (write_file is independent per file)\n3. After all writes, run verification script\n4. Update overview and Content.md last\n\n## Verification Script Pattern\n\nUse `execute_code` with tempfile scripts that check:\n- File count matches expected\n- All files > 1KB (not stubs)\n- `## Sources` section present in every file\n- ````mermaid` blocks have valid diagram types (no plain text in mermaid fence)\n- Overview has sufficient wikilinks (≥ half the file count)\n- Content.md references correct overview name\n\n```python\n# Skeleton verification script\nimport os, re, tempfile\nverify = r\"\"\"...checks...\"\"\"\ntmp = os.path.join(tempfile.gettempdir(), \"hermes-verify-\u003Cvault>.py\")\nwith open(tmp, \"w\") as f: f.write(verify)\nrc = os.system(f'python \"{tmp}\"')\nos.remove(tmp)\n```\n\n## Anti-patterns\n\n- Don't build academic syllabi for practical teaching — ask about the target student\n- Don't over-engineer taxonomy — >8 categories is too many. User rejected 8-section English structure.\n- Don't create `Topic\u002FTopic.md` folder-per-file wrappers — flat files in category folders\n- Don't write walls of prose — tables, bullets, headers\n- Don't skip gap analysis — show what's being filled before writing\n- Don't fabricate image URLs — use authoritative sources or skip\n- Don't delete ASCII before Mermaid is confirmed working\n- Don't leave broken Mermaid blocks — verify after edits\n- Don't rename files on disk while also changing wikilinks — use `patch()` on content, `mv` for files, update references after\n- Don't remove the old stub until the new vault is verified complete\n- **Summary vs complete book:** a PDF under 1MB with ~27 pages is a student summary. The user may later provide the 2-8MB, 200+ page complete book. Don't rewrite — add missing chapters and enrich existing files with the full book's depth (personal stories, examples, additional sections). Use `ls -la` to check file size before extraction.\n\n## Bulk Tagging\n\nAdd Obsidian YAML frontmatter `tags: [...]` to all `.md` files based on vault path and folder structure.\n\n### Tag Hierarchy\n- **Vault-level tag** based on root folder: `programming`, `software-engineering`, `fitness`, `english`, `math`\n- **Sub-tags** from folder names: `database`, `api`, `networking`, `book-summary`, `design-patterns`\n- **Book summaries:** add `book-summary` + author tag (`uncle-bob`, `pragmatic-programmer`)\n- **Overview\u002FMOC files:** add `overview` tag\n- **Respect existing frontmatter:** merge new tags into existing YAML frontmatter. Don't overwrite user's existing tags.\n\n### Tag Cleanup\nAfter initial tagging, scan for false matches:\n- `grammar`\u002F`foundation` leaking into software-engineering files (folder name overlap)\n- `discrete-math`\u002F`graphs` hitting GraphQL or database graph files\n- `clean-code` hitting `clean-coder` files\nRemove false matches with a second pass.\n\n### Script Reference\nSee `scripts\u002Ftag-vault.py` for the bulk tagging + cleanup script.\n\n## Wikilink Repair\n\nFind and fix broken `[[wikilinks]]` across all vaults. Obsidian resolves wikilinks by filename (not path), so map broken names to correct filenames.\n\n### Common Breakage Patterns\n- **Wrong chapter numbers:** SWEBOK files reference old numbering (`06_` → `08_`)\n- **Case mismatches:** `[[SOLID Principles]]` → `[[solid-principles]]`\n- **Renamed files:** `[[03 Migration & Versioning]]` → `[[03 Migration Backup & Scaling]]`\n- **Folder links:** `[[01 Gestalt Laws\u002F]]` → `[[01 Law of Proximity]]` (filename-only)\n- **Cross-vault links:** use Obsidian's `..\u002Fvault-name\u002FNote Name` format\n\n### Approach\n1. Build a set of all existing filenames (case-insensitive)\n2. Scan all `.md` files for `[[wikilinks]]`\n3. For each broken link, find the closest matching existing file\n4. Batch-replace with correct targets\n5. Re-scan to verify count goes to zero (except user's personal notes)\n\n### Script Reference\nSee `scripts\u002Ffix-wikilinks.py` for the bulk repair script.\n\n### Script Reference\nSee `scripts\u002Ffix-wikilinks.py` for the bulk repair script.\n\n## Checklist Simplification (Ponytail Mode)\n\nWhen user invokes ponytail skill on checklists: turn overengineered reference manuals into actual tick-box checklists.\n\n### Pattern\n- **Reference manual** (100-300 lines): code examples, version trivia, tutorials, migration notes → stays as reference\n- **Launch checklist** (30-50 lines): `- [ ]` tick boxes, one-liners, `→ [[vault]]` links for deep knowledge\n- Each checklist file lives in its domain folder next to the reference files\n\n### Two-Layer Checklist Architecture\n\nThe generic + framework companion pattern. One framework-agnostic launch checklist, then framework-specific companions that inherit from it:\n\n```\nbackend-checklist\u002F\n├── API Launch.md              ← Generic: tick first, 45 items\n├── spring-boot-api.md          ← Reference manual (263 lines)\n├── fiber-v3-api.md             ← Go\u002FFiber companion, ~80 items\n├── nestjs-api.md               ← NestJS companion, ~75 items\n└── rust-axum-api.md            ← Rust\u002FAxum companion, ~80 items\n\nfrontend-checklist\u002F\n├── Frontend Launch.md          ← Generic: tick first, 48 items\n├── react-js.md                 ← Reference manual (134 lines)\n├── react-js-v2.md              ← React\u002FNext.js launch companion, ~55 items\n├── vue-js.md                   ← Vue 3 + Nuxt companion, ~70 items\n└── angular.md                  ← Angular 17+ companion, ~80 items\n```\n\nEach framework companion: references the generic (`Tick [[API Launch]] first`), adds framework-specific items (middleware chain, DI, build tools), and follows the same section structure as the generic for consistency.\n\n### Rules\n- No code examples in launch checklists (generic or companion)\n- No version-specific trivia\n- No tutorials\n- Every item: `- [ ] Short action → [[vault note]]` for how\n- Keep original deep-reference files — don't delete, just add the slim version\n- Framework companions should have the same top-level sections as the generic for easy cross-referencing\n- After building a companion, **cross-check** all companions in the same domain: if NestJS has a Swagger section but Fiber doesn't, add it to Fiber too\n- When a user asks \"what framework for X?\", give a one-line recommendation with brief rationale before building the checklist\n\n### Pitfalls\n- **Missing form validation:** checklists under \"State & Data\" or \"Forms\" should include both client-side validation (Zod, class-validator) AND server-side re-validation (client UX, server security). User caught this gap in Frontend Launch.\n- **Inconsistent companions:** after creating a new framework companion, scan the others for sections the new one introduced that the old ones lack (e.g., Swagger\u002FOpenAPI, Form validation, Observability)\n","# Vault Completion\n\nComplete workflow for filling Panomete's Obsidian vaults from overview files. Covers gap analysis, note format preferences, Mermaid diagram insertion, cross-vault linking, and content migration.\n\n## When to Use\n\n- User has an Overview\u002FMOC file with `[[wikilinks]]` pointing to non-existent notes\n- \"Fill in the missing notes\", \"Complete the vault\", \"Summarize X based on the overview\"\n- User has an old stub note that needs expanding into a full topic vault\n- User wants Mermaid diagrams added to existing pattern\u002Farchitecture notes\n\n## Core Workflow\n\n1. **Read source material** — reference document (SWEBOK chapter, book TOC, website)\n2. **Read the Overview\u002FMOC** — identify dead `[[wikilinks]]` vs existing files\n3. **Present gap analysis** — table: Topic | In Overview? | Has Note? | Status\n4. **Fill missing notes** — synthesize from source + your knowledge. Priority: user-specified URL → provided reference → own knowledge\n5. **Update Overview** — add `[[wikilinks]]` to plain-text headings\n6. **Verify** — run verification script: file count, size >1KB, Sources present, Mermaid valid\n\n## Note Format\n\n- `# Topic N: Title` + brief intro\n- Tables over prose for rules, comparisons, patterns\n- `## When to Use` with categorized examples\n- `## Comparison` for similar\u002Fconfusable concepts (use ❌\u002F✅ pairs)\n- `## Practical Applications` — \"Why This Matters in SE\" or equivalent\n- `⚠️ Target-Audience Traps` — dedicated error-pattern section if teaching specific audience (Thai speakers, etc.)\n- `## Quick Test` — 5 questions with answers\n- `## Sources` — cite reference material\n\n### Style Rules\n- Tables > prose, bold keywords, scannable, practical not academic\n- ❌\u002F✅ pairs for immediate contrast\n- Images: `![](url)` from authoritative sources only — never fabricate URLs\n\n## Directory Structure\n\n- **Category folders** with numbered prefixes: `01 Foundation\u002F`, `02 Tenses & Time\u002F`\n- **Flat files inside** — NOT folder-per-topic. `Topic Name.md` goes directly in its category folder\n- Files numbered for teaching order: `01 Parts of Speech.md`, `02 Articles.md`\n- For sub-topics needing individual files: subfolder with Overview index: `05 12 English Tense\u002F` containing `05 12 English Tense Overview.md` + `05.1 Present Simple.md` through `05.12 Future Perfect Continuous.md`\n- **Sub-topic folder pattern:** when a topic naturally splits into many sub-topics (e.g., 12 tenses, 22 design patterns, 15 UX laws), create a numbered subfolder containing an overview index and individual numbered files. The folder replaces the single `.md` file: `05 12 English Tense\u002F` instead of `05 12 English Tense.md`. Individual sub-topic files use decimal numbering: `05.1`, `05.2`, `05.12`.\n- Overview file lives at vault root OR inside the topic folder (when there are many files)\n\n## Mermaid Diagrams\n\nObsidian renders Mermaid natively. Prefer over ASCII art for design patterns, architecture, flows.\n\n### When to Add Mermaid\n- **classDiagram** — design patterns, OOP, architecture components\n- **sequenceDiagram** — API flows, auth, Saga orchestration, event chains\n- **graph TD\u002FLR** — deployment pipelines, decision trees, protocol flows\n- **stateDiagram-v2** — circuit breaker, order lifecycle, auth states\n\n### GoF Design Pattern Conventions\n- Interfaces: `\u003C\u003Cinterface>>`, Abstract classes: `\u003C\u003Cabstract>>`\n- Relationships: `..>` (Dependency), `-->` (Association), `o--` (Aggregation), `*--` (Composition), `..|>` (Implementation), `\u003C|--` (Inheritance)\n- Keep diagrams focused — pattern participants, not every method\n\n### ASCII Removal Workflow\n1. Add Mermaid alongside existing ASCII — don't delete ASCII yet\n2. Once all files have Mermaid, ASK before stripping ASCII\n3. Batch-remove with Python script using `patch()` or direct file writes\n4. Verify: no `┌└├┐┘┤─│┬┴┼` chars remain\n5. Re-verify: all files still have ````mermaid` blocks, no broken mermaid (plain text inside mermaid fence)\n\n### Mermaid Verification\nCheck all files:\n- ````mermaid` present\n- First line after fence is a valid diagram type\n- No plain text accidentally pulled into mermaid block during edits\n\n## Cross-Vault Linking\n\nWhen a topic spans vaults (programming-note stubs ↔ software-engineering-note deep content):\n1. Identify overlap — compare both vaults\n2. Fill the stub vault with practical notes + Mermaid\n3. Cross-link from overview: \"For philosophy see [[Boundaries]] in Clean Architecture\"\n4. Update Content.md to route to new full notes\n5. Remove old stub after verification\n\n## Content Migration (Stub -> Full Vault)\n\n1. Create `Topic\u002F` folder with overview + category subfolders + numbered topic files\n2. Move content from old stub into new overview (preserve: personal experiments, GitHub links, home server configs)\n3. Update root Content.md to reference `[[Topic Overview]]`\n4. Delete old stub file\n5. Verify: old file gone, folder has correct count, Content.md updated\n\n## Content Hub Pattern (programming-note)\n\nWhen a vault root has a `Content.md` that links to both stubs and full vaults:\n- Rewrite it as a routing table: Topic | Primary Content | Local Note\n- When a stub becomes a full vault, update the routing table — both columns point to `[[New Overview]]`\n- The Content.md becomes a compass: quick stubs for scanning, deep vaults for learning\n- Keep unique local content (personal GitHub repos, home server configs) in the new overview\n\n## Stub Removal Workflow\n\n1. Create full vault folder with overview + category subfolders + numbered topic files\n2. Verify all content from old stub is covered in new vault\n3. Run verification script (file count, Sources sections, Mermaid validity)\n4. Update root Content.md routing table\n5. `rm` the old stub file\n6. Re-verify old stub is gone + Content.md has correct link\n\n## Batch Construction\n\nFor large vaults (>10 files):\n1. Create ALL directories first — single `mkdir -p` with all paths\n2. Write files in parallel batches (write_file is independent per file)\n3. After all writes, run verification script\n4. Update overview and Content.md last\n\n## Verification Script Pattern\n\nUse `execute_code` with tempfile scripts that check:\n- File count matches expected\n- All files > 1KB (not stubs)\n- `## Sources` section present in every file\n- ````mermaid` blocks have valid diagram types (no plain text in mermaid fence)\n- Overview has sufficient wikilinks (≥ half the file count)\n- Content.md references correct overview name\n\n```python\n# Skeleton verification script\nimport os, re, tempfile\nverify = r\"\"\"...checks...\"\"\"\ntmp = os.path.join(tempfile.gettempdir(), \"hermes-verify-\u003Cvault>.py\")\nwith open(tmp, \"w\") as f: f.write(verify)\nrc = os.system(f'python \"{tmp}\"')\nos.remove(tmp)\n```\n\n## Anti-patterns\n\n- Don't build academic syllabi for practical teaching — ask about the target student\n- Don't over-engineer taxonomy — >8 categories is too many. User rejected 8-section English structure.\n- Don't create `Topic\u002FTopic.md` folder-per-file wrappers — flat files in category folders\n- Don't write walls of prose — tables, bullets, headers\n- Don't skip gap analysis — show what's being filled before writing\n- Don't fabricate image URLs — use authoritative sources or skip\n- Don't delete ASCII before Mermaid is confirmed working\n- Don't leave broken Mermaid blocks — verify after edits\n- Don't rename files on disk while also changing wikilinks — use `patch()` on content, `mv` for files, update references after\n- Don't remove the old stub until the new vault is verified complete\n- **Summary vs complete book:** a PDF under 1MB with ~27 pages is a student summary. The user may later provide the 2-8MB, 200+ page complete book. Don't rewrite — add missing chapters and enrich existing files with the full book's depth (personal stories, examples, additional sections). Use `ls -la` to check file size before extraction.\n\n## Bulk Tagging\n\nAdd Obsidian YAML frontmatter `tags: [...]` to all `.md` files based on vault path and folder structure.\n\n### Tag Hierarchy\n- **Vault-level tag** based on root folder: `programming`, `software-engineering`, `fitness`, `english`, `math`\n- **Sub-tags** from folder names: `database`, `api`, `networking`, `book-summary`, `design-patterns`\n- **Book summaries:** add `book-summary` + author tag (`uncle-bob`, `pragmatic-programmer`)\n- **Overview\u002FMOC files:** add `overview` tag\n- **Respect existing frontmatter:** merge new tags into existing YAML frontmatter. Don't overwrite user's existing tags.\n\n### Tag Cleanup\nAfter initial tagging, scan for false matches:\n- `grammar`\u002F`foundation` leaking into software-engineering files (folder name overlap)\n- `discrete-math`\u002F`graphs` hitting GraphQL or database graph files\n- `clean-code` hitting `clean-coder` files\nRemove false matches with a second pass.\n\n### Script Reference\nSee `scripts\u002Ftag-vault.py` for the bulk tagging + cleanup script.\n\n## Wikilink Repair\n\nFind and fix broken `[[wikilinks]]` across all vaults. Obsidian resolves wikilinks by filename (not path), so map broken names to correct filenames.\n\n### Common Breakage Patterns\n- **Wrong chapter numbers:** SWEBOK files reference old numbering (`06_` → `08_`)\n- **Case mismatches:** `[[SOLID Principles]]` → `[[solid-principles]]`\n- **Renamed files:** `[[03 Migration & Versioning]]` → `[[03 Migration Backup & Scaling]]`\n- **Folder links:** `[[01 Gestalt Laws\u002F]]` → `[[01 Law of Proximity]]` (filename-only)\n- **Cross-vault links:** use Obsidian's `..\u002Fvault-name\u002FNote Name` format\n\n### Approach\n1. Build a set of all existing filenames (case-insensitive)\n2. Scan all `.md` files for `[[wikilinks]]`\n3. For each broken link, find the closest matching existing file\n4. Batch-replace with correct targets\n5. Re-scan to verify count goes to zero (except user's personal notes)\n\n### Script Reference\nSee `scripts\u002Ffix-wikilinks.py` for the bulk repair script.\n\n### Script Reference\nSee `scripts\u002Ffix-wikilinks.py` for the bulk repair script.\n\n## Checklist Simplification (Ponytail Mode)\n\nWhen user invokes ponytail skill on checklists: turn overengineered reference manuals into actual tick-box checklists.\n\n### Pattern\n- **Reference manual** (100-300 lines): code examples, version trivia, tutorials, migration notes → stays as reference\n- **Launch checklist** (30-50 lines): `- [ ]` tick boxes, one-liners, `→ [[vault]]` links for deep knowledge\n- Each checklist file lives in its domain folder next to the reference files\n\n### Two-Layer Checklist Architecture\n\nThe generic + framework companion pattern. One framework-agnostic launch checklist, then framework-specific companions that inherit from it:\n\n```\nbackend-checklist\u002F\n├── API Launch.md              ← Generic: tick first, 45 items\n├── spring-boot-api.md          ← Reference manual (263 lines)\n├── fiber-v3-api.md             ← Go\u002FFiber companion, ~80 items\n├── nestjs-api.md               ← NestJS companion, ~75 items\n└── rust-axum-api.md            ← Rust\u002FAxum companion, ~80 items\n\nfrontend-checklist\u002F\n├── Frontend Launch.md          ← Generic: tick first, 48 items\n├── react-js.md                 ← Reference manual (134 lines)\n├── react-js-v2.md              ← React\u002FNext.js launch companion, ~55 items\n├── vue-js.md                   ← Vue 3 + Nuxt companion, ~70 items\n└── angular.md                  ← Angular 17+ companion, ~80 items\n```\n\nEach framework companion: references the generic (`Tick [[API Launch]] first`), adds framework-specific items (middleware chain, DI, build tools), and follows the same section structure as the generic for consistency.\n\n### Rules\n- No code examples in launch checklists (generic or companion)\n- No version-specific trivia\n- No tutorials\n- Every item: `- [ ] Short action → [[vault note]]` for how\n- Keep original deep-reference files — don't delete, just add the slim version\n- Framework companions should have the same top-level sections as the generic for easy cross-referencing\n- After building a companion, **cross-check** all companions in the same domain: if NestJS has a Swagger section but Fiber doesn't, add it to Fiber too\n- When a user asks \"what framework for X?\", give a one-line recommendation with brief rationale before building the checklist\n\n### Pitfalls\n- **Missing form validation:** checklists under \"State & Data\" or \"Forms\" should include both client-side validation (Zod, class-validator) AND server-side re-validation (client UX, server security). User caught this gap in Frontend Launch.\n- **Inconsistent companions:** after creating a new framework companion, scan the others for sections the new one introduced that the old ones lack (e.g., Swagger\u002FOpenAPI, Form validation, Observability)\n",{"name":5,"description":7},"main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fhermes-main-profile\u002Fvault-completion",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add oat431\u002Fhermes_config_backup --skill vault-completion",{"tool":39,"command":40},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill vault-completion",{"tool":42,"command":43},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill vault-completion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fvault-completion\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fmermaid-verify.py","SCRIPT","脚本",2316,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fvault-completion\u002Freferences\u002Fmermaid-verify.py",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"scripts\u002Ffix-wikilinks.py",4695,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fvault-completion\u002Fscripts\u002Ffix-wikilinks.py",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Ftag-vault.py",6373,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fvault-completion\u002Fscripts\u002Ftag-vault.py",[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]