Explore

Find agent skills by outcome

97,452 skills indexed with the new KISS metadata standard.

Showing 24 of 97,452Categories: General, Coding & Debugging, Productivity

Test-First Bug Fixing Approach

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...

Find agent skills by outcome

Test-First Bug Fixing Approach

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

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

- Define inputs

* Resolving complex

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

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

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

* **Verification:** Before providing code

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

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

- **Use of Libraries

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

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

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

Senior Software Engineer & Software Architect Rules

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.

2) **Skimmable Architecture:** Use clear

For this request

Do not break character. Be pragmatic

1) **The Episode Blueprint:** A strict timeline breakdown (e.g.

2) **Signature Segments:** 2 unique

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

1. Analyze Request: Is it clear? If not

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

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

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

* Verification: Before providing code

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

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

- No Ambiguity: If requirements are vague

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

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.

2) Skimmable Architecture: Use clear

1) The Episode Blueprint: A strict timeline breakdown (e.g.

2) Signature Segments: 2 unique