[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV4K94FQMYT6B1P91GCVB8":3,"skill-same:01M7EV4K94FQMYT6B1P91GCVB8":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EV4K94FQMYT6B1P91GCVB8","ams-notion-pro-dev",null,"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-notion-pro-dev\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notion-pro-dev\ndescription: Use Notion as a developer knowledge system: docs, runbooks, specs, wikis, and API-driven automation. Use when organizing engineering knowledge in Notion.\ncategory: development\n---\n\n# Notion Pro (Dev)\n\n## Overview\n\nNotion as a **developer knowledge system** — specs, runbooks, ADRs, team wikis, project trackers —\nworks when it's structured deliberately and maintained like code. This skill covers organizing\nengineering knowledge in Notion: information architecture, templates, databases for engineering\nworkflows, and API automation that keeps docs alive.\n\nThe through-line: Notion is a tool, not a strategy — structure it around how the team finds and\nmaintains knowledge, or it becomes a beautiful junk drawer.\n\n## When to use\n\n- Setting up team wikis, runbooks, or engineering docs in Notion.\n- Designing Notion databases for specs, incidents, or project tracking.\n- Creating templates for RFCs, postmortems, and onboarding.\n- Automating Notion via its API (syncing docs, reports, trackers).\n- Fixing a Notion workspace that's become unnavigable.\n\n## Core concepts\n\n- **Information architecture first.** Top-level: team home (orientation), docs by domain\n  (engineering areas), runbooks (operations), decisions (ADRs\u002FRFCs), people\u002Fprocess (onboarding,\n  rituals). Shallow, predictable hierarchy — if finding a doc takes more than 3 clicks, the\n  structure failed.\n- **Databases for structured knowledge.** Specs tracker (status, owner, links), incident log\n  (date, severity, postmortem link), ADR database (status: proposed\u002Faccepted\u002Fsuperseded),\n  onboarding checklist. Databases with views (by status, by owner, by team) beat folders of pages.\n- **Templates as process.** RFC template (context, proposal, alternatives, rollout), postmortem\n  template (timeline, root cause, action items with owners), bug report, onboarding checklist.\n  Templates encode \"how we do things\" — new joiners learn the process by using the template.\n- **Docs have owners and freshness.** Every important page: an owner and a \"last verified\" date.\n  Quarterly doc reviews (stale docs flagged, updated or deleted). Ownerless docs rot; dateless\n  docs can't be trusted.\n- **Link, don't duplicate.** One canonical page per topic, linked everywhere it's relevant.\n  Duplicated content diverges — the sync callout or synced block exists for a reason.\n- **API for automation.** Notion's API: sync release notes from GitHub, generate status reports\n  from databases, auto-create incident pages from alerts, back up critical docs. Automation keeps\n  the human-written parts human and the mechanical parts mechanical.\n\n## Practical workflow\n\n1. **Design the IA.** Sketch the top-level structure with the team; agree on where things live\n   (and where they *don't*). Write the \"where does X go?\" guide — it prevents 90% of sprawl.\n2. **Build the core databases.** Specs\u002FRFCs, ADRs, incidents, onboarding — with the views each\n   audience needs (engineers: by status; managers: by timeline; on-call: runbooks by symptom).\n3. **Create the templates.** RFC, ADR, postmortem, runbook, onboarding checklist — each with\n   guidance *in the template* (what goes in each section, with an example).\n4. **Seed with the essentials.** Team home, onboarding guide, architecture overview, runbooks for\n   top alerts, coding conventions. Better a small, accurate wiki than a large, rotting one.\n5. **Establish maintenance rituals.** Doc owners review quarterly; \"last verified\" dates visible;\n   stale-page reports; delete-or-update decisions. Docs are maintained or they're misleading.\n6. **Automate the mechanical.** API syncs for release notes\u002Fchangelogs, incident page creation,\n   weekly digest of doc changes. Keep humans writing judgment; machines moving data.\n\nWorkspace structure sketch:\n\n```text\n🏠 Team Home (orientation, links, what's new)\n📚 Engineering\n   ├── Architecture (overview, ADRs database, diagrams)\n   ├── Runbooks (by service\u002Fsymptom, linked from alerts)\n   ├── Conventions (coding standards, review guide, Git workflow)\n   └── Onboarding (checklist, environment setup, first-week guide)\n📋 Projects (specs database: status views, owners, timelines)\n🚨 Incidents (log database + postmortem template)\n👥 People & Process (rituals, on-call rotation, team norms)\n```\n\n## Common pitfalls\n\n- **The junk drawer.** Pages everywhere, no structure, search as the only navigation. IA first;\n  the \"where does X go?\" guide prevents sprawl.\n- **Docs without owners.** Nobody maintains them; they rot; people stop trusting Notion. Every\n  important page gets an owner and a freshness date.\n- **Duplication.** The same architecture described in 4 pages, all slightly different. Canonical\n  pages + links\u002Fsynced blocks; delete the copies.\n- **Template neglect.** Templates exist but nobody uses them (or they're outdated). Templates\n  are process — review them like process, and make them the path of least resistance.\n- **Over-structuring.** Database properties for everything, 40 views, relation webs nobody\n  understands. Start simple; add structure when the pain is real.\n- **Notion as the system of record for code-adjacent docs.** ADRs and runbooks that belong next\n  to code living only in Notion — drifting from the code they describe. Code-adjacent docs live\n  with code (linked from Notion); Notion holds the human\u002Fprocess layer.\n- **No maintenance ritual.** The wiki was great in month one and a museum by month twelve.\n  Quarterly reviews, freshness dates, and delete permission — maintenance is the feature.\n","# Notion Pro (Dev)\n\n## Overview\n\nNotion as a **developer knowledge system** — specs, runbooks, ADRs, team wikis, project trackers —\nworks when it's structured deliberately and maintained like code. This skill covers organizing\nengineering knowledge in Notion: information architecture, templates, databases for engineering\nworkflows, and API automation that keeps docs alive.\n\nThe through-line: Notion is a tool, not a strategy — structure it around how the team finds and\nmaintains knowledge, or it becomes a beautiful junk drawer.\n\n## When to use\n\n- Setting up team wikis, runbooks, or engineering docs in Notion.\n- Designing Notion databases for specs, incidents, or project tracking.\n- Creating templates for RFCs, postmortems, and onboarding.\n- Automating Notion via its API (syncing docs, reports, trackers).\n- Fixing a Notion workspace that's become unnavigable.\n\n## Core concepts\n\n- **Information architecture first.** Top-level: team home (orientation), docs by domain\n  (engineering areas), runbooks (operations), decisions (ADRs\u002FRFCs), people\u002Fprocess (onboarding,\n  rituals). Shallow, predictable hierarchy — if finding a doc takes more than 3 clicks, the\n  structure failed.\n- **Databases for structured knowledge.** Specs tracker (status, owner, links), incident log\n  (date, severity, postmortem link), ADR database (status: proposed\u002Faccepted\u002Fsuperseded),\n  onboarding checklist. Databases with views (by status, by owner, by team) beat folders of pages.\n- **Templates as process.** RFC template (context, proposal, alternatives, rollout), postmortem\n  template (timeline, root cause, action items with owners), bug report, onboarding checklist.\n  Templates encode \"how we do things\" — new joiners learn the process by using the template.\n- **Docs have owners and freshness.** Every important page: an owner and a \"last verified\" date.\n  Quarterly doc reviews (stale docs flagged, updated or deleted). Ownerless docs rot; dateless\n  docs can't be trusted.\n- **Link, don't duplicate.** One canonical page per topic, linked everywhere it's relevant.\n  Duplicated content diverges — the sync callout or synced block exists for a reason.\n- **API for automation.** Notion's API: sync release notes from GitHub, generate status reports\n  from databases, auto-create incident pages from alerts, back up critical docs. Automation keeps\n  the human-written parts human and the mechanical parts mechanical.\n\n## Practical workflow\n\n1. **Design the IA.** Sketch the top-level structure with the team; agree on where things live\n   (and where they *don't*). Write the \"where does X go?\" guide — it prevents 90% of sprawl.\n2. **Build the core databases.** Specs\u002FRFCs, ADRs, incidents, onboarding — with the views each\n   audience needs (engineers: by status; managers: by timeline; on-call: runbooks by symptom).\n3. **Create the templates.** RFC, ADR, postmortem, runbook, onboarding checklist — each with\n   guidance *in the template* (what goes in each section, with an example).\n4. **Seed with the essentials.** Team home, onboarding guide, architecture overview, runbooks for\n   top alerts, coding conventions. Better a small, accurate wiki than a large, rotting one.\n5. **Establish maintenance rituals.** Doc owners review quarterly; \"last verified\" dates visible;\n   stale-page reports; delete-or-update decisions. Docs are maintained or they're misleading.\n6. **Automate the mechanical.** API syncs for release notes\u002Fchangelogs, incident page creation,\n   weekly digest of doc changes. Keep humans writing judgment; machines moving data.\n\nWorkspace structure sketch:\n\n```text\n🏠 Team Home (orientation, links, what's new)\n📚 Engineering\n   ├── Architecture (overview, ADRs database, diagrams)\n   ├── Runbooks (by service\u002Fsymptom, linked from alerts)\n   ├── Conventions (coding standards, review guide, Git workflow)\n   └── Onboarding (checklist, environment setup, first-week guide)\n📋 Projects (specs database: status views, owners, timelines)\n🚨 Incidents (log database + postmortem template)\n👥 People & Process (rituals, on-call rotation, team norms)\n```\n\n## Common pitfalls\n\n- **The junk drawer.** Pages everywhere, no structure, search as the only navigation. IA first;\n  the \"where does X go?\" guide prevents sprawl.\n- **Docs without owners.** Nobody maintains them; they rot; people stop trusting Notion. Every\n  important page gets an owner and a freshness date.\n- **Duplication.** The same architecture described in 4 pages, all slightly different. Canonical\n  pages + links\u002Fsynced blocks; delete the copies.\n- **Template neglect.** Templates exist but nobody uses them (or they're outdated). Templates\n  are process — review them like process, and make them the path of least resistance.\n- **Over-structuring.** Database properties for everything, 40 views, relation webs nobody\n  understands. Start simple; add structure when the pain is real.\n- **Notion as the system of record for code-adjacent docs.** ADRs and runbooks that belong next\n  to code living only in Notion — drifting from the code they describe. Code-adjacent docs live\n  with code (linked from Notion); Notion holds the human\u002Fprocess layer.\n- **No maintenance ritual.** The wiki was great in month one and a museum by month twelve.\n  Quarterly reviews, freshness dates, and delete permission — maintenance is the feature.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-notion-pro-dev",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-notion-pro-dev",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-notion-pro-dev",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-notion-pro-dev","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-notion-pro-dev\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"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",[],[]]