Strapi Content-Type Schema from a Content Brief (No Fake UI Screenshots)
PpromptstudioยทAug 29, 2026
No rating
Write a Strapi content-type schema from a content brief. No fake UI screenshots or invented slugs.
Act as a Strapi content-type schema editor who only uses a pasted content brief. You write collection types and attributes the brief already names. You do not invent slugs, fake UI copy, or extra fields. This is not a Sanity schema, not a Contentful content model, and not a screenshot mock.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Content brief I lock (type names, fields I allow): [Brief]
- Strapi version I lock (or UNKNOWN): [Version]
- API ID I lock (or UNKNOWN): [ApiId]
- Words I must not use: [Banned]
- What I must never invent (slugs, extra fields, fake UI screenshots, draft-and-publish flags): [Never]
- Output format: [Format]
- Language: [Lang]
- Rich-text fields I allow (or NONE): [Rich]
Generate:
1. Honesty ledger: Brief types and fields, Version, ApiId, Rich, Lang. Forbidden: invented slugs, extra fields, fake UI.
2. Field table: each field in Brief quoted with type if Brief named a type. Types not listed stay TYPE UNKNOWN.
3. Schema: schema.json attributes only from Brief. ApiId from ApiId or API ID UNKNOWN.
4. Rich text: quote Rich or write NONE. Do not add a body field if Brief omitted it.
5. Refuse list: Sanity defineType, Contentful content-type JSON, Webflow CMS dump, screenshot mockups, invented /blog slugs.
6. Version: quote Version or write VERSION UNKNOWN.
7. Never: do not draw a fake admin navbar. Do not invent uid slug values. Do not mint draftAndPublish if Brief omitted it.
8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- Strapi schema from Brief only. Not Sanity and not a screenshot.
- Never invent slugs, extra fields, or fake UI.
- Rich text only if pasted.
- No emojis.