---
title: Critical AI Prompt Battle
author: Sarah Ciston
editors: 
    - Emily Martinez
    - Minne Atairu
category: critical-ai
---

# p5.js Critical AI Prompt Battle
By Sarah Ciston
With Emily Martinez and Minne Atairu

## What are we making?

In this tutorial, you can build a tool to run several AI chat prompts at once and compare their results. You can use it to explore what models 'know' about various concepts, communities, and cultures.

This tutorial is part 2 in a series of 5 tutorials that focus on using AI creatively and thoughtfully. 
- Part 1: [Making a ToolBox for Making Critical AI]([XXX])
- Part 3: [Training Dataset Explorer]([XXX])
- Part 4: [Machine Learning Model Inspector & Poetry Machine]([XXX])
- Part 5: [Putting Critical Tools into Practice]([XXX])

The code and content in this tutorial build on information from the prior tutorial to start creating your first tool for your p5.js Critical AI Kit. It also builds on fantastic work on critical prompt programming by Yasmin Morgan (2022), Katy Gero et al.(2024), and Minne Atairu (2024).

## Why compare prompts?

When you're using a chatbot to generate code or an email, it's easy to imagine its outputs are neutral and harmless. It seems like any system would output basically the same result. Does this matter for basic uses like making a plain image or having a simple conversation? Absolutely. Training datasets are shaping even the most innocuous outputs. This training shows up in subtle insidious ways. 

Unfortunately, the sleek chatbot interface hides all the decision-making that leads to a prompt output. To glimpse the differences, we can test many variations by making our own tool. With our tool, we can hope to understand more about the underlying assumptions contained in the training dataset. That gives us more information to decide how we select and use these models — and for which contexts. 

## Steps

### 1. Make a copy of your toolkit prototype.

Use [Tutorial One]([XXX]) as a template. Make a copy and rename the new Space "Critical AI Prompt Battle" to follow along.

To jump ahead, you can make a copy of the [finished example in the editor]([XXX]). But we really encourage you to type along with us! 

### X. Import the Hugging Face library for working with Transformer models. 

Put this code at the top of `sketch.js`:

```javascript
import { pipeline, env } from 'https://cdn.jsdelivr.net/npm/@xenova/transformers@2.10.1';
env.allowLocalModels = false; // skip local model check
```

The import phrase says we are bringing in a library (or module) and the curly braces let us specify which specific functions from the library we want to use, in case we don't want to import the entire thing. It also means we have brought these particular functions into this "namespace" so that later we can refer to them without using their library name in front of the function name — but also we should not name any other variables or functions the same thing. More information on importing [Modules]([XXX]).

### X. Create global variables to use later. 

Declare these variables at the top of your script so that they can be referenced in multiple functions throughout the project:

```javascript
var PROMPT_INPUT = `The [BLANK] has a job as a [MASK], but...` // a field for writing or changing a text value
var PREPROMPT = `Please complete the phrase and fill in any [MASK]: `
var promptField // an html element to hold the prompt
var outText // an html element to hold the results
var blanksArray = [] // an empty list to store all the variables we enter to modify the prompt

```
We will be making a form that lets us write a prompt and send it to a model. The `PROMPT_INPUT` variable will carry the prompt we create. Think about what prompt you'd like to use first to test your model. You can change it later; we're making a tool for that! A basic prompt may include WHAT/WHO is described, WHERE they are, WHAT they're doing, or perhaps describing HOW something is done. 

<!-- The `OUTPUT_LIST` will store results we get back from the model.  -->
<!-- For fill-mask tasks, it will replace one `[MASK]` with one word (called a "token").  -->

It might look a bit like MadLibs; however, the model will make a prediction based on context. The model's replacement words will be the most likely examples based on its training data. When writing your prompt, consider what you can learn about the rest of the sentence based on how the model responds (Morgan 2022, Gero 2023). 

When writing your prompt, replace one of these aspects with [BLANK]. We will fill this blank in with a choice of words we provide. You can also leave another words for the model to fill in on its own, using the word [MAKS]. We will instruct the model to replace these on its own when we write the PREPROMPT. 

<!-- Often fill-mask tasks are used for facts, like "The capital of France is [MASK].  -->

For our critical AI `PROMPT_INPUT` example, we will try something quite simple that also has subjective social aspects: `The [BLANK] has a job as a [MASK], but....`

<!-- When writing your prompt, replace one of these aspects with [MASK] so that you instruct the model to fill it in iteratively with the words you provide (Morgan 2022, Gero 2023).  -->
<!-- Also leave some of the other words for the model to fill in on its own, using the word [FILL]. We instructed the model to replace these on its own in the PREPROMPT.  -->
<!-- It will have extra inputs for making variations of the prompt it sends.  -->
<!-- and the `blankArray` will carry the variations we tell the model to insert into the prompt.  -->

Next create a `PREPROMPT` variable that will give instructions to the model. This can be optional, but it helps to specify any particulars. Here we'll use `Please complete the phrase and fill in any [MASK]: `. We will make a list that combines the pre-prompt and several variations of the prompt we devise that will get sent to the model as a long string.

We are making our own version of what is called a ‘fill mask’ task. Often fill mask tasks are used for standardized facts, like "The capital of France is [MASK]. But since we want to customize our task, we are using a more general purpose model instead.

The last three variables `promptField`, `outText`, and `blanksArray` are declared at the top of our program as global variables so that we can access them in any function, from any part of the program.

### X. Select the task and type of model.

<!-- Let's write a function to keep all our machine learning model activity together. The first task we will do is called a "fill mask," which uses an "encoder-only" transformer model [XXX-explain] to fill in missing words. Call the function `fillInTask()` and put `async` in front of the function call.    -->

Let's write a function to keep all our machine learning model activity together. The first task we will do is called "text-to-text generation,” which uses a transformer model [XXX-explained in Tutorial1 or else here]. Call the function `textGenTask()` and put `async` in front of the function call.

About `async` and `await`: Because [inference][XXX-explain] processing takes time, we want our code to wait for the model to work. We will put an `await` flag in front of several functions to tell our program not to move on until the model has completely finished. This prevents us from having empty strings as our results. Any time we use `await` inside a function, we will also have to put an `async` flag in front of the function declaration. For more about working with asynchronous functions, see [Dan Shiffman's video on Promises]([XXX]).

Here's our basic model:

```js
async function textGenTask(pre,prompt,blanks){
    console.log('text-gen task initiated')

    let INPUT = pre + prompt // bring our prompt and preprompt into the function

    let MODEL = 'Xenova/flan-alpaca-large' // name of the model we use for this task

    const pipe = await pipeline('text2text-generation', MODEL) //initiate the pipeline we imported

    // let options = { max_new_tokens: 60, top_k: 90, repetition_penalty: 1.5 }

    // RUN INPUT THROUGH MODEL
    var out = await pipe(INPUT) // we can add options to this later

    console.log(await out)
    console.log('text-gen task completed')
}
```

<!-- ```js

async function fillInTask(){
    const pipe = await pipeline('fill-mask', 'Xenova/bert-base-uncased');

    let out = await pipe(PROMPT_INPUT);

    console.log(out) // Did it work? :)
    // yields { score, sequence, token, token_str } for each result

    return await out
}

await fillInTask()
``` -->

Inside this function, create a variable and name it `pipe`. Assign it to the predetermined machine learning pipeline using the `pipeline()` method we imported. The 'pipeline' represents a string of pre-programmed tasks that have been combined, so that we don't have to program every setting manually. We name these a bit generically so we can reuse the code for other tasks later.

Pass into your method the `('text2text-generation', 'Xenova/flan-alpaca-large')` to tell the pipeline to carry out this kind of text-to-text generation task, using the specific model named. If we do not pick a specific model, it will select the default for that task (in this case it is `gpt2`). We will go into more details about switching up models and tasks in the [next tutorial]([XXX]).

<!-- [XXX][If you want to change the model, you  ...] We use the models that are labeled specifically for the task we have chosen. Also the models made by `Xenova` are customized for our Transformers.js library, so for ease we'll stick with those.-->

We can add `console.log(textGenTask(PREPROMPT,PROMPT_INPUT,blankArray)` at the bottom of our code to test the model results in the console. For example, this is what my first run yielded:

`{ generated_text: "The woman has a job as a nurse but she isn't sure how to make the most of it." }`
`{ generated_text: "The non-binary person has a job as a nurse but she is not sure how to handle the stress of being an adult." }`
`{ generated_text: "The man has a job as a doctor but his life is filled with uncertainty. He's always looking for new opportunities and challenges, so it can be difficult to find the time to pursue them all." }`

Or another example: `The woman has a job as a nurse and wishes for different jobs. The man has a job as an engineer and wishes for different careers. The non-binary person has a job as an architect and hopes to pursue her dreams of becoming the best designer in the world.`
​
What can this simple prompt tell us about the roles and expectations of these figures as they are depicted by the model? 

[Add more?][XXX]


Finally, you can preload the model on your page for better performance. In the `README.md` file, add `Xenova/flan-alpaca-large` (no quote marks) to the list of models used by your program:

```
title: P5tutorial2
emoji: 🦝
colorFrom: blue
colorTo: purple
sdk: static
pinned: false
models:
  - Xenova/flan-alpaca-large
license: cc-by-nc-4.0
```

### X. Add model results processing

Let's look more closely at what the model outputs for us. In the example, we get a Javascript array, with just one item: an object that contains a property called `generated_text`. This is the simplest version of an output, and the outputs may get more complicated as you request additional information from different types of tasks. For now, we can extract just the string of text we are looking for with this code:

```js
//...model function
let OUTPUT_LIST = out[0].generated_text

console.log(OUTPUT_LIST)
console.log('text-gen parsing complete')

return await OUTPUT_LIST
```

We also put console logs to tell us that we reached this point. They’re always optional.


<!-- Let's look more closely at what the model outputs for us. In the example, we get a list of five outputs, and each output has four properties: `score`, `sequence`, `token`, and `token_str`.  -->

<!-- Here's an example: [REPLACE][XXX]
```js
{ score: 0.2668934166431427, 
    sequence: "the vice president retired after returning from war.",
    token: 3394,
    token_str: "retired"
}
``` -->

<!-- The `sequence` is a complete sentence including the prompt and the replaced word. Initially, this is the variable we want to display. You might also want to look deeper at the other components. `token_str` is the fill-in word separate from the prompt. `token` is the number assigned to that word, which can be used to look up the word again. It's also helpful to understand how frequently that word is found in the model. `score` is a float (decimal) representing how the model ranked these words when making the selection.  -->

We also put console logs to tell us that we reached this point. They’re always optional. It’s helpful to print out the whole output to the console, because as you see additional properties appear, you may want to utilize them in your Critical AI Kit.

Next we will build a friendly interface to send our model output into, so we don't always have to use the console.

<!-- ```js
// a generic function to pass in different model task functions
// async function getOutputs(task){
  let output = await task

  await output.forEach(o => {
    OUTPUT_LIST.push(o.sequence) // put only the full sequence in a list
  })

  console.log(OUTPUT_LIST)
// }
//replace fillInTask with:
await getOutputs(fillInTask())
``` -->

<!-- ### X. Write instructions for your model.  -->

<!-- We can instruct the model by giving it pre-instructions that go along with every prompt. We'll write also write those instructions now. Later, when we write the function to run the model, we will move them into that function.  -->
   

<!-- // let PREPROMPT = `Return an array of sentences. In each sentence, fill in the [BLANK] in the following sentence with each word I provide in the array ${blankArray}. Replace any [FILL] with an appropriate word of your choice.` -->

<!-- With the dollar sign and curly braces `${blankArray}`, we make a "string variable." This calls all the items that will be stored inside `blankArray` and inserts them into the `PREPROMPT` string. Right now that array is empty, but when we move `PREPROMPT` into the model function, it will not get created until `blankArray` has values stored in it. -->

<!-- CONFIGURATIONS POSSIBLE: https://huggingface.co/docs/transformers.js/api/utils/generation#new_module_utils/generation..GenerationConfig_new -->

### X. [TO-DO] Add elements to your web interface. 

Next we will build a friendly interface to send our model output into, so we don't always have to use the console.

### X. [TO-DO] Send model results to the web interface.

As we connect the interface, we can test our interface with the simple example output we've been using, or start playing with new prompts already.

We’ll keep using `console.log()` as our backup.

[TO-DO][XXX]

### X. [TO-DO] Put your tool to the test.

Make a list of topics that interest you to try with your tool. Experiment with adding variety and specificity to your prompt and the blanks you propose. Try different sentence structures and topics. 

What’s the most unusual or obscure, most ‘usual’ or ‘normal’, or most nonsensical blank you might propose?

Try different types of nouns — people, places, things, ideas; different descriptors — adjectives and adverbs — to see how these shape the results. For example, do certain places or actions often get associated with certain moods, tones, or phrases? Where are these based on outdated or stereotypical assumptions? 

How does the output change if you change the language, dialect, or vernacular (e.g. slang versus business phrasing)? How does it change with demographic characteristics or global contexts? (Atairu 2024). 

Is the model capable of representing a variety of contexts? What do you notice the model does well at representing, and where does it fall short? Where do you sense gaps, and how does it expose these or patch them over?

What kinds of prompts work and don’t work as you compare them at scale in a “prompt battle”?

### X. [TO-DO] Bonus: Test with more complex examples (add a field, add a parameter, add a model?)

You can change which model your tool works with by README.md and to sketch.js
Search the list of models available.

[TO-DO][XXX]

### Reflections 

Here we have created a tool to test different kinds of prompts quickly and to modify them easily, allowing us to compare prompts at scale. By comparing how outputs change with subtle shifts in prompts, we can explore how implicit bias emerges from [repeated and amplified through] large-scale machine learning models. It helps us understand that unwanted outputs are not just glitches in an otherwise working system, and that every output (no matter how boring) contains the influence of its dataset.

### Compare different prompts:

See how subtle changes in your inputs can lead to large changes in the output. Sometimes these also reveal large gaps in the model's available knowledge. What does the model 'know' about communities who are less represented in its data? How has this data been limited? 

### Reconsider neutral: 

This tool helps [reveal/us recognize] that [no version of a text, and no language model, is neutral./there is no 'neutral' output]. Each result is informed by context. Each result reflects differences in representation and cultural understanding, which have been amplified by the statistical power of the model. 

### Consider your choice of words and tools:

How does this help you think "against the grain"? Rather than taking the output of a system for granted as valid, how might you question or reflect on it? How will you use this tool in your practice? 

## Next steps

### Expand your tool:

This tool lets you scale up your prompt adjustments. We have built a tool comparing word choices in the same basic prompt. You've also built a simple interface for accessing pre-trained models that does not require using [a login/another company's interface]. It lets you easily control your input and output, with the interface you built. 

Keep playing with the p5.js DOM functions to build your interface & the HuggingFace API. What features might you add? You might also adapt this tool to compare wholly different prompts, or even to compare different models running the same prompt. 

Next we will add additional aspects to the interface that let you adjust more features and explore even further. We’ll also try different machine learning tasks you might use in your creative coding practice. In natural language processing alone, there’s also named entity recognition, question answering, summarization, translation, categorization, speech processing, and more. 


## Further considerations

### Flag your work:

Consider making it a habit to add text like "AI generated" to the title of any content you produce using a generative AI tool, and include details of your process in its description (Atairu 2024).

### [TO-DO]

## References

Atairu, Minne. 2024. "AI for Art Educators." AI for Art Educators. https://aitoolkit.art/

Katy Ilonka Gero, Chelse Swoopes, Ziwei Gu, Jonathan K. Kummerfeld, and Elena L. Glassman. 2024. Supporting Sensemaking of Large Language Model Outputs at Scale. In Proceedings of the CHI Conference on Human Factors in Computing Systems (CHI '24). Association for Computing Machinery, New York, NY, USA, Article 838, 1–21. https://doi.org/10.1145/3613904.3642139

Morgan, Yasmin. 2022. "AIxDesign Icebreakers, Mini-Games & Interactive Exercises." https://aixdesign.co/posts/ai-icebreakers-mini-games-interactive-exercises 

NLP & Transformers Course from Hugging Face: 
https://huggingface.co/learn/nlp-course/chapter1/3




============================================
<!-- More background: https://huggingface.co/tasks/text-generation
 -->

Tutorial 1:

<!-- Play with different models: https://huggingface.co/chat/ -->

### X. [TO-DO] Get to know the terms and tools.

API:
Model:
Dataset:
[TO-DO]:


### X. [TO-DO] Create HuggingFace account. 

[TO-DO][XXX]

### X. Create a Hugging Face Space.

A Hugging Face Space is just like a GitHub repo with GitHub Pages, except it's hosted by Hugging Face and already attached to its datasets, models, and API. 

Visit `https://huggingface.co/new-space?`.

Name your Space. Maybe something like `p5jsCriticalAIKit` or `criticalAITutorial1`

Select `static` and then select a `Blank` template. Make sure you keep the default settings of `FREE` CPU basic, and you can choose whether you want your space to be public or private.  

Your new Space should load on the `App` page, which is its web page. It should say `Running` at the top in green if it worked. Click on the drop down menu next to Running. Select Files to see your file tree and repository (repo) in the web interface. 

![screenshot of new space app page]()
![screenshot of new space app page with file menu]()

Click "Add File" to make a new `sketch.js` file. Go ahead and click "Commit" to save the new file before you get started editing it. You can hit "Edit" to make changes to the file in your browser. 

Alternately, you can clone the whole repository to work from your desktop. Refer to [p5.js Tutorial on Setup]() or [Dan Shiffman’s Hosting a p5.js Sketch with GitHub Pages](https://youtu.be/ZneWjyn18e8) which also works for HF Spaces)] for more detailed information about setting up your workspace. We recommend this, especially if you’re already familiar or willing to dive in!

### X. Add p5.js to the Space 

Edit `index.html` to include the p5.js library by including this line inside the `<head></head> tags:

`<script src="https://cdnjs.cloudflare.com/ajax/libs/p5.js/1.10.0/p5.min.js"></script>`

If you like, you can change the title of your page to your preference. You can also remove any elements inside the `<body></body>` tags, since we will replace them. 

Next, update `index.html` to reference the `sketch.js` file we created. Add this line inside the `<body></body>` tags:

`<script type="module" src="sketch.js"></script>` // make sure it has the type attribute "module"

The script element importing the sketch file may be familiar to you. Importantly, it also needs the `type="module"` attribute, so that we can use both p5.js and other libraries in the file. Let's set that up next...

### X. Create a class instance of p5 in `sketch.js`.

Our p5.js Instance is basically a wrapper that allows us to hold all of our p5.js functions together in one place and label them, so that the program can recognize them as belonging to p5.js. 

First we declare a `new p5()` class instance:

```javascript
new p5(function (p5) {
    //
})
```
Then, all our usual p5.js coding will happen within these curly braces. 

```js
new p5(function (p5) {
    p5.setup = function(){
        //
    }

    p5.draw = function(){
        // 
    }
})
```
Important: When using any functions specific to p5.js, you will start them out with a label of whatever you called your p5.js instance. In this case we called it `p5` so our functions will be called `p5.setup()` and `p5.draw()` instead of the `setup()` and `draw()` you may recognize. 

This will apply to any other function that is special to p5.js, like `p5.noCanvas`, but *not* to other functions which are standard to Javascript. Anything code written outside of the `new p5(){}` instance will not understand any p5.js syntax. 

Let's add the instance mode version of `p5.noCanvas()` because we will be working directly with the DOM and don't need a canvas.

```js
new p5(function (p5) {
    p5.setup = function(){
        p5.noCanvas()
        console.log('p5 instance loaded')
    }

    p5.draw = function(){
        // 
    }
})
```
We can also check that the p5 instance is working correctly by adding `console.log('p5 instance loaded')` to `p5.setup()`, since you won't yet see a canvas or any DOM elements

Check that the page loaded, since we don't have a canvas. Add this outside of the p5.js instance:

```js
window.onload = function(){
    console.log('DOM loaded, sketch.js loaded')
}

```


### X. Create a web interface and add template features.

We'll build an easy p5.js web interface so that we can interact with our Critical AI Kit. Create three new functions and run them in the In the `p5.setup()` function. Add a fourth function named `displayResults()` but don't run it in Setup. Instead it will run with a button press we make later.

```js
new p5(function (p5){
    p5.setup = function(){
        p5.noCanvas()
        console.log('p5 instance loaded')

        makeTextDisplay()
        makeFields()
        makeButtons()
    }

    function makeTextDisplay(){
        //
    }

    function makeFields(){
        //
    }

    function makeButtons(){
        //
    }

    function displayResults(){
        //
    }
})
```

For a deep dive into how to use the p5.DOM features, see [DOM TUTORIAL]((XXX)). Here we'll quickly put some placeholder text, input fields, and buttons on the page that you can expand on later. First, add a title, a description, and some alt text for accessibility. Don't forget to add `p5.` in front of every function that is specific to p5.js. 

```js
function makeTextDisplay(){
    let title = p5.createElement('h1','p5.js Critical AI Kit')
    let intro = p5.createP(`Description`)
    let altText = p5.describe(p5.describe(`Pink and black text on a white background with form inputs and buttons. The text describes a p5.js tool that lets you explore machine learning interactively. When the model is run it adds text at the bottom showing the output results.`))
}
```

For now, we'll just add a single input field, for writing prompts. It won't work yet because we'll need to connect it to the rest of the form. We describe its size, give it a label, and give it the class `prompt`.

```js
function makeFields(){
    let pField = p5.createInput(``)
    pField.size(700)
    pField.attribute('label', `Write a prompt here:`)
    p5.createP(pField.attribute('label'))
    pField.addClass("prompt")
  }

```

We'll add one button that will let us send prompts to the model. We create a variable called `submitButton`, use it to create a button with the `p5.createButton` function, and display the text `"SUBMIT"` on the button. We also size the button and give it a class. For now it won't do anything because we haven't used its `.mousePressed()` method to call any functions, but we'll add that later. 

```js
function makeButtons(){
    let submitButton = p5.createButton("SUBMIT")
    submitButton.size(170)
    submitButton.class('submit')
    // submitButton.mousePressed()
  }
```

And how about somewhere to display the results we get from our model? We won't see them yet, because we haven't run the model, but let's add a header and a paragraph for our outputs to come. When we are up and running we'll put this together with our model outputs to display the results on our web page.

```js
function displayResults(){
    let outHeader = p5.createElement('h3',"Results") 
    let outText = p5.createP('')
```

### X. Add CSS flair. 

Create a `style.css` file and paste in this code:

[Link to raw file]([XXX)

You can also write your own or revamp this code! See [CSS Tutorial [XXX]]([XXX]) for more details on playing with styles.

### X. Add authorization to your space. [MAY NOT BE NEEDED][XXX]

We'll use some template configuration code to make sure our program talks to the Hugging Face API. 

Paste this code into your `sketch.js` file:

```js
[XXX-TO-DO][MAY NOT NEED]
```

Also add this to your `README.md`:

```markdown
hf_oauth: true
hf_oauth_scopes:
  - read-repos
  - write-repos
  - inference-api
```

When you next load your app, click `Authorize`

![screenshot of Hugging Face app authorization screen]() 

To check if your authorization has worked, visit the Settings for your Hugging Face profile. Click `Connected Apps` and you should see the name of your `Space`.

![screenshot of authorized space in Hugging Face Settings interface]() 

<!-- EXAMPLES: https://huggingface.co/docs/huggingface.js/main/en/index#huggingfaceinference-examples -->

To adjust the configuration of your HF space: 
https://huggingface.co/docs/hub/spaces-config-reference
<!-- https://huggingface.co/docs/huggingface.js/hub/README#oauth-login -->
<!-- https://huggingface.co/spaces/huggingfacejs/client-side-oauth/blob/main/index.html →-->


**ALT if not using HF Spaces:**
### X. Get a HuggingFace API key.
	https://huggingface.co/docs/hub/spaces-overview#managing-secrets
### X. Connect your API key to your p5.js instance.

## Reflections & Next Steps

We’ve now put together all the basic foundations of a web page ready to host some Critical AI tools. As we move on to [XXX]



<!-- 
# - gpt-3.5-turbo
# - bigscience/bloom-560m
# - Xenova/distilgpt2
# - HuggingFaceH4/zephyr-7b-gemma-v0.1
# - HuggingFaceH4/zephyr-7b-beta
# - openai-community/gpt2
# - meta-llama/Meta-Llama-3-70B-Instruct
# - Xenova/detr-resnet-50
# - Xenova/gpt2
# - Xenova/bloom-560m
# - Xenova/gpt-3.5-turbo
# - Xenova/llama-68m
# - Xenova/LaMini-Flan-T5-783M
# - meta-llama/Meta-Llama-3-8B -->