| name | new-blog-post |
| description | Prepares files for a new blog post — creates the markdown file in content/blog, writes frontmatter, copies media assets, and sets up a branch. Use when starting a new blog post from a .md/.doc file or raw text. |
| argument-hint | [source-file-or-text] |
Prepare the following files for a new blog post. Follow best practices in @AGENTS.md.
First, ensure that the repo is on the main branch and has the latest changes pulled from the remote.
Take any file, like a .md or .doc file, or raw text input, and create a new markdown file in the /content/blog directory.
- Slugify the title for the filename. Only use lower-case characters and hyphens. DO NOT use dates, special characters, or spaces.
- Write the frontmatter metadata using the @AGENTS.md as a guide.
- Add a
tags field with one or more topics from this list (pick all that apply):
"AI & Agents", "Background Jobs & Scheduling", "Company & Product News", "Durable Execution", "Engineering", "Incidents & Security", "Integrations & Partners", "Next.js & Frameworks", "Observability & Debugging", "Queues & Flow Control", "Realtime", "SDKs & Languages", "Tutorials & Guides", "Workflows & Orchestration"- If a new topic is needed, add it here and also update the list in
AGENTS.md.
- Ensure all internal links are relative to the domain, not including
http://www.inngest.com.
- Use Ref Tags (e.g.,
?ref=blog-introducing-checkpointing) on internal links for marketing attribution. The ref tag should be in the format of blog-<slugified-title>.
For all media do the following:
- Create a sub-directory for all blog assets using the sluggified title:
/public/assets/blog/<slugified-title>
- Copy any included media assets into that directory.
- Update all media URLs within the blog post to point to the correct location in the new asset directory.
If assets are copied from a directory, remove those files after they are successfully copied.
- DO NOT modify files outside of the
/content/blog or /public/assets/blog directories unless explicitly asked.
Create a new branch in the format blog/<slugified-title> and stage only the new files.
