contributing-to-lt-frameworklisted

# Contributing to the lt Framework Framework-level development happens in the **framework repositories**, not in consuming application code. This skill covers the round-trip: edit framework source → link into a starter → run/test → unlink → prepare an upstream contribution. ## When This Skill Activates - Modifying `@lenne.tech/nest-server` or `@lenne.tech/nuxt-extensions` source code - Validating a framework change by exercising it from `nest-server-starter` or `nuxt-base-starter` - Setting up or tearing down `pnpm link` between a framework repo and a starter - Preparing a pull request against `nest-server` or `nuxt-extensions` ## Skill Boundaries | User Intent | Correct Skill | |-------------|---------------| | "Modify @lenne.tech/nest-server itself" | **THIS SKILL** | | "Change @lenne.tech/nuxt-extensions source" | **THIS SKILL** | | "Link framework locally for testing" | **THIS SKILL** | | "Build a feature in my app" | generating-nest-servers / developing-lt-frontend | | "Update nest-server version in my project" | nest-server-updating | | "Sync vendored core from upstream" | nest-server-core-vendoring / nuxt-extensions-core-vendoring | | "Open a PR with my vendored-core change" | nest-server-core-vendoring → `nest-server-core-contributor` agent | ## The Base Repos ("Grund-Repos") When the user says **"Grund-Repos"** (or "base repos" / "the foundation repos"), they mean **exactly these seven** — the repositories every customer project inherits from: | Repo | Role |