pnpm 11 + Turborepo monorepo. Requires Node >= 22.13. Every PR must pass typecheck + lint (one workflow), Prettier, and a typos check. Other checks are path-filtered: Studio unit tests/build and the lint ratchet (ESLint warning count must not increase) run on apps/studio/** changes; app-specific test suites run on their own paths. Never hand-edit generated files: packages/api-types/types/*, */routeTree.gen.ts, **/generated/, apps/docs/features/docs/generated/, apps/www/.generated/**, `supabase/functions/common/database-
Next.js app router + MDX. Dev server: pnpm dev:docs → http://localhost:3001/docs (the bare / 404s). style-guide/ holds the docs style guide as plain markdown. Load the file you need rather than the whole directory. No tool enforces the guide, so applying it is the author's job, or the skill's. Load these before working. pm-the-docs, write-the-docs, edit-the-docs, ask-the-docs, and review-the-docs back the docs authoring process. See CONTRIBUTING.md for which stage each covers. They apply the style guide above. For architecture questions…
When starting the dev server, run: Full documentation: https://docs.astro.build Consult these guides before working on related tasks: To run a full production build, run: Content lives under src/content/guides/*.{md,mdx}. Keep it plain GitHub-Flavored Markdown: - No custom/JSX components in guide bodies — content is also exported as plain .md (see below), and a component wouldn't survive that export. - For callouts, use GitHub's native alert syntax (> [!NOTE], > [!TIP], > [!IMPORTANT], > [!WARNING], > [!CAUTION]) — the build renders these…
Next.js pages router + TanStack Start (mid-migration, see below), React 19. Dev server: pnpm dev:studio → http://localhost:8082. Load the skills matching the task; stack them when a task spans areas: Studio is migrating from the Next.js pages router (pages/) to TanStack Start (routes/). Both runtimes ship side-by-side; the STUDIOFRAMEWORK env var selects which one pnpm dev/build runs (default: next, resolved in scripts/dispatch.js). Full route map and strategy: TANSTACKMIGRATION.md.
These rules apply to all public contributions and interactions, no matter how they're done. The entity operating or authorizing the contributions and interactions is responsible for them. AI assistance does not relieve contributors of responsibility for their work. "The AI did it" is not an excuse. Violations may result in contributions being closed without further comment. Cases of deception, evasion, or repeat violations may result in account bans. Allowed: - All AI usage that remains non-public (e.g. questions, reviews, local…
MicrosoftAGENTS.md