fixing skill
This commit is contained in:
@@ -11,7 +11,9 @@ Strictly adhere to the rules and best practices defined in the local [STYLE_GUID
|
||||
|
||||
## Key Guidelines
|
||||
- **Clear & Concise Writing**: Favor simple sentence structures and active voice.
|
||||
- **Structural Integrity**: Use hierarchical headings correctly (H1, H2, H3). All headings must have an empty newline immediately following them.
|
||||
- **Structural Integrity**: Use hierarchical headings correctly (H1, H2, H3). All headings must have an empty newline immediately following them in all sessions.
|
||||
- **Semantic Markdown**: Use appropriate elements (lists, code blocks, tables) for clarity.
|
||||
- **Google Style**: Follow the local style guide precisely for all formatting and wording.
|
||||
- **Alerts & Callouts**: Use GitHub-style alerts (`> [!NOTE]`, `> [!IMPORTANT]`, etc.).
|
||||
- **Spacing Enforcement**: Always guarantee a single empty newline immediately following every heading in all markdown (.md) documents.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user