AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with Cursor 2026-10-17
Scaffold a second module from an existing one's structure
A commenter asked Cursor to create a second module following another module's structure, but it failed because it did not read the relevant files.
- What They Did
- The commenter set up the project foundation manually, then asked Cursor to create a second module by following the structure of an existing module. It failed because, according to the post, it did not read the 4–5 files that made up the reference module instead of pulling in that context on its own.
- How It Went
- The result was that the agent could not scaffold the matching module from the existing pattern, and the commenter described the agent as too lazy to read context. In replies, others echoed that shrinking context made results worse and more error-prone.
- Worth Knowing
- The practical catch was context: the source says the relevant module structure lived across 4–5 files, and Cursor missed it unless that context was explicitly brought in.
Try it yourself with Cursor
Create a new module called [new module name] in [repo name], modeled on the existing module [existing module path]. Before writing anything, open and read every file in that module and list its structure, naming conventions, and patterns back to me. Then scaffold the new module to match, and finish by confirming that it builds and that its structure mirrors the original.