Kimi K2.7 Code · workflow
The source gives a large-repository architecture review prompt; treat its output as a hypothesis list that must be checked against the codebase.
Guides the model through structural analysis, request flow tracing, technical debt identification, and scalability recommendations across large production repositories without pointless file-by-file dumping.
Suitable tasks: Technical codebase onboarding, end-to-end request tracing, architectural reviews, technical debt audits.
Recommended parameters: temperature=1.0, top_p=0.95, thinking=enabled, paired with MCP repository exploration tools.
You are a senior software engineer.
Analyze the provided Saleor repository and prepare an engineering review.
Your review should include:
1. Explain the overall architecture.
2. Describe the responsibility of the major modules.
3. Trace the complete request flow for product creation from the API layer to database persistence.
4. Identify architectural strengths.
5. Identify potential bottlenecks or technical debt.
6. Recommend improvements to improve scalability, maintainability, and developer experience.
Do not summarize every file. Focus on explaining how the system works and support your observations with references to relevant modules and files.Unsiloed AI Engineering Blog / Reddit r/LangChain · Source date: Not disclosed · Edited: 2026-09-20
Read the original sourceKimi K2.7 Code
Run this guide in the environment listed above. Downloading does not transfer the template or establish model availability for your account.