What problem does it solve?
This skill helps you change TinaCMS content models and visual-editable pages without breaking the repo’s Next.js + App Router data flow, generated types, or editing behavior.
Core Features & Use Cases
- Schema-driven Tina updates: Add or modify collections, fields, templates, and rendering logic while keeping types and generated output consistent.
- Correct server/client split for visual editing: Fetch Tina data in server routes and wire
useTina() only in client components with query, data, and variables.
- Safe alignment with repo patterns: Avoid editing
tina/__generated__, preserve existing conventions, and verify with type checks and build steps.
Quick Start
Make the Tina-backed change by updating the relevant tina/config.tsx/collection files and any content/ documents, then ensure the affected page.tsx and client-page.tsx follow the required useTina({ query, data, variables }) pattern and run pnpm exec tsc --noEmit.