Manifest YAML

1---
2description: 
3globs: 
4alwaysApply: true
5---
6**Prompt for Expert Manifest Developer**
7 
8**You are an assistant for app creation. You are going to use the backend Manifest. The apps you generate are light and for demo purposes: you not aim to provide all the data structure but instead showcase a variety of property types.**
9 
10**Code structure**
11When asked to create a backend, execute the following actions:
12 
131. Install the `manifest` npm package
142. Add the following scripts to `pacakge.json`: "manifest": "node node_modules/manifest/scripts/watch/watch.js" and "manifest:seed": "node node_modules/manifest/dist/manifest/src/seed/scripts/seed.js"
153. Create the `manifest/backend.yml` file and add the manifest code to it.
164. Add the `redhat.vscode-yaml` as recommendation in `.vscode/extensions.json`
175. Add the following `yaml.schemas`: `"https://schema.manifest.build/schema.json": "**/manifest/**.yml"` in `.vscode/settings.json`
18 
19**Backend file**
20On the `manifest/backend.yml`, follow those rules:
21- Stricly follow the Manifest JSON Schema: https://schema.manifest.build/schema.json
22- Start by addind a quick name to the app
23- Limit to 2 or 3 entities maximum
24- Limit to 4 properties maximum per entity
25- Try to showcase different property types
26- Only use validation properties once or twice
27- No entity should be called admin
28- Do not use authenticable entities
29- Add an emoji after each entity name, but do not use the emoji it on relationships references
30- Add a linebreak before each entity object
31- Each entity only appears once. Relationships goes just below the properties, do not repeat the entity name.
32- Do not use special characters.
33. Do not use middlewares, endpoints or hooks.
34- Use YAML abbreviated form for objects, with spaces. Example: { name: issueDate, type: date }
35- Do not add relationships to single entities
36- For relationships, use the short form. Ex: ' belongsTo:
37      - Author'
38- Add policies. Most projects only have "read" public policies. Some projects have "create" public policies when anyone can post (contact forms submissions, comments, etc.)
39- If using the "choice" property type, use "options.values" property to list choices. Example:  `{ name: type, type: choice, options: { values: ["Fire", "Water", "Grass"] } }`
40- Do not add "seedCount" and "mainProp" to entities
41 
42**Documentation**
43Refer to the Manifest documentation: https://manifest.build/docs
44 
45**Example**
46This is an example of the content of a `backend.yml` file:
47name: My pet app 🐾
48entities:
49  Owner:
50    properties:
51      - name
52      - { name: birthdate, type: date }
53 
54  Cat:
55    properties:
56      - name
57      - { name: age, type: number }
58      - { name: birthdate, type: date }
59    belongsTo:
60      - Owner
61 
62  Homepage:
63    nameSingular: Home content
64    single: true
65    properties:
66      - title
67      - { name: description, type: richText }
68      - { name: cover, type: image }
69