[2.15.2] Fix skill spec compliance across all skills

Fixed issues flagged by skill-creator spec:
- Reference files now use proper markdown links instead of backtick text
- Descriptions use third person ("This skill should be used when...")
- Added Skill Compliance Checklist to CLAUDE.md with validation commands

Affected skills: agent-native-architecture, andrew-kane-gem-writer,
compound-docs, create-agent-skills, dhh-rails-style, dhh-ruby-style,
dspy-ruby, every-style-editor, file-todos, frontend-design, gemini-imagegen

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

plugins/compound-engineering/CLAUDE.md

@@ -52,6 +52,39 @@ skills/
 
 **Why `workflows:`?** Claude Code has built-in `/plan` and `/review` commands. Using `name: workflows:plan` in frontmatter creates a unique `/workflows:plan` command with no collision.
 
+## Skill Compliance Checklist
+
+When adding or modifying skills, verify compliance with skill-creator spec:
+
+### YAML Frontmatter (Required)
+
+- [ ] `name:` present and matches directory name (lowercase-with-hyphens)
+- [ ] `description:` present and uses **third person** ("This skill should be used when..." NOT "Use this skill when...")
+
+### Reference Links (Required if references/ exists)
+
+- [ ] All files in `references/` are linked as `[filename.md](./references/filename.md)`
+- [ ] All files in `assets/` are linked as `[filename](./assets/filename)`
+- [ ] All files in `scripts/` are linked as `[filename](./scripts/filename)`
+- [ ] No bare backtick references like `` `references/file.md` `` - use proper markdown links
+
+### Writing Style
+
+- [ ] Use imperative/infinitive form (verb-first instructions)
+- [ ] Avoid second person ("you should") - use objective language ("To accomplish X, do Y")
+
+### Quick Validation Command
+
+```bash
+# Check for unlinked references in a skill
+grep -E '`(references|assets|scripts)/[^`]+`' skills/*/SKILL.md
+# Should return nothing if all refs are properly linked
+
+# Check description format
+grep -E '^description:' skills/*/SKILL.md | grep -v 'This skill'
+# Should return nothing if all use third person
+```
+
 ## Documentation
 
 See `docs/solutions/plugin-versioning-requirements.md` for detailed versioning workflow.