cf-optimizelisted

# $cf-optimize Optimize: **$ARGUMENTS** ## Purpose Structured workflow for optimizing existing features, algorithms, or performance-critical code. Ensures every optimization is measured before and after so you know it actually helped. ## Workflow ### Step 0: Custom Guide ```! bash "${PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-optimize ``` If the block above printed anything, apply only the `## Before`, `## Rules`, and `## After` sections; if it shows the raw command instead of output, re-run that exact `load-custom-guide.sh` fence now. ### Step 1: Detect Available Tools Run quick availability checks for profiling/benchmarking tools. Store the result for use in later steps. ```bash # Node.js / JavaScript command -v clinic >/dev/null 2>&1 && echo "TOOL:clinic" command -v 0x >/dev/null 2>&1 && echo "TOOL:0x" npx lighthouse --version >/dev/null 2>&1 && echo "TOOL:lighthouse" # General command -v hyperfine >/dev/null 2>&1 && echo "TOOL:hyperfine" command -v perf >/dev/null 2>&1 && echo "TOOL:perf" # Web / Bundle command -v webpack-bundle-analyzer >/dev/null 2>&1 && echo "TOOL:webpack-bundle-analyzer" ``` If no tools are found, note this and proceed in **AI-only mode** — all profiling will be done via code instrumentation and manual timing. Results in AI-only mode are estimates; flag this clearly in the final report. ### Step 2: Understand the Target 1. Read `$ARGUMENTS` to identify what to optimize 2. If the target is vague, ask the user to clarify what "better" mean