windrose-md

How to drive the live Windrose plugin via the windrose MCP tools — find/open maps, see the canvas, place tiles/objects, verify changes. Use whenever interacting with the running Obsidian instance through mcp__windrose__* tools. Eval is the LAST resort; this skill maps every common task to its dedicated tool and documents the proven eval recipes for the rare rest.

Use this skill whenever writing, reviewing, or refactoring any CSS, whether in plain .css files, styled-components, CSS Modules, Tailwind arbitrary values, inline styles in React/Vue/Svelte, or any other frontend context. This skill ensures modern CSS features are used wherever browser support allows — things like clamp(), :has(), container queries, OKLCH colors, scroll-driven animations, anchor positioning, @starting-style, light-dark(), text-wrap: balance, and more. Trigger this skill any time CSS is being written or touched, even indirectly (e.g. a component that needs responsive sizing, a theme system, an animation, a layout). Do NOT default to legacy patterns like px-based media queries, JS-driven animations, or CSS-in-JS workarounds when a native modern CSS feature exists and is supported by the project's browser targets.

Four-axis debug harness for the running Obsidian app — compile, static-verify, runtime-probe, visual-confirm. Use for any UI, plugin, or integration change where you need to see/prove the live state.

Perform thorough code review of staged changes in the src directory. Reviews for coding best practices, project patterns, type safety, and potential issues. Runs review-comments skill afterward.

Reviews recent code changes for frivolous, overly verbose, or LLM-like comments and removes them. Use when you want to clean up comment noise from recent commits, after generating code, or when explicitly asked to review comments.

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"