Update MD
VerifiedCreate or update project documentation in Markdown. Use when building a new project doc set, updating existing docs after a deploy or feature change, or esta...
$ Add to .claude/skills/ About This Skill
# update-md
Core Principles
- Split, don't consolidate — One file per concern. Never dump everything into one doc.
- Overview is always the entry point — Every project has a `PROJECT-OVERVIEW.md` that's lean and links to everything else.
- 按需讀取 — Detail files are only read when needed; keep them out of the overview.
- Update rules are mandatory — Every doc set must define when each file should be updated.
- Deploy = Update docs — Docs update immediately after every deploy. No exceptions.
Standard Doc Set Structure
Every project follows this pattern:
``` PROJECT-OVERVIEW.md ← 精簡總覽,每 session 必讀 PROJECT-DEPLOY.md ← 部署、Docker、Nginx、SSL、環境變數 PROJECT-APPS.md ← 功能規格(如有多個 app/module) PROJECT-DB.md ← 數據庫 schema 及連接設定 PROJECT-HISTORY.md ← 版本日誌,每次 deploy 後更新 ```
Add or remove files based on project complexity. See `references/doc-templates.md` for file templates.
OVERVIEW.md Must-Haves
- Project name, domain/URL, status, VM/hosting info
- Feature/tool status table (✅ / 🔄 / ⏳ / ❌)
- Doc map table (file → content)
- Update rules table (change type → files to update)
- Current version number
Update Rules (include in every OVERVIEW.md)
| 改動類型 | 需要更新 | |----------|----------| | 新功能 / 改功能 | OVERVIEW(狀態)+ APPS | | 新版本發布 | HISTORY + OVERVIEW(版本號)| | 部署/基礎設施改動 | DEPLOY | | DB schema 改動 | DB |
Status Symbols
Use consistently across all docs:
- ✅ 完成
- 🔄 進行中
- ⏳ 待開始
- ❌ 取消 / 廢棄
When Updating Docs
- Identify which files are affected by the change (use the update rules table)
- Update only those files — don't touch unrelated docs
- Update version number in OVERVIEW if it's a release
- Add entry to HISTORY with date, version, and bullet points
Creating a New Doc Set
- Create `PROJECT-OVERVIEW.md` first — establish the doc map before writing detail files
- Add detail files as needed (DEPLOY, APPS, DB, HISTORY)
- Add the doc map to the project's `AGENTS.md` so agents know which files exist
- Reference `references/doc-templates.md` for boilerplate
See `references/doc-templates.md` for ready-to-use file templates.
Use Cases
- Create structured Markdown documentation for new software projects
- Update existing project docs after deploys, feature changes, or architecture updates
- Generate standardized README files with consistent formatting and sections
- Maintain living documentation that stays in sync with code changes
- Build documentation sets covering setup, usage, API reference, and architecture
Pros & Cons
Pros
- +Covers both creation and maintenance of project documentation
- +Supports post-deploy and post-feature documentation updates
- +Markdown format is universal and works with all documentation platforms
Cons
- -Generic documentation tool — no specialized templates or framework-specific sections
- -No automated code-to-doc synchronization
FAQ
What does Update MD do?
What platforms support Update MD?
What are the use cases for Update MD?
100+ free AI tools
Writing, PDF, image, and developer tools — all in your browser.
Next Step
Use the skill detail page to evaluate fit and install steps. For a direct browser workflow, move into a focused tool route instead of staying in broader support surfaces.