muslewski

Use when the user wants to adopt this knowledge base, onboard a brownfield vault, act on "atlas adopt reported unclassified notes", or migrate existing docs/mind into atlas. Deterministic adopt first; this skill classifies leftover notes and proposes zone cards without stamping.

Use when navigating a repo's code or its Atlas — locating a definition/usage/file, tracing an import, or finding which zone/decision/spec explains something. Reach here before reflexive grep+Read.

Use when finishing a change in a repo that has an Atlas — before ending the session or opening a PR, to keep the vault's zone cards, stamps, and ledger entries in sync with the code just changed.

Use when an Atlas vault is empty or near-empty (0–2 zones after atlas init) — bootstrap 4–8 seeded zone cards from a real codebase analysis. Also use for "seed the mind", "initial zones", "first map pass", "bootstrap atlas", or atlas-fleet seed-empty.

Use when the user wants to update atlas, an atlas update is available, doctor or status reports a version nudge / pending migrations, or they ask to bring the vault to latest. Deterministic migrate first; this skill handles AI-merge of locally edited vendored files.

Use when authoring or editing an Atlas note (zone, decision, spec, plan, idea, debt, pillar) — the summary and section structure determine what a retrieval engine surfaces later.

Use when navigating this repo's code or Mind — find a definition/usage/file, trace an import, locate which note/decision explains something. Reach here BEFORE reflexive grep+Read.

Use at the start of any task in this repo to orient before coding — find the right zone, its anchors, invariants, and lineage via the Mind (fairy-tale-mind/).

Use when writing or editing any user-facing copy for Yours Fairy Tale — headlines, subheads, CTAs, button labels, microcopy, errors, empty states, emails, notifications, or marketing text.

Use when integrating Better Auth with PayloadCMS v3 in a Next.js app — adding customer accounts alongside Payload's native admin panel, bridging Better Auth to Payload's database, or deciding sign-up/session/access-control patterns. Especially before reaching for the payload-auth plugin or making a customer users collection auth:true.

Use when adding or editing the transitions between page sections on Yours Fairy Tale — the "waves" / dividers between differently-colored full-bleed sections, or the footer's entry wave. Apply on every page, not just the homepage.

Use when starting work, before opening a PR, or resolving a merge conflict while other agent sessions may be running in parallel on the same repo. Coordinate through the `sage` CLI — collision check, claim intent, merge brief, why-diverged — so parallel sessions merge smoothly. Advisory only; a silent no-op when SAGE is off or not installed.

Validate the SAGE fleet-judge install — config, emitter hook, settings wiring, linked skills, current repo. Trigger: /sage-doctor

Use when navigating this repo's code or Mind — find a definition/usage/file, trace an import, locate which note/decision explains something. Reach here BEFORE reflexive grep+Read.

Use FIRST when starting work in the ogrody-kryscar repo — orient via the Mind (kryscar-mind/) before reading code, so you don't reinvent existing zones. Points to the Map index, zone cards, and conventions.

Use when authoring or editing an Atlas note (zone, decision, spec, plan, idea, debt, pillar) — the summary and section structure determine what a retrieval engine surfaces later.

Use when you want two different frontier models fused into one advisor brain for a high-leverage decision — "fuse", "fusion advisor", "get a second/peer model on this", "have Grok weigh in", "advisor fusion", "am I sure — bring in another model". This session reasons, consults a second frontier model (Grok) as a context-isolated peer, reconciles by verifying (not voting), then delegates execution via the `armory` launcher. NOT for routine steps (cost gate), and NOT for execution dispatch (that is the `armory` launcher).