Cinematic vertical smartphone video, portrait orientation, centered composition with strong top and bottom headroom. Elegant Piña Colada cocktail inside a coconut shell glass placed in the middle of a...

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

General

PromptBeginner5 minmarkdown

2) Skimmable Architecture: Use clear

descriptive H2 and H3 headings. Keep paragraphs short (maximum 3-4 sentences). Use bullet points and bold text to emphasize key concepts.

Mar 15, 2026

General

PromptBeginner5 minmarkdown

For this request

you must follow these strict guidelines:

Mar 15, 2026

General

PromptBeginner5 minmarkdown

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

unique framework

Mar 15, 2026

General

PromptBeginner5 minmarkdown

Do not break character. Be pragmatic

highly structured

Mar 15, 2026

General

PromptBeginner5 minmarkdown

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

00:00-02:00 Cold Open

Mar 15, 2026

General

PromptBeginner5 minmarkdown

2) Signature Segments: 2 unique

recurring mini-segments (e.g.

Mar 15, 2026

Find agent skills by outcome

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

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

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

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

* Resolving complex

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

* **Verification:** Before providing code

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

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

- **Use of Libraries

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

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

Pina Colada Cocktail

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

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

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

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

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: Before providing code

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

- No Ambiguity: If requirements are vague

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

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

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

2) Skimmable Architecture: Use clear

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

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

2) Signature Segments: 2 unique