Loading...
Loading...
Found 3 Skills
Review a Prepr CMS schema, live or as schema files in prepr/schema/, and report what to improve. Use this skill whenever the user wants to review, audit, or improve a Prepr content model, asks "is this schema any good", wants a second opinion before content is added, or inherits an environment and wants to understand its model. Makes no changes; fixes go through create-schema.
Build or change a Prepr CMS content model, either live in an environment through the MCP server or as JSON schema files in prepr/schema/ for Git sync. Use this skill whenever the user wants to create or modify a model, component, enum, or field, turn an agreed content model plan into a working schema, add a content type to an existing Prepr environment or schema files, or apply a fix from a schema review. For deciding what the model should be from a vague brief, the design-schema skill applies first.
Set up and run Git-backed schema sync between a repository and Prepr CMS environments, with schema files in prepr/schema/. Use this skill whenever the user wants to sync a Prepr schema via GitHub, GitLab, Bitbucket or Azure DevOps, get local schema file changes into a Prepr environment, export an environment's schema to the repository, promote schema between development, acceptance and production, add schema validation to CI, debug a schema import that fails or returns github.validation.failed, check whether the schema files and an environment have drifted, or asks why schema file edits have not appeared in Prepr. Also use it when the user considers direct environment-to-environment sync.