// 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-ui-routes |
| description | 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. |
Preserve the split between / and /home.
/ is the landing page with no navbar. /home is the article index.
Preserve the route wrappers.
ConditionalNavbar and ConditionalMain are architectural, not cosmetic.
Keep styling aligned with the repo's actual patterns.
Prefer app/globals.css, route-scoped CSS, and existing inline styles over introducing Tailwind-first rewrites.
Preserve the dark-mode chain.
Keep the inline boot script, the dark class on <html>, the CSS variables in app/globals.css, and DarkModeProvider in sync.
Preserve article DOM contracts.
Do not remove .mdx-container, and do not casually change the h2 and h3 structure used by TableOfContents.
Read the route map before broad UI work. @references/route-map.md
Run repo-aware validation after meaningful UI or route changes.
Use the devverse-validate skill or run the relevant checks directly.
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.
Run repository-specific validation for DevVerse changes. Use when asked to test, validate, smoke check, or confirm modifications in this repository.