skills/personal-finance-coach/SKILL.md
Expert personal finance coach with deep knowledge of tax optimization, investment theory (MPT, factor investing), retirement mathematics (Trinity Study, SWR research), and wealth-building strategies grounded in academic research. Activate on 'personal finance', 'investing', 'retirement planning', 'tax optimization', 'FIRE', 'SWR', '4% rule', 'portfolio optimization'. NOT for tax preparation services, specific securities recommendations, guaranteed return promises, or replacing licensed financial advisors for complex situations.
npx skillsauth add curiositech/windags-skills personal-finance-coachInstall 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 personal finance coach grounded in academic research and quantitative analysis, not platitudes.
CLIENT PROFILE ASSESSMENT:
├── Income < $75K annually?
│ ├── Emergency fund < 3 months? → Build emergency fund first (HYSA)
│ ├── No 401k match? → Target-date fund in 401k, maximize match
│ └── Basic setup: 80/20 stocks/bonds, 3-fund portfolio maximum
├── Income $75K-$250K annually?
│ ├── Time horizon > 20 years?
│ │ ├── High volatility tolerance? → 90/10 stocks/bonds, tilt small/value
│ │ └── Moderate tolerance? → 70/30 stocks/bonds, broad market
│ ├── Time horizon 10-20 years?
│ │ ├── Moderate tolerance? → 60/40 stocks/bonds
│ │ └── Low tolerance? → 50/50 stocks/bonds, consider I-bonds
│ └── Time horizon < 10 years? → Conservative allocation, bond ladder
└── Income > $250K annually?
├── Tax optimization priority? → Asset location strategy, tax-loss harvesting
├── Retirement in 15+ years? → Factor tilting, international diversification
└── Complex situation? → ESCALATE to fee-only fiduciary advisor
CURRENT CAPE LEVEL:
├── CAPE < 15 (cheap market):
│ ├── Conservative personality? → 4.0% SWR
│ ├── Flexible spending? → 4.5% SWR with guardrails
│ └── Very flexible? → 5.0% SWR with dynamic adjustments
├── CAPE 15-25 (normal market):
│ ├── 30+ year horizon? → 4.0% SWR
│ ├── 20-30 year horizon? → 3.5% SWR
│ └── <20 year horizon? → 3.0% SWR
└── CAPE > 25 (expensive market, like today):
├── Inflexible spending? → 3.0% SWR maximum
├── Some flexibility? → 3.5% SWR with guardrails
└── High flexibility? → 4.0% SWR with dynamic withdrawals
Detection Rule: If portfolio has >5 asset classes or >10 holdings Symptoms: Tracking spreadsheets, constant rebalancing anxiety, minimal performance difference Fix: Consolidate to 3-fund portfolio (Total Stock, International, Bonds). Complexity rarely beats simplicity after costs.
Detection Rule: If making investment decisions primarily for tax benefits Symptoms: "I bought this REIT because it's tax-deductible," avoiding index funds for "tax efficiency" Fix: Optimize for after-tax returns first, tax efficiency second. A 7% taxable return beats a 4% tax-free return if you're in the 25% bracket.
Detection Rule: If using 4% rule without checking current market valuations Symptoms: "Trinity Study says 4% is safe forever," ignoring that CAPE is currently 30+ (historically expensive) Fix: Adjust SWR based on starting valuations. At CAPE 30+, start at 3.0-3.5% maximum.
Detection Rule: If retirement plan uses average returns without modeling order of returns Symptoms: "Market averages 10%, so I need $1M for $100K/year," no contingency for early bear markets Fix: Model sequence risk scenarios. Plan flexibility (cut spending 10-20%) or use dynamic withdrawal strategies.
Detection Rule: If spending months researching 0.1% expense ratio differences while missing employer match Symptoms: Endless forum posts about Vanguard vs. Fidelity, no actual investing happening Fix: "Good enough" beats "perfect." Start with target-date fund, optimize later.
Scenario: Sarah, 45, accumulated $1.2M, wants to retire. Current CAPE: 32 (expensive).
Decision Process:
Implementation: Use Guyton-Klinger guardrails—if withdrawal rate climbs to 4.2% (20% above 3.5%), cut spending 10%. If it drops to 2.8%, can increase spending 10%.
Scenario: Mike, 35, software engineer earning $180K, wants to optimize taxes.
Decision Process:
Result: Saves ~$1,500 annually in taxes through proper asset location alone.
Scenario: Janet, 62, planning retirement at 65 with $800K portfolio, needs $40K annually.
Decision Process:
Implementation: Reduce equity allocation from 80% to 50% over 3 years, plan 3.5% initial withdrawal rate with part-time income bridge.
Before completing any personal finance recommendation, verify:
Do NOT use this skill for:
Escalation Triggers:
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.