skills.rest
LeonardoTan19
LeonardoTan19COMMUNITY
Explore all skills by this author →
GitHub

backend-schema

Applies content-type schemas from a design doc to Strapi via strapi-mcp.

2|1|Updated May 1, 2026
Search Tags:#deployment#backend#schema#phased#content-type#strapi
One-click install
npx skills add https://github.com/LeonardoTan19/metaforge --skill backend-schema
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-schema
Source: https://github.com/LeonardoTan19/metaforge/tree/main/skills/backend-schema
Command: npx skills add https://github.com/LeonardoTan19/metaforge --skill backend-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables safe, structured execution of Strapi content-type schema changes by following a design-driven, two-phase workflow, ensuring deploy integrity and traceability.

Core Features & Use Cases

  • Strict two-phase staging: Stage changes and then commit them in a single batch to minimize risk.
  • Design-driven execution: Load the content-type spec from docs/metaforge/specs/ and apply changes without redesign.
  • Process transparency: Enforces readback of current schema and review steps before changes are applied.

Quick Start

Load the design doc from docs/metaforge/specs/ and execute the Phase A Stage followed by Phase B Commit to apply the content-type schema changes to your Strapi backend.

Frequently Asked Questions about backend-schema

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

FAQPage Schema
How do I apply Strapi content-type schema changes across environments safely?▼

Strapi content-type schema changes require a complete design doc at docs/metaforge/specs/, a running Strapi backend, and access to strapi-mcp tooling to stage and commit batch updates.

What is the safest way to update Strapi content types from a design doc?▼

Design-driven schema execution enforces readback of the current Strapi schema and requires review steps before changes are applied, ensuring process transparency and safe deployment.

How does two-phase staging work for Strapi schema execution?▼

The two-phase staging process enforces readback of current schemas and review steps before applying changes, ensuring process transparency and safe content-type updates.

Do I need a running Strapi backend to sync content-type schemas via strapi-mcp?▼

You also need a complete design doc at docs/metaforge/specs/ to ensure design-driven execution without redesigning the content-type spec.

When should I use phased schema execution for Strapi content types?▼

This approach is applicable when you have a complete design doc and need to minimize risk by batching Strapi content-type schema changes into a single commit.

Related Skills

Explore More Software Engineering Skills→
LeonardoTan19LeonardoTan19
2

brainstorming

Guide collaborative brainstorming to produce formal design documents and implementation handoffs.

Community
Advanced
LeonardoTan19LeonardoTan19
2

api-client-gen

Generate a typed TypeScript API client from Strapi content-type schemas and route contracts.

Community
Advanced
strapistrapi
5

seed-content

Scrape strapi.io content, map it to local Strapi schemas, and seed via MCP.

Official
Advanced
jtucker9jtucker9

migration-planner

Generate ordered migration scripts and rollback plans from schema diffs.

Community
Advanced