Get started with a good prompt
Writing a good AI Prompt
The CLEAR prompting framework offers a good way to think about how to start and continue prompting throughout your build:
Concise - Use clear simple language in your prompt, with important information only.
Logical - Keep your prompt in a logical order.
Explicit - Make your prompt specific, include only details that are relevant.
Adaptive - Change up your prompting based on the results you get from the agent.
Reflective - Look through what the Agent has built and evaluate what you need from there, changing the prompt to address any missing aspects.
Find out more here about the CLEAR framework as described by Texas A&M UCC.
Writing a Stacker prompt
Keep your initial prompt focused on only one use case or problem to start. You will be able to add more details and customizations as you continue. You need to be precise about what you want from your agent and what should appear in your app.
App parts that should be included in your prompt:
The better you can write these pieces to be precise and detailed the best position you will be in to then later customize your app and data.
Pages
In Stacker pages are the items that will appear on the left side navigation bar. Pages can be backed by data tables. Data is stored on the data tab, this includes your fields and data in the fields.
Some pages can be custom pages, a combination of data from different tables and static widgets displaying text or photos.
Questions to ask yourself while deciding on your page structures:
What do you want to show on the navigation?
What are these pages called?
What types of views or layouts should your pages be?
Fields
Data is displayed using a collection of fields. This is how the data is formatted onto the page and can be rearranged by referencing fields.
Questions to ask yourself while deciding on what data you want to be present in your app:
What information do you want present on each page?
Do any of the pages (or tables) need to be linked together?
Who
Who are your users that will be interacting with the app?
This can include customers, clients, or team members. Who are these people and what would you call them in your app.
i.e. My sales team will be accessing the app to see their clients.
This outputs a sales team table and a clients table that will appear on the navigation as two separate pages.
The What and How
What are people expected to see or do when they login?
This can be anything from seeing their sales for the month or seeing the status of the deals in a pipeline. Or if clients are accessing the portal, should they be seeing a page with their profile and only their information.
i.e My sales team can see all of their deals on a board view based on their status. The deals should be connected to a client and a sales team member.
This will output a sales team, deals and a clients table, each appearing on the navigation, linking together and displaying in a layout that makes sense. For example, deals should appear as a board view.
Example prompt:
#Overview Your task is to build a two sided recruitment portal for recruitment consulants to manage their candidates and for our internal team of CSMs to oversee the process. Below is the app structure.
#App Structure The app should be made up of the following pages: Clients - Our customers looking for candidates Job Postings - Job vacancies that consultants need to fill for our customers Consultants - Part time recruitment freelancers who we onboard on to the system CSMs - our internal team of client specialists who oversee some set of consultants and manage a book of business (Clients) Candidates - Prospective hires for our Clients who can have candidacy for one or a number of Job Postings
#Other Requirements - Consultants need to be able to add and manage their own sourced Candidates on a board view - CSMs need to view the consultants they are presently working with and their own Client list - Need to view the candidate pipeline on each Job posting - Need to store information for all these pages
Clarifying questions
Now that you have a use case and a structure to your app send your prompt to the agent. You will be asked clarifying questions about your use case. Help the agent understand better by answering the questions to the best you can. The agent will generally give you options to choose from to help you determine the best response.
Once you have finished with all of the clarifying questions your build will begin. Give the agent a few minutes to finish the build.
Continue to customize
Check out your finished app and continue customizing your app! Next we will start by looking at the page layouts to see what we can customize.
Last updated