claude-evolve 1.3.25 → 1.3.26
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/claude-evolve-ideate +30 -0
- package/package.json +1 -1
package/bin/claude-evolve-ideate
CHANGED
|
@@ -342,6 +342,16 @@ Requirements for new CSV rows:
|
|
|
342
342
|
- Each description should be one clear sentence describing a specific algorithmic change
|
|
343
343
|
- Descriptions should explore completely different approaches than existing ones
|
|
344
344
|
- All new rows should have empty performance and status fields
|
|
345
|
+
|
|
346
|
+
CRITICAL CSV FORMAT RULES:
|
|
347
|
+
- DO NOT modify the CSV header row
|
|
348
|
+
- DO NOT change the column order
|
|
349
|
+
- DO NOT add extra columns or fields
|
|
350
|
+
- DO NOT modify existing rows - only append new ones
|
|
351
|
+
- DO NOT add extra blank lines or formatting
|
|
352
|
+
- Maintain exact CSV format: id,basedOnId,description,performance,status
|
|
353
|
+
- Leave performance and status fields completely empty (just commas)
|
|
354
|
+
- Use proper CSV quoting only when descriptions contain commas
|
|
345
355
|
- CRITICAL: You must read existing evolution files to avoid suggesting changes that:
|
|
346
356
|
* Have already been tried and failed
|
|
347
357
|
* Are impossible given the codebase structure
|
|
@@ -395,6 +405,16 @@ Requirements for new CSV rows:
|
|
|
395
405
|
- Each description should be one clear sentence about parameter tuning
|
|
396
406
|
- Focus on adjusting hyperparameters, thresholds, sizes, learning rates
|
|
397
407
|
- All new rows should have empty performance and status fields
|
|
408
|
+
|
|
409
|
+
CRITICAL CSV FORMAT RULES:
|
|
410
|
+
- DO NOT modify the CSV header row
|
|
411
|
+
- DO NOT change the column order
|
|
412
|
+
- DO NOT add extra columns or fields
|
|
413
|
+
- DO NOT modify existing rows - only append new ones
|
|
414
|
+
- DO NOT add extra blank lines or formatting
|
|
415
|
+
- Maintain exact CSV format: id,basedOnId,description,performance,status
|
|
416
|
+
- Leave performance and status fields completely empty (just commas)
|
|
417
|
+
- Use proper CSV quoting only when descriptions contain commas
|
|
398
418
|
- CRITICAL: You must read the parent algorithm file to understand:
|
|
399
419
|
* What parameters are actually tunable in the code
|
|
400
420
|
* What changes made this algorithm successful vs its parent
|
|
@@ -448,6 +468,16 @@ Requirements for new CSV rows:
|
|
|
448
468
|
- Each description should be one clear sentence about architectural changes
|
|
449
469
|
- Keep core insights but change implementation approach
|
|
450
470
|
- All new rows should have empty performance and status fields
|
|
471
|
+
|
|
472
|
+
CRITICAL CSV FORMAT RULES:
|
|
473
|
+
- DO NOT modify the CSV header row
|
|
474
|
+
- DO NOT change the column order
|
|
475
|
+
- DO NOT add extra columns or fields
|
|
476
|
+
- DO NOT modify existing rows - only append new ones
|
|
477
|
+
- DO NOT add extra blank lines or formatting
|
|
478
|
+
- Maintain exact CSV format: id,basedOnId,description,performance,status
|
|
479
|
+
- Leave performance and status fields completely empty (just commas)
|
|
480
|
+
- Use proper CSV quoting only when descriptions contain commas
|
|
451
481
|
- CRITICAL: You must read the parent algorithm file to understand:
|
|
452
482
|
* What structural elements can be modified within the codebase constraints
|
|
453
483
|
* What architectural decisions led to this algorithm's success
|