[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWEBTA466Z9PSRFHAY1YF1":3,"skill-same:01M7EWEBTA466Z9PSRFHAY1YF1":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},"01M7EWEBTA466Z9PSRFHAY1YF1","ams-whiteboard-pro",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-whiteboard-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: whiteboard-pro\ndescription: Master digital whiteboards: facilitation, templates, visual collaboration, and workshop design. Use when running remote workshops, brainstorms, or visual planning sessions.\ncategory: productivity\n---\n\n# Whiteboard Pro\n\n## Overview\n\nDigital whiteboards (Miro, FigJam, Mural, and equivalents) are infinite canvases for visual collaboration: sticky notes, diagrams, flows, and freeform sketching.\n\nThey shine for workshops, retros, journey mapping, brainstorming, and planning — anywhere spatial thinking beats documents.\n\nPro skill: designing boards people can actually use (structure + guidance), facilitating live sessions, and converting output to action.\n\n## When to use\n\n- Running remote workshops, retros, or brainstorms\n- Facilitating design sprints or planning sessions\n- Visual collaboration across time zones (async boards)\n- Journey mapping, diagramming, or systems thinking\n- Teaching or training with visual interaction\n\n## Core concepts\n\n- **Board architecture.**\n  Zones with clear labels, flow arrows showing sequence, color coding by category. A board should be navigable without a guide.\n- **Templates.**\n  Retro, brainstorm, journey map, kanban, 2x2 — start from templates, customize lightly. Templates teach the method implicitly.\n- **Facilitation frames.**\n  Each activity gets: instructions, example, timer, and a defined output. Frames make async participation possible too.\n- **Sticky note discipline.**\n  One idea per note, short text, color by category\u002Fauthor. 50-word stickies are mini-docs, not brainstorming.\n- **Dot voting.**\n  Converge with limited votes per person. Forces prioritization; surfaces real preferences vs. loudest voices.\n- **Async boards.**\n  Boards that work without live facilitation: clear instructions, examples, deadlines. Essential across time zones.\n- **Timers and timeboxes.**\n  Visible timers per activity. Whiteboard sessions expand without timeboxes — energy and focus are finite.\n- **Export and action.**\n  Boards produce decisions and tasks. Export summaries, assign owners, move tasks to trackers. The board is not the deliverable.\n\n## Practical workflow\n\n1. **Define the outcome.**\n   Before building: what decision, list, or plan must this board produce? Design backward from the output.\n2. **Build the board.**\n   Zones in sequence, facilitation frames per activity (instructions + example + timer), color legend, clear start point.\n3. **Prepare participants.**\n   Share board link + 2-min intro video or instructions ahead. First-time users need onboarding, not just a link.\n4. **Facilitate actively.**\n   Welcome, explain, demo one activity, timebox strictly, energize between segments, converge with voting.\n5. **Manage the loud\u002Fquiet.**\n   Silent brainstorming first (everyone writes), then share. Dot voting over verbal consensus. Structure protects quiet voices.\n6. **Converge deliberately.**\n   Cluster, vote, prioritize, decide. End every session with decisions + owners + next steps, captured on the board.\n7. **Follow up async.**\n   Share board summary + decisions within 24h. Open items get owners and deadlines in the task tracker.\n8. **Template the winners.**\n   Save successful board designs as team templates. Build a library: retro, planning, brainstorm, review.\n\n## Common pitfalls\n\n- **Blank canvas chaos.**\n  'Here's a board, go!' produces mess and silence. Structure + instructions + examples, always.\n- **No timeboxes.**\n  Open-ended whiteboarding drains energy and overruns. Timers visible, segments tight, breaks scheduled.\n- **Facilitation-free.**\n  Assuming the board runs itself. Someone must facilitate: guide, timekeep, converge, decide.\n- **Sticky novels.**\n  Paragraphs on stickies kill scanning and clustering. One idea, few words, always.\n- **Skipping convergence.**\n  Divergent brainstorms with no voting or prioritizing. The session must end with decisions, not just ideas.\n- **Board as archive.**\n  Important outcomes living only on the board. Export decisions\u002Ftasks to durable systems; boards are working space.\n- **Ignoring async participants.**\n  Designing only for live attendees. Frames with instructions let timezone-shifted teammates contribute meaningfully.\n- **Tool wars.**\n  Debating platforms instead of facilitating. Pick one team standard; the facilitation matters 10x more than the tool.\n","# Whiteboard Pro\n\n## Overview\n\nDigital whiteboards (Miro, FigJam, Mural, and equivalents) are infinite canvases for visual collaboration: sticky notes, diagrams, flows, and freeform sketching.\n\nThey shine for workshops, retros, journey mapping, brainstorming, and planning — anywhere spatial thinking beats documents.\n\nPro skill: designing boards people can actually use (structure + guidance), facilitating live sessions, and converting output to action.\n\n## When to use\n\n- Running remote workshops, retros, or brainstorms\n- Facilitating design sprints or planning sessions\n- Visual collaboration across time zones (async boards)\n- Journey mapping, diagramming, or systems thinking\n- Teaching or training with visual interaction\n\n## Core concepts\n\n- **Board architecture.**\n  Zones with clear labels, flow arrows showing sequence, color coding by category. A board should be navigable without a guide.\n- **Templates.**\n  Retro, brainstorm, journey map, kanban, 2x2 — start from templates, customize lightly. Templates teach the method implicitly.\n- **Facilitation frames.**\n  Each activity gets: instructions, example, timer, and a defined output. Frames make async participation possible too.\n- **Sticky note discipline.**\n  One idea per note, short text, color by category\u002Fauthor. 50-word stickies are mini-docs, not brainstorming.\n- **Dot voting.**\n  Converge with limited votes per person. Forces prioritization; surfaces real preferences vs. loudest voices.\n- **Async boards.**\n  Boards that work without live facilitation: clear instructions, examples, deadlines. Essential across time zones.\n- **Timers and timeboxes.**\n  Visible timers per activity. Whiteboard sessions expand without timeboxes — energy and focus are finite.\n- **Export and action.**\n  Boards produce decisions and tasks. Export summaries, assign owners, move tasks to trackers. The board is not the deliverable.\n\n## Practical workflow\n\n1. **Define the outcome.**\n   Before building: what decision, list, or plan must this board produce? Design backward from the output.\n2. **Build the board.**\n   Zones in sequence, facilitation frames per activity (instructions + example + timer), color legend, clear start point.\n3. **Prepare participants.**\n   Share board link + 2-min intro video or instructions ahead. First-time users need onboarding, not just a link.\n4. **Facilitate actively.**\n   Welcome, explain, demo one activity, timebox strictly, energize between segments, converge with voting.\n5. **Manage the loud\u002Fquiet.**\n   Silent brainstorming first (everyone writes), then share. Dot voting over verbal consensus. Structure protects quiet voices.\n6. **Converge deliberately.**\n   Cluster, vote, prioritize, decide. End every session with decisions + owners + next steps, captured on the board.\n7. **Follow up async.**\n   Share board summary + decisions within 24h. Open items get owners and deadlines in the task tracker.\n8. **Template the winners.**\n   Save successful board designs as team templates. Build a library: retro, planning, brainstorm, review.\n\n## Common pitfalls\n\n- **Blank canvas chaos.**\n  'Here's a board, go!' produces mess and silence. Structure + instructions + examples, always.\n- **No timeboxes.**\n  Open-ended whiteboarding drains energy and overruns. Timers visible, segments tight, breaks scheduled.\n- **Facilitation-free.**\n  Assuming the board runs itself. Someone must facilitate: guide, timekeep, converge, decide.\n- **Sticky novels.**\n  Paragraphs on stickies kill scanning and clustering. One idea, few words, always.\n- **Skipping convergence.**\n  Divergent brainstorms with no voting or prioritizing. The session must end with decisions, not just ideas.\n- **Board as archive.**\n  Important outcomes living only on the board. Export decisions\u002Ftasks to durable systems; boards are working space.\n- **Ignoring async participants.**\n  Designing only for live attendees. Frames with instructions let timezone-shifted teammates contribute meaningfully.\n- **Tool wars.**\n  Debating platforms instead of facilitating. Pick one team standard; the facilitation matters 10x more than the tool.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-whiteboard-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":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-whiteboard-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-whiteboard-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-whiteboard-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-whiteboard-pro\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",[],[]]