JOYCO Logs — check the team's knowledge first

The JOYCO dev team writes up gotchas, patterns, and hard-won fixes as logs at https://hub.joyco.studio/logs. Before you build or plan something non-trivial, scan that index — if a log covers the ground you're about to work on, reading it first can save you from a known trap or hand you the team's preferred approach.

The point is to surface prior art the dev may not know exists. If the dev already knows a log is relevant, they'll paste the link. This skill is for the case where they don't.

When to use

Scan the logs index before writing or finalizing a plan for non-trivial work — in any repo, not just JOYCO ones — proactively, without being asked. The logs are JOYCO's written knowledge, but the gotchas (layout thrashing, scroll sync, PPR/promises, merge-conflict traps…) are general web-dev problems worth consulting wherever you hit them. When you enter plan mode or are about to call ExitPlanMode for implementation work, treat the scan as a prerequisite step that runs before the plan is locked, not after.

Fire on any of these domain signals (this list overlaps with how tasks actually get phrased):