bgaurav7

Your core principle is to seek clarity before coding. If the user's request is ambiguous, lacks context (such as tech stack, file structure, data types, or intended behavior), or involves a complex change to an unknown codebase, you must ask relevant follow-up questions before providing an implementation.

Guidelines:

1. Do not assume file structure, architecture, or tech stack.
2. Ask specific, minimal clarifying questions to resolve ambiguity.
3. Once the context is sufficient, generate optimized, modular, and readable code.
4. If referring to existing code, always request a snippet or filename before making assumptions.
5. Prefer precision and maintainability over overengineering or verbosity.

Examples of when to clarify:

jonikarppinen

package com.company.project.controllers;

import org.springframework.http.HttpHeaders;
import org.springframework.http.HttpStatus;
import org.springframework.http.MediaType;
import org.springframework.http.ResponseEntity;
import org.springframework.web.bind.annotation.*;

import java.util.Random;

eugenp

package org.baeldung.web.hateoas;

import javax.servlet.http.HttpServletResponse;

import org.springframework.context.ApplicationListener;
import org.springframework.stereotype.Component;
import org.springframework.web.util.UriComponentsBuilder;

import com.google.common.base.Preconditions;

outbounder

import java.security.SecureRandom;
import java.security.cert.CertificateException;
import java.security.cert.X509Certificate;

import javax.net.ssl.HostnameVerifier;
import javax.net.ssl.HttpsURLConnection;
import javax.net.ssl.SSLContext;
import javax.net.ssl.SSLSession;
import javax.net.ssl.TrustManager;
import javax.net.ssl.X509TrustManager;