tina-cms

Update TinaCMS collections and visual-editing workflows in Next.js App Router repositories.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/git-bhanu/prasun1111 --skill tina-cms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tina-cms
Source: https://github.com/git-bhanu/prasun1111/tree/main/.agents/skills/tina-cms
Command: npx skills add https://github.com/git-bhanu/prasun1111 --skill tina-cms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about tina-cms

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

FAQPage Schema
How do I update TinaCMS collections without breaking Next.js App Router data flow?

To update TinaCMS collections safely, modify the relevant tina/config.tsx and content documents while ensuring affected page.tsx and client-page.tsx files maintain the correct useTina({ query, data, variables }) pattern. Run pnpm exec tsc --noEmit to verify schema-to-renderer alignment.

What's the best way to add new fields to TinaCMS content models?

Add or modify fields directly in your tina/config.tsx collection definitions and content documents. Ensure rendering logic matches the updated schema and run type checks to confirm generated types remain consistent across your Next.js repository.

Does TinaCMS generated output need manual edits in a Next.js project?

TinaCMS generated files in the tina/__generated__ directory should never be edited directly. Always modify source collection files and let Tina generate the types and output deterministically to prevent schema-to-renderer misalignment.

Why does my TinaCMS visual editing break after changing content models?

TinaCMS visual editing breaks when server/client component splits are incorrect. Data must be fetched in server routes, and useTina({ query, data, variables }) must be wired only in client components to maintain proper editing behavior.

Can I use TinaCMS with existing Next.js App Router conventions and patterns?

TinaCMS integrates with existing Next.js App Router conventions by preserving your current patterns. It enforces deterministic Tina config alignment and correct generated type imports without forcing structural changes to your repository.