fix(skill): add technical accuracy guardrails to blog-writer skill#7584
Merged
leecalcote merged 3 commits intomasterfrom Apr 3, 2026
Merged
fix(skill): add technical accuracy guardrails to blog-writer skill#7584leecalcote merged 3 commits intomasterfrom
leecalcote merged 3 commits intomasterfrom
Conversation
Address PR #7581 review feedback by enhancing the blog-writer skill to prevent recurring mistakes: contradictory CLI commands, unpinned install versions, brand name capitalization errors, and wrong outro CSS values. - Add command sequence verification and version pinning rules to SKILL.md - Add brand name capitalization checklist (MeshMates, not Meshmates) - Expand quality checklist into structure, technical accuracy, and taxonomy sections - Add Code Examples and CLI Commands section to blog-structure.md with wrong/right examples - Fix outro CSS spec: 1rem font-size and 1rem padding (not 0.9rem/3rem) - Add div.outro style to Blog.style.js with reviewer-approved values - Clarify tag casing conventions in tags-categories.md (ai is intentionally lowercase) Signed-off-by: Lee Calcote <lee.calcote@layer5.io>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Layer5 blog-writer skill docs and supporting assets to reduce recurring technical/content mistakes (CLI consistency, version pinning, brand/taxonomy casing) and align blog styling/specs (notably the outro block).
Changes:
- Add/expand blog-writer guardrails and checklists (command consistency, version pinning, brand capitalization, taxonomy casing).
- Update blog reference docs with a CLI/code examples section and corrected outro styling guidance.
- Update site styling and hero-image generation to match reviewer-approved visuals (outro styles + multi-stop gradient background technique).
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
src/collections/blog/Blog.style.js |
Adds div.outro styling per updated blog structure guidance. |
.claude/skills/layer5-blog-writer/scripts/generate_hero_image.py |
Replaces blurred-blob background with multi-stop gradient layers and updates SVG defs generation. |
.claude/skills/layer5-blog-writer/references/tags-categories.md |
Clarifies casing requirements and explicitly documents lowercase ai. |
.claude/skills/layer5-blog-writer/references/blog-structure.md |
Documents correct outro specs and adds pinned-version/command-consistency examples. |
.claude/skills/layer5-blog-writer/SKILL.md |
Adds brand capitalization rules and technical accuracy guardrails/checklists. |
Comment on lines
+26
to
+37
| div.outro { | ||
| display: flex; | ||
| padding-left: 1rem; | ||
| padding-right: 1rem; | ||
| font-size: 1rem; | ||
| border-top: 1px solid ${(props) => props.theme.primaryLightColor}; | ||
| border-bottom: 1px solid ${(props) => props.theme.primaryLightColor}; | ||
| margin-top: 1rem; | ||
| padding-top: 1rem; | ||
| padding-bottom: 1rem; | ||
| background-color: ${(props) => props.theme.secondaryLightColorTwo}; | ||
| } |
There was a problem hiding this comment.
display: flex will lay out all direct children of the outro in a row by default, which can easily break typical outro content (multiple paragraphs, CTA components, etc.). If flex isn’t required, remove it; if it is required, set flex-direction: column; (and optionally gap) so the outro behaves like a normal stacked content block.
Comment on lines
+283
to
+289
| | Property | `div.intro` | `div.outro` | | ||
| | ------------ | -------------------------- | ---------------------- | | ||
| | Border style | `1px dashed` (teal) | `1px solid` (teal) | | ||
| | Font style | `italic` | Normal (not italic) | | ||
| | Font size | `0.8rem` | `1rem` | | ||
| | Padding L/R | `3rem` | `1rem` | | ||
| | Tone | Reflective, sets the scene | Direct, action-forward | |
There was a problem hiding this comment.
This table has an extra leading | on each row (|| ...), which typically renders an empty first column in Markdown. Use a single leading pipe per row (| Property | ... | ... |, etc.) so the table renders correctly.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Lee Calcote <leecalcote@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Lee Calcote <leecalcote@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Address PR #7581 review feedback by enhancing the blog-writer skill to prevent recurring mistakes: contradictory CLI commands, unpinned install versions, brand name capitalization errors, and wrong outro CSS values.
Description
This PR fixes #
Notes for Reviewers
Signed commits