with one click
developer-experience
// Planned adjacent, non-primary: Improve contributor inner loops, onboarding, local setup ergonomics, and fast feedback without absorbing CI, deployment, or runtime operations.
// Planned adjacent, non-primary: Improve contributor inner loops, onboarding, local setup ergonomics, and fast feedback without absorbing CI, deployment, or runtime operations.
| name | developer-experience |
| description | Planned adjacent, non-primary: Improve contributor inner loops, onboarding, local setup ergonomics, and fast feedback without absorbing CI, deployment, or runtime operations. |
| metadata | {"surface":"planned-adjacent","primary-route":"false","support-tier":"planned"} |
This pack's native-safe metadata marks it as surface: planned-adjacent, primary-route: false, and support-tier: planned.
Use this pack as a bounded planned adjacent surface after ../../reference/routing-matrix.md points here for contributor-facing workflow work: onboarding, local setup contracts, repo ergonomics, package and workspace conventions, fast feedback loops, and review norms that shape the pre-merge inner loop.
This pack keeps the local developer path explicit, fast, and debuggable once the dominant route is already chosen. It is not the primary place to discover adjacent-pack routing, helper fit, or support posture, so send that first pass back to ../../reference/routing-matrix.md. Use the overlays in reference/package-managers-monorepos.md and reference/local-dev-environments.md when workspace shape, toolchain constraints, local services, or environment setup details dominate the task, and keep CI, deployment, and runtime ownership with devops-platform.
For setup posture, prefer refining an existing project in place. Treat direct create / init / new flows as greenfield-only and use them only when explicitly requested. Defer the full setup policy to ../../reference/project-setup-policy.md.
../../reference/routing-matrix.md first so planned-adjacent routing, helper discovery, and non-primary positioning come from the matrix instead of this pack.reference/package-managers-monorepos.md for workspace and toolchain shape, or reference/local-dev-environments.md for environment bootstrap and parity concerns.review-work after substantial developer-experience changes.Explore before editing so local setup scripts, workspace rules, and contributor docs match existing repo conventions.Librarian or Context7 when package-manager, workspace, or local environment tooling details need a source-of-truth check.../../reference/routing-matrix.md.devops-platform when local development depends on containers, seeded services, or environment parity, but keep contributor ergonomics as the primary outcome.documentation-sdk when onboarding, command docs, or examples need to become durable reference material.reference/package-managers-monorepos.md for workspace boundaries, lockfile and package-manager choices, task orchestration, and monorepo ergonomics.reference/local-dev-environments.md for prerequisites, environment files, local services, containerized dev setups, seeded data, and cross-platform setup friction.