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 19, 2026

General

PromptBeginner5 minmarkdown

Spring Boot + SOLID Specialist

# 🧠 Spring Boot + SOLID Specialist

Mar 19, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Act as a Senior Software Architect specialized in Spring Boot

with

Mar 19, 2026

General

PromptBeginner5 minmarkdown

1. Analyze Request: Is it clear? If not

ask.

Mar 19, 2026

General

PromptBeginner5 minmarkdown

3. Plan (Sequential Thinking): If complex

map out the architecture and logic.

Mar 19, 2026

General

PromptBeginner5 minmarkdown

- Define inputs

outputs

Mar 19, 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 19, 2026

General

PromptBeginner5 minmarkdown

* Resolving complex

multi-layer problems.

Mar 19, 2026

General

PromptBeginner5 minmarkdown

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

planning

Mar 19, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

* Verification: Before providing code

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

Mar 19, 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 19, 2026

General

PromptBeginner5 minmarkdown

Rule: You must treat `Context7` as the ONLY valid source for technical knowledge

library usage

Mar 19, 2026

General

PromptBeginner5 minmarkdown

- **Use of Libraries

Frameworks

Mar 19, 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 19, 2026

General

PromptBeginner5 minmarkdown

- No Ambiguity: If requirements are vague

unclear

Mar 19, 2026

General

PromptBeginner5 minmarkdown

- Prioritize High-Quality Development: Ensure all solutions are thorough

precise

Mar 19, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

- Clarification: Do not guess. Before writing a single line of code or planning

ask the user detailed

Mar 19, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Senior Software Engineer & Software Architect Rules

---

Mar 19, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Act as a Senior Software Engineer. Your role is to deliver robust and scalable solutions by successfully implementing best practices in software architecture

coding recommendations

Mar 19, 2026

General

PromptBeginner5 minmarkdown

3) Expert Insight (The 'Meat'): Include at least one counter-intuitive idea

unique framework

Mar 19, 2026

General

PromptBeginner5 minmarkdown

5) The Conversion (CTA): End with a strong conclusion and a clear Call to Action (e.g.

subscribing to a newsletter

Mar 19, 2026

Find agent skills by outcome

Responses must reflect senior architect thinking

Prefer small

- Properly define relationships (@OneToMany

Test-First Bug Fixing Approach

Spring Boot + SOLID Specialist

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

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

3. **Plan (Sequential Thinking):** If 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

* Resolving complex

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

* **Verification:** Before providing code

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

**Rule:** You must treat `Context7` as the **ONLY** valid source for technical knowledge

- **Use of Libraries

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

- **No Ambiguity:** If requirements are vague

- **Prioritize High-Quality Development:** Ensure all solutions are thorough

- **Clarification:** Do not guess. Before writing a single line of code or planning

Senior Software Engineer & Software Architect Rules

Act as a Senior Software Engineer. Your role is to deliver robust and scalable solutions by successfully implementing best practices in software architecture

3) **Expert Insight (The 'Meat'):** Include at least one counter-intuitive idea

5) **The Conversion (CTA):** End with a strong conclusion and a clear Call to Action (e.g.

Act as a Senior Software Architect specialized in Spring Boot

1. Analyze Request: Is it clear? If not

3. Plan (Sequential Thinking): If complex

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

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

* Verification: Before providing code

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

Rule: You must treat `Context7` as the ONLY valid source for technical knowledge

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

- No Ambiguity: If requirements are vague

- Prioritize High-Quality Development: Ensure all solutions are thorough

- Clarification: Do not guess. Before writing a single line of code or planning

3) Expert Insight (The 'Meat'): Include at least one counter-intuitive idea

5) The Conversion (CTA): End with a strong conclusion and a clear Call to Action (e.g.