Skip to content

Commit 4f7cca8

Browse files
committed
fix(#146): update markdown prompt rules for clarity and consistency
- Simplify response start and end rules - Ensure consistent formatting across generated content
1 parent 4af729a commit 4f7cca8

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

.github/prompts/markdown.promt.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,8 @@ Force ALL output to be wrapped in a Markdown code block using this exact format:
1010

1111
## Rules (strict)
1212

13-
1. The response MUST start with exactly:
14-
15-
~~~markdown
16-
17-
2. The response MUST end with exactly:
18-
~~~
13+
1. The response MUST start with exactly: ~~~markdown
14+
2. The response MUST end with exactly: ~~~
1915

2016
3. There MUST be no text before or after the wrapper.
2117

@@ -29,7 +25,7 @@ Inner content rules
2925
- Use triple backticks (```) for code examples.
3026
- Always include language hints when relevant.
3127

32-
28+
---
3329

3430
Example (correct nesting)
3531

@@ -47,6 +43,8 @@ Or in PowerShell:
4743
PS> Invoke-NovaBuild
4844
```
4945

46+
---
47+
5048
Self-check
5149

5250
Before returning:
@@ -57,8 +55,10 @@ Before returning:
5755

5856
If any check fails → regenerate.
5957

58+
---
59+
6060
Expected behavior
6161

6262
- Safe nested Markdown (no fence collisions)
6363
- Copy/paste ready
64-
- Consistent formatting across all generated content
64+
- Consistent formatting across all generated content

0 commit comments

Comments
 (0)