Tighten content skills: remove no-ops and redundancy

[ankur-arch]

Summary

Follow-up to #7975 (merged). A surgical editing pass over the three content skills to remove no-ops and within-file redundancy and make the instructions tighter for both an agent and a human reader. No behavioral rules were dropped — only ceremony and restatement.

Changes

content-write-blog/SKILL.md

• Cut the "Keep the boundary clear at every step" no-op (the surrounding sentences already establish the boundary).
• Tightened the structured-question guidance.

content-create-hero-image/SKILL.md

• Folded the "Read first" navigation block into one line — the per-reference "read before designing / before the review pass" directives already live in the References list right below it.
• Trimmed the wordy Pre-conditions.
• Dropped five Anti-patterns bullets that only restate the Output contract and Validation checklist (SVG-meta, raster-hero, PNG/SVG-only, filenames, temp dir). Kept the creative/brand traps a checklist can't catch (generic-AI look, off-system styling, decorative logos, centering, fabricated palettes, tagline filler, single-reference copying).

docs-writer/SKILL.md

• Dropped the "This skill is opinionated" filler; kept the house-style precedence rule.

Notes

• Net: 3 files, +10 / −23 lines.
• Deliberately conservative: anti-pattern safety rails, the inline "Can't use backticks in section headings #1 off-brand bug" font warning, the Validation gate, and the worked examples were all preserved — those reinforce behavior that an agent benefits from seeing at the point of use.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified guidance for creating hero images, including where to find usage examples, required inputs, and what information must be provided before starting.
  • Tightened instructions for blog writing workflows, making the scope of the task and question formats clearer.
  • Updated documentation-writing guidance to better handle house style conflicts and when to flag them.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jun 25, 2026 12:41pm
docs	Ready	Preview, Comment	Jun 25, 2026 12:41pm
eclipse	Ready	Preview, Comment	Jun 25, 2026 12:41pm
site	Ready	Preview, Comment	Jun 25, 2026 12:41pm

[coderabbitai]

Walkthrough

The PR rewrites guidance in three skill docs: the hero-image skill now points operators to README.md, tightens preconditions, and trims anti-pattern wording; the blog-writing skill clarifies operator-owned workflow steps and question handling; the docs-writer skill rephrases the house-style conflict instruction.

Changes

Skill instruction wording updates

Layer / File(s)	Summary
Hero image guidance and constraints .claude/skills/content-create-hero-image/SKILL.md	Replaces the read-first block with README guidance, compacts slug and reference preconditions, and rewrites anti-patterns to reference Output contract and Validation for format, filename, and destination rules.
Blog and docs wording .claude/skills/content-write-blog/SKILL.md, .claude/skills/docs-writer/SKILL.md	Clarifies the blog skill’s content-only boundary and question-selection wording, and rephrases the docs-writer house-style conflict instruction.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• prisma/web#7975: Introduces the content-create-hero-image, content-write-blog, and docs-writer skill definitions that these wording edits refine.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the PR’s main edit: tightening content skills by removing redundant, no-op guidance.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands.}

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jun 25, 2026, 12:48 PM

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.claude/skills/content-create-hero-image/SKILL.md:
- Around line 75-77: The precondition in `SKILL.md` is too restrictive because
it only allows a blog post slug or title, which conflicts with the
README-supported PR URL entry point. Update the precondition to include PR URL
as an accepted input for the `content-create-hero-image` flow, or revise the
precondition text to match the documented contract in `README.md` so the entry
points stay consistent.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1b441a0c-8509-4db9-a85d-a40011a65d56

📥 Commits

Reviewing files that changed from the base of the PR and between 0946b4c and 926d648.

📒 Files selected for processing (3)

• .claude/skills/content-create-hero-image/SKILL.md
• .claude/skills/content-write-blog/SKILL.md
• .claude/skills/docs-writer/SKILL.md