Conversation
Deploy preview
|
|
Vale prose linter → found 2 errors, 2 warnings, 0 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 27:12 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
| 32:69 | warning | Use 'Markdown' instead of 'markdown'. | Vale.Terms |
| 33:91 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 39:56 | error | Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. | PostHogBase.EnDash |
|
My only small comment is that it wasn't immediately intuitive to me that I needed to right click on the link > click on "Copy link" to get the relative URL to paste on the article; so I wasn't sure where the link was and what exactly was it. Maybe we can add an instruction for Claude to spell out the suggested link's relative path So like → heatmaps (/heatmaps) – blah blah blah rationale → A/B testing guide for engineers (/product-engineers/ab-testing-guide-for-engineers) – blah blah blah rationale So that I can see at a glance what exactly it is recommending, if that makes sense 
|
2 participants
Changes
Based on @natalia-amorim's internal link spreadsheet, added a skill to just suggest them for a given blog post with
/suggest-links