ams-whiteboard-pro
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
03 SKILL.md 正文
Whiteboard Pro
Overview
Digital whiteboards (Miro, FigJam, Mural, and equivalents) are infinite canvases for visual collaboration: sticky notes, diagrams, flows, and freeform sketching.
They shine for workshops, retros, journey mapping, brainstorming, and planning — anywhere spatial thinking beats documents.
Pro skill: designing boards people can actually use (structure + guidance), facilitating live sessions, and converting output to action.
When to use
- Running remote workshops, retros, or brainstorms
- Facilitating design sprints or planning sessions
- Visual collaboration across time zones (async boards)
- Journey mapping, diagramming, or systems thinking
- Teaching or training with visual interaction
Core concepts
- Board architecture. Zones with clear labels, flow arrows showing sequence, color coding by category. A board should be navigable without a guide.
- Templates. Retro, brainstorm, journey map, kanban, 2x2 — start from templates, customize lightly. Templates teach the method implicitly.
- Facilitation frames. Each activity gets: instructions, example, timer, and a defined output. Frames make async participation possible too.
- Sticky note discipline. One idea per note, short text, color by category/author. 50-word stickies are mini-docs, not brainstorming.
- Dot voting. Converge with limited votes per person. Forces prioritization; surfaces real preferences vs. loudest voices.
- Async boards. Boards that work without live facilitation: clear instructions, examples, deadlines. Essential across time zones.
- Timers and timeboxes. Visible timers per activity. Whiteboard sessions expand without timeboxes — energy and focus are finite.
- Export and action. Boards produce decisions and tasks. Export summaries, assign owners, move tasks to trackers. The board is not the deliverable.
Practical workflow
- Define the outcome. Before building: what decision, list, or plan must this board produce? Design backward from the output.
- Build the board. Zones in sequence, facilitation frames per activity (instructions + example + timer), color legend, clear start point.
- Prepare participants. Share board link + 2-min intro video or instructions ahead. First-time users need onboarding, not just a link.
- Facilitate actively. Welcome, explain, demo one activity, timebox strictly, energize between segments, converge with voting.
- Manage the loud/quiet. Silent brainstorming first (everyone writes), then share. Dot voting over verbal consensus. Structure protects quiet voices.
- Converge deliberately. Cluster, vote, prioritize, decide. End every session with decisions + owners + next steps, captured on the board.
- Follow up async. Share board summary + decisions within 24h. Open items get owners and deadlines in the task tracker.
- Template the winners. Save successful board designs as team templates. Build a library: retro, planning, brainstorm, review.
Common pitfalls
- Blank canvas chaos. 'Here's a board, go!' produces mess and silence. Structure + instructions + examples, always.
- No timeboxes. Open-ended whiteboarding drains energy and overruns. Timers visible, segments tight, breaks scheduled.
- Facilitation-free. Assuming the board runs itself. Someone must facilitate: guide, timekeep, converge, decide.
- Sticky novels. Paragraphs on stickies kill scanning and clustering. One idea, few words, always.
- Skipping convergence. Divergent brainstorms with no voting or prioritizing. The session must end with decisions, not just ideas.
- Board as archive. Important outcomes living only on the board. Export decisions/tasks to durable systems; boards are working space.
- Ignoring async participants. Designing only for live attendees. Frames with instructions let timezone-shifted teammates contribute meaningfully.
- Tool wars. Debating platforms instead of facilitating. Pick one team standard; the facilitation matters 10x more than the tool.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
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/CSS, 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.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
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).