skills/interior-design-expert/SKILL.md
Expert interior designer with deep knowledge of space planning, color theory (Munsell, NCS), lighting design (IES standards), furniture proportions, and AI-assisted visualization. Use for room layout optimization, lighting calculations, color palette selection for interiors, furniture placement, style consultation. Activate on "interior design", "room layout", "lighting design", "furniture placement", "space planning", "Munsell color". NOT for exterior/landscape design, architectural structure, web/UI design (use web-design-expert), brand color theory (use color-theory-palette-harmony-expert), or building codes/permits.
npx skillsauth add curiositech/windags-skills interior-design-expertInstall 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.
Expert interior designer combining classical training with computational design tools and AI-assisted visualization.
INPUT: Room dimensions, natural light, budget, lifestyle
├── Small room (<15m²) + Limited natural light
│ └── Scandinavian: White walls, light wood, maximize reflection
├── Large room (>30m²) + High budget
│ ├── Traditional decor style → Mid-Century Modern: Statement pieces, rich materials
│ └── Minimal lifestyle → Japandi: Low furniture, earth tones, negative space
├── Medium room + Family with children
│ └── Transitional: Durable fabrics, rounded corners, washable surfaces
└── Any size + Bold personality
└── Maximalist: Curated collections, pattern mixing, rich color layers
ROOM TYPE → PRIORITY ORDER
Living Room: Ambient (recessed) → Accent (table lamps) → Task (reading light)
Kitchen: Task (under-cabinet) → Ambient (pendant) → Accent (art lighting)
Bedroom: Ambient (soft ceiling) → Task (bedside) → Accent (mood lighting)
Home Office: Task (desk lamp) → Ambient (overhead) → Accent (wall wash)
BUDGET CONSTRAINTS:
High budget: All three layers + smart controls
Medium budget: Ambient + Task, manual controls
Low budget: Focus on Task lighting, supplement with floor lamps
1. Assess natural light:
├── North-facing → Warm undertones (avoid cool grays)
├── South-facing → Can handle cool tones
└── East/West → Test at different times
2. Room function priority:
├── Sleep/relax → Low chroma, warm colors (Munsell value 6-8)
├── Work/focus → Mid-chroma, balanced temperature (value 5-7)
└── Entertain → Higher chroma acceptable (value 4-9)
3. Size perception needs:
├── Make larger → Light values (7-9), cool hues
└── Make cozier → Mid values (4-6), warm hues
Detection Rule: If all furniture matches a single trending aesthetic without considering room constraints Symptoms: Mid-Century pieces crammed in Victorian house, Scandinavian all-white in dark north-facing room Fix: Analyze actual conditions first: room proportions, light quality, architectural style, lifestyle needs
Detection Rule: If room has only one central light source Symptoms: Harsh shadows on faces, can't read comfortably, no ambiance control Fix: Layer lighting - add table lamps for ambient, task lighting for activities, dimmers for flexibility
Detection Rule: If furniture clearances are <450mm or sectional blocks 50%+ of room circulation Symptoms: Can't walk around furniture, room feels cramped despite adequate square footage Fix: Map circulation paths first (900-1200mm primary), then size furniture to remaining space
Detection Rule: If paint colors chosen from tiny swatches or computer screens only Symptoms: Color looks completely different once painted, clashes with lighting, regret and repainting costs Fix: Test large samples (60x60cm minimum) in YOUR lighting conditions for 48+ hours
Detection Rule: If all major furniture pieces share identical finish/style/era Symptoms: Room feels like showroom floor, lacks personality and visual interest Fix: Follow 60-30-10 rule - 60% neutral base, 30% coordinating elements, 10% accent colors/styles
Context: 25m² studio, north-facing window, €3000 budget, young professional
Step 1 - Space Analysis: North light = warm color bias needed, single room = zones required Decision Point Applied: Small room + limited light → Scandinavian approach with strategic zoning
Step 2 - Layout Strategy:
Step 3 - Color Selection:
Step 4 - Lighting Layers:
Trade-off Analysis: Chose multipurpose furniture over separate pieces (ottoman storage vs separate ottoman + storage cabinet) - less visual clutter but reduced specialized function.
Context: 40m² living room, low ceilings (2.4m), active family with toddler
Step 1 - Constraint Analysis: Low ceiling = no chandeliers, toddler = no sharp edges/fragile items Decision Point Applied: Medium room + family → Transitional style with safety priorities
Step 2 - Lighting Challenge: Single central fixture created harsh shadows, couldn't read on sofa Failure Mode Avoided: Lighting Desert - added three layers instead of upgrading single fixture
Step 3 - Layer Implementation:
Step 4 - Safety Integration: Rounded coffee table, wall-mounted TV, covered outlets, no floor lamps in toddler paths
Trade-off Analysis: Higher-quality fewer pieces vs more budget options - chose durable sofa in performance fabric over multiple cheaper furniture pieces.
Do NOT use interior-design-expert for:
Delegate to other skills when:
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.