Abstraction AI - Context Compiler

Generated documents

Ready to generate 11 documents

Next: have a coding AI implement it

How to use: Put the original context and the generated 11 documents into your repo, then send the prompt below to Cursor / Claude Code / Augment Code. It will understand the requirements and implement the system end-to-end.

From now on, without asking me questions or waiting for confirmation, complete this project end-to-end—from understanding to implementation.

Step 1: Understand everything first (use as much effort and compute as needed):
- Browse all files and subdirectories in this workspace, including all docs—do not miss anything.
- Understand what each file and document is for, how they relate, and what the project is supposed to do overall.
- If there are multiple spec/design docs and raw conversation context, synthesize them to infer the real requirements and constraints (do not rely on only one file).
- If the environment allows and it is safe, you may look up relevant public information to fill gaps and produce a complete solution.

Step 2: After you understand it, implement everything without stopping at a planning-only level:
- You may summarize the goal and route in a few sentences, then immediately start building—do not wait for my approval.
- Create/modify files in a sensible order to implement frontend, backend, data, model calls, and anything else required.
- Prefer isolated environments (e.g., venv or containers) when dependencies are needed; keep it reproducible and avoid polluting global state.
- Do not only output TODO lists. Provide concrete code, config, commands, and how to run.

Step 3: Keep validating and improving until the project is truly usable:
- Use requirements, edge cases, and acceptance criteria in the docs to design and run reasonable tests (automated or clear manual steps).
- When you find conflicts/inconsistencies, resolve them yourself as much as possible; align code and docs, and record your assumptions when needed.
- When information is missing, make reasonable assumptions, write them down, and keep going—do not stop to ask me whether you should proceed.

Only if you hit hard external blockers (permissions, missing credentials, etc.) should you briefly explain the issue. Otherwise, continue until you believe the project has no obvious problems and meets all known requirements.

Turn one conversation into 11 spec docs engineers can build from

Get started

Compiling documents...

Generated documents

Turn one conversation into 11 spec docs engineers can build from

Get started

Compiling documents...

Generated documents

How likely are you to recommend this tool to a friend?