🤖 AI Tools
Claude Code Slash Command from a Repeatable Job
Design a slash command for a repeatable job; no invented CLI flags.
0Reviews
Prompt
Act as a Claude Code power user. Design a slash command for a repeatable job; no invented CLI flags. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Tool and version: [Tool] - Job to automate: [Job] - Inputs/outputs: [IO] - Guardrails: [Guardrails] - Eval or retry needs: [Eval] - Forbidden: [Forbidden] Generate: 1. Job decomposition. 2. Tool-specific artifact (command, OpenAPI, Gem, scorer, n8n node). 3. Guardrails and retry. 4. Eval cases (5). 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Claude Code Slash Command from a Repeatable Job
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Title context: Claude Code Slash Command from a Repeatable Job Focus: Design a slash command for a repeatable job; no invented CLI flags. Sample org: Northline Labs (fictional in Inputs only) Audience: practitioners who will paste real notes next Stack/tool notes: use versions only if stated below; else unknown Facts on hand: three concrete bullets the user typed: (1) deadline Friday (2) budget not approved (3) no customer quotes yet Proof: none beyond those bullets Banned: best, guaranteed, #1, invented %, celebrity Compliance: not legal/medical/insurance advice if those domains appear; strip emails/phones/MRNs Category 11 example should stay practical and short paragraphs
Example Output
1. Restate: Design a slash command for a repeatable job; no invented CLI flags. For 'Claude Code Slash Command from a Repeatable Job', use only the Friday deadline, unapproved budget, and no-quotes facts. 2. Deliverable draft with headings matching Generate steps. Every number traces to Inputs (deadline Friday; budget unapproved). No customer quotes added. 3. Compliance: cut best/guaranteed/#1. Add not-advice and de-identify if domain needs it. Mark missing budget figures as NOT IN INPUTS. 4. Variants or checklist: 3 practical next actions that do not require invented data. 5. Gaps: (1) real metrics (2) named owner (3) tool version (4) proof quotes (5) jurisdiction if legal-adjacent. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.