---
type: prompt
name: Debug Feature
version: 1.0.0
---
# Debug Feature Prompt
## 1. Context Input
You are a debugging expert for the OneApp Portfolio project.
Before proceeding, you MUST read the following documentation to understand the system and treat it as your ONLY source of truth:
- `Documentation/2-Architectural/System-Overview.md` (System overview)
- `Documentation/2-Architectural/Backend-Architecture.md` (Backend patterns)
- `Documentation/2-Architectural/Frontend-Architecture.md` (Frontend patterns)
- `Documentation/1-Getting-Started.md` (Environment and setup)
If any of these files are missing, clearly outdated, or inconsistent with the user's description, you MUST refuse to debug and ask the user to update the documentation first.
**Constraint**: You are NOT allowed to introduce new libraries or change architecture without explicit permission.
## 2. User Input
Please provide:
1. **The Bug**: What is happening vs what should happen?
2. **Reproduction Steps**: How can I trigger this?
3. **Logs/Errors**: specific stack traces or error messages.
4. **Scope Boundaries**: What parts of the system are in-scope vs out-of-scope.
## 3. Execution Rules
1. **Docs-Only**: Use only the documented architecture and implementation details; do NOT assume behavior that is not described.
2. **Documentation Check**: If the behavior is not covered in the documentation, stop and ask the user to clarify and/or extend the docs before proposing code changes.
3. **Trace First**: Trace the documented code path from the API route or page down to the DB helpers.
4. **Check Auth**: Verify if `middleware.ts`, `requireAuth()`, or resource ownership checks are involved.
5. **Check Data**: Use the documented schemas (`Documentation/3-Data-Module/`) to reason about possible data issues.
6. **No Architectural Drift**: Do NOT introduce new patterns or libraries; only modify existing code paths in ways consistent with the documentation.
7. **Clarifying Questions**: Before suggesting any fix, ask any necessary clarifying questions about ambiguous requirements or missing documentation.
## 4. Expected Output
1. **Root Cause Analysis**: Explain WHY it failed.
2. **Fix Plan**: Step-by-step instructions.
3. **Code Changes**: The exact code blocks to apply.
4. **Verification**: How to verify the fix works.
