Menu
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
| name | Simplification Cascades |
| description | Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z" |
| when_to_use | when implementing the same concept multiple ways, accumulating special cases, or complexity is spiraling |
| version | 1.1.0 |
Sometimes one insight eliminates 10 things. Look for the unifying principle that makes multiple components unnecessary.
Core principle: "Everything is a special case of..." collapses complexity dramatically.
| Symptom | Likely Cascade |
|---|---|
| Same thing implemented 5+ ways | Abstract the common pattern |
| Growing special case list | Find the general case |
| Complex rules with exceptions | Find the rule that has no exceptions |
| Excessive config options | Find defaults that work for 95% |
Look for:
Ask: "What if they're all the same thing underneath?"
Before: Separate handlers for batch/real-time/file/network data Insight: "All inputs are streams - just different sources" After: One stream processor, multiple stream sources Eliminated: 4 separate implementations
Before: Session tracking, rate limiting, file validation, connection pooling (all separate) Insight: "All are per-entity resource limits" After: One ResourceGovernor with 4 resource types Eliminated: 4 custom enforcement systems
Before: Defensive copying, locking, cache invalidation, temporal coupling Insight: "Treat everything as immutable data + transformations" After: Functional programming patterns Eliminated: Entire classes of synchronization problems
