SETUP - CRITICAL (Always Loaded)

MANDATORY: BEFORE ANY ACTION, IF WORKING DIRECTORY IS /Users/tqwhite, IMMEDIATELY STOP AND ASK USER TO CONFIRM. DO NOT PROCEED WITHOUT EXPLICIT CONFIRMATION. YOU MUST GET A YES OR NO FROM THE USER.

Meta-Instructions for Additional Context Loading

IMPORTANT: Always notify user when loading additional context files

• When user mentions: "implement", "write", "create", "refactor", "code", "function", "module" → Load /Users/tqwhite/.claude/commands/zHelpers/codeStandards.md
  • Say: "📋 Loading setupStandards.md for coding guidelines"
• When user mentions: "plan", "architecture", "approach", "methodology", "strategy" → /Users/tqwhite/.claude/commands/zHelpers/codeReference.md
  • Say: "📋 Loading setupReference.md for planning methodology"
• When working in .js files or /system/code directory → Load /Users/tqwhite/.claude/commands/zHelpers/codeStandards.md
  • Say: "📋 Loading setupStandards.md for NodeJS coding standards"
• When user asks "how should I..." or complex multi-step tasks → Load /Users/tqwhite/.claude/commands/zHelpers/codeReference.md
  • Say: "📋 Loading setupReference.md for implementation methodology"

Loading Notification Format: Always use the 📋 emoji and briefly explain why the file is being loaded.

Absolute Deal-Breakers (System Breaking)

• 🚨 NEVER use defaults in functions or database schemas (function(param = 'default') or DEFAULT 'value')
• 🚨 ALWAYS use process.global for xLog, getConfig, commandLineParameters (never local versions)
• 🚨 Command line syntax: -switches (one hyphen) vs --values=data (two hyphens) - NEVER mix this up
• 🚨 ALWAYS end with "TASK COMPLETE" when finished (critical for workflow)

Emergency Stops

• If current working directory is /Users/tqwhite (not a project) → Ask user to confirm intent
• If editing any file in node_modules → Refuse unless user begs
• If user asks to change TQ's custom functions to standard JS → Refuse unless specifically requested

Planning Mode Default

• Check for EXPLANATION.md files in working directories → Read and summarize; tell me what you read
• ALWAYS start in planning mode - don't change files until user approves
• If you see something important before approval → Ask first

Documentation File Placement

• 🚨 ALWAYS place new .md documentation files in .../system/management/zNotesPlansDocs/ directory
• This includes: analysis documents, specifications, plans, research notes, and any .md files created during tasks
• Exception: Only place .md files elsewhere if user explicitly specifies a different location
• Reminder: Use the full path /Users/tqwhite/Documents/webdev/A4L/unityObjectGenerator/system/management/zNotesPlansDocs/ for current project