changelog-writer
Changelog Writer
Create clear, accurate changelog entries that help developers understand what's new in Lightfast releases.
Critical: Fact-Check First
Before writing anything, verify against docs/architecture/implementation-status/README.md:
-
Check implementation status to verify:
- What's actually completed vs planned
- Current limitations and known gaps
- Technical accuracy of claims
-
Never oversell:
- Use specific names: "GitHub File Sync (File Contents)" not "GitHub Integration"
- Disclose limitations: "Currently supports X; Y coming in vZ"
- Be honest about conditionals: "when 3+ customers request"
-
Verify every claim:
More from lightfastai/lightfast
blog-writer
Create category-aware, AEO-optimized blog posts for Lightfast. Use when writing technology deep-dives, company announcements, or product launches.
196seo
Optimize content for search engines and AI answer engines. Use when writing or auditing SEO for any Lightfast page.
32turborepo
|
13react-doctor
Run after making React changes to catch issues early. Use when reviewing code, finishing a feature, or fixing bugs in a React project.
11remotion-best-practices
Best practices for Remotion - Video creation in React
10vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
9