Define technology choices and architectural constraints for AG Grid development.
npx skills add https://github.com/ag-grid/ag-grid --skill technology-stack
Please help me install this Agent Skill. Skill: technology-stack Source: https://github.com/ag-grid/ag-grid/tree/main/.rulesync/skills/technology-stack Command: npx skills add https://github.com/ag-grid/ag-grid --skill technology-stack
This document codifies the technology choices and architectural constraints that guide AG Grid development, ensuring minimal runtime dependencies, consistent tooling, and a framework-agnostic core.
Audit planned dependencies to ensure zero-runtime dependencies and align with the framework-agnostic core and build tooling.
High-intent search queries and answers about installing and using this skill.
You maintain a framework-agnostic core by isolating core logic from framework-specific wrappers. The framework wrappers provide integrations around the framework-agnostic core, ensuring zero-runtime dependencies and clear packaging boundaries across packages.
Zero-runtime dependencies mean core libraries include no third-party runtime dependencies. This minimizes bundle size and avoids conflicts during dependency selection, ensuring the framework-agnostic core remains lightweight and conflict-free.
Audit planned dependencies by checking each package against the zero-runtime constraint. Align dependency selection with the framework-agnostic core and build tooling standards, using Nx for monorepo management and Yarn for package management.
Yes, AG Grid development requires TypeScript in strict mode. It adopts Nx for monorepo management, Yarn for package management, and ESBuild/Rollup for bundling to enforce standardized tooling and clear packaging boundaries.
No, core libraries must have zero third-party runtime dependencies. While framework-specific wrappers handle integrations, the core logic must remain framework-agnostic and free of runtime dependencies to minimize bundle size and avoid conflicts.
The best way to enforce clear packaging boundaries is adopting standardized tooling. Use Nx for monorepo management, maintain a framework-agnostic core, and isolate framework-specific wrappers while enforcing zero-runtime dependencies.
ViewableGravyConfigure monorepo package references with workspace dependencies, Nx, and TypeScript path aliases.
manastalukdarAnalyze JavaScript bundle sizes for Webpack, Vite, esbuild, and Rollup projects.
Motion-CoreBuild and edit MotionGPU core and Svelte, React, and Vue adapters for WGSL shader pipelines.
wshobsonManage monorepos with Turborepo, Nx, and pnpm workspaces.
