Write, rewrite, and audit Remix guide chapters in Markdown documentation.
npx skills add https://github.com/remix-run/remix --skill write-guides
Please help me install this Agent Skill. Skill: write-guides Source: https://github.com/remix-run/remix/tree/main/.agents/skills/write-guides Command: npx skills add https://github.com/remix-run/remix --skill write-guides
Guide chapters often drift into generic, AI-sounding prose with abstract claims, repeated takeaways, and inconsistent code examples. This Skill enforces the concrete, conversational voice of the Remix docs so chapters read like a person walking through real code.
01-start-here.md, using concrete files, routes, handlers, and responses instead of abstract framing.remix/... paths, routes.<name>.href(...) usage, and the local chapter formatter config./docs/... links.docs/guides/app/actions/docs/chapters/, run the audit workflow to flag AI-sounding prose, then rewrite sections while preserving anchors and running Prettier on the result.Ask the assistant to audit the guide chapter at docs/guides/app/actions/docs/chapters/02-routing.md for AI-sounding prose and report findings with line numbers.
High-intent search queries and answers about installing and using this skill.
Read 01-start-here.md first for voice, then read the target chapter fully. Replace abstract framing with concrete files, routes, and responses, remove repeated takeaways, and re-read the chapter next to 01-start-here.md to smooth voice mismatches.
Run the audit workflow: read the file with line numbers, group findings by pattern such as generic transitions or placeholder nouns, quote the triggering phrases, and suggest rewrite directions without editing unless asked.
Import from remix/... rather than @remix-run/..., use TypeScript extensions in relative imports, use routes.<name>.href(...) for links and redirects, and return explicit Web Response objects from actions. Let the chapter's .oxfmtrc.json formatter handle snippet style.
Only after checking for incoming links with rg "#anchor-name" guides packages. Preserve anchors that other chapters link to, and remove explicit anchors that merely repeat the generated heading anchor.
Link when the guide intentionally skips exhaustive syntax, options, or package surface area. Teach just enough API for the reader to follow the guide, show one strong advanced example, and avoid duplicating reference material.
remix-runBuild and review Remix 3 applications with routing, middleware, and validation.
kael-odinRevise novel chapters by applying feedback from merged review JSON files.
jellyrockDetect broken links, invalid frontmatter paths, and stale anchors in JellyRock documentation.
patricio0312revGenerate API documentation from JSDoc comments in TypeScript projects.