clean-docs
Use planning-with-files skill with reset. The task:
Task
Scan every .mdx doc in www/content/docs/ and clean it following @docs/solutions/style.md.
Rules
KEEP (do not remove)
- Callouts (
<Callout>) — especially at end of sections - Intro/transitioning text at start of docs and sections ("In this guide...", "Let's...", "We'll...")
- Conversational tone, progressive build-up, celebratory endings
- All technical content — be lossless on information
REMOVE
- Marketing filler: "battle-tested", "secret sauce", "you can copy into your project"
- True redundancy: same info stated twice in same doc (duplicate code blocks, sentences restating a table above)
More from udecode/better-convex
spec-flow-analyzer
Analyzes specifications and feature descriptions for user flow completeness and gap identification. Use when a spec, plan, or feature description needs flow analysis, edge case discovery, or requirements validation.
6frontend-design
This skill should be used when creating distinctive, production-grade frontend interfaces with high design quality. It applies when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
6frontend-design-frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
5convex
ALWAYS use this skill when working with convex or better-convex. Covers the common end-to-end feature path using cRPC + ORM + auth + React, with setup/bootstrap and niche depth in references.
3agent-browser
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
3trace
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
2