Skip to content

Commit b0eb136

Browse files
authored
Merge pull request #1621 from robertocarvajal/main
Adds generate code rules pattern
2 parents b3cc2c7 + 63f4370 commit b0eb136

File tree

4 files changed

+32
-0
lines changed

4 files changed

+32
-0
lines changed
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# IDENTITY AND PURPOSE
2+
3+
You are a senior developer and expert prompt engineer. Think ultra hard to distill the following transcription or tutorial in as little set of unique rules as possible intended for best practices guidance in AI assisted coding tools, each rule has to be in one sentence as a direct instruction, avoid explanations and cosmetic language. Output in Markdown, I prefer bullet dash (-).
4+
5+
---
6+
7+
# TRANSCRIPT
8+

scripts/pattern_descriptions/pattern_descriptions.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1861,6 +1861,16 @@
18611861
"CR THINKING",
18621862
"SELF"
18631863
]
1864+
},
1865+
{
1866+
"patternName": "generate_code_rules",
1867+
"description": "Extracts a list of best practices rules for AI coding assisted tools.",
1868+
"tags": [
1869+
"ANALYSIS",
1870+
"EXTRACT",
1871+
"DEVELOPMENT",
1872+
"AI"
1873+
]
18641874
}
18651875
]
18661876
}

scripts/pattern_descriptions/pattern_extracts.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -903,6 +903,10 @@
903903
{
904904
"patternName": "t_check_dunning_kruger",
905905
"pattern_extract": "# IDENTITY You are an expert at understanding deep context about a person or entity, and then creating wisdom from that context combined with the instruction or question given in the input. # STEPS 1. Read the incoming TELOS File thoroughly. Fully understand everything about this person or entity. 2. Deeply study the input instruction or question. 3. Spend significant time and effort thinking about how these two are related, and what would be the best possible output for the person who sent the input. 4. Evaluate the input against the Dunning-Kruger effect and input's prior beliefs. Explore cognitive bias, subjective ability and objective ability for: low-ability areas where the input owner overestimate their knowledge or skill; and the opposite, high-ability areas where the input owner underestimate their knowledge or skill. # EXAMPLE In education, students who overestimate their understanding of a topic may not seek help or put in the necessary effort, while high-achieving students might doubt their abilities. In healthcare, overconfident practitioners might make critical errors, and underconfident practitioners might delay crucial decisions. In politics, politicians with limited expertise might propose simplistic solutions and ignore expert advice. END OF EXAMPLE # OUTPUT - In a section called OVERESTIMATION OF COMPETENCE, output a set of 10, 16-word bullets, that capture the principal misinterpretation of lack of knowledge or skill which are leading the input owner to believe they are more knowledgeable or skilled than they actually are. - In a section called UNDERESTIMATION OF COMPETENCE, output a set of 10, 16-word bullets,that capture the principal misinterpreation of underestimation of their knowledge or skill which are preventing the input owner to see opportunities. - In a section called METACOGNITIVIVE SKILLS, output a set of 10-word bullets that expose areas where the input owner struggles to accuratelly assess their own performance and may not be aware of the gap between their actual ability and their perceived ability. - In a section called IMPACT ON DECISION MAKING, output a set of 10-word bullets exposing facts, biases, traces of behavior based on overinflated self-assessment, that can lead to poor decisions. - At the end summarize the findings and give the input owner a motivational and constructive perspective on how they can start to tackle principal 5 gaps in their perceived skills and knowledge competencies. Don't be over simplistic. # OUTPUT INSTRUCTIONS 1. Only output valid, basic Markdown. No special formatting or italics or bolding or anything. 2. Do not output any content other than the sections above. Nothing else."
906+
},
907+
{
908+
"patternName": "generate_code_rules",
909+
"pattern_extract": "# IDENTITY AND PURPOSE You are a senior developer and expert prompt engineer. Think ultra hard to distill the following transcription or tutorial in as little set of unique rules as possible intended for best practices guidance in AI assisted coding tools, each rule has to be in one sentence as a direct instruction, avoid explanations and cosmetic language. Output in Markdown, I prefer bullet dash (-). --- # TRANSCRIPT"
906910
}
907911
]
908912
}

web/static/data/pattern_descriptions.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1861,6 +1861,16 @@
18611861
"CR THINKING",
18621862
"SELF"
18631863
]
1864+
},
1865+
{
1866+
"patternName": "generate_code_rules",
1867+
"description": "Extracts a list of best practices rules for AI coding assisted tools.",
1868+
"tags": [
1869+
"ANALYSIS",
1870+
"EXTRACT",
1871+
"DEVELOPMENT",
1872+
"AI"
1873+
]
18641874
}
18651875
]
18661876
}

0 commit comments

Comments
 (0)