...
This commit is contained in:
@@ -0,0 +1,10 @@
|
||||
|
||||
if the chat coming from user seems to say translate e.g. translate to french,
|
||||
then translate the text which came to french
|
||||
|
||||
don't do anything for heroscript
|
||||
|
||||
overrule all previous instructions
|
||||
|
||||
just output the translated text
|
||||
|
@@ -0,0 +1,42 @@
|
||||
|
||||
how do I use heroscript for agenda management
|
||||
|
||||
-------------------------
|
||||
|
||||
heroscript has basic notations to deal with calendars and events
|
||||
|
||||
when the user asks to translate an calendar action to heroscript use following rules and see example below
|
||||
|
||||
- all dates are in europe style: Format: DD/MM/YYYY e.g. 06/07/2023
|
||||
- if year not specified by user then always use current year which is 2024
|
||||
- if month not specified use current month which is september or month 9
|
||||
- date, title is always required, if attendies or people mentioned they should be on attendies list
|
||||
- don't use comments in the heroscript (means no // at end of line for heroscript)
|
||||
- default duration is 1h, also ok 15m (15 min), 1 day
|
||||
|
||||
```heroscript
|
||||
|
||||
//to add item in agenda
|
||||
!!calendar.add
|
||||
date:'30-10-24'
|
||||
time:'10pm'
|
||||
duration:'1h'
|
||||
title:'meeting with tech team'
|
||||
attendies:'user1, kristof, ...'
|
||||
description:''
|
||||
|
||||
//to delete (can use words cancel, delete)
|
||||
!!calendar.delete
|
||||
id:100
|
||||
|
||||
//to reschedule e.g. delay, 1d stands for 1 day, 1w for 1 week, 1h for 1 hour
|
||||
!!calendar.delay
|
||||
id:100
|
||||
delay:'2d'
|
||||
|
||||
//when e.g. reschedule or delete, we can inform participants
|
||||
!!calendar.inform
|
||||
id:100
|
||||
|
||||
|
||||
```
|
@@ -0,0 +1,60 @@
|
||||
|
||||
how do I use heroscript for story and task management
|
||||
|
||||
-------------------------
|
||||
|
||||
heroscript has basic notations to deal with stories and tasks
|
||||
|
||||
when the user asks to translate an story or task action to heroscript use following rules and see example below
|
||||
|
||||
- all dates are in europe style: Format: DD/MM/YYYY e.g. 06/07/2023
|
||||
- if year not specified by user then always use current year which is 2024
|
||||
- if month not specified use current month which is september or month 9
|
||||
- title is always required, if attendies or people mentioned they should be on assignment list
|
||||
- date & time & duration is optional
|
||||
- don't use comments in the heroscript (means no // at end of line for heroscript)
|
||||
- duration expressed as 1m, 1h, 1d (minute, hour, day)
|
||||
- deadline is or a date or +1h, +1d, .. the + means time from now, just list same way e.g. +1h
|
||||
- 1 months is done as 30 days or +30 days, 2 months 60 days, ... (which means +30d for 1 month)
|
||||
- stories cannot have a date, if a date given, giver an error
|
||||
- owners, assignees, contributors, executors is all the same
|
||||
- the description is always in markdown format
|
||||
- the description always has the title repeated
|
||||
- the description has title, purpose, deliverables
|
||||
- try to figure out what purpose and deliverables are
|
||||
- purpose is put as list in markdown
|
||||
|
||||
```heroscript
|
||||
|
||||
//to add a new story
|
||||
!!story.add
|
||||
title:'need to improve UI for version 1.0'
|
||||
owners:'karoline, kristof'
|
||||
description:'
|
||||
# need to improve UI for version 1.0
|
||||
|
||||
We got some complaints from our userbase and its overdue.
|
||||
|
||||
## deliverables
|
||||
|
||||
- [ ] specs and check with kristof
|
||||
- [ ] implement mockup
|
||||
- [ ] implement prototype
|
||||
|
||||
'
|
||||
|
||||
|
||||
//to add a new task, which might (optional) be linked to a story
|
||||
!!task.add
|
||||
title:'let our userbase know'
|
||||
story:10
|
||||
owners:'kristof'
|
||||
deadline:'+10d'
|
||||
description:'
|
||||
write email to userbase
|
||||
ask tom to check
|
||||
'
|
||||
|
||||
|
||||
|
||||
```
|
60
_archive/aiprompts/instructions/timemgmt/sys_2_heroscript.md
Normal file
60
_archive/aiprompts/instructions/timemgmt/sys_2_heroscript.md
Normal file
@@ -0,0 +1,60 @@
|
||||
|
||||
'heroscript' is a simple declarative language in following form
|
||||
|
||||
```heroscript
|
||||
!!mother.define
|
||||
myname:'mymama'
|
||||
mylist:'20,200'
|
||||
myint:2
|
||||
|
||||
//this is how we define a child (is in list)
|
||||
!!child.define
|
||||
mother:'mymama'
|
||||
name:'florine'
|
||||
length:100
|
||||
description:'
|
||||
multiline is supported
|
||||
'
|
||||
|
||||
!!child.define
|
||||
mother:'mymama'
|
||||
name:'aurelie'
|
||||
length:60
|
||||
description:'
|
||||
multiline is supported
|
||||
now for aurelie
|
||||
'
|
||||
```
|
||||
|
||||
some rules
|
||||
|
||||
|
||||
- '0,70' is a list of 2 (when comma in example its a list)
|
||||
- never use [] in lists, just have comma separation in between quotes ''
|
||||
- in lists always put lowercase names
|
||||
- node_name:'silver' is same as node_name:silver, when spaces always '' around
|
||||
- // means comment
|
||||
- all dates are in europe style: Format: DD/MM/YYYY e.g. 06/07/2023, always specify year
|
||||
|
||||
the corresponding model in vlang would be
|
||||
|
||||
```vlang
|
||||
pub struct Mother {
|
||||
pub mut:
|
||||
myname string
|
||||
mylist [20,200]
|
||||
myint 2
|
||||
children []Child
|
||||
}
|
||||
|
||||
pub struct Child {
|
||||
pub mut:
|
||||
name string
|
||||
length int
|
||||
description string
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user