Use when working in the Unbili MkDocs notes repository to follow the project's maintenance, validation, deployment, and logging conventions. Trigger for content edits, theme/config changes, workflow updates, or site publishing in this repo.
Resources
10Install
npx skillscat add walkindadhh/notes Install via the SkillsCat registry.
SKILL.md
Unbili Maintainer
This repository is a MkDocs + Material notes site rooted at D:\Unbili.
Before changing repository conventions, deployment behavior, structure, or content patterns, read:
README.mdMAINTENANCE_LOG.md.claude/commands/notes-guide.mdscripts/validate-mkdocs.ps1when build validation is relevant
Core rules
- Do not leave partial edits in
docs/ormkdocs.ymlif the task is meant to be published. - Prefer
scripts/validate-mkdocs.ps1for validation when you do not want to refresh trackedsite/. - Use plain
mkdocs buildonly when you intentionally want updated generated output insite/. - Do not disable or rewrite the repository's established deploy workflow unless the owner explicitly asks for that.
Maintenance log policy
- Any important update must be recorded in
MAINTENANCE_LOG.mdbefore ending the task. - Treat these as important updates by default:
- content changes with visible user-facing impact
- style or theme changes
- navigation or structure changes
- workflow, script, or deployment changes
- publishing/deployment actions
- When in doubt, append a short log entry instead of skipping it.
Deployment workflow
- Validate locally first when practical.
- If publishing is intended, follow the repository's current deployment flow and ensure the published result matches the edited source.
Editing scope
- Reuse existing note patterns and admonition styles instead of inventing one-off formats.
- Keep repository conventions synchronized across
SKILL.md,README.md,.claude/commands/notes-guide.md, andMAINTENANCE_LOG.mdwhen relevant.