format: apply repo prettier (3.8.1) to the folded skills tree

963 markdown files reformatted with the repository's pinned prettier so
pnpm format:check covers the folded tree like every other repo file.

The formatter's embedded-language pass also normalized code fences
(TS semicolons, closed HTML tags in examples, lowercased CSS hex colors,
one renumbered list that skipped an index). Alphanumeric token deltas vs
the fold commit were audited file-by-file; all are formatter-equivalent
markup normalizations plus the four sanitized skills.

packages/mosaic/framework/skills/skill-creator/SKILL.md

@@ -335,7 +335,6 @@ scripts/package_skill.py <path/to/skill-folder> ./dist
 The packaging script will:
 
 1. **Validate** the skill automatically, checking:
-
    - YAML frontmatter format and required fields
    - Skill naming conventions and directory structure
    - Description completeness and quality

packages/mosaic/framework/skills/skill-creator/references/output-patterns.md

@@ -16,14 +16,17 @@ ALWAYS use this exact template structure:
 # [Analysis Title]
 
 ## Executive summary
+
 [One-paragraph overview of key findings]
 
 ## Key findings
+
 - Finding 1 with supporting data
 - Finding 2 with supporting data
 - Finding 3 with supporting data
 
 ## Recommendations
+
 1. Specific actionable recommendation
 2. Specific actionable recommendation
 ```
@@ -38,12 +41,15 @@ Here is a sensible default format, but use your best judgment:
 # [Analysis Title]
 
 ## Executive summary
+
 [Overview]
 
 ## Key findings
+
 [Adapt sections based on what you discover]
 
 ## Recommendations
+
 [Tailor to the specific context]
 
 Adjust sections as needed for the specific analysis type.
@@ -62,18 +68,22 @@ Generate commit messages following these examples:
 Input: Added user authentication with JWT tokens
 Output:
 ```
+
 feat(auth): implement JWT-based authentication
 
 Add login endpoint and token validation middleware
+
 ```
 
 **Example 2:**
 Input: Fixed bug where dates displayed incorrectly in reports
 Output:
 ```
+
 fix(reports): correct date formatting in timezone conversion
 
 Use UTC timestamps consistently across report generation
+
 ```
 
 Follow this style: type(scope): brief description, then detailed explanation.

packages/mosaic/framework/skills/skill-creator/references/workflows.md

@@ -25,4 +25,4 @@ For tasks with branching logic, guide Claude through decision points:
 
 2. Creation workflow: [steps]
 3. Editing workflow: [steps]
-```
+```