← ClaudeAtlas

week-startlisted

Run the Week-Ahead Scan for the trading journal (CLAUDE.md Section 13, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively through the trading-journal MCP server, no markdown output. Context only — creates no verdict, thesis, or hypothetical. Invoke Sunday evening or Monday morning, before that day's daily session.
latuconsinafr/claude-code-config · ★ 0 · AI & Automation · score 65
Install: claude install-skill latuconsinafr/claude-code-config
# Week-Ahead Scan (global, MCP-only) **Replaces the old project-local `/week-start`** (formerly at `Journals/.claude/skills/week-start/`, deferring to `Journals/PROMPTS.md`). Same reasoning as `sod/SKILL.md`'s header — that file and `PROMPTS.md` are left in place, unused. `CLAUDE.md` at `/Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md` remains the rulebook; §13 governs this cadence's cascade rule. **Instruments — resolved live via `get_active_instruments`, same as `sod/SKILL.md`.** Call it in Step 0 alongside the connectivity check and use its full pair codes for every subsequent MCP call — do not assume EU/GU/UJ/XAU (used here for readability only) is still the active set. **This still sets context only — no verdict, thesis, or hypothetical.** Those only ever originate from a daily (`/sod`) session; if asked for a directional call here, decline and point to `/sod`. **It does, as of 2026-08-25, produce a real weekly technical score and fundamental digest** for the heatmap (`write_technical_score`/`write_fundamental_digest`, timeframe `1W`) — that's scoring, not a trading decision, and the distinction stays absolute: a number on the heatmap is not a verdict. **As of 2026-08-30, it also writes validated levels** (`write_level`, timeframe `1W`) for any zone named in Step 4.2 that clears §3.3's validation bar — `get_active_levels` has no timeframe filter, so a weekly level surfaces on the "levels to watch" widget alongside daily ones from `/sod`. ## Step 0 — confirm