skills/focus-a-model-of-sensemaking/SKILL.md
Use for sensemaking, frame revision, anomaly handling, questioning strategy, and ambiguity diagnosis with the Data/Frame model before action is chosen. NOT for deterministic classification, settled execution planning, or situations where the frame is already stable.
npx skillsauth add curiositech/windags-skills focus-a-model-of-sensemakingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Source basis: the Data/Frame model from Klein Associates on how people build, test, preserve, and replace interpretive frames under ambiguity.
flowchart TD
A[Ambiguous or unstable situation] --> B[Name current frame]
B --> C{Which function fits now?}
C -->|Elaborate| D[Add detail within current frame]
C -->|Question| E[Test assumptions inside the frame]
C -->|Preserve| F[Handle minor inconsistency cheaply]
C -->|Compare| G[Assess competing frames]
C -->|Seek| H[Gather evidence to stress-test the frame]
C -->|Re-frame| I[Replace the active interpretation]
D --> J{Anomalies accumulating?}
E --> J
F --> J
G --> J
H --> J
I --> K[Set explicit transition to decision-making]
J -->|Yes| G
J -->|No| K
references/data-frame-reciprocity-in-agent-systems.md: load when designing the loop between current interpretation and next evidence sought.references/fragmentary-mental-models-for-agents.md: load when choosing what kind of knowledge structures to give the system.references/sensemaking-decision-making-separation.md: load when action bias is collapsing understanding and decision into one phase.references/expert-questioning-strategies.md: load when question quality, not question quantity, is the real bottleneck.references/frame-elaboration-vs-frame-comparison.md: load when the system is stuck preserving one frame for too long.references/sensemaking-triggers-and-anomaly-detection.md: load when you need criteria for when deliberate sensemaking should start.data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.