skills/fancy-yard-landscaper/SKILL.md
Expert landscape designer transforming yards through photo mapping, 3D visualization, seasonal planning, and deep plant knowledge. Specializes in fast-growing privacy screens (knows arborvitae pitfalls), architecture-appropriate design, outdoor living spaces, and realistic maintenance expectations. Activate on "landscape design", "yard design", "garden planning", "plant selection", "privacy screen", "outdoor living", "backyard makeover", "arborvitae", "hedge", "fast growing tree", "landscaping ideas". NOT for interior design (use interior-design-expert), hardscape construction (consult contractors), or lawn care chemicals (consult local experts).
npx skillsauth add curiositech/windags-skills fancy-yard-landscaperInstall 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.
Transform your outdoor space into a beautiful, functional landscape with expert plant knowledge and design principles.
CLIENT REQUEST → First Assessment
├── Has photos + measurements + specific needs?
│ ├── YES → Proceed to analysis phase
│ └── NO → STOP. Get documentation first (see Quality Gates)
│
├── ANALYSIS PHASE: What's the primary constraint?
│ ├── PRIVACY (most common)
│ │ ├── Need screening within 2 years?
│ │ │ ├── YES → Fast-growth options + fence hybrid
│ │ │ └── NO → Quality long-term species
│ │ └── Deer pressure high?
│ │ ├── YES → Avoid arborvitae, use resistant species
│ │ └── NO → Full plant palette available
│ │
│ ├── SHADE/SUN Issues
│ │ ├── Less than 3 hours sun?
│ │ │ ├── YES → Shade-tolerant palette only
│ │ │ └── NO → Assess partial vs full sun zones
│ │ └── More than 8 hours intense sun?
│ │ ├── YES → Drought-tolerant, heat-resistant
│ │ └── NO → Standard sun/part-shade options
│ │
│ └── BUDGET Constraints
│ ├── Under $2000 total?
│ │ ├── YES → Phased approach, start with structure
│ │ └── NO → Can do comprehensive design
│ └── DIY vs Professional install?
│ ├── DIY → Simplify design, standard plants
│ └── PRO → More complex features possible
DRAINAGE ASSESSMENT (critical but often skipped)
├── Does water pool after rain?
│ ├── YES → Poor drainage confirmed
│ │ ├── Clay soil + pooling → Install bioswale or French drain
│ │ ├── Just clay → Amend beds with compost + sand
│ │ └── Compacted → Core aeration + organic matter
│ │
│ └── NO → Test infiltration rate
│ ├── Dig 12" hole, fill with water, time drainage
│ ├── Drains in <2 hours → Good drainage, standard plants
│ ├── 2-6 hours → Moderate, some wet-soil adaptations
│ └── >6 hours → Poor drainage, see above solutions
│
├── PLANT SELECTION SHIFTS based on drainage:
│ ├── Poor drainage → River birch, bald cypress, inkberry holly
│ ├── Good drainage → Standard palette
│ └── Excellent drainage → Drought-tolerant, Mediterranean plants
URGENCY vs QUALITY Trade-off
├── IMMEDIATE (fence + plants)
│ ├── 6' fence now, plants to soften/replace over time
│ ├── Cost: $25-50/linear foot fencing + $200-400 plants
│ └── Result: Privacy now, beauty in 3-5 years
│
├── FAST (2-3 years acceptable)
│ ├── 6-8' specimens of proven species
│ ├── Cost: $150-300 per plant, closer spacing
│ └── Result: Screening in 2-3 years, mature in 5-7
│
└── PATIENT (5+ years acceptable)
├── 3-5' healthy nursery stock, proper spacing
├── Cost: $50-100 per plant, wider spacing
└── Result: Better long-term health, lower cost
DETECTION RULE: Client says "I want arborvitae for privacy" as first plant mentioned SYMPTOMS: Fixated on single species, ignores site conditions, dismisses alternatives DIAGNOSIS: Falling for nursery marketing without understanding trade-offs FIX:
DETECTION RULE: Spacing plants based on nursery size, not mature spread SYMPTOMS: Plants too close to house/fence/each other, "room for one more" thinking DIAGNOSIS: Not visualizing 10-20 year growth FIX:
DETECTION RULE: Any plant within 3 feet of house foundation SYMPTOMS: Shrubs touching walls, blocking windows, pest entry points DIAGNOSIS: Traditional "foundation planting" mentality without modern understanding FIX:
DETECTION RULE: Planning around clearance/sale plants without species research SYMPTOMS: "I got 20 arborvitae for $300!" without knowing mature needs DIAGNOSIS: Price-first instead of site-appropriate selection FIX:
DETECTION RULE: Client wants "low maintenance" but selects high-maintenance plants SYMPTOMS: Roses + boxwood + pristine lawn + perfect edges desired with "no work" DIAGNOSIS: Instagram expectations without reality check FIX:
SCENARIO: Colonial home, 40' back fence needs screening, heavy deer pressure, $3000 budget, 5-year timeline acceptable
DECISION PROCESS:
NOVICE WOULD MISS: Would pick arborvitae based on "fast growing" label, ignore deer evidence EXPERT CATCHES: Deer scat near fence = avoid deer-favorite plants, mix species for resilience
OUTCOME: Initial slower growth but no deer damage, full screening by Year 5, 20+ year lifespan
SCENARIO: Townhouse backyard, 80% shade from surrounding buildings, wants "garden room" feel, concrete patio exists
DECISION PROCESS:
NOVICE WOULD MISS: Would try sun plants in shade, create busy mixed borders EXPERT CATCHES: Embrace shade as design opportunity, use foliage contrast instead of flowers
OUTCOME: Sophisticated shade garden, low maintenance, year-round structure
SCENARIO: Ranch home, noisy road frontage, $1200 budget, need screening ASAP, willing to replace in 10-15 years
DECISION PROCESS:
TRADE-OFF ANALYSIS:
EXPERT INSIGHT: Sometimes temporary solutions are appropriate if client understands trade-offs explicitly
This skill should NOT be used for:
Delegation Points:
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.