publish: Stop getting generic output from Copilot

posts/danieldiaz-qaa/1.agent-skills.md

@@ -1,6 +1,6 @@
 ---
 title: Stop getting generic output from Copilot. Teach it your patterns.
-published: false
+published: true
 description: Teach Copilot your team conventions with Agent Skills
 tags: 'vscode, githubcopilot, agentskills, ai'
 cover_image: ./assets/header.png
@@ -52,12 +52,18 @@ Here's the minimum a skill needs to actually work:
 
 **`.github/skills/component-structure/SKILL.md`**
 
-````markdown
+Frontmatter:
+
+```yaml
 ---
 name: component-structure
 description: Guidelines for creating React components following team conventions: named exports, props interface, no inline JSX logic.
 ---
+```
 
+Body:
+
+```markdown
 # Component Structure Skill
 
 ## When to use
@@ -70,7 +76,14 @@ Creating new React components or reviewing component patterns.
 - No inline logic in JSX, extract to handlers or custom hooks
 - Error boundaries at page level, not inside components
 
-## Pattern
+## Never do this
+- Default exports
+- Logic directly in JSX
+- Props without an explicit interface
+```
+
+Pattern example:
+
 ```typescript
 interface ButtonProps {
   label: string;
@@ -91,12 +104,6 @@ export function Button({ label, onClick, disabled = false }: ButtonProps) {
 }
 ```
 
-## Never do this
-- Default exports
-- Logic directly in JSX
-- Props without an explicit interface
-````
-
 The `name` field must match the directory name exactly. The `description` is what Copilot reads to decide whether to load the skill, so be specific. Full frontmatter reference: [SKILL.md file format](https://code.visualstudio.com/docs/copilot/customization/agent-skills#_skillmd-file-format).
 
 Four sections. One pattern. A few explicit don'ts.