The Software Architect & Code Generator

Top-Prompts

Write production code, tests, and documentation.

01 The Concept

Most developers get half-finished code snippets, placeholders (`// TODO`), and missing imports from LLMs. A Software Architect Prompt forces the model to write complete, production-grade files with strict error handling, complete test suites, and clean directory layouts.

This template enforces a no-placeholder policy, demands unit tests covering positive and edge cases, and structures outputs with clear file paths.

02 Weak vs. Strong

EX 01Go API Handler & Unit Test Prompt

You are a Principal Backend Architect. Design a Go HTTP handler for saving a user profile. [CODING RULES] - Output complete, compiler-ready files. Placeholders (e.g. '// TODO', '// implement later') are strictly forbidden. - Include all necessary package imports. - Error handling must be explicit and idiomatic. Return descriptive JSON errors with appropriate HTTP status codes. [DELIVERABLES] 1. `handler.go`: The HTTP handler function matching `http.HandlerFunc`. 2. `handler_test.go`: Complete unit tests covering successful save, database error, and invalid request payload. 3. Rationale: A Markdown table comparing memory-based sessions vs PostgreSQL-based profile tables.

→ Why it works

Explicitly bans placeholders, demands full import lists, and forces handler and test files to be output as complete entities.

EX 02TypeScript Repository Layer Prompt

You are a Staff Software Architect. Create a TypeScript repository class `InvoiceRepository` using Prisma client. [CONSTRAINTS] - Write out the complete file, including imports. No truncations. - Implement methods: `create`, `findById`, and `markAsPaid`. - Include input validation for UUID formats and currency amounts. - Provide a complete unit test suite `invoice.spec.ts` using Jest.

→ Why it works

Demands complete imports, names files specifically, and mandates validation constraints on inputs to guarantee production readiness.

03 Key Points

01Staff Engineer roleplay: set the expected quality level to senior software architect.

02Zero placeholder rule: explicitly ban `// TODO` or code truncations.

03Error validation: require robust, language-idiomatic error handling for all external inputs.

04Complete unit tests: demand tests alongside code, showing mock setups where necessary.

05Rationale table: require a brief trade-off table comparing the chosen approach to alternative patterns.

04 Model-Specific Notes

Claude writes highly readable, clean code and adheres closely to structural constraints. Use XML tags for different files (`<file name="handler.go">`).

05 For Your Role

It's like instructing a builder. If you just ask for a house plan, they might draw a sketch. If you demand blueprints, material specifications, and structural tests, you get a real plan.

Next: The Business Analyst & Decision Framework →