create-complementary

Generate Strapi CMS schemas, TypeScript types, and GraphQL fragments for complementary components.

2|3|Updated May 19, 2022
One-click install
npx skills add https://github.com/SKLINET/strapi-boilerplate --skill create-complementary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-complementary
Source: https://github.com/SKLINET/strapi-boilerplate/tree/main/.cursor/skills/create-complementary
Command: npx skills add https://github.com/SKLINET/strapi-boilerplate --skill create-complementary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of reusable Strapi complementary components by automating the generation of CMS schemas, TypeScript types, and GraphQL fragments, reducing boilerplate and ensuring consistent project structure.

Core Features & Use Cases

  • Automated component scaffolding for CMS schema, TypeScript types, and GraphQL fragments
  • Consistent naming, fragment generation, and transformer boilerplate
  • Use case: rapidly add reusable components like buttons, videos, or forms across blocks and content types

Quick Start

Create a new complementary component by following the guided prompts to generate the CMS schema, TypeScript types, and GraphQL fragments.

Frequently Asked Questions about create-complementary

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

FAQPage Schema
How do I generate a Strapi component schema with TypeScript types and GraphQL fragments?

You can scaffold a Strapi complementary component with TypeScript types and GraphQL fragments by following guided prompts that generate the CMS schema and update fragments and transformers automatically.

What is a complementary component in Strapi for frontend reuse?

A Strapi complementary component is a reusable UI block with an automated CMS schema, TypeScript types, and GraphQL fragments designed for consistent frontend integration across content types.

Can I use this to create reusable UI components across multiple Strapi content types?

Yes, you can scaffold reusable UI components for multiple Strapi content types by generating shared CMS schemas, TypeScript types, and GraphQL fragments that integrate across blocks and content types.

Does the scaffolding process validate component name uniqueness in Strapi?

Yes, the scaffolding process validates component name uniqueness in Strapi to prevent schema conflicts and ensure that generated TypeScript types and GraphQL fragments maintain a consistent project structure.

What's the best way to add GraphQL fragments when extending a Strapi boilerplate?

The best way to add GraphQL fragments when extending a Strapi boilerplate is to use automated scaffolding that generates fragments alongside TypeScript types and CMS schemas while updating transformers for consistent frontend integration.