| name | nami-blog-manager |
| description | Manage the Nami Blog at anoochit/namiBlog. Use this for creating new posts, maintaining the index, and deploying changes. |
Nami Blog Manager
Manage blog posts, rebuild navigation, validate metadata, and deploy updates automatically.
Config
Load repository + path configuration from:
references/config.md
Repository Structure
blog/
├── index.md
└── posts/
├── YYYY-MM-DD-title.md
└── ...
Core Behavior
- Automate whenever safe.
- Minimize unnecessary questions.
- Preserve existing content unless editing explicitly.
- Keep Markdown Obsidian-compatible.
- Keep
blog/index.md synchronized with posts.
- Rebuild index before every deployment.
- Never deploy inconsistent state.
Post Rules
Filename
Format:
YYYY-MM-DD-slug.md
Example:
2026-05-13-fastmcp-tools.md
Slug Rules
Convert titles into URL-safe slugs:
- lowercase
- hyphen-separated
- remove symbols/special chars
- collapse duplicate hyphens
Example:
"Hello MCP World!" → hello-mcp-world
Duplicate Handling
If filename already exists:
hello-world.md
hello-world-2.md
hello-world-3.md
Frontmatter Schema
Every post must include:
---
title: Post Title
date: YYYY-MM-DD
tags:
- tag1
- tag2
---
Optional fields may be preserved if already present.
Workflows
1. Create Post
Flow
- Generate slug from title.
- Generate unique filename.
- Save file to
blog/posts/.
- Add valid YAML frontmatter and Markdown content.
- Trigger:
- Validate (Post Only)
- Rebuild Index (Incremental)
2. Update Post
Flow
- Locate target post.
- Preserve untouched sections.
- Update requested content only.
- Validate frontmatter (Post Only).
- Trigger Rebuild Index (Incremental).
3. Validate Posts
Modes
- Full Mode: Scan all files (Default).
- Targeted Mode: Validate modified/new file only (Optimization).
Recovery
- Auto-repair metadata.
- Report issues for unrecoverable errors.
4. Rebuild Index
Optimization
- Incremental Update: Refresh only the entry for the modified post.
- Full Rebuild: Required for bulk structural changes.
Output Format
- [Post Title](posts/YYYY-MM-DD-slug.html) (YYYY-MM-DD)
Important
GitHub Pages resolves Markdown as HTML.
Always use:
posts/file.html
Never:
posts/file
posts/file.md
5. Deploy
Preconditions
Before deployment:
- index rebuilt
- validation passed
- no partial updates
Flow
- Consolidate modified files.
- Push via:
mcp_push_files
- Repository:
anoochit/namiBlog
- Branch:
blog
Commit Message Rules
Format:
Blog: [Action] - [Details]
Examples:
Blog: Add post - FastMCP Tools
Blog: Update index - Latest posts
Blog: Fix typo - Agent Memory
Execution Pipeline
Create / Update Post
↓
Validate (Modified Only)
↓
Update Index (Incremental)
↓
Deploy
Note: Use --no-rebuild flag to bypass validation/index update during bulk operations.
Safety Rules
- Never deploy broken indexes.
- Never overwrite unrelated content.
- Never remove metadata silently.
- Never deploy partially processed posts.
- Skip corrupted files safely when unrecoverable.
- Prefer repair over failure.
Output Style
- concise
- structured
- automation-first
- deterministic formatting
- clean Markdown only
