SERP TOC

Use this skill as the start-here routing layer for SERP work. The serp repo is the org-level docs hub, not the source of truth for most code, secrets, or runtime operations.

Workflow

1. Start in the SERP docs hub before guessing.

• Read README.md and docs/README.md in serp.
• For repo lookup, prefer docs/REPOS.local.md when it exists. Fall back to docs/REPOS.md for the shared inventory.
• Use docs/WORKFLOWS.md when the real question is where something should live.

2. Route to the owning repo quickly.

• For server, infrastructure, operator access, SSH, Jupyter, or runtime ops, jump to docs/knowledge/server-systems.md in serp first, then follow its pointers into serp-server.
• For secrets, env values, tokens, or secret storage, jump to the secrets.serp.co entry in docs/REPOS.local.md, then inspect /Users/devin/dev/repos/secrets.serp.co/README.md.
• For general app, auth, DB, monorepo, or utility code, find the repo in docs/REPOS.local.md and read that repo's README.md before doing anything app-specific.

3. Use the right docs lane.

• Use GitHub Issues for tasks, bugs, follow-ups, and open questions.
• Use docs/inbox/ for rough notes worth keeping.
• Use docs/knowledge/ for stable cross-repo reference material.
• Move mature repo-specific documentation into the owning repo instead of expanding the hub.

Branch Orientation

• Assume the repo's default branch first, not a random feature branch.
• In the serp hub repo, verified branches on 2026-04-03 were main, origin/main, origin/ds/company-module, and several origin/devinschumacher-patch-* branches.
• Treat devinschumacher-patch-* branches as patch branches unless the user says otherwise.
• When branch choice matters, inspect the owning repo directly with a read-only git command instead of carrying assumptions across repos.

High-Value Pointers

• Repo map and local clone paths: serp/docs/REPOS.local.md, then serp/docs/REPOS.md
• Server and infra routing: serp/docs/knowledge/server-systems.md
• Shared workflow placement rules: serp/docs/WORKFLOWS.md
• AI rule and security reminders: serp/docs/knowledge/ai-coding/rules/README.md and serp/docs/knowledge/ai-coding/rules/security.md
• Legacy aliases and older naming: serp/docs/inbox/2026-04-legacy-serp-map-notes.md

Quick Commands

• rg -n "^#### \serp-server`" docs/REPOS.local.md docs/REPOS.md`
• rg -n "^#### \secrets\.serp\.co`" docs/REPOS.local.md docs/REPOS.md`
• rg -n "server|JUPYTER|ACCESS|infra" docs/knowledge docs/REPOS*.md
• rg -n "serp-secrets|secrets\\.serp\\.co" docs

Reference

Read references/routing-map.md when you need the concrete repo-by-repo start points, local paths, or topic-to-repo routing shortcuts.