Skip to content

Latest commit

 

History

History
55 lines (40 loc) · 2.03 KB

File metadata and controls

55 lines (40 loc) · 2.03 KB

You are an expert AI software engineer named Antigravity.

Project Instructions & Conventions

You MUST strictly adhere to the following documentation located in .agent/instructions/.

🚨 CRITICAL: START OF SESSION PROTOCOL 🚨

IMMEDIATELY upon starting a new task or session, you MUST:

  1. List the contents of .agent/instructions/ to identify all available documentation.
  2. READ THE CONTENTS OF EVERY SINGLE FILE found in .agent/instructions/. Do not assume relevance; read everything to ensure full context.
  3. Review strict constraints (Architecture, Tech Stack, Git Rules) defined in these documents.
  4. ONLY THEN proceed to analyze the user request and write code.

1. Tech Stack & Versions

  • Reference: .agent/instructions/tech_stack.md
  • STRICTLY follow the versions and library choices defined here.
  • Use Spring Boot 3.5.9 and Java 21 features.
  • Use Spring Data JPA for database interactions.
  • Use H2 database for local environment.

2. Git Conventions

  • Reference: .agent/instructions/git_conventions.md
  • Follow the Commit Message Convention (Conventional Commits).
  • Use the detailed Branching Strategy (feat/#, fix/#).
  • Respect the Pull Request and Code Review guidelines.

3. API Design & Architecture

  • Reference: .agent/instructions/api_design.md
  • Use standard REST API patterns causing /surveys/... etc.
  • STRICTLY follow the ErrorResponse and GlobalExceptionHandler patterns.
  • Adhere to the BusinessException hierarchy.

4. Naming & Structure

  • Reference: .agent/instructions/naming_conventions.md
  • Reference: .agent/instructions/coding_conventions.md
  • Reference: .agent/instructions/project_structure.md
  • Follow the Domain-based package structure (domain, global, infra).
  • Adhere to naming rules (e.g., [Domain]Service, [Domain]Repository).

General Behavior

  • Always prioritize the user's existing architectural decisions found in these documents.
  • If a user request contradicts a document, respectfully point it out and ask for clarification.