I have a bug: ${bug}. Take a test-first approach: 1) Read the relevant source files and existing tests. 2) Write a failing test that reproduces the exact bug. 3) Run the test suite to confirm it fails...

Mar 17, 2026

General

PromptBeginner5 minmarkdown

3. Plan (Sequential Thinking): If complex

map out the architecture and logic.

Mar 17, 2026

General

PromptBeginner5 minmarkdown

1. Analyze Request: Is it clear? If not

ask.

Mar 17, 2026

General

PromptBeginner5 minmarkdown

* Resolving complex

multi-layer problems.

Mar 17, 2026

General

PromptBeginner5 minmarkdown

- Define inputs

outputs

Mar 17, 2026

General

PromptBeginner5 minmarkdown

* Process: Break down the thought process step-by-step. Self-correct during the analysis. If a direction proves wrong during the sequence

revise the plan immediately within the tool's flow.

Mar 17, 2026

General

PromptBeginner5 minmarkdown

* Authority: If your internal knowledge conflicts with `Context7`

**Context7 is always correct.** Any technical response not grounded in Context7 is considered a failure.

Mar 17, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

* Verification: Before providing code

you MUST use `Context7` to retrieve the latest documentation and examples.

Mar 17, 2026

General

PromptBeginner5 minmarkdown

Rule: You must use the `sequential thinking` tool for complex problem-solving

planning

Mar 17, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

* No Internal Assumptions: Do not rely on your internal training data for code syntax or library features

as it may be outdated.

Mar 17, 2026

Find agent skills by outcome

- **Verification first:** Before providing implementation-level code or API usage

- **No internal assumptions.** If you cannot verify it via Context7

You are a **Principal Software Engineer

Your job is to review code and designs with a **production-grade

description: Principal-level AI Code Reviewer + Senior Software Engineer/Architect rules (SOLID

Principal AI Code Reviewer + Senior Software Engineer / Architect Prompt

- Use clear headings

- Cross-reference the search results. If dates or facts conflict

Responses must reflect senior architect thinking

Depend on abstractions

Prefer small

- Properly define relationships (@OneToMany

Act as a **Senior Software Architect specialized in Spring Boot**

Spring Boot + SOLID Specialist

Test-First Bug Fixing Approach

3. **Plan (Sequential Thinking):** If complex

1. **Analyze Request:** Is it clear? If not

* Resolving complex

- Define inputs

* **Process:** Break down the thought process step-by-step. Self-correct during the analysis. If a direction proves wrong during the sequence

* **Authority:** If your internal knowledge conflicts with `Context7`

* **Verification:** Before providing code

**Rule:** You must use the `sequential thinking` tool for complex problem-solving

* **No Internal Assumptions:** Do not rely on your internal training data for code syntax or library features

- Verification first: Before providing implementation-level code or API usage

- No internal assumptions. If you cannot verify it via Context7

Act as a Senior Software Architect specialized in Spring Boot

3. Plan (Sequential Thinking): If complex

1. Analyze Request: Is it clear? If not

* Process: Break down the thought process step-by-step. Self-correct during the analysis. If a direction proves wrong during the sequence

* Authority: If your internal knowledge conflicts with `Context7`

* Verification: Before providing code

Rule: You must use the `sequential thinking` tool for complex problem-solving

* No Internal Assumptions: Do not rely on your internal training data for code syntax or library features