deterministic-coder

Files (1)

• SKILL.md

SKILL.md (first lines)

## STRAYLIGHT-CORE PROTOCOL ACTIVE

This skill enforces full straylight-core conformance. All code modifications MUST:
- Follow RFC straylight-001 (Standard Nix) naming and patterns
- Avoid all banned constructs (see below)
- Use complete file reads (no grep, no partial)
- Trace dependency graphs before modification
- Pass all verification checks
- For agent code: Support chat templates (Qwen3/ChatML) and thinking blocks per `STRAYLIGHT_STANDARDS.md`

---

## What I Do

Execute well-defined coding tasks with maximum consistency and precision:
- Fix bugs with minimal variation in approach
- Implement features according to clear specifications
- Refactor code following established patterns
- Convert code between formats or languages
- Update dependencies and configuration
- Apply routine code transformations

---

## Configuration

**Temperature: 0.3** - Deterministic, consistent solutions
**Thinking Budget: 2,048 tokens** - Focused reasoning
**Tool Strategy: Auto with parallel execution**

---

## MANDATORY PROTOCOL

### Before ANY Code Modification:

1. **Read ENTIRE target file** (no grep, no head, no partial)
2. **Trace dependencies upstream** (imports -> transitive imports)
3. **Trace consumers downstream** (exports -> consumers -> transitive consumers)
4. **Verify no banned constructs will be introduced**

### Banned Constructs - Zero Tolerance

**TypeScript:**
```typescript
any, unknown, as unknown as, as Type, !, ??, ||
// @ts-ignore, // @ts-expect-error, eval(), Function()
```

**Lean4:**
```lean
partial def, sorry, panic!, unreachable!, native_decide
```

**Haskell:**
```haskell
undefined, error "...", unsafeCoerce, unsafePerformIO
```

**PureScript:**
```purescript
unsafePartial, unsafeCoerce, undefined
```

**Nix:**
```nix
with lib;, with pkgs;, rec {...}, heredocs, default.nix in packages, camelCase
```

**Bash:**
```bash
# ONLY PERMITTED: exec program "$@"
# BANNED: if, for, while, case, &&, ||, variables, functions
```

---

## Execution Guidelines

1. **Complete File Reads**
   - Read ALL of target file before modification
   - State: "Read [filename]: [N] lines, [M] exports"
   - Chunk into <=500 line segments if too large

2. **Dependency Tracing**
   - Map: Module <- Imports <- Transitive Imports
   - Map: Module -> Exports -> Consumers -> Transitive Consumers
   - Fix ALL instances of a pattern across codebase

3. **Code is Truth, Types Describe**
   - NEVER delete code to satisfy TypeScript
   - ALWAYS update type definitions to match working code
   - If code works but types complain -> fix types

4. **Validation (MANDATORY)**
   ```bash
   npx tsc --noEmit
   npm test
   npx biome check
   scripts/check-formal-escapes.sh
   ```

5. **Documentation**
   - Provide file paths with line numbers (e.g., `src/utils.ts:45`)
   - Update relevant docs if behavior changed

---

## When to Use Me

- Bug fixes
- Implementing clear specifications
- Refactoring to established patterns
- Dependency updates
- Code conversions
- Consistent pattern application

---

From justinfleek/ComfyUI-Lattice-Compositor, MIT.

More from justinfleek/ComfyUI-Lattice-Compositor