About the Seminar
Most AI coding tutorials assume a single repo on your laptop. Real teams don't work that way.
This workshop walks from the simple case (five repos, all cloned locally) to the real case (dozens of repos, each developer with a partial checkout) and shows how to scale agentic development anyway.
We build a progressive toolchain - each tool is introduced once, then reused in every subsequent block:
| Layer | Role |
| Cursor | Local agent IDE — rules, skills, multi-root workspace |
| Meta repo | Orchestration, knowledge, cross-repo conventions |
| Reposwarm | Generated architecture catalog across the org |
| Cloud agents | Full-org visibility without every dev cloning everything |
| Automations | Hooks, scheduled runs, repeatable team workflows |
Who Is This Seminar For?
Developers (mid-level and above), tech leads and platform engineers who already work - or expect to work - in organizations with multiple repositories: microservices, monorepo-adjacent polyrepos, product + infra + shared-library splits or client/partner repo boundaries.
This workshop is for you if:
- Your team maintains 5–50+ repos and context is scattered.
- Different developers clone different subsets of the org.
- Cross-repo changes (API contract + consumer + docs) are painful.
- You want AI agents that understand architecture, not just one folder.
Key Topics
The Multi-Repo Reality
Live tour of a demo GitHub organization with multiple repos.
Simple case: 5 repos, all cloned locally.
Real case: org with too many repos; why local agents lose the map. Preview the stack.
Cursor for Multi-Repo Work
Multi-root workspace setup. cursor/rules, skills, AGENTS.md per repo vs. shared.
Hands-on: implement a cross-repo change in the simple 5-repo layout.
Tool introduced: Cursor local agent.
Meta Repos: The Team's Control Plane
Knowledge base, operations, shared rules.
Hands-on: scaffold/extend a meta repo; wire Cursor to treat it as the orchestration layer.
Re-run Block 1 tasks from the meta repo.
Tool introduced: Meta repo.
Reposwarm: Architecture Catalog
Reposwarm: scan the org, generate a catalog (services, dependencies, entry points).
Hands-on: generate and inspect the catalog; add meta-repo pointers.
Tool introduced: Reposwarm.
Cloud Agents: Full Org Context
Why Cloud Agents need all repos. Bootstrapping: org clone + Reposwarm catalog as architecture index. Hands-on: launch a Cloud Agent task spanning 3+ repos using catalog-informed context.
Automations + Team Rollout
Cursor Automations: hooks, scheduled runs, ticket-driven workflows.
Scaling patterns: onboarding a new dev with partial clone + catalog.
Anti-patterns and guardrails.
Wrap-up & Q&A.
Topics & Technologies
- Tools: Cursor, Cloud Agents, Cursor Automations, Cursor Rules & Skills, GitHub Organizations
- Architecture Patterns: Multi-Repo, Meta Repo, Reposwarm, Partial Clone, Architecture Catalog, Cross-Repo Changes
- Agentic Development: Agentic Coding, Context Management, Plan Mode, Delegated Cloud Tasks, Team Playbooks
- Process & Scaling: Polyrepo SDLC, Developer Onboarding, Consistency Across Teams, Review Gates, Catalog Freshness