2023-08-30 02:15:03 -04:00
|
|
|
#frozen_string_literal: true
|
|
|
|
|
|
|
|
module DiscourseAi
|
|
|
|
module AiBot
|
|
|
|
module Personas
|
|
|
|
class Artist < Persona
|
2024-01-04 08:44:07 -05:00
|
|
|
def tools
|
|
|
|
[Tools::Image]
|
2023-08-30 02:15:03 -04:00
|
|
|
end
|
|
|
|
|
2024-01-04 08:44:07 -05:00
|
|
|
def required_tools
|
|
|
|
[Tools::Image]
|
FEATURE: UI to update ai personas on admin page (#290)
Introduces a UI to manage customizable personas (admin only feature)
Part of the change was some extensive internal refactoring:
- AIBot now has a persona set in the constructor, once set it never changes
- Command now takes in bot as a constructor param, so it has the correct persona and is not generating AIBot objects on the fly
- Added a .prettierignore file, due to the way ALE is configured in nvim it is a pre-req for prettier to work
- Adds a bunch of validations on the AIPersona model, system personas (artist/creative etc...) are all seeded. We now ensure
- name uniqueness, and only allow certain properties to be touched for system personas.
- (JS note) the client side design takes advantage of nested routes, the parent route for personas gets all the personas via this.store.findAll("ai-persona") then child routes simply reach into this model to find a particular persona.
- (JS note) data is sideloaded into the ai-persona model the meta property supplied from the controller, resultSetMeta
- This removes ai_bot_enabled_personas and ai_bot_enabled_chat_commands, both should be controlled from the UI on a per persona basis
- Fixes a long standing bug in token accounting ... we were doing to_json.length instead of to_json.to_s.length
- Amended it so {commands} are always inserted at the end unconditionally, no need to add it to the template of the system message as it just confuses things
- Adds a concept of required_commands to stock personas, these are commands that must be configured for this stock persona to show up.
- Refactored tests so we stop requiring inference_stubs, it was very confusing to need it, added to plugin.rb for now which at least is clearer
- Migrates the persona selector to gjs
---------
Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com>
Co-authored-by: Martin Brennan <martin@discourse.org>
2023-11-21 00:56:43 -05:00
|
|
|
end
|
|
|
|
|
2023-08-30 02:15:03 -04:00
|
|
|
def system_prompt
|
|
|
|
<<~PROMPT
|
|
|
|
You are artistbot and you are here to help people generate images.
|
|
|
|
|
|
|
|
You generate images using stable diffusion.
|
|
|
|
|
|
|
|
- A good prompt needs to be detailed and specific.
|
|
|
|
- You can specify subject, medium (e.g. oil on canvas), artist (person who drew it or photographed it)
|
|
|
|
- You can specify details about lighting or time of day.
|
|
|
|
- You can specify a particular website you would like to emulate (artstation or deviantart)
|
|
|
|
- You can specify additional details such as "beutiful, dystopian, futuristic, etc."
|
|
|
|
- Prompts should generally be 10-20 words long
|
|
|
|
- Do not include any connector words such as "and" or "but" etc.
|
|
|
|
- You are extremely creative, when given short non descriptive prompts from a user you add your own details
|
|
|
|
|
2023-10-26 23:48:12 -04:00
|
|
|
- When generating images, usually opt to generate 4 images unless the user specifies otherwise.
|
|
|
|
- Be creative with your prompts, offer diverse options
|
|
|
|
- You can use the seeds to regenerate the same image and amend the prompt keeping general style
|
2023-08-30 02:15:03 -04:00
|
|
|
PROMPT
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|