skills.rest
sjtw
sjtwCOMMUNITY
Explore all skills by this author →
GitHub

build-evaluation-developer

Codify safety and performance invariants for modifying a DFS-based weapon build evaluator.

1|1|Updated Dec 16, 2023
Search Tags:#testing#debugging#optimization#concurrency#go#evaluator#dfs
One-click install
npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill build-evaluation-developer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-evaluation-developer
Source: https://github.com/sjtw/tarkov-build-optimiser/tree/main/.cursor/skills/build-evaluation-developer
Command: npx skills add https://github.com/sjtw/tarkov-build-optimiser --skill build-evaluation-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides safety-focused guidelines for modifying the weapon build evaluation logic, preventing runaway searches and ensuring thread safety in the DFS engine.

Core Features & Use Cases

  • Safety invariants and scope boundaries for modifying the DFS-based evaluator.
  • Guidance on pre-evaluation setup, concurrency handling, and caching considerations.
  • Use cases include adding new metrics, debugging suboptimal builds, and ensuring performance stability.

Quick Start

Follow the developer checklist to safely extend the evaluator, then run the recommended tests.

Frequently Asked Questions about build-evaluation-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely extend a DFS-based evaluator without causing exponential search growth?▼

To safely extend a DFS-based evaluator, follow a developer checklist to codify safety invariants, maintain strict scope boundaries for pruning logic, and run comprehensive tests to prevent exponential search growth.

How do I handle thread safety when modifying a Go concurrency evaluator?▼

Handle thread safety in a Go concurrency evaluator by applying disciplined pre-evaluation setup and thread-safe patterns, ensuring concurrent processSlots modifications do not create race conditions during metric evaluation.

Why does my weapon build evaluator return suboptimal builds after adding new metrics?▼

Weapon build evaluators return suboptimal builds when pruning logic and new metrics violate performance invariants, requiring you to debug scope boundaries and validate changes across all weapons and trader levels.

What's the best way to add new metrics to a high-performance DFS evaluator?▼

The best way to add new metrics to a high-performance DFS evaluator is codifying safety invariants first, updating processSlots logic carefully, and running recommended tests to ensure performance stability.

What are the limitations of modifying pruning logic in a DFS weapon build evaluator?▼

Modifying pruning logic in a DFS weapon build evaluator risks runaway searches and suboptimal builds if scope boundaries are ignored, making comprehensive testing and strict adherence to safety invariants essential.

Related Skills

Explore More Software Engineering Skills→
geoffjaygeoffjay
8

go-concurrency

Guide Go concurrency design with goroutines, channels, and synchronization primitives.

Community
Intermediate
Vasallo94Vasallo94
8

Test Runner

Run and debug Python test suites with pytest and uv.

Community
Intermediate
MimicHunterZMimicHunterZ
56

flutter-caching

Implement caching and offline-first persistence in Flutter applications.

Community
Advanced
StudentCristianStudentCristian

nw-production-safety

Enforce four-layer input validation, output filtering, and production readiness checks.

Community
Advanced