We’ve found that Creo performs best when you divide your prompts into “Backend specification” and “Frontend specification” inputs when editing tools.

This separation:

  • Minimizes AI hallucination
  • Provides clarity
  • Reduces review time for changes

Here are some examples to help you understand the difference between a good and a bad prompt:

Example 1

Bad

Backend specification:

Build me an Applicant Tracking System

Frontend specification:

[blank]

Good

Backend specification:

Add an endpoint to call this API: https://6609b6140f324a9a2883ac57.mockapi.io/api/v1/products. Response schema looks like this: id, createdAt, name, price, material.

Filter the products by price above 300. Return the filtered products.

Frontend specification:

Add a table to show me the products retrieved from the endpoint above. Make sure the table is within a card and has some margin and padding. Change the title and description to something appropriate to the tool.

Example 2

Bad

Backend specification:

[blank]

Frontend specification:

Rearrange the elements on top to make it look nicer

Good

Backend specification:

[blank]

Frontend specification:

Use flex to arrange the elements on top in the following order:

- The logo should be on the left

- The search bar should be in the middle

- The user avatar should be on the right