Stop Team Using Different Coding Standards — DeepSeek Prompts for Agency Junior Developers (Beginner Level)

You are a senior software engineer with 10 years of experience in digital agency environments, framework migrations, and enforcing coding standards across junior development teams. Help me write the code from scratch so I can cut code review time in half. My situation: Framework being migrated to: [e.g., jQuery to React / Bootstrap 4 to Tailwind CSS / PHP procedural to Laravel MVC] Agency team size and composition: [e.g., 5 developers including 3 juniors / rotating freelance contributors / mixed team with no agreed standards document] Coding standard inconsistency: [e.g., some developers use tabs, others use spaces / component naming is different in every file / some files use async/await, others use raw promises with no rule] Feature being built from scratch: [e.g., user authentication flow / product listing page / contact form with API integration] Code review bottleneck: [e.g., reviewer spends 30 minutes per PR fixing formatting / the same style issues appear in every review / no linter is configured so style decisions are made during review instead of at write time] Junior developer experience level: [e.g., 6 months of experience / knows HTML, CSS, and basic JavaScript / has never worked with a linter or style guide] Delivery deadline: [e.g., client demo in 2 weeks / sprint ends Friday / feature must ship before the senior developer goes on leave] Deliver: The complete feature code written from scratch in the new framework: structured with consistent naming, spacing, and pattern conventions explained in comments — written at a level a junior developer can read and learn from, not just copy A coding standards reference card: a one-page document defining 8 non-negotiable rules for this codebase — naming conventions, file structure, comment requirements, async pattern, component boundaries, error handling style, import order, and spacing — with a correct and incorrect example for each rule A linter configuration file: the complete ESLint, Prettier, or framework-equivalent configuration that enforces the 8 standards automatically — with a comment explaining what each rule does and why it is set to that value A pre-commit hook setup: the configuration that runs the linter before every commit and blocks the commit if any standard is violated — with setup instructions written for a junior developer who has never configured a git hook A code review checklist: 6 items the reviewer checks on every PR — not style items the linter already catches, but logic, security, readability, and maintainability items that require human judgment A pattern reference for the new framework: 3 complete code examples showing the correct way to handle the most common junior mistakes in this framework — state management, async data fetching, and conditional rendering — each with an annotation explaining the decision A junior developer self-review guide: 5 questions the junior developer answers before submitting a PR — designed to catch the most common review failures before the reviewer sees the code A standards enforcement retrospective template: a 10 minute team meeting format for the end of each sprint to review which standards violations appeared most often, why they happened, and whether the linter rule needs to be adjusted Configure the linter before writing the first line of feature code — a standard that is not enforced automatically is not a standard, it is a preference that the reviewer has to repeat every week.