create-content-component

Generate Strapi schemas and Next.js React components for content components.

5|4|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/strapi/website --skill create-content-component
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-content-component
Source: https://github.com/strapi/website/tree/main/.agents/skills/create-content-component
Command: npx skills add https://github.com/strapi/website --skill create-content-component

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of new content components, ensuring consistency across both your Strapi backend and Next.js frontend, and preventing redundant code.

Core Features & Use Cases

  • Dual-Platform Component Creation: Generates necessary files for both Strapi (schema) and Next.js (React component).
  • Intelligent Reuse: Prioritizes reusing existing utility components to maintain a DRY codebase.
  • Deterministic Conflict Resolution: Automatically handles existing components by reusing, extending, or creating new versions, avoiding user prompts.
  • Use Case: When adding a new "testimonial" section to your website, this Skill will create the sections.testimonials schema in Strapi and the StrapiTestimonials React component in your UI, linking them seamlessly.

Quick Start

Create a new page builder component named 'featured-products' in the 'sections' category with 'name', 'description', and 'image' attributes.

Frequently Asked Questions about create-content-component

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

FAQPage Schema
How do I create Strapi content components and Next.js React components together?

To create Strapi content components and Next.js React components together, this Skill automates schema generation and React component scaffolding simultaneously. It links both platforms seamlessly by registering dynamic zones and deriving attributes, ensuring your page builder interfaces are immediately ready for use.

What is the best way to manage code reuse when building Strapi and Next.js page builder components?

The best way to manage code reuse for Strapi and Next.js page builder components is using intelligent reuse prioritization. This approach automatically detects existing utility components and applies deterministic conflict resolution to reuse, extend, or create new versions without prompting, maintaining a DRY codebase.

Can I generate a Next.js component and Strapi schema for a custom category automatically?

Yes, you can generate a Next.js component and Strapi schema for a custom category automatically. The Skill supports custom categories and attribute derivation, allowing you to specify a category like 'sections' and define attributes to scaffold both the backend schema and frontend UI instantly.

Does this component generation approach handle naming conflicts between existing Strapi schemas and Next.js UI?

Yes, this component generation approach handles naming conflicts deterministically. It automatically resolves conflicts between existing Strapi schemas and Next.js UI components by reusing, extending, or creating new versions, entirely avoiding user prompts and ensuring smooth dual-platform component management.

How do I add a new dynamic zone section to a Strapi and Next.js monorepo?

To add a new dynamic zone section to a Strapi and Next.js monorepo, the Skill handles dynamic zone registration automatically. It scaffolds the necessary React component and generates the corresponding Strapi schema, ensuring the new section integrates seamlessly into your page builder interfaces.

Why does generating UI components separately for Strapi and Next.js cause redundant code?

Generating UI components separately for Strapi and Next.js causes redundant code because backend schemas and frontend interfaces become out of sync. This Skill prevents redundancy by streamlining creation across both platforms, prioritizing existing utility reuse, and ensuring consistency between schema attributes and React components.