[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVCZ2JFMW3JATEM3906YP8":3,"skill-same:01M7EVCZ2JFMW3JATEM3906YP8":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},"01M7EVCZ2JFMW3JATEM3906YP8","pocketbase-pro",null,"PocketBase backend mastery — collections, APIs, and self-hosted operations — use when building on PocketBase.","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-pocketbase-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pocketbase-pro\ndescription: PocketBase backend mastery — collections, APIs, and self-hosted operations — use when building on PocketBase.\ncategory: pocketbase\n---\n\n## Overview\n\nPocketBase is an open-source backend in a single Go binary: embedded database\n(SQLite), auth, file storage, realtime, and an admin dashboard — no separate\nservices to operate. This skill covers data modeling with collections, using\nthe generated APIs, and running PocketBase reliably in production.\n\n## When to use\n\n- Modeling data with PocketBase collections (base, auth, view)\n- Choosing between the REST API and the realtime\u002Fclient SDKs\n- Designing API rules (PocketBase's per-collection access control)\n- Backing up, scaling, and updating a PocketBase instance\n- Extending with Go\u002FJavaScript hooks and custom routes\n\n## Core concepts\n\n**Collections are the schema.** Base collections hold regular records; auth\ncollections add users with email\u002Fpassword\u002FOAuth2; view collections expose\nSQL queries as read-only collections. Fields are typed (text, number, bool,\ndate, file, relation, JSON…), and relations are first-class — design them\nlike a normalized relational schema, because that's what it is.\n\n**API rules are the security model.** Each collection defines list\u002Fview\u002F\ncreate\u002Fupdate\u002Fdelete rules as filter expressions evaluated against the\nrequest (`@request.auth.id != \"\"`, `@request.data.owner = @request.auth.id`).\nNo rule = denied. Rules run per record, so design them carefully — they're\nyour authorization layer, equivalent in spirit to row-level security.\n\n**One binary, embedded SQLite.** PocketBase's simplicity is the feature: a\nsingle executable with data in one directory. This makes deploys trivial but\nshapes scaling — SQLite handles impressive throughput on one node (WAL mode,\nproper indexes), and PocketBase is fundamentally single-node; scale vertically\nand know the ceiling rather than assuming horizontal scale-out.\n\n**SDKs over raw REST.** The official JS\u002FDart SDKs handle auth state, token\nrefresh, and realtime subscriptions; use them instead of hand-rolling HTTP.\nThe admin dashboard (`\u002F_\u002F`) is genuinely useful for inspecting data and\ntesting rules during development.\n\n**Migrations are code.** Collection changes made in the dashboard generate\nmigration files — commit them and apply via `migrate` commands so environments\nstay in sync. Dashboard-clicking without migrations is how staging and prod\ndrift apart.\n\n## Practical workflow\n\n1. **Model collections** with proper field types and relations; add indexes\n   for your query patterns (PocketBase exposes index management per\n   collection).\n2. **Write API rules first**, before client code: define who can do what per\n   collection and operation; test with authenticated and anonymous requests\n   (the dashboard's API preview helps).\n3. **Build the client** with the SDK: auth flows, CRUD with `expand` for\n   relations, pagination (`page`\u002F`perPage`), and filters using PocketBase's\n   filter syntax.\n4. **Handle files** via file fields with thumbs\u002Fprotected-file rules; serve\n   private files through signed\u002Fauthorized access, not public URLs, when\n   they need protection.\n5. **Deploy as one unit:** the binary + data directory on a VM\u002Fcontainer with\n   persistent storage; reverse-proxy with TLS; schedule data-directory\n   backups (SQLite file copies are consistent when done correctly — or use\n   the backup API).\n6. **Update carefully:** test new versions in staging (migrations run on\n   boot), keep backups before upgrading, and pin versions in production.\n\n## Common pitfalls\n\n- **Permissive API rules in production** (`\"\"` = public on list\u002Fview) —\n  audit every collection's rules; the dashboard flags public access, heed it.\n- **No migration discipline** — dashboard changes never exported; environments\n  diverge and deploys become manual archaeology.\n- **Treating it as horizontally scalable** — it's single-node by design;\n  plan vertical scaling and know your throughput ceiling via load testing.\n- **Backing up the data dir while writes happen** without SQLite-safe\n  procedure — use the built-in backup or WAL-aware copy methods.\n- **Storing secrets in collection records** — API rules protect records, but\n  secrets belong in environment config \u002F a secrets manager, not the database.\n- **N+1 via expand abuse** — expanding deep relation trees on list endpoints\n  generates heavy queries; paginate and expand narrowly.\n","## Overview\n\nPocketBase is an open-source backend in a single Go binary: embedded database\n(SQLite), auth, file storage, realtime, and an admin dashboard — no separate\nservices to operate. This skill covers data modeling with collections, using\nthe generated APIs, and running PocketBase reliably in production.\n\n## When to use\n\n- Modeling data with PocketBase collections (base, auth, view)\n- Choosing between the REST API and the realtime\u002Fclient SDKs\n- Designing API rules (PocketBase's per-collection access control)\n- Backing up, scaling, and updating a PocketBase instance\n- Extending with Go\u002FJavaScript hooks and custom routes\n\n## Core concepts\n\n**Collections are the schema.** Base collections hold regular records; auth\ncollections add users with email\u002Fpassword\u002FOAuth2; view collections expose\nSQL queries as read-only collections. Fields are typed (text, number, bool,\ndate, file, relation, JSON…), and relations are first-class — design them\nlike a normalized relational schema, because that's what it is.\n\n**API rules are the security model.** Each collection defines list\u002Fview\u002F\ncreate\u002Fupdate\u002Fdelete rules as filter expressions evaluated against the\nrequest (`@request.auth.id != \"\"`, `@request.data.owner = @request.auth.id`).\nNo rule = denied. Rules run per record, so design them carefully — they're\nyour authorization layer, equivalent in spirit to row-level security.\n\n**One binary, embedded SQLite.** PocketBase's simplicity is the feature: a\nsingle executable with data in one directory. This makes deploys trivial but\nshapes scaling — SQLite handles impressive throughput on one node (WAL mode,\nproper indexes), and PocketBase is fundamentally single-node; scale vertically\nand know the ceiling rather than assuming horizontal scale-out.\n\n**SDKs over raw REST.** The official JS\u002FDart SDKs handle auth state, token\nrefresh, and realtime subscriptions; use them instead of hand-rolling HTTP.\nThe admin dashboard (`\u002F_\u002F`) is genuinely useful for inspecting data and\ntesting rules during development.\n\n**Migrations are code.** Collection changes made in the dashboard generate\nmigration files — commit them and apply via `migrate` commands so environments\nstay in sync. Dashboard-clicking without migrations is how staging and prod\ndrift apart.\n\n## Practical workflow\n\n1. **Model collections** with proper field types and relations; add indexes\n   for your query patterns (PocketBase exposes index management per\n   collection).\n2. **Write API rules first**, before client code: define who can do what per\n   collection and operation; test with authenticated and anonymous requests\n   (the dashboard's API preview helps).\n3. **Build the client** with the SDK: auth flows, CRUD with `expand` for\n   relations, pagination (`page`\u002F`perPage`), and filters using PocketBase's\n   filter syntax.\n4. **Handle files** via file fields with thumbs\u002Fprotected-file rules; serve\n   private files through signed\u002Fauthorized access, not public URLs, when\n   they need protection.\n5. **Deploy as one unit:** the binary + data directory on a VM\u002Fcontainer with\n   persistent storage; reverse-proxy with TLS; schedule data-directory\n   backups (SQLite file copies are consistent when done correctly — or use\n   the backup API).\n6. **Update carefully:** test new versions in staging (migrations run on\n   boot), keep backups before upgrading, and pin versions in production.\n\n## Common pitfalls\n\n- **Permissive API rules in production** (`\"\"` = public on list\u002Fview) —\n  audit every collection's rules; the dashboard flags public access, heed it.\n- **No migration discipline** — dashboard changes never exported; environments\n  diverge and deploys become manual archaeology.\n- **Treating it as horizontally scalable** — it's single-node by design;\n  plan vertical scaling and know your throughput ceiling via load testing.\n- **Backing up the data dir while writes happen** without SQLite-safe\n  procedure — use the built-in backup or WAL-aware copy methods.\n- **Storing secrets in collection records** — API rules protect records, but\n  secrets belong in environment config \u002F a secrets manager, not the database.\n- **N+1 via expand abuse** — expanding deep relation trees on list endpoints\n  generates heavy queries; paginate and expand narrowly.\n",{"name":5,"category":24,"description":7},"pocketbase","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-pocketbase-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 pocketbase-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill pocketbase-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill pocketbase-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-pocketbase-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",[],[]]