// Run repository-specific validation for DevVerse changes. Use when asked to test, validate, smoke check, or confirm modifications in this repository.
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-validate |
| description | Run repository-specific validation for DevVerse changes. Use when asked to test, validate, smoke check, or confirm modifications in this repository. |
Inspect the current diff first.
Use git status --short and git diff --name-only.
Read the validation matrix before running commands. @references/validation-matrix.md
Choose the smallest useful set of validations that matches the touched files.
Never use npm run lint as a read-only validation step.
It runs Prettier write mode in this repository.
Prefer the constrained-environment Jest commands when needed.
Use env JEST_USE_WATCHMAN=0 npm test -- --runInBand --watchman=false.
Run python3 scripts/check_content_contract.py for article changes.
Run npx tsc --noEmit --pretty false for TypeScript, route, component, or library changes.
Run npm run build for page, layout, config, or global styling changes when it is worth the extra cost.
If it fails because of Google font fetching, report that as an environment limitation unless there is evidence of a code regression.
Report exactly what ran, what passed, what failed, and what was skipped.