# PROMPT_LIBRARY.md

# Inveetaire AI Prompt Library

Version : 1.0

Status : ACTIVE

---

# Purpose

This document contains standardized prompts for AI-assisted development.

Every prompt follows the Inveetaire architecture and development standards.

Always reference:

- AI.md
- PROJECT.md
- WORKFLOW.md
- IMPLEMENTATION_ROADMAP.md
- PRD
- SAD
- DDD
- PDD
- ADR
- MIB
- TCS

AI must never redesign the architecture.

---

# PROMPT 01

New Module

---

Implement Task ID:

[TASK_ID]

Follow:

PRD

SAD

DDD

PDD

DBP

ADR

MIB

TCS

Requirements

- Implement ONLY this Task.
- Do not modify unrelated modules.
- Do not redesign architecture.
- Follow existing folder structure.
- Keep Controllers thin.
- Put business logic inside Services.
- Follow Definition of Done.
- Explain every file created.

Stop after implementation.

---

# PROMPT 02

Continue Existing Module

---

Continue implementation for

[TASK_ID]

Do not restart.

Review existing implementation first.

Only continue unfinished work.

Do not refactor unrelated code.

Maintain backward compatibility.

---

# PROMPT 03

Review Module

---

Review Module

[MODULE]

Review only.

Do not generate code.

Evaluate:

Architecture

Naming

Security

Performance

Workspace Isolation

Validation

Audit Logging

TCS Compliance

List findings.

Categorize:

Critical

Major

Minor

Suggestions

---

# PROMPT 04

Bug Fix

---

Bug Report

[DESCRIPTION]

Tasks

Reproduce

Find root cause

Fix root cause

Regression Test

Do not redesign.

Do not refactor unrelated files.

Explain what caused the issue.

---

# PROMPT 05

Refactoring

---

Refactor Module

[MODULE]

Goals

Improve readability.

Reduce duplication.

Improve maintainability.

Rules

No feature changes.

No database changes.

No architecture changes.

Behaviour must remain identical.

---

# PROMPT 06

Feature Enhancement

---

Enhance

[FEATURE]

Requirements

Must already exist in PRD.

Must already exist in MIB.

No architecture redesign.

Preserve compatibility.

Explain affected files.

---

# PROMPT 07

Database Changes

---

Implement database changes.

Follow

PDD

DDD

ADR

Requirements

Never change schema without approval.

Generate migration.

Update Model.

Update Service.

Update Validation.

Stop.

---

# PROMPT 08

UI Development

---

Build UI for

[MODULE]

Requirements

TailwindCSS only.

Alpine.js only.

Responsive.

Accessible.

Reusable components.

No business logic.

No inline CSS.

No inline JavaScript.

---

# PROMPT 09

Testing

---

Generate testing checklist.

Cover

Validation

Permissions

Workspace Isolation

Security

Edge Cases

Performance

Manual Testing

No code generation.

---

# PROMPT 10

Documentation

---

Generate documentation for

[MODULE]

Include

Overview

Architecture

Dependencies

Workflow

Routes

Views

Services

Known Limitations

Future Improvements

---

# PROMPT 11

Security Review

---

Review

[MODULE]

Check

CSRF

XSS

SQL Injection

Authentication

Authorization

Workspace Isolation

Soft Delete

Audit Logging

List vulnerabilities.

Do not generate unrelated improvements.

---

# PROMPT 12

Performance Review

---

Review

[MODULE]

Check

Database Queries

Indexes

Loops

Memory

Response Time

Duplicate Queries

Scalability

Recommend improvements.

---

# PROMPT 13

Pre-Commit Review

---

Review current changes.

Check

Architecture

Coding Standards

Naming

Security

Performance

Acceptance Criteria

Definition of Done

Only review.

No implementation.

---

# PROMPT 14

Release Readiness

---

Evaluate release readiness.

Check

Completed Tasks

Known Bugs

Database

Security

Testing

Documentation

Deployment

Provide Go / No-Go recommendation.

---

# PROMPT 15

Architecture Consultation

---

Evaluate proposed solution.

Do NOT implement.

Compare against

PRD

SAD

DDD

PDD

ADR

DBP

Explain

Pros

Cons

Impact

Recommendation

Wait for approval.

---

# Prompt Usage Rules

Always implement

ONE Task ID.

Never combine prompts.

Never redesign architecture.

Always explain decisions.

Always reference official documentation.

When unsure

STOP

Explain

Ask

Wait.

---

# Final Principle

Prompt consistency creates implementation consistency.

Never improvise.

Follow the architecture.

Build one task at a time.

---

# PROMPT 16

Implementation Session Template

---

Current Task: [TASK_ID]

Mandatory References (read before writing any code):

- AI.md (Sections 21-27 — operational rules)
- WORKFLOW.md (Steps 8A and 8B)
- MIB — locate [TASK_ID] and read "Files Expected"
- Sprint Execution Plan — confirm task scope

Requirements:

Implement ONLY Task [TASK_ID].

Do NOT implement any part of [NEXT_TASK_ID] or later tasks.

Create ONLY the files listed in MIB under "[TASK_ID] — Files Expected."

Do NOT execute git commands.

Prepare a commit message at the end, but do NOT run it.

Do NOT run terminal commands that write or delete files
without stating the command first and waiting for confirmation.

If you need to create a file NOT listed in "Files Expected":

  STOP.
  Explain why the file is needed.
  Reference the documentation gap.
  Wait for approval.

If you encounter a decision not covered by documentation:

  STOP.
  Explain the conflict.
  Wait for approval.

After implementation, provide:

1. Implementation Summary
2. Files Created (confirm each maps to "Files Expected")
3. Acceptance Criteria Verification
4. Definition of Done Checklist
5. Proposed Git Commit Message (do NOT execute)
6. Any deviations from documentation

Do not continue to [NEXT_TASK_ID].

Wait for approval.

---

# PROMPT 17

Git Commit Session Template

---

Review the completed work for Task [TASK_ID].

Step 1

Run: git status

Confirm only expected files are staged.

Confirm .env is NOT staged.

Confirm no files outside Task [TASK_ID] scope are present.

Step 2

Present findings.

List every file that will be committed.

Flag any unexpected file.

Step 3

Present the proposed commit message:

  [TASK_ID] Brief description of what was implemented

Wait for user to confirm the commit message.

Step 4

Wait for user to say "commit" before running git add and git commit.

Wait for user to say "push" before running git push.

Do NOT execute any git command without explicit instruction in the current message.
