Add session concierge rule and TasteRay resource map to CLAUDE.md

[michalwolniak-sys]

Co to robi

Na początku sesji (przy pierwszym konkretnym zadaniu) Claude sam sprawdza, czy podłączone repozytoria, serwery MCP i skille pasują do zadania — i jeśli czegoś brakuje, mówi o tym z góry prostym językiem, z konkretnym następnym krokiem (a co może, podłącza sam). Gdy wszystko jest na miejscu, nie wspomina o zasobach i po prostu działa. Dochodzi też zasada: przy funkcjach „na styku dwóch repo" (notyfikacje, karty w iframe, deep linki) Claude nie zgaduje drugiej strony, tylko prosi o brakujące repo.

Po co

Wolniak coraz częściej sam coś buduje w Claude, ale nie ma na tyle głębokiej wiedzy technicznej, żeby zawsze wiedzieć, które repo/narzędzia podłączyć — więc dokładamy do CLAUDE.md kontekst, dzięki któremu Claude sam się o niego upomina.

Zakres

Wyłącznie CLAUDE.md (instrukcje ładowane na starcie sesji) — kod produktu bez zmian. Ta sama sekcja idzie do trzech repo (skills, tasteray-postman, tasteray-mvp), żeby ładowała się niezależnie od tego, które repo jest w sesji — stąd trzy bliźniacze PR-y.

🤖 Generated with Claude Code
https://claude.ai/code/session_01363PA7wb3vD6CPN4982ZDh

---

Generated by Claude Code

Summary by CodeRabbit

• Documentation
  • Updated session setup guidance with enhanced resource availability verification procedures to help identify missing components during initial configuration.
  • Added comprehensive resource mapping documentation clarifying system dependencies, cross-system integration points, and configuration requirements across related components.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 98fad4a2-69b6-4b45-87d0-3bc313c64593

📥 Commits

Reviewing files that changed from the base of the PR and between 07cbeea and 53a82ea.

📒 Files selected for processing (1)

• CLAUDE.md

 _________________________________________________
< We don't ship debt; we refinance it into tests. >
 -------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/stoic-hawking-7har3n

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can use TruffleHog to scan for secrets in your code with verification capabilities.

Add a TruffleHog config file (e.g. trufflehog-config.yml, trufflehog.yml) to your project to customize detectors and scanning behavior. The tool runs only when a config file is present.

[coderabbitai]

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details

{}

[Stasieniec]

Thanks for putting this together — the resource map is genuinely useful context. Two suggestions before merging: one about what goes in, one about where.

1. Let's drop the "Session concierge" rule (plus the MCP-notes, add_repo, and task-table parts)

CLAUDE.md is loaded at the start of every session for everyone working in this repo — including automated/CI runs. So a start-of-session behavioral rule, and especially output "written for a non-technical reader," changes the experience for the whole team, not just one person. That kind of personal default is better kept in personal/user-level config than in the shared repo file.

The MCP-notes paragraph, the add_repo steps, and the task→repo table are tied to cloud session setup rather than being facts about the repo, so they'd come out too. (Same goes for the "duplicated verbatim — update all copies together" footer — that's a maintenance trap waiting to drift.)

2. The repo map is great, but it's mostly already documented — and barely applies here

The identical 39-line block is going into three repos, but each one already documents most of it, in different places. For this repo specifically, almost none of the map is relevant — a skills session rarely needs the cross-repo D1 / notification contracts. The one genuinely useful orientation note is small. Suggest adding this after ## Purpose:

## Where this fits

These skills are consumed by **Ray**, the assistant in `tasteray-mvp` (the Next.js app), for elicitation and recommendation conversations. Siblings: `tasteray-mvp` (the app, owns the main D1) and `tasteray-postman`/**brain** (cards, notifications). You normally only need *this* repo to edit skills.

If we'd rather keep this doc minimal, closing this PR is also fine — the map lands more usefully in the other two.

Companion comments on the sibling PRs (tasteray-postman#67, tasteray-mvp#1044) cover what each of those should keep.