[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMYVWSPM2KCS9T1WGR8STD":3,"skill-same:01M7EMYVWSPM2KCS9T1WGR8STD":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMYVWSPM2KCS9T1WGR8STD","epub-pro",null,"EPUB ebook creation and processing — structure, metadata, validation — use when generating or parsing ebooks.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-epub-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: epub-pro\ndescription: EPUB ebook creation and processing — structure, metadata, validation — use when generating or parsing ebooks.\ncategory: document-processing\n---\n\n## Overview\n\nEPUB is the open ebook standard: a zipped package of XHTML content, CSS, images,\nand metadata (OPF). Creating valid, good-looking EPUBs means understanding that\npackage structure — and that \"renders in my reader\" is not the same as \"valid\nEPUB\". This skill covers authoring, generation, and parsing.\n\n## When to use\n\n- Generating ebooks from Markdown, HTML, or structured content\n- Fixing or validating EPUB files (EpubCheck)\n- Designing reflowable layouts that work across readers (Kindle, Apple Books, Kobo)\n- Extracting text and metadata from EPUBs for indexing\n- Handling covers, TOCs (NCX\u002Fnav), and embedded fonts\n\n## Core concepts\n\n**EPUB is a zip with rules.** `mimetype` file first and uncompressed, then\n`META-INF\u002Fcontainer.xml`, then the OPF package document listing every resource\nin the manifest with a spine defining reading order. Violate the packaging\nrules and some readers refuse the file even if the content is fine.\n\n**Reflowable is the default; fixed-layout is the exception.** Reflowable EPUBs\nadapt to screen size and user font settings — right for novels, non-fiction,\ndocs. Fixed-layout (page-precise) suits children's books and comics but\nsacrifices accessibility and adaptability. Choose deliberately.\n\n**CSS support varies by reader.** Keep stylesheets simple: basic typography,\nmargins, and page-break controls work everywhere; floats, absolute positioning,\nand web fonts are inconsistently supported. Embedded fonts work if subsetted\nand declared properly — but increase file size and may be overridden by reader\nsettings anyway.\n\n**Navigation documents matter.** EPUB 3 uses an XHTML nav document for the TOC;\nEPUB 2 used NCX. Include both for maximum compatibility. A proper hierarchical\nTOC (parts → chapters → sections) is the difference between a professional\nebook and an amateur one.\n\n**Metadata is discoverability.** Title, creator, language, identifier, and\ncover image in the OPF — plus schema.org refinements for series info. Validate\nwith EpubCheck; it's the industry gatekeeper for distribution channels.\n\n## Practical workflow\n\n1. **Author in a simple source format** (Markdown or semantic HTML) — one\n   chapter per file keeps the pipeline clean.\n2. **Convert with a real toolchain** (Pandoc-style converters or dedicated EPUB\n   libraries) using a checked-in CSS file and metadata config; don't hand-roll\n   the zip packaging.\n3. **Set the cover, TOC depth, and metadata** explicitly — these are the first\n   things readers and stores check.\n4. **Validate with EpubCheck** and fix every error (warnings: triage, but fix\n   most); validation failures block distribution on major stores.\n5. **Test on multiple readers** — at minimum one Kindle, one Apple Books\u002FKobo,\n   and one generic EPUB reader; check the cover, TOC navigation, images, and a\n   long chapter's typography.\n6. **For parsing\u002Fextraction:** unzip, read the OPF for spine order, extract\n   XHTML in spine order, strip to text preserving chapter boundaries and\n   image references.\n\n## Common pitfalls\n\n- **Skipping validation** — \"opens in Calibre\" ≠ valid; stores and some\n  devices reject invalid EPUBs.\n- **Absolute positioning and complex CSS** — renders unpredictably across\n  readers; keep it simple and reflowable.\n- **Huge unoptimized images** — bloat file size and crash low-memory readers;\n  resize and compress images for ebook dimensions.\n- **Missing or flat TOC** — a 300-page book with a 3-entry TOC is nearly\n  unnavigable; generate the TOC from real heading structure.\n- **DRM confusion** — standard EPUBs have no DRM; adding DRM requires specific\n  vendor toolchains (and locks out readers); decide distribution strategy\n  before production.\n- **Hardcoded font sizes in px** — ignore user preferences and break\n  accessibility; use relative units (em\u002F%) and let readers control base size.\n","## Overview\n\nEPUB is the open ebook standard: a zipped package of XHTML content, CSS, images,\nand metadata (OPF). Creating valid, good-looking EPUBs means understanding that\npackage structure — and that \"renders in my reader\" is not the same as \"valid\nEPUB\". This skill covers authoring, generation, and parsing.\n\n## When to use\n\n- Generating ebooks from Markdown, HTML, or structured content\n- Fixing or validating EPUB files (EpubCheck)\n- Designing reflowable layouts that work across readers (Kindle, Apple Books, Kobo)\n- Extracting text and metadata from EPUBs for indexing\n- Handling covers, TOCs (NCX\u002Fnav), and embedded fonts\n\n## Core concepts\n\n**EPUB is a zip with rules.** `mimetype` file first and uncompressed, then\n`META-INF\u002Fcontainer.xml`, then the OPF package document listing every resource\nin the manifest with a spine defining reading order. Violate the packaging\nrules and some readers refuse the file even if the content is fine.\n\n**Reflowable is the default; fixed-layout is the exception.** Reflowable EPUBs\nadapt to screen size and user font settings — right for novels, non-fiction,\ndocs. Fixed-layout (page-precise) suits children's books and comics but\nsacrifices accessibility and adaptability. Choose deliberately.\n\n**CSS support varies by reader.** Keep stylesheets simple: basic typography,\nmargins, and page-break controls work everywhere; floats, absolute positioning,\nand web fonts are inconsistently supported. Embedded fonts work if subsetted\nand declared properly — but increase file size and may be overridden by reader\nsettings anyway.\n\n**Navigation documents matter.** EPUB 3 uses an XHTML nav document for the TOC;\nEPUB 2 used NCX. Include both for maximum compatibility. A proper hierarchical\nTOC (parts → chapters → sections) is the difference between a professional\nebook and an amateur one.\n\n**Metadata is discoverability.** Title, creator, language, identifier, and\ncover image in the OPF — plus schema.org refinements for series info. Validate\nwith EpubCheck; it's the industry gatekeeper for distribution channels.\n\n## Practical workflow\n\n1. **Author in a simple source format** (Markdown or semantic HTML) — one\n   chapter per file keeps the pipeline clean.\n2. **Convert with a real toolchain** (Pandoc-style converters or dedicated EPUB\n   libraries) using a checked-in CSS file and metadata config; don't hand-roll\n   the zip packaging.\n3. **Set the cover, TOC depth, and metadata** explicitly — these are the first\n   things readers and stores check.\n4. **Validate with EpubCheck** and fix every error (warnings: triage, but fix\n   most); validation failures block distribution on major stores.\n5. **Test on multiple readers** — at minimum one Kindle, one Apple Books\u002FKobo,\n   and one generic EPUB reader; check the cover, TOC navigation, images, and a\n   long chapter's typography.\n6. **For parsing\u002Fextraction:** unzip, read the OPF for spine order, extract\n   XHTML in spine order, strip to text preserving chapter boundaries and\n   image references.\n\n## Common pitfalls\n\n- **Skipping validation** — \"opens in Calibre\" ≠ valid; stores and some\n  devices reject invalid EPUBs.\n- **Absolute positioning and complex CSS** — renders unpredictably across\n  readers; keep it simple and reflowable.\n- **Huge unoptimized images** — bloat file size and crash low-memory readers;\n  resize and compress images for ebook dimensions.\n- **Missing or flat TOC** — a 300-page book with a 3-entry TOC is nearly\n  unnavigable; generate the TOC from real heading structure.\n- **DRM confusion** — standard EPUBs have no DRM; adding DRM requires specific\n  vendor toolchains (and locks out readers); decide distribution strategy\n  before production.\n- **Hardcoded font sizes in px** — ignore user preferences and break\n  accessibility; use relative units (em\u002F%) and let readers control base size.\n",{"name":5,"category":24,"description":7},"document-processing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-epub-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill epub-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill epub-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill epub-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-epub-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]