// MDX article conventions for DevVerse. Use when adding or editing files under content/, changing article metadata, updating author or date lines, or modifying code that parses article content for feeds, related posts, reading stats, or RAG ingestion.
MDX article conventions for DevVerse. Use when adding or editing files under content/, changing article metadata, updating author or date lines, or modifying code that parses article content for feeds, related posts, reading stats, or RAG ingestion.
Feed, sitemap, metadata, and publishing guidance for DevVerse. Use when modifying lib/rss.ts, lib/jsonfeed.ts, feed routes, next-sitemap.config.js, app/layout.tsx metadata, manifest or robots files, or SEO-related site metadata.
DevVerse chat, citation, and retrieval workflow. Use when modifying the chat page, the chat API route, citation parsing, local retrieval fallback, Pinecone or Gemini integration, or the article vectorization pipeline.
Refresh Pinecone article embeddings after MDX article changes or RAG chunking and metadata changes. Use when content updates should be reflected in chat retrieval or when the vectorization pipeline changes.
Supabase auth, favorites, and security boundaries for DevVerse. Use when changing files under supabase/, auth or favorites UI, or the verify-email and reset-password API routes.
Route and UI conventions for the DevVerse Next.js app. Use when modifying app routes, layout, navigation, page components, global styling, route-scoped CSS, article rendering, favorites UI, or chat UI.
| name | devverse-content-mdx |
| description | MDX article conventions for DevVerse. Use when adding or editing files under content/, changing article metadata, updating author or date lines, or modifying code that parses article content for feeds, related posts, reading stats, or RAG ingestion. |
| user-invocable | false |
Treat content/*.mdx as the canonical article store.
Do not model article changes around supabase/articles.sql; runtime content comes from MDX files.
Keep the article contract stable.
Use a literal export const metadata = { title, description, topics };, keep ### Author: ..., keep > Date: YYYY-MM-DD, and keep the article body starting with a top-level # heading.
Use the checked-in template when creating a new article. @templates/article-template.mdx
Read the contract notes before changing metadata conventions. @references/article-contract.md
If you change metadata shape or article template rules, update every dependent parser in the same task.
After content edits, run python3 .claude/scripts/check_content_contract.py.
After content edits that should affect chat retrieval, consider devverse-refresh-vectors.
