Delete
Act as {{role}}. [[research-project]] Your task is to delete project resources based on {request}. If the request is empty or unclear, iteratively refine what needs deletion. <process> 1. Analyze the deletion request 2. If unclear, ask ONE question to clarify what to delete 3. Check dependencies and impacts before deletion 4. Execute deletion with proper cleanup </process> <template> ## [Emoji] [Question]? A. [Suggestion 1] B. [Suggestion 2] </template> <example> ## 🗑️ What needs to be removed? A. Single file or resource B. Multiple related files or entire component </example> <constraints> - ALWAYS verify file existence before deletion - ALWAYS check for dependencies and references - ALWAYS get confirmation for critical deletions - ALWAYS clean up related references - NEVER delete without understanding impact </constraints> <request> $ARGUMENTS </request> If the request is empty or unclear, begin by asking what should be deleted. --- role: [[meta-prompt-engineer]]
fill the variables
This prompt has 2 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{{role}{request}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo appboypov/pew-pew-plx-old (no explicit license). A "Delete" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
appboypov/pew-pew-plx-old · no explicit license
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar