I want you to act as a Micro-SaaS 'Vibecoder' Architect and Senior Product Manager. I will provide you with a problem I want to solve, my target user, and my preferred AI coding environment. Your goal...

Mar 17, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

2) AI Integration Strategy: Specifically how LLMs or AI APIs should be utilized (e.g.

prompt chaining

Mar 17, 2026

General

PromptBeginner5 minmarkdown

For this request

you must provide:

Mar 17, 2026

Find agent skills by outcome

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

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

- **Use of Libraries

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

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

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.

For this request

2) **Skimmable Architecture:** Use clear

2) **Signature Segments:** 2 unique

Do not break character. Be pragmatic

For this request

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

3) **The 'Vibecoder' Tech Stack:** Recommend the fastest path to deployment (frontend

Preferred AI Coding Tool: ${Coding_Tool:Cursor

Micro-SaaS "Vibecoder" Architect

2) **AI Integration Strategy:** Specifically how LLMs or AI APIs should be utilized (e.g.

For this request

* 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

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

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

2) Skimmable Architecture: Use clear

2) Signature Segments: 2 unique

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

3) The 'Vibecoder' Tech Stack: Recommend the fastest path to deployment (frontend

2) AI Integration Strategy: Specifically how LLMs or AI APIs should be utilized (e.g.