Files
lcbp3/specs/99-archives/prompt.md
T
admin 9c0978f3fa
Build and Deploy / deploy (push) Successful in 4m24s
260311:1638 20260311:1700 n8n workflow
2026-03-11 16:38:49 +07:00

31 KiB

🚀 Ultimate Prompt Library for Software Engineering

AI Prompt Library āļŠāļģāļŦāļĢāļąāļšāļāļēāļĢāļžāļąāļ’āļ™āļē Software āđāļšāļšāļ„āļĢāļšāļ§āļ‡āļˆāļĢ āļ•āļąāđ‰āļ‡āđāļ•āđˆāļāļēāļĢāļ§āļēāļ‡āđāļœāļ™āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ āļāļēāļĢāļ­āļ­āļāđāļšāļš UX/UI āļāļēāļĢāļžāļąāļ’āļ™āļēāļĢāļ°āļšāļš āđ„āļ›āļˆāļ™āļ–āļķāļ‡āļāļēāļĢ Deploy āđāļĨāļ° Optimize āđƒāļ™ Production [āļŠāļ·āđˆāļ­āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ] = LCBP3-DMS (Laem Chabang Port Phase 3 - Document Management System)

🧭 1. Strategy & Product Planning

ðŸŸĄ Product Owner ðŸŸĒ Basic

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒāđ€āļ›āđ‰āļēāļŦāļĄāļēāļĒāļ˜āļļāļĢāļāļīāļˆāđāļĨāļ°āļāļģāļŦāļ™āļ” MVP

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Product Owner āļŠāļģāļŦāļĢāļąāļšāđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ [āļŠāļ·āđˆāļ­āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ]

āļŠāđˆāļ§āļĒāļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒ:

  • āđ€āļ›āđ‰āļēāļŦāļĄāļēāļĒāļ˜āļļāļĢāļāļīāļˆ
  • āļāļĨāļļāđˆāļĄāļœāļđāđ‰āđƒāļŠāđ‰āļ‡āļēāļ™āļŦāļĨāļąāļ
  • āļ›āļąāļāļŦāļēāļ—āļĩāđˆāļœāļđāđ‰āđƒāļŠāđ‰āđ€āļˆāļ­
  • āđ‚āļ­āļāļēāļŠāļ—āļēāļ‡āļ•āļĨāļēāļ”

Output format (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  1. System goals
  2. Target users
  3. User pain points
  4. Feature list (āđāļšāđˆāļ‡ Must-have / Nice-to-have / Out of scope)
  5. MVP scope
  6. Future roadmap (3 phases)
  7. Success metrics (KPIs)

ðŸ”ĩ Business Analyst ðŸŸĄ Intermediate

āđāļ•āļ Requirement āļ­āļĒāđˆāļēāļ‡āļĨāļ°āđ€āļ­āļĩāļĒāļ”

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Business Analyst āļŠāđˆāļ§āļĒāļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒ requirement āļ‚āļ­āļ‡āļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Context āļˆāļēāļ Product Owner: [āļ§āļēāļ‡ Output āļˆāļēāļ Product Owner Prompt āļ—āļĩāđˆāļ™āļĩāđˆ]

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒ:

  • Functional requirements
  • Non-functional requirements (Performance / Security / Scalability)
  • User roles āđāļĨāļ° permission matrix
  • Use cases (Happy path + Alternative path)
  • Business rules
  • Edge cases
  • Assumptions / Open questions

Constraints:

  • āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown
  • āđƒāļŠāđ‰āļ āļēāļĐāļēāļ—āļĩāđˆ Developer āđ€āļ‚āđ‰āļēāđƒāļˆāđ„āļ”āđ‰āļ—āļąāļ™āļ—āļĩ
  • āļĢāļ°āļšāļļ priority (P0/P1/P2) āļ—āļļāļ requirement

Output:

  • Feature list āļžāļĢāđ‰āļ­āļĄ priority
  • MVP scope
  • Roadmap
  • Requirement document (Markdown)

⚩ AI Project Manager ðŸŸĄ Intermediate

āļ§āļēāļ‡āđāļœāļ™āļāļēāļĢāļžāļąāļ’āļ™āļēāđ€āļ›āđ‡āļ™ Phase

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ AI Project Manager

Context:

  • āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ: [āļŠāļ·āđˆāļ­āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ]
  • āļ—āļĩāļĄ: [Frontend / Backend / DevOps / QA āļˆāļģāļ™āļ§āļ™āļ„āļ™āđāļ•āđˆāļĨāļ°āļāđˆāļēāļĒ]
  • Timeline āļĢāļ§āļĄ: [āļāļĩāđˆāļŠāļąāļ›āļ”āļēāļŦāđŒ/āđ€āļ”āļ·āļ­āļ™]
  • Methodology: [Agile / Scrum / Kanban]

Requirements āļˆāļēāļ Business Analyst: [āļ§āļēāļ‡ Output āļˆāļēāļ BA Prompt āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown table):

| Phase | Description | Deliverables | Dependency | Duration | Definition of Done |

āļžāļĢāđ‰āļ­āļĄāļŠāļĢāđ‰āļēāļ‡:

  • Risk register (Top 5 risks + mitigation)
  • Sprint breakdown (āļ–āđ‰āļēāđƒāļŠāđ‰ Scrum)
  • Milestone checklist

ðŸŽĻ 2. UX / UI & Information Architecture

ðŸŸĢ UX Researcher ðŸŸĄ Intermediate

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒāļ›āļĢāļ°āļŠāļšāļāļēāļĢāļ“āđŒāļœāļđāđ‰āđƒāļŠāđ‰

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ UX Researcher āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒ UX āļŠāļģāļŦāļĢāļąāļš [āļ›āļĢāļ°āđ€āļ āļ—āđ€āļ§āđ‡āļš/āđāļ­āļ›]

āļāļĨāļļāđˆāļĄāđ€āļ›āđ‰āļēāļŦāļĄāļēāļĒ: [āļĢāļ°āļšāļļāļœāļđāđ‰āđƒāļŠāđ‰: āļ­āļēāļĒāļļ / āļ­āļēāļŠāļĩāļž / tech-savviness / device āļ—āļĩāđˆāđƒāļŠāđ‰]

Context āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ: [āļ§āļēāļ‡ Product Owner Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • User personas (3 āđāļšāļš āļžāļĢāđ‰āļ­āļĄ quote āļˆāļģāļĨāļ­āļ‡)
  • User journey map (āļ•āļēāļĄ persona āļŦāļĨāļąāļ)
  • Pain points āđāļĒāļāļ•āļēāļĄ journey stage
  • UX opportunities āļžāļĢāđ‰āļ­āļĄ priority
  • Accessibility considerations (WCAG 2.1)

ðŸŸĒ Information Architect ðŸŸĒ Basic

āļ­āļ­āļāđāļšāļšāđ‚āļ„āļĢāļ‡āļŠāļĢāđ‰āļēāļ‡āđ€āļ§āđ‡āļšāđ„āļ‹āļ•āđŒ

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Information Architect

āļŠāđˆāļ§āļĒāļ­āļ­āļāđāļšāļš Sitemap āļŠāļģāļŦāļĢāļąāļšāđ€āļ§āđ‡āļš [āļ›āļĢāļ°āđ€āļ āļ—āđ€āļ§āđ‡āļš]

User personas: [āļ§āļēāļ‡ UX Researcher Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Primary navigation (max 7 items)
  • Secondary navigation
  • Sitemap (āđāļšāļš tree structure)
  • Content grouping āļžāļĢāđ‰āļ­āļĄāđ€āļŦāļ•āļļāļœāļĨ
  • URL structure recommendation
  • Breadcrumb strategy

ðŸ”ī UX/UI Designer ðŸŸĄ Intermediate

āļ­āļ­āļāđāļšāļšāļŦāļ™āđ‰āļēāđ€āļ§āđ‡āļš

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ UX/UI Designer

āļ­āļ­āļāđāļšāļšāļŦāļ™āđ‰āļē [āļŠāļ·āđˆāļ­āļŦāļ™āđ‰āļē]

āđ€āļ›āđ‰āļēāļŦāļĄāļēāļĒ: [āđ€āļŠāđˆāļ™ āđ€āļžāļīāđˆāļĄ conversion / āļĨāļ” bounce rate] Platform: [Web / Mobile / Both] Brand tone: [āđ€āļŠāđˆāļ™ Professional / Friendly / Minimal]

Sitemap context: [āļ§āļēāļ‡ IA Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Page structure āđāļĨāļ° section order āļžāļĢāđ‰āļ­āļĄāđ€āļŦāļ•āļļāļœāļĨ
  • UI components list (āđāļ•āđˆāļĨāļ° section)
  • Color palette (Hex code) + Typography guideline
  • Wireframe āđāļšāļš text layout (ASCII āļŦāļĢāļ·āļ­ structured text)
  • CTA strategy
  • Mobile-first considerations
  • Accessibility notes (contrast ratio / touch target size)

🏛ïļ 3. System Architecture

🛠ïļ Solution Architect ðŸ”ī Advanced

āļ­āļ­āļāđāļšāļš Architecture āļĢāļ°āļ”āļąāļšāļŠāļđāļ‡

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Solution Architect āļ­āļ­āļāđāļšāļš Architecture āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļ›āļĢāļ°āđ€āļ āļ—āļĢāļ°āļšāļš]

Context: [āļ§āļēāļ‡ Product Owner Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Constraints:

āļĢāļ­āļ‡āļĢāļąāļšāļœāļđāđ‰āđƒāļŠāđ‰ [āļˆāļģāļ™āļ§āļ™] concurrent users

Team skill: [Tech stack āļ—āļĩāđˆāļ—āļĩāļĄāļ–āļ™āļąāļ”] Requirements:

  • āļĢāļ­āļ‡āļĢāļąāļšāļœāļđāđ‰āđƒāļŠāđ‰ [āļˆāļģāļ™āļ§āļ™] concurrent users
  • Expected growth: [x āđ€āļ—āđˆāļēāđƒāļ™ y āļ›āļĩ]
  • Budget: [Cloud budget/month]
  • Compliance: [PDPA / GDPR / HIPAA āļ–āđ‰āļēāļĄāļĩ]
  • Team skill: [Tech stack āļ—āļĩāđˆāļ—āļĩāļĄāļ–āļ™āļąāļ”]

Thought Process Requirement: āļāđˆāļ­āļ™āļŠāļĢāļļāļ›āļœāļĨ āđƒāļŦāđ‰āļ„āļļāļ“āļ—āļģ Trade-off Analysis āđ‚āļ”āļĒāđ€āļ›āļĢāļĩāļĒāļšāđ€āļ—āļĩāļĒāļšāđāļ™āļ§āļ—āļēāļ‡āļ—āļĩāđˆāđ€āļ›āđ‡āļ™āđ„āļ›āđ„āļ”āđ‰ 2-3 āđāļ™āļ§āļ—āļēāļ‡ (āđ€āļŠāđˆāļ™ Monolith vs Microservices āļŦāļĢāļ·āļ­ RDBMS vs NoSQL) āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒāļ‚āđ‰āļ­āļ”āļĩ-āļ‚āđ‰āļ­āđ€āļŠāļĩāļĒāđƒāļ™āļĄāļļāļĄāļ‚āļ­āļ‡ Latency, Cost āđāļĨāļ° Maintenance āļžāļĢāđ‰āļ­āļĄāļĢāļ°āļšāļļāđ€āļŦāļ•āļļāļœāļĨāļ—āļĩāđˆāļ„āļļāļ“āđ€āļĨāļ·āļ­āļāđāļ™āļ§āļ—āļēāļ‡āļŠāļļāļ”āļ—āđ‰āļēāļĒ

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • System architecture overview
  • Component diagram (text-based)
  • Decision Log: āđ€āļŦāļ•āļļāļœāļĨāđ€āļšāļ·āđ‰āļ­āļ‡āļŦāļĨāļąāļ‡āļāļēāļĢāđ€āļĨāļ·āļ­āļ Tech stack
  • Data flow diagram
  • Recommended tech stack āļžāļĢāđ‰āļ­āļĄāđ€āļŦāļ•āļļāļœāļĨ
  • Trade-offs āļ‚āļ­āļ‡ architecture āļ—āļĩāđˆāđ€āļĨāļ·āļ­āļ
  • Estimated infrastructure cost
  • Scaling strategy (Horizontal / Vertical)

🔗 Integration Architect ðŸ”ī Advanced

āļ­āļ­āļāđāļšāļšāļāļēāļĢāđ€āļŠāļ·āđˆāļ­āļĄāļ•āđˆāļ­āļĢāļ°āļšāļš

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Integration Architect

āļ­āļ­āļāđāļšāļš Integration āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

āļĢāļ°āļšāļšāļ—āļĩāđˆāļ•āđ‰āļ­āļ‡āđ€āļŠāļ·āđˆāļ­āļĄāļ•āđˆāļ­:

  • [āļĢāļ°āļšāļš A: āđ€āļŠāđˆāļ™ Payment Gateway]
  • [āļĢāļ°āļšāļš B: āđ€āļŠāđˆāļ™ CRM]
  • [āļĢāļ°āļšāļš C: āđ€āļŠāđˆāļ™ ERP]

Solution Architecture: [āļ§āļēāļ‡ Architect Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Integration pattern āļ—āļĩāđˆāđ€āļĨāļ·āļ­āļ (Sync / Async / Event-driven) āļžāļĢāđ‰āļ­āļĄāđ€āļŦāļ•āļļāļœāļĨ
  • API strategy (REST / GraphQL / gRPC)
  • Webhook design
  • Message queue strategy (āļ–āđ‰āļēāđƒāļŠāđ‰)
  • Retry strategy āđāļĨāļ° circuit breaker pattern
  • Error handling āđāļĨāļ° dead letter queue
  • Data consistency strategy

🌐 API Architect ðŸŸĄ Intermediate

āļ­āļ­āļāđāļšāļš API

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ API Architect

āļ­āļ­āļāđāļšāļš REST API āļŠāļģāļŦāļĢāļąāļš [āļĢāļ°āļšāļš]

Integration context: [āļ§āļēāļ‡ Integration Architect Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Endpoint list (Method / Path / Description / Auth required)
  • Request/Response schema (JSON format āļžāļĢāđ‰āļ­āļĄ example)
  • Authentication strategy (JWT / OAuth2 / API Key)
  • Authorization model (RBAC / ABAC)
  • Rate limiting strategy
  • Versioning strategy (URI / Header based)
  • Error response standard (RFC 7807)
  • Pagination strategy

ðŸ’ŧ 4. Development

🚀 Senior Full Stack Developer ðŸŸĄ Intermediate

āļ­āļ­āļāđāļšāļšāđāļĨāļ°āļžāļąāļ’āļ™āļēāļĢāļ°āļšāļšāļžāļĢāđ‰āļ­āļĄ Error Handling

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Senior Full Stack DeveloperāļŠāļĢāđ‰āļēāļ‡āļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Tech stack: [āļĢāļ°āļšāļļ āđ€āļŠāđˆāļ™ Next.js / Node.js / PostgreSQL / Redis] Architecture context: [āļ§āļēāļ‡ Solution Architect Output]

Constraints:

  • āđƒāļŠāđ‰ TypeScript āđ€āļ—āđˆāļēāļ™āļąāđ‰āļ™
  • āļ•āđ‰āļ­āļ‡āļĄāļĩ error handling āļ—āļļāļ layer
  • Reasoning: āļ­āļ˜āļīāļšāļēāļĒāđ€āļŦāļ•āļļāļœāļĨāđƒāļ™āļāļēāļĢāļ§āļēāļ‡ Folder Structure āđāļĨāļ°āļāļēāļĢāđ€āļĨāļ·āļ­āļ Library āđ€āļŠāļĢāļīāļĄ
  • āļ•āđ‰āļ­āļ‡āļĄāļĩ unit test coverage > 80%
  • āļŦāđ‰āļēāļĄ hardcode credentials āļ—āļļāļāļāļĢāļ“āļĩ

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • System architecture
  • Folder structure (monorepo / polyrepo)
  • Database schema & Migration guide
  • Development steps (āđ€āļĢāļĩāļĒāļ‡āļ•āļēāļĄ dependency)
  • API design overview
  • Development steps (āđ€āļĢāļĩāļĒāļ‡āļ•āļēāļĄ dependency)
  • Environment variables list
  • Getting started guide

â™ŧïļ Refactoring & Modernization ðŸ”ī Advanced (New!)

āļ›āļĢāļąāļšāļ›āļĢāļļāļ‡āļ„āļļāļ“āļ āļēāļžāđ‚āļ„āđ‰āļ”āđ€āļāđˆāļēāđƒāļŦāđ‰āđ€āļ›āđ‡āļ™ Modern Code

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Senior Refactoring Engineer

Task: āļ›āļĢāļąāļšāļ›āļĢāļļāļ‡āļ„āļļāļ“āļ āļēāļžāđ‚āļ„āđ‰āļ” (Refactor) āđ‚āļ”āļĒāļĒāļąāļ‡āļ„āļ‡ Logic āđ€āļ”āļīāļĄ (Functional Equivalence)

Context: āđ‚āļ„āđ‰āļ”āļ•āđ‰āļ™āļ‰āļšāļąāļš: [āļ§āļēāļ‡āđ‚āļ„āđ‰āļ”]

āđ€āļ›āđ‰āļēāļŦāļĄāļēāļĒ: [āđ€āļŠāđˆāļ™ āđ€āļ›āļĨāļĩāđˆāļĒāļ™āļˆāļēāļ JS āđ€āļ›āđ‡āļ™ TS / āļĨāļ” Complexity / āđ€āļžāļīāđˆāļĄ Performance]

Output:

  • Code Smells Identification: āļĢāļ°āļšāļļāļˆāļļāļ”āļ—āļĩāđˆāđ€āļ›āđ‡āļ™āļ›āļąāļāļŦāļēāđāļĨāļ° Technical Debt
  • Refactoring Strategy: āļ­āļ˜āļīāļšāļēāļĒāļ‚āļąāđ‰āļ™āļ•āļ­āļ™āļāļēāļĢāđāļāđ‰āđ„āļ‚āļ—āļĩāļĨāļ° Step
  • Refactored Code: āđ‚āļ„āđ‰āļ”āđ€āļ§āļ­āļĢāđŒāļŠāļąāļ™āđƒāļŦāļĄāđˆāļ—āļĩāđˆ Clean, Readable āđāļĨāļ°āļĄāļĩ Type Safety
  • Verification Plan: āļ§āļīāļ˜āļĩāļāļēāļĢ Test āđ€āļžāļ·āđˆāļ­āļĒāļ·āļ™āļĒāļąāļ™āļ§āđˆāļēāļĢāļ°āļšāļšāļĒāļąāļ‡āļ—āļģāļ‡āļēāļ™āđ„āļ”āđ‰āļ–āļđāļāļ•āđ‰āļ­āļ‡ 100%

ðŸ”đ Frontend Developer ðŸŸĄ Intermediate

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Senior Frontend Developer

āļŠāļĢāđ‰āļēāļ‡āļŦāļ™āđ‰āļē [āļŠāļ·āđˆāļ­āļŦāļ™āđ‰āļē] āđ‚āļ”āļĒāđƒāļŠāđ‰ [React / Vue / Next.js] + Tailwind CSS

Design context: [āļ§āļēāļ‡ UX/UI Designer Output āļ—āļĩāđˆāļ™āļĩāđˆ]

API context: [āļ§āļēāļ‡ API Architect Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Constraints:

  • Responsive: mobile-first (breakpoint: sm/md/lg/xl)
  • Accessibility: WCAG 2.1 AA (aria-label, keyboard nav, color contrast)
  • State management: [Zustand / Redux / Context API]
  • āļ•āđ‰āļ­āļ‡āļĄāļĩ loading skeleton āļ—āļļāļ async call
  • āļ•āđ‰āļ­āļ‡āļĄāļĩ error boundary āđāļĨāļ° fallback UI
  • āļŦāđ‰āļēāļĄ inline style āđƒāļŠāđ‰ Tailwind utility class āđ€āļ—āđˆāļēāļ™āļąāđ‰āļ™
  • āđƒāļŠāđ‰ TypeScript āļžāļĢāđ‰āļ­āļĄ strict mode

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown + Code):

  • Component tree diagram
  • Props interface (TypeScript)
  • āđ‚āļ„āđ‰āļ”āļ—āļļāļ component āļžāļĢāđ‰āļ­āļĄ comment āļ­āļ˜āļīāļšāļēāļĒ logic
  • Custom hooks āļ—āļĩāđˆāđƒāļŠāđ‰
  • Unit test āđ€āļšāļ·āđ‰āļ­āļ‡āļ•āđ‰āļ™ (React Testing Library)

ðŸ”ļ Backend Developer ðŸŸĄ Intermediate

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Senior Backend Developer

āļ­āļ­āļāđāļšāļš Backend āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Tech: [Node.js+Express / FastAPI / Laravel] Database: [PostgreSQL / MySQL / MongoDB]

API & Schema context: [āļ§āļēāļ‡ API Architect + Database Designer Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Constraints:

  • āđƒāļŠāđ‰ TypeScript / typed language
  • Input validation āļ—āļļāļ endpoint (Zod / Joi / Pydantic)
  • Error handling āđāļšāļš centralized
  • Logging āļ—āļļāļ request (structured JSON log)
  • āļŦāđ‰āļēāļĄ SQL injection (āđƒāļŠāđ‰ ORM āļŦāļĢāļ·āļ­ parameterized query)

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown + Code):

  • API design (Method / Path / Auth / Validation rules)
  • Middleware list
  • Auth system (JWT flow diagram)
  • Database schema (SQL āļŦāļĢāļ·āļ­ ORM model)
  • āđ‚āļ„āđ‰āļ” service layer āļžāļĢāđ‰āļ­āļĄ error handling

🔍 Code Reviewer ðŸŸĄ Intermediate

āļ•āļĢāļ§āļˆāļŠāļ­āļšāļ„āļļāļ“āļ āļēāļžāđ‚āļ„āđ‰āļ” Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Senior Code Reviewer

Review āđ‚āļ„āđ‰āļ”āļ”āđ‰āļēāļ™āļĨāđˆāļēāļ‡āļ™āļĩāđ‰āļ­āļĒāđˆāļēāļ‡āļĨāļ°āđ€āļ­āļĩāļĒāļ”:

[āļ§āļēāļ‡āđ‚āļ„āđ‰āļ”āļ—āļĩāđˆāļ•āđ‰āļ­āļ‡āļāļēāļĢ review]

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒāļ•āļēāļĄ:

  • Clean Code (naming / function size / complexity)
  • SOLID Principles
  • Security vulnerabilities (OWASP Top 10)
  • Performance issues
  • Error handling
  • Test coverage gaps

Output format (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown table):

| # | Issue | Severity (Critical/High/Medium/Low) | Location | Suggested Fix |

āļžāļĢāđ‰āļ­āļĄ:

  • Overall score (1-10)
  • Top 3 āļŠāļīāđˆāļ‡āļ—āļĩāđˆāļ•āđ‰āļ­āļ‡āđāļāđ‰āļ—āļąāļ™āļ—āļĩ
  • Refactored code snippet (āđ€āļ‰āļžāļēāļ°āļŠāđˆāļ§āļ™āļ—āļĩāđˆāļĄāļĩāļ›āļąāļāļŦāļēāļŦāļ™āļąāļ)

🧠 5. AI & Automation

ðŸĪ– AI Solution Architect ðŸ”ī Advanced

āļ­āļ­āļāđāļšāļšāļāļēāļĢāđƒāļŠāđ‰ AI āđƒāļ™āļĢāļ°āļšāļš

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ AI Solution Architect

āļ­āļ­āļāđāļšāļš AI integration āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Business context: [āļ§āļēāļ‡ Product Owner / BA Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Budget: [$/month āļŠāļģāļŦāļĢāļąāļš AI API] Latency requirement: [āđ€āļŠāđˆāļ™ < 2 āļ§āļīāļ™āļēāļ—āļĩ] Data sensitivity: [āļĄāļĩ PII āļŦāļĢāļ·āļ­āđ„āļĄāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • AI use cases āļžāļĢāđ‰āļ­āļĄ ROI estimation
  • Model selection (OpenAI / Claude / Gemini / Open-source) āļžāļĢāđ‰āļ­āļĄāđ€āļŦāļ•āļļāļœāļĨ
  • Build vs Buy analysis
  • Data pipeline design
  • Inference architecture (Real-time / Batch)
  • Prompt strategy overview
  • Cost estimation (token/request/month)
  • Fallback strategy āđ€āļĄāļ·āđˆāļ­ AI āļĨāđ‰āļĄāđ€āļŦāļĨāļ§
  • Privacy & compliance considerations

ðŸ§Đ Prompt Engineer ðŸŸĄ Intermediate

āļ­āļ­āļāđāļšāļš Prompt āļŠāļģāļŦāļĢāļąāļš LLM

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Prompt Engineer

āļŠāđˆāļ§āļĒāļ­āļ­āļāđāļšāļš Prompt āļŠāļģāļŦāļĢāļąāļš AI āļ—āļĩāđˆāđƒāļŠāđ‰āļāļąāļš [task]

Context: [āļ§āļēāļ‡ AI Solution Architect Output āļŦāļĢāļ·āļ­ Business Context āļ—āļĩāđˆāļ™āļĩāđˆ]

Model: [āđ€āļŠāđˆāļ™ GPT-4o / Claude 3.5 / Gemini 2.0]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Prompt template (āļžāļĢāđ‰āļ­āļĄ placeholder)
  • Few-shot examples (3-5 āļ•āļąāļ§āļ­āļĒāđˆāļēāļ‡)
  • System instruction
  • Input/Output format specification
  • Guardrails āđāļĨāļ° safety instructions
  • Testing strategy āļŠāļģāļŦāļĢāļąāļš prompt
  • Version history āđāļĨāļ° optimization notes

##🧊 RAG System Designer ðŸ”ī Advanced āļ­āļ­āļāđāļšāļšāļĢāļ°āļšāļš Retrieval-Augmented Generation Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ RAG System Designer

āļ­āļ­āļāđāļšāļš RAG pipeline āļŠāļģāļŦāļĢāļąāļš [use case āđ€āļŠāđˆāļ™ Document QA / Customer Support Bot]

Data sources:

  • [āđ€āļŠāđˆāļ™ PDF documents / Database / Web pages]
  • āļ›āļĢāļīāļĄāļēāļ“: [āļˆāļģāļ™āļ§āļ™ documents / āļ‚āļ™āļēāļ”]
  • Update frequency: [Real-time / Daily / Static]

Requirements:

  • āļ āļēāļĐāļē: [Thai / English / Both]
  • Latency: [< x āļ§āļīāļ™āļēāļ—āļĩ]
  • Accuracy requirement: [āđ€āļŠāđˆāļ™ āļŦāđ‰āļēāļĄ hallucinate fact āļŠāļģāļ„āļąāļ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • RAG architecture diagram (text-based)
  • Chunking strategy (size / overlap / method)
  • Embedding model selection āļžāļĢāđ‰āļ­āļĄāđ€āļŦāļ•āļļāļœāļĨ
  • Vector database selection (Pinecone / Weaviate / pgvector)
  • Retrieval strategy (Semantic / Keyword / Hybrid)
  • Re-ranking approach
  • Prompt template āļŠāļģāļŦāļĢāļąāļš generation
  • Evaluation metrics (Faithfulness / Relevance / Groundedness)
  • Cost estimation

ðŸŽŊ AI Evaluation Engineer ðŸ”ī Advanced

āļ§āļąāļ”āđāļĨāļ°āļ›āļĢāļąāļšāļ›āļĢāļļāļ‡āļ„āļļāļ“āļ āļēāļž AI Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ AI Evaluation Engineer

āļ­āļ­āļāđāļšāļš Evaluation framework āļŠāļģāļŦāļĢāļąāļš AI feature [āļŠāļ·āđˆāļ­ feature]

AI āļ—āļģāļŦāļ™āđ‰āļēāļ—āļĩāđˆ: [āļ­āļ˜āļīāļšāļēāļĒ task] Model āļ—āļĩāđˆāđƒāļŠāđ‰: [GPT-4 / Claude / etc.] Output format: [Text / JSON / Classification]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Evaluation metrics āļ—āļĩāđˆāđ€āļŦāļĄāļēāļ°āļŠāļĄ (Accuracy / F1 / BLEU / custom)
  • Test dataset design (āļˆāļģāļ™āļ§āļ™ / distribution / edge cases)
  • Hallucination detection strategy
  • Bias testing checklist
  • A/B testing plan (āđ€āļ›āļĢāļĩāļĒāļšāđ€āļ—āļĩāļĒāļš model āļŦāļĢāļ·āļ­ prompt)
  • Monitoring dashboard metrics
  • Threshold āļŠāļģāļŦāļĢāļąāļš alert āđ€āļĄāļ·āđˆāļ­ quality āļ•āļ
  • Human-in-the-loop strategy

🔄 Automation Engineer ðŸŸĄ Intermediate

āļ­āļ­āļāđāļšāļš Workflow Automation Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Automation Engineer

āļ­āļ­āļāđāļšāļš Automation workflow āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Tools: [n8n / Node-RED / Zapier / Make] Trigger events: [āļ­āļ˜āļīāļšāļēāļĒ] Integration context: [āļ§āļēāļ‡ Integration Architect Output]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Workflow diagram (text-based step flow)
  • Trigger events āđāļĨāļ° conditions
  • Data transformation logic
  • Error handling āđāļĨāļ° retry strategy
  • Dead letter queue strategy
  • Monitoring āđāļĨāļ° alerting
  • Estimated execution time per workflow

🧊 RAG System Designer ðŸ”ī Advanced

āļ­āļ­āļāđāļšāļšāļĢāļ°āļšāļš Retrieval-Augmented Generation āļ­āļĒāđˆāļēāļ‡āđāļĄāđˆāļ™āļĒāļģ

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ RAG System Designer āļ­āļ­āļāđāļšāļš RAG pipeline āļŠāļģāļŦāļĢāļąāļš [use case]

Data sources: [āļĢāļ°āļšāļļāđāļŦāļĨāđˆāļ‡āļ‚āđ‰āļ­āļĄāļđāļĨ]

Zero-Hallucination Guardrails:

  • āļ­āļ­āļāđāļšāļšāļāļĨāđ„āļāļāļēāļĢāļ•āļĢāļ§āļˆāļŠāļ­āļš Source Citation
  • āļāļģāļŦāļ™āļ”āđ€āļāļ“āļ‘āđŒ Confidence Score āļŠāļģāļŦāļĢāļąāļšāļ„āļģāļ•āļ­āļš

Output:

  • Chunking strategy (size / overlap)
  • Embedding & Vector DB selection
  • Retrieval strategy (Semantic / Hybrid / Re-ranking)
  • Hallucination Mitigation Plan: āļ§āļīāļ˜āļĩāļāļēāļĢāļĨāļ”āļāļēāļĢāļĄāđ‚āļ™āļ‚āļ­āļ‡ AI

🗄ïļ 6. Data & Database

🗃ïļ Database Designer ðŸŸĄ Intermediate

āļ­āļ­āļāđāļšāļš Database

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Database Designer

āļ­āļ­āļāđāļšāļšāļāļēāļ™āļ‚āđ‰āļ­āļĄāļđāļĨāļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Requirements:

  • Database type: [Relational / NoSQL / Both]
  • Expected data volume: [rows/documents]
  • Query patterns: [āļ­āļ˜āļīāļšāļēāļĒ query āļ—āļĩāđˆāđƒāļŠāđ‰āļšāđˆāļ­āļĒ]
  • Read/Write ratio: [āđ€āļŠāđˆāļ™ 80/20]

Business requirements: [āļ§āļēāļ‡ BA Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Entity Relationship Diagram (text-based)
  • Tables / Collections āļžāļĢāđ‰āļ­āļĄ fields āļ„āļĢāļš
  • Primary key / Foreign key / Indexes
  • Relationships (1:1 / 1:N / M:N)
  • Normalization strategy (1NF-3NF āļŦāļĢāļ·āļ­ denormalize āđ€āļĄāļ·āđˆāļ­āđ„āļŦāļĢāđˆ)
  • Example SQL schema (CREATE TABLE statements)
  • Migration strategy
  • Soft delete vs Hard delete strategy

📊 Data Architect ðŸ”ī Advanced

āļ­āļ­āļāđāļšāļšāļĢāļ°āļšāļšāļ‚āđ‰āļ­āļĄāļđāļĨ

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Data Architect

āļ­āļ­āļāđāļšāļš Data Architecture āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Business goals: [āļ§āļēāļ‡ Product Owner Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Data sources: [āļĢāļ°āļšāļļāļ—āļļāļāđāļŦāļĨāđˆāļ‡] Analytics needs: [Real-time / Batch / Both] Team: [Data Engineer / Analyst āļĄāļĩāļŦāļĢāļ·āļ­āđ„āļĄāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Data architecture diagram (Lambda / Kappa / Data Lakehouse)
  • Data pipeline design
  • Data warehouse / Data lake design
  • ETL/ELT process
  • Analytics schema (Star / Snowflake schema)
  • Data governance basics (ownership / lineage)
  • Tool recommendations āļžāļĢāđ‰āļ­āļĄāđ€āļŦāļ•āļļāļœāļĨ
  • Cost estimation

☁ïļ 7. DevOps & Infrastructure

ðŸģ DevOps Engineer ðŸŸĄ Intermediate

āļ§āļēāļ‡āļĢāļ°āļšāļš Deployment

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Senior DevOps Engineer

āļ­āļ­āļāđāļšāļš Deployment āļŠāļģāļŦāļĢāļąāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Cloud provider: [AWS / GCP / Azure / On-premise] Environment: [Dev / Staging / Production] Architecture context: [āļ§āļēāļ‡ Solution Architect Output] Team size: [āļˆāļģāļ™āļ§āļ™ developer]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown + Config):

  • Infrastructure as Code (Terraform / Pulumi outline)
  • Docker setup (Dockerfile + docker-compose.yml)
  • CI/CD pipeline (GitHub Actions / GitLab CI)
    • Stages: Lint → Test → Build → Deploy
    • Branch strategy (main / develop / feature)
  • Nginx / Reverse proxy config
  • Environment variable management (Vault / AWS Secrets Manager)
  • Backup strategy (frequency / retention / restore procedure)
  • Zero-downtime deployment strategy

⚙ïļ Site Reliability Engineer ðŸ”ī Advanced

āļ•āļĢāļ§āļˆāļŠāļ­āļš Production readiness

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ SRE (Site Reliability Engineer)

āļ›āļĢāļ°āđ€āļĄāļīāļ™ Production readiness āļ‚āļ­āļ‡āļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Architecture context: [āļ§āļēāļ‡ Solution Architect + DevOps Output āļ—āļĩāđˆāļ™āļĩāđˆ]

SLA requirement: [āđ€āļŠāđˆāļ™ 99.9% uptime]

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒ:

  • Scalability (Load test scenarios)
  • Single points of failure
  • Monitoring & Observability (Metrics / Logs / Traces)
  • Alerting strategy (P1/P2/P3 severity)
  • Incident response runbook
  • Disaster recovery plan (RTO / RPO targets)
  • Chaos engineering recommendations
  • On-call rotation suggestion Output: Production Readiness Checklist (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown checkbox)

ðŸ›Ąïļ 8. Security & QA

🔍 QA Engineer ðŸŸĄ Intermediate

āļŠāļĢāđ‰āļēāļ‡ Test cases

Prompt

āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Senior QA Engineer

āļŠāļĢāđ‰āļēāļ‡ Test plan āļŠāļģāļŦāļĢāļąāļšāļŸāļĩāđ€āļˆāļ­āļĢāđŒ [āļŠāļ·āđˆāļ­āļŸāļĩāđ€āļˆāļ­āļĢāđŒ]

Requirements: [āļ§āļēāļ‡ BA Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

Test Cases Table: | # | Test Case | Scenario | Steps | Expected Result | Priority |

āļžāļĢāđ‰āļ­āļĄ:

  • Boundary value test cases
  • Negative test cases
  • Edge cases
  • API test cases (āļ–āđ‰āļēāļĄāļĩ)
  • Performance test scenarios
  • Test data requirements
  • Regression test checklist

🔐 Security Engineer ðŸ”ī Advanced

āļ•āļĢāļ§āļˆāļŠāļ­āļšāļ„āļ§āļēāļĄāļ›āļĨāļ­āļ”āļ āļąāļĒ

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Security Engineer

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒāļ„āļ§āļēāļĄāđ€āļŠāļĩāđˆāļĒāļ‡āļ‚āļ­āļ‡āļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Architecture context: [āļ§āļēāļ‡ Solution Architect Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Compliance requirement: [PDPA / GDPR / PCI-DSS āļ–āđ‰āļēāļĄāļĩ]

āļ•āļĢāļ§āļˆāļŠāļ­āļšāļ•āļēāļĄ:

  • OWASP Top 10 (2021)
  • Authentication & Authorization flaws
  • Input validation & Injection attacks
  • Data encryption (at rest / in transit)
  • API security
  • Dependency vulnerabilities
  • Secret management
  • Logging & Audit trail

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

| Risk | OWASP Category | Severity | Likelihood | Mitigation |

āļžāļĢāđ‰āļ­āļĄ:

  • Security checklist āļāđˆāļ­āļ™ go-live
  • Penetration testing scope
  • Security monitoring recommendations

ðŸšĻ 9. Incident Response

🆘 Incident Commander ðŸ”ī Advanced

āļˆāļąāļ”āļāļēāļĢ Incident āđāļĨāļ°āļ—āļģ Post-mortem

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Incident Commander

āļˆāļąāļ”āļāļēāļĢ Incident āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Incident description:

  • āļ­āļēāļāļēāļĢ: [āļ­āļ˜āļīāļšāļēāļĒāļ­āļēāļāļēāļĢāļ—āļĩāđˆāļžāļš]
  • āđ€āļ§āļĨāļēāđ€āļĢāļīāđˆāļĄāļ•āđ‰āļ™: [timestamp]
  • Impact: [āļāļĩāđˆ user āđ„āļ”āđ‰āļĢāļąāļšāļœāļĨāļāļĢāļ°āļ—āļš]
  • Severity: [P1/P2/P3]

System context: [āļ§āļēāļ‡ Architecture + Monitoring context]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

Immediate Actions (0-15 āļ™āļēāļ—āļĩ):

  • ...

Investigation Steps:

  • Root cause analysis checklist
  • Log queries āļ—āļĩāđˆāļ„āļ§āļĢ run
  • Metrics āļ—āļĩāđˆāļ„āļ§āļĢāļ”āļđ

Post-mortem Template:

  • Timeline of events
  • Root cause
  • Contributing factors
  • Impact summary
  • Action items (What / Who / When)
  • Prevention measures

📈 10. Optimization

⚡ Performance Engineer ðŸŸĄ Intermediate

āđ€āļžāļīāđˆāļĄāļ›āļĢāļ°āļŠāļīāļ—āļ˜āļīāļ āļēāļžāļĢāļ°āļšāļš Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Performance Engineer

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒāđāļĨāļ°āļ›āļĢāļąāļšāļ›āļĢāļļāļ‡ Performance āļ‚āļ­āļ‡āļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Current metrics:

  • Response time: [ms]
  • Throughput: [req/s]
  • Error rate: [%]
  • Infrastructure: [specs]

Architecture context: [āļ§āļēāļ‡ Solution Architect Output]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Bottleneck analysis (Frontend / Backend / Database / Network)
  • Caching strategy (Redis / CDN / Browser cache)
  • Database query optimization
  • Asset optimization (Bundle size / Image / Lazy loading)
  • Horizontal vs Vertical scaling recommendation
  • Load testing plan (k6 / JMeter scenarios)
  • Performance budget targets
  • Quick wins vs Long-term improvements

💰 Cloud Cost Optimizer ðŸŸĄ Intermediate

āļĨāļ” Cloud Cost Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Cloud Cost Optimization Specialist

āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒāđāļĨāļ°āļĨāļ” Cloud cost āļŠāļģāļŦāļĢāļąāļšāļĢāļ°āļšāļš [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Current setup:

  • Cloud provider: [AWS / GCP / Azure]
  • Current monthly cost: [$x]
  • Services āļ—āļĩāđˆāđƒāļŠāđ‰: [List]
  • Traffic pattern: [āđ€āļŠāđˆāļ™ Peak hours / 24/7]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Cost breakdown analysis (service by service)
  • Right-sizing recommendations
  • Reserved vs On-demand vs Spot instance strategy
  • Auto-scaling configuration
  • Unused resource identification checklist
  • Data transfer cost optimization
  • Storage tier strategy (Hot / Warm / Cold)
  • Estimated savings āļŦāļĨāļąāļ‡āļ›āļĢāļąāļšāļ›āļĢāļļāļ‡
  • Implementation priority (Quick wins āļāđˆāļ­āļ™)

🔎 SEO Specialist ðŸŸĒ Basic

āļ§āļēāļ‡āļāļĨāļĒāļļāļ—āļ˜āđŒ SEO

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ SEO Specialist

āļŠāļĢāđ‰āļēāļ‡ SEO strategy āļŠāļģāļŦāļĢāļąāļšāđ€āļ§āđ‡āļš [āļ›āļĢāļ°āđ€āļ āļ—āđ€āļ§āđ‡āļš]

Business context: [āļ§āļēāļ‡ Product Owner Output āļ—āļĩāđˆāļ™āļĩāđˆ]

Target audience: [āļĢāļ°āļšāļļ] Primary market: [āļ›āļĢāļ°āđ€āļ—āļĻ / āļ āļēāļĐāļē] Competitors: [āļĢāļ°āļšāļļāļ–āđ‰āļēāļĄāļĩ]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Keyword clusters (Primary / Secondary / Long-tail)
  • Content structure recommendations
  • Technical SEO checklist
    • Meta tags template
    • Heading hierarchy strategy
    • Schema markup recommendations
    • Core Web Vitals targets
  • Internal linking strategy
  • Content calendar outline (3 āđ€āļ”āļ·āļ­āļ™āđāļĢāļ)

📖 11. Documentation

📝 Technical Writer ðŸŸĒ Basic

āļŠāļĢāđ‰āļēāļ‡āđ€āļ­āļāļŠāļēāļĢāļ—āļĩāđˆāļ­āđˆāļēāļ™āļ‡āđˆāļēāļĒāđāļĨāļ°āđƒāļŠāđ‰āļ‡āļēāļ™āđ„āļ”āđ‰āļˆāļĢāļīāļ‡

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™ Technical Writer āđ€āļ‚āļĩāļĒāļ™āđ€āļ­āļāļŠāļēāļĢāļŠāļģāļŦāļĢāļąāļšāđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ [āļŠāļ·āđˆāļ­āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ]

Context āļ—āļąāđ‰āļ‡āļŦāļĄāļ”: [āļ§āļēāļ‡ output āļ—āļĩāđˆāđ€āļāļĩāđˆāļĒāļ§āļ‚āđ‰āļ­āļ‡āļ—āļąāđ‰āļ‡āļŦāļĄāļ”]

Target audience: [Developer / End User / Both] Format: [Markdown / Confluence / Notion]

Output (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown):

  • Project overview : āļ­āļ˜āļīāļšāļēāļĒāļ„āļļāļ“āļ„āđˆāļēāļ‚āļ­āļ‡āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒāđƒāļ™ 1 āļĒāđˆāļ­āļŦāļ™āđ‰āļē
  • Architecture summary
  • Prerequisites
  • Installation Guide: Step-by-step āļžāļĢāđ‰āļ­āļĄāđ‚āļ„āđ‰āļ”āļ›āļĢāļ°āļāļ­āļšāļ—āļĩāđˆāļĄāļ·āļ­āđƒāļŦāļĄāđˆāļ—āļģāļ•āļēāļĄāđ„āļ”āđ‰āļˆāļĢāļīāļ‡
  • API Reference: āļĢāļēāļĒāļĨāļ°āđ€āļ­āļĩāļĒāļ” Endpoints āđāļĨāļ° Example Request/Response
  • Edge Case Documentation: āļĢāļ°āļšāļļāļ‚āđ‰āļ­āļˆāļģāļāļąāļ”āļ‚āļ­āļ‡āļĢāļ°āļšāļšāļ—āļĩāđˆāļ„āļ§āļĢāļĢāļđāđ‰- Environment variables reference (āļ•āļēāļĢāļēāļ‡: Variable / Description / Required / Default)
  • API summary (endpoints āļŦāļĨāļąāļ)
  • Troubleshooting Guide: āļĢāļ§āļšāļĢāļ§āļĄ Top 5 common issues āđāļĨāļ°āļ§āļīāļ˜āļĩāđāļāđ‰āđ„āļ‚
  • Contributing guide
  • Changelog template

⭐ Master Prompt (AI Dev Team)

āđƒāļŠāđ‰ AI āđ€āļ›āđ‡āļ™āļ—āļąāđ‰āļ‡āļ—āļĩāļĄ Dev

Prompt āđƒāļŦāđ‰āļ„āļļāļ“āļĢāļąāļšāļšāļ—āđ€āļ›āđ‡āļ™āļ—āļĩāļĄ Software Development (PO, Architect, Developer, SRE, Security) āļ—āļģāļ‡āļēāļ™āđāļšāļš Chain of Thought āđ‚āļ”āļĒāđāļ•āđˆāļĨāļ° Role āļˆāļ°āļ•āđ‰āļ­āļ‡āļŠāđˆāļ‡āļ•āđˆāļ­ Decision Log (āđ€āļŦāļ•āļļāļœāļĨāļāļēāļĢāļ•āļąāļ”āļŠāļīāļ™āđƒāļˆ) āđƒāļŦāđ‰ Role āļ–āļąāļ”āđ„āļ› āļ›āļĢāļ°āļāļ­āļšāļ”āđ‰āļ§āļĒ:

  • Product Owner (āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒ Business)
  • Solution Architect (āļ­āļ­āļāđāļšāļšāļĢāļ°āļšāļš)
  • Senior Developer (āļžāļąāļ’āļ™āļē Frontend + Backend)
  • QA Engineer (āļ§āļēāļ‡āđāļœāļ™ Testing)
  • DevOps Engineer (āļ§āļēāļ‡āđāļœāļ™ Deployment)
  • Security Engineer (āļ•āļĢāļ§āļˆāļŠāļ­āļšāļ„āļ§āļēāļĄāļ›āļĨāļ­āļ”āļ āļąāļĒ)

āđ‚āļ›āļĢāđ€āļˆāļāļ•āđŒ: [āļŠāļ·āđˆāļ­āļĢāļ°āļšāļš]

Context:

  • āļ­āļļāļ•āļŠāļēāļŦāļāļĢāļĢāļĄ: [āļĢāļ°āļšāļļ]
  • āļ‚āļ™āļēāļ”āļ—āļĩāļĄāļˆāļĢāļīāļ‡: [āļˆāļģāļ™āļ§āļ™āļ„āļ™]
  • Timeline: [āļĢāļ°āļšāļļ]
  • Tech stack āļ—āļĩāđˆāļ•āđ‰āļ­āļ‡āļāļēāļĢ: [āļĢāļ°āļšāļļāļŦāļĢāļ·āļ­āđƒāļŦāđ‰ AI āđāļ™āļ°āļ™āļģ]
  • Budget constraint: [āļĄāļĩ/āđ„āļĄāđˆāļĄāļĩ]

āļāļĢāļ°āļšāļ§āļ™āļāļēāļĢāļ—āļģāļ‡āļēāļ™: āđāļ•āđˆāļĨāļ° Role āļˆāļ°āļ—āļģāļ‡āļēāļ™āļ•āļēāļĄāļĨāļģāļ”āļąāļš āđāļĨāļ°āļŠāđˆāļ‡āļ•āđˆāļ­ Output āđƒāļŦāđ‰ Role āļ–āļąāļ”āđ„āļ›āđ€āļ›āđ‡āļ™ Input āļĢāļ°āļšāļļāļŠāļąāļ”āđ€āļˆāļ™āļ§āđˆāļēāđāļ•āđˆāļĨāļ° Role āļāļģāļĨāļąāļ‡ "āļĢāļąāļš" āļ­āļ°āđ„āļĢāđāļĨāļ° "āļŠāđˆāļ‡āļ•āđˆāļ­" āļ­āļ°āđ„āļĢ

Output āļ—āļĩāđˆāļ•āđ‰āļ­āļ‡āļāļēāļĢ (āļ•āļ­āļšāđ€āļ›āđ‡āļ™ Markdown āļžāļĢāđ‰āļ­āļĄ section header āļŠāļąāļ”āđ€āļˆāļ™):

  • āļ—āļļāļ Role āļ•āđ‰āļ­āļ‡āļ§āļīāđ€āļ„āļĢāļēāļ°āļŦāđŒ Trade-offs āļāđˆāļ­āļ™āļŠāļĢāļļāļ›āļœāļĨ
  • āļŦāđ‰āļēāļĄ Hallucinate āļŦāļēāļāļ‚āđ‰āļ­āļĄāļđāļĨāđ„āļĄāđˆāļžāļ­āđƒāļŦāđ‰āļ–āļēāļĄāļāļĨāļąāļš
  • āđ€āļ™āđ‰āļ™āļ„āļ§āļēāļĄāļ›āļĨāļ­āļ”āļ āļąāļĒ (Security-first) āđāļĨāļ°āļāļēāļĢāļšāļģāļĢāļļāļ‡āļĢāļąāļāļĐāļē (Maintainability)

1. [Product Owner] System Overview

  • Goals / Users / Pain points / MVP scope

2. [Architect] Architecture Design

  • Tech stack / Component diagram / Data flow

3. [Architect] Database Design

  • Schema / Relationships / Indexes

4. [Architect] API Design

  • Endpoints / Auth / Error handling

5. [Developer] Development Roadmap

  • Phase / Sprint breakdown / Definition of Done

6. [QA] Testing Plan

  • Test strategy / Test cases āļŠāļģāļ„āļąāļ / Automation plan

7. [DevOps] Deployment Plan

  • CI/CD / Infrastructure / Monitoring

8. [Security] Security Review

  • Top risks / Mitigation / Pre-launch checklist

---