▸case-08 We are migrating 12 separate Node.js polyrepos into a unified repository. Most developers want to jump straight into moving folders, but we want to follow a structured migration workflow. What workflow steps should guide this migration? | fail→fail | 26,248 | 15,429 | -41% | 1 | 1 | 0% | 2,663 | 3,051 | +15% | 0 | 0 | — |
▸case-17 To build our workspace faster, our lead engineer suggests executing `npm run build` in all subpackages concurrently using `npm-run-all --parallel`. However, application packages fail to compile because internal shared library dependencies have not completed building. How should task execution order be managed across workspace packages? | pass→pass | 11,746 | 10,244 | -13% | 1 | 1 | 0% | 2,018 | 2,095 | +4% | 0 | 0 | — |
▸case-01 We are launching a new engineering initiative with three frontend web applications and two backend microservices. Can you help us design our unified repository workspace structure and evaluate build systems, providing a complete setup playbook with steps to verify our setup? | fail→pass | 22,788 | 19,513 | -14% | 1 | 1 | 0% | 4,675 | 4,038 | -14% | 0 | 0 | — |
▸case-02 Our team is combining eight separate repositories into a single workspace, but our CI/CD pipeline is running builds for every project on every commit. Could you create a tailored optimization strategy that sets up task orchestration, build caching, and targeted PR testing so we only run checks on modified modules? | pass→pass | 18,066 | 30,647 | +70% | 1 | 1 | 0% | 2,912 | 4,335 | +49% | 0 | 0 | — |
▸case-03 We need to extract reusable React UI components and shared utility functions into internal libraries across multiple projects in our monorepo. Can you outline an architectural blueprint for our workspace configuration, dependency boundaries, and package tagging strategy? | fail→pass | 21,590 | 15,531 | -28% | 1 | 1 | 0% | 3,677 | 3,316 | -10% | 0 | 0 | — |
▸case-04 We have a single standalone Python FastAPI application in its own repository, and the Docker image build takes 15 minutes due to unoptimized layer caching in our Dockerfile. How should we structure the Dockerfile instruction order and multi-stage build stages to speed up the container build? | pass→pass | 15,439 | 16,987 | +10% | 1 | 1 | 0% | 2,925 | 3,477 | +19% | 0 | 0 | — |
▸case-05 We need to set up remote state storage and DynamoDB state locking for our AWS Terraform infrastructure scripts stored in a standalone ops repository. What is the recommended S3 bucket policy and backend block structure for Terraform version 1.5? | pass→pass | 15,097 | 12,359 | -18% | 1 | 1 | 0% | 2,696 | 2,760 | +2% | 0 | 0 | — |
▸case-06 Our standalone Nginx server needs to handle SSL/TLS termination for `api.example.com` and proxy traffic to a local backend daemon listening on port 8080. How should we write the `nginx.conf` server block and SSL directive list? | pass→pass | 14,699 | 11,069 | -25% | 1 | 1 | 0% | 2,839 | 2,489 | -12% | 0 | 0 | — |
▸case-07 Our enterprise organization has a mix of massive C++ binaries and Java services with complex build graphs, strict custom rule requirements, and hundreds of engineers. We are deciding between lightweight JS-focused workspace managers versus multi-language build systems with starlark rules. Which tool architecture fits multi-language hermetic builds best, and what initial clarifying questions should be asked? | pass→pass | 17,472 | 13,108 | -25% | 1 | 1 | 0% | 2,691 | 2,403 | -11% | 0 | 0 | — |
▸case-09 Our team's CI builds are slow because every runner executes task builds from scratch without sharing build outputs across GitHub Actions runners. We want to configure shared artifact caching across team members and CI runners. What strategy should be prioritized early in the setup? | pass→pass | 12,808 | 10,254 | -20% | 1 | 1 | 0% | 1,979 | 2,022 | +2% | 0 | 0 | — |
▸case-10 In our multi-project TypeScript repository, application A depends on library B, which depends on library C. When running the build command for application A, how should the build system orchestrate the task graph so dependent targets build in parallel where possible? | pass→pass | 14,104 | 16,126 | +14% | 1 | 1 | 0% | 2,531 | 3,119 | +23% | 0 | 0 | — |
▸case-11 We have feature packages, UI packages, and low-level core packages in our multi-project codebase. Developers keep importing feature modules directly inside core utilities, creating circular dependencies. How should package boundaries be enforced? | pass→pass | 16,966 | 16,862 | -1% | 1 | 1 | 0% | 2,800 | 3,286 | +17% | 0 | 0 | — |
▸case-12 Our pull request checks currently build and test all 40 packages in our repository, taking 45 minutes per PR. We want our pull request workflow to identify only the projects impacted by changes in the PR. What capability should be configured? | pass→pass | 7,774 | 7,302 | -6% | 1 | 1 | 0% | 1,183 | 1,540 | +30% | 0 | 0 | — |
▸case-13 Our team built a massive shared utility package containing UI components, database drivers, crypto helpers, and logging utilities. It has become bloated and difficult to maintain. What design principle should be applied to refine this shared package? | pass→pass | 11,234 | 11,310 | +1% | 1 | 1 | 0% | 1,844 | 2,163 | +17% | 0 | 0 | — |
▸case-14 Across 15 projects in our repository, different teams are installing different patch versions of third-party packages, leading to duplicate bundle inclusions. How should dependency updates and version alignment be handled? | pass→pass | 23,801 | 12,158 | -49% | 1 | 1 | 0% | 2,550 | 2,630 | +3% | 0 | 0 | — |
▸case-15 When running local development builds across multiple packages, developers frequently recompile unchanged packages repeatedly. How should local task execution be optimized? | pass→pass | 14,820 | 12,156 | -18% | 1 | 1 | 0% | 2,279 | 2,273 | -0% | 0 | 0 | — |
▸case-16 We are designing a new monorepo workspace for a web app, a mobile app, and shared core state management libraries. What initial step must be taken when defining the workspace architecture? | pass→pass | 9,397 | 9,579 | +2% | 1 | 1 | 0% | 1,448 | 1,794 | +24% | 0 | 0 | — |
▸case-18 How can an engineering organization ensure that team members know who maintains which workspace package in a large multi-project repository? | pass→pass | 13,881 | 17,434 | +26% | 1 | 1 | 0% | 2,232 | 3,017 | +35% | 0 | 0 | — |
▸case-19 To make our monorepo clean and readable for new hires, how should workspace root and package folder structures and scripts be named? | pass→pass | 16,677 | 16,529 | -1% | 1 | 1 | 0% | 2,789 | 3,136 | +12% | 0 | 0 | — |
▸case-20 Our engineers need a clear visual reference to understand how workspace applications and internal packages connect with one another over time. What best practice addresses this requirement? | pass→pass | 11,217 | 9,321 | -17% | 1 | 1 | 0% | 1,761 | 1,841 | +5% | 0 | 0 | — |
▸case-21 We are setting up a workspace for 40 developers and want to ensure downstream builds do not re-run tasks that succeeded in previous commits across different CI nodes. What caching component must be configured for the CI infrastructure? | pass→pass | 5,262 | 7,753 | +47% | 1 | 1 | 0% | 808 | 1,516 | +88% | 0 | 0 | — |
▸case-22 A startup with 3 frontend developers working on a single web application is considering setting up a complex monorepo build system with custom build rules and remote build execution clusters. Is this toolchain selection appropriate? | fail→fail | 13,156 | 10,174 | -23% | 1 | 1 | 0% | 2,059 | 1,912 | -7% | 0 | 0 | — |