content-generator

Standardize SnipGeek blog and note content with MDX components and SEO frontmatter.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ieproject-app/SnipGeek --skill content-generator-ieproject-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-generator
Source: https://github.com/ieproject-app/SnipGeek/tree/main/.agent/skills/content-generator
Command: npx skills add https://github.com/ieproject-app/SnipGeek --skill content-generator-ieproject-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and standardizes SnipGeek content generation for blogs and notes, ensuring consistent MDX components, SEO frontmatter, tag standardization, and proper file placement.

Core Features & Use Cases

  • Enforces root-level content folders (_posts, _notes, _pages) and mandatory semester subfolders (YYYY-H1, YYYY-H2) to organize content chronologically.
  • Distinguishes blog posts from technical notes, applying respective frontmatter and bilingual requirements, and guiding MDX component usage.
  • Provides a reusable blueprint for content creation and modification, ensuring consistent metadata, tag rules, and hero-image handling.

Quick Start

Write a new blog post in _posts/en/2026-H1/your-slug.mdx following the standard frontmatter and MDX structure.

Frequently Asked Questions about content-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize SEO frontmatter for MDX blog posts and notes?

Standardize SEO frontmatter for MDX blog posts and notes by enforcing kebab-case slugs, a heroImage field for blogs, 3–6 tags, and mandatory semester folders (YYYY-H1 or YYYY-H2) based on the date field.

What's the best way to organize MDX content folders chronologically by semester?

Organize MDX content chronologically by placing files into root-level _posts or _notes directories, then sorting them into mandatory semester subfolders derived from the date field (YYYY-H1 or YYYY-H2).

Do I need a specific tag structure for bilingual EN and ID MDX content?

Bilingual EN and ID MDX content requires 3–6 standardized tags, including a platform tag and a versioned tag when the content is OS-specific, ensuring consistent categorization across both languages.

Why does my generated blog post need a hero image in the frontmatter?

A generated blog post needs a heroImage frontmatter field to meet SnipGeek content rules, which distinguish blog posts from technical notes and enforce specific metadata requirements for visual consistency.

Can I use kebab-case slugs for root-level content pages and technical notes?

Yes, you can and must use kebab-case slugs for root-level content pages and technical notes to enforce standardization, alongside applying respective frontmatter and bilingual requirements to _pages and _notes directories.

What are the limitations of automated content generation for MDX files?

Automated content generation for MDX files is limited to EN and ID outputs under _posts and _notes, restricting file placement to root-level directories and enforcing strict semester folder structures without flexible path overrides.