wanshuiyin/auto-claude-code-research-in-sleep1 file

Dse Loop

Autonomous design space exploration loop for computer architecture and EDA. Runs a program, analyzes results, tunes parameters, and iterates until objective is met or timeout. Use when user says \"DSE\", \"design space exploration\", \"sweep parameters\", \"optimize\", \"find best config\", or wants iterative parameter tuning.

Specification
Skill ID
wanshuiyin/auto-claude-code-research-in-sleep/dse-loop
Publisher
wanshuiyin
Repository
auto-claude-code-research-in-sleep
Installs
0
Files
1
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

wanshuiyin/auto-claude-code-research-in-sleep/dse-loopInstalls these files
  • SKILL.md

What this skill tells the agent

DSE Loop: Autonomous Design Space Exploration

🔁 Do not wrap this skill in `/loop` / `CronCreate`. It already loops internally until its objective is met or it times out. Unlike the verdict-bearing review/audit skills, its stop gate is an objective machine-checkable metric (Type-A), so its self-termination is safe same-model — the reason not to wrap it is scheduler duplication, not the verdict fence. See `shared-references/external-cadence.md`.

Autonomously explore a design space: run → analyze → pick next parameters → repeat, until the objective is met or timeout is reached. Designed for computer architecture and EDA problems.

Context: $ARGUMENTS

Safety Rules — READ FIRST

NEVER do any of the following:

  • sudo anything
  • rm -rf, rm -r, or any recursive deletion
  • rm any file you did not create in this session
  • Overwrite existing source files without reading them first
  • git push, git reset --hard, or any destructive git operation
  • Kill processes you did not start

If a step requires any of the above, STOP and report to the user.

Constants (override via $ARGUMENTS)

ConstantDefaultDescription
TIMEOUT2hTotal wall-clock budget. Stop exploring after this.
MAX_ITERATIONS50Hard cap on number of design points evaluated.
PATIENCE10Stop early if no improvement for this many consecutive iterations.
OBJECTIVEminimizeminimize or maximize the target metric.

Override inline: /dse-loop "task desc — timeout: 4h, max_iterations: 100, patience: 15"

Typical Use Cases

ProblemProgramParametersObjective
Microarch DSEgem5 simulationcache size, assoc, pipeline width, ROB size, branch predictormaximize IPC or minimize area×delay
Synthesis tuningyosys/DC scriptoptimization passes, target freq, effort levelminimize area at timing closure
RTL parameterizationverilator simdata width, FIFO depth, pipeline stages, buffer sizesmeet throughput target at min area
Compiler flagsgcc/llvm build + benchmark-O levels, unroll factor, vectorization, schedulingminimize runtime or code size
Placement/routingopenroad/innovusutilization, aspect ratio, layer configminimize wirelength / timing
Formal verificationabc/sbybound depth, engine, timeout per propertymaximize coverage in time budget
Memory subsystemcacti / ramulatorbank count, row buffer policy, schedulingoptimize bandwidth/energy

Workflow

Phase 0: Parse Task & Setup

  1. Parse $ARGUMENTS to extract:
  • Program: what to run (command, script, or Makefile target)
  • Parameter space: which knobs to tune and their ranges/options (may be incomplete — see step 2)
  • Objective metric: what to optimize (and how to extract it from output)
  • Constraints: hard limits that must not be violated (e.g., timing must close)
  • Timeout: wall-clock budget
  • Success criteria: when is the result "good enough" to stop early?
  1. Infer missing parameter ranges — If the user provides parameter names but NOT ranges/options, you MUST infer them before exploring:

a. Read the source code — search for the parameter names in the codebase:

  • Look for argparse/click definitions, config files, Makefile variables, module parameters, #define, parameter (SystemVerilog), localparam, etc.
  • Extract defaults, types, and any comments hinting at valid values

b. Apply domain knowledge to set reasonable ranges: | Parameter type | Inference strategy | |---------------|-------------------| | Cache/memory sizes | Powers of 2, typically 1KB–16MB | | Associativity | Powers of 2: 1, 2, 4, 8, 16 | | Pipeline width / issue width | Small integers: 1, 2, 4, 8 | | Buffer/queue/FIFO depth | Powers of 2: 4, 8, 16, 32, 64 | | Clock period / frequency | Based on technology node; try ±50% from default | | Bound depth (BMC/formal) | Geometric: 5, 10, 20, 50, 100 | | Timeout values | Geometric: 10s, 30s, 60s, 120s, 300s | | Boolean/enum flags | Enumerate all options found in source | | Continuous (learning rate, threshold) | Log-scale sweep: 5 points spanning 2 orders of magnitude around default | | Integer counts (threads, cores) | Linear: from 1 to hardware max |

c. Start conservative — begin with 3-5 values per parameter. Expand range later if the best result is at a boundary.

d. Log inferred ranges — write the inferred parameter space to dse_results/inferred_params.md so the user can review:

      # Inferred Parameter Space

      | Parameter | Source | Default | Inferred Range | Reasoning |
      |-----------|--------|---------|---------------|-----------|
      | CACHE_SIZE | config.py:42 | 32768 | [8192, 16384, 32768, 65536, 131072] | powers of 2, ±2x from default |
      | ASSOC | config.py:43 | 4 | [1, 2, 4, 8] | standard associativities |
      | BMC_DEPTH | run_bmc.py:15 | 10 | [5, 10, 20, 50] | geometric, common BMC depths |

e. Boundary expansion — during the search, if the best result is at the min or max of a range, automatically extend that range by one step in that direction (but log the extension).

  1. Read the project to understand:
  • How to run the program
  • Where results are produced (stdout, log files, reports)
  • How to parse the objective metric from output
  • Current/baseline configuration (if any)
  1. Create working directory: dse_results/ in project root
  • dse_results/dse_log.csv — one row per design point
  • dse_results/DSE_REPORT.md — final report
  • dse_results/DSE_STATE.json — state for recovery
  • dse_results/inferred_params.md — inferred parameter space (if ranges were not provided)
  • dse_results/configs/ — config files for each run
  • dse_results/outputs/ — raw output for each run
  1. Write a parameter extraction script (dse_results/parse_result.py or similar) that takes a run's output and returns the objective metric as a number. Test it on a baseline run first.
  1. Run baseline (iteration 0): run the program with default/current parameters. Record the baseline metric. This is the point to beat.

Phase 1: Initial Exploration

Goal: Quickly survey the space to understand which parameters matter most.

Strategy: Latin Hypercube Sampling or structured sweep of key parameters.

  1. Pick 5-10 diverse design points that span the parameter ranges
  2. Run them (in parallel if independent, via background processes or sequential)
  3. Record all results in dse_log.csv: `` iteration,param1,param2,...,metric,constraint_met,timestamp,notes 0,default,default,...,baseline_val,yes,2026-03-13T10:00:00,baseline 1,val1a,val2a,...,result1,yes,2026-03-13T10:05:00,initial sweep ... ``
  4. Analyze: which parameters have the most impact on the objective?
  5. Narrow the search to the most sensitive parameters

Phase 2: Directed Search

Goal: Converge toward the optimum by making informed choices.

Strategy: Adaptive — pick the approach that fits the problem:

  • Few parameters (≤3): Fine-grained grid search around the best region from Phase 1
  • Many parameters (>3): Coordinate descent — optimize one parameter at a time, holding others at current best
  • Binary/categorical params: Enumerate promising combinations
  • Continuous params: Binary search or golden section between best neighbors
  • Multi-objective: Track Pareto frontier, explore along the front

For each iteration:

  1. Select next design point based on results so far:
  • Look at the trend: which direction improves the metric?
  • Avoid re-running configurations already evaluated

Use this skill in a project

Open any RiverX project, search the Skills panel for wanshuiyin/auto-claude-code-research-in-sleep/dse-loop, and install it in one click.

Use this skill