readme-pages Publishing Skill
Create publish-ready Markdown files for the readme-pages Astro site.
Content Locations
- •
src/content/notes/— dated notes/essays (default) - •
src/content/recipes/— cooking recipes - •
src/content/pages/— site pages (only when explicitly requested)
Workflow
- •Determine content type (note, recipe, or page)
- •Generate filename:
YYYY-MM-DD-slug.mdusing Europe/Copenhagen date - •Create frontmatter + content following templates
- •Save to
/mnt/user-data/outputs/and present file
Filename Rules
Pattern: YYYY-MM-DD-slug.md
Slug requirements:
- •Lowercase only (a-z, 0-9, hyphen)
- •No spaces, underscores, or dots
- •3-8 words, hyphen-separated
Frontmatter
Notes (required fields)
yaml
--- title: "Title Here" date: 2025-12-26 description: "1-2 sentence summary." tags: ["tag-one", "tag-two"] ---
Recipes (additional fields)
yaml
--- title: "Recipe Title" date: 2025-12-26 description: "Short description." tags: ["dessert", "baking"] prepTime: "15 minutes" cookTime: "30 minutes" servings: 4 difficulty: "easy" ---
Critical Rules
- •Title only in frontmatter — never repeat as
# Titlein body - •Body starts with intro paragraph, first heading is
##(H2) - •Tags must be kebab-case — see
references/tags.mdfor current taxonomy - •Always output downloadable file — save to outputs directory
Content Structure
Notes
- •Intro (2-4 sentences)
- •Main content with H2/H3 sections
- •"What to do next" (3-7 bullets) for how-to posts
- •"Sources" if citing external facts
Recipes
- •Intro (1-2 sentences about the dish)
- •
## Ingredients(with sublists for categories) - •
## Instructions(numbered steps) - •
## Tips(optional) - •
## Storage(optional)
Voice
- •Practical, direct, specific
- •Enterprise-leaning (architecture, tradeoffs, verification)
- •Avoid hype; focus on what to do and how to validate
- •Use examples over abstractions
Templates
See references/examples.md for copy-paste templates.
Tag Selection
See references/tags.md for current taxonomy. Use 2-6 tags. Prefer existing tags.