Skip to content
Skills Library
Programming · Planning

csharp-zero-gc

/csharp-zero-gc

C# zero-GC engineering plans. Use when the user asks to make a system allocation-free, or mentions zero-GC, zero allocation, GC spikes, per-frame allocation budgets, object pooling systems, or preventing GC regressions. Produces a plan with commitment levels, acceptance criteria and regression guards, not a one-off code fix. For general stutter or FPS problems, or a single allocation found while optimizing, use unity-performance instead.

Licence
Apache-2.0
Last repository change
29.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
10
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

C# zero-GC engineering plans. Use when the user asks to make a system allocation-free, or mentions zero-GC, zero allocation, GC spikes, per-frame allocation budgets, object pooling systems, or preventing GC regressions. Produces a plan with commitment levels, acceptance criteria and regression guards, not a one-off code fix. For general stutter or FPS problems, or a single allocation found while optimizing, use unity-performance instead.

Original author description

C# zero-GC engineering plans. Use when the user asks to make a system allocation-free, or mentions zero-GC, zero allocation, GC spikes, per-frame allocation budgets, object pooling systems, or preventing GC regressions. Produces a plan with commitment levels, acceptance criteria and regression guards, not a one-off code fix. For general stutter or FPS problems, or a single allocation found while optimizing, use unity-performance instead.

How it works

  1. Choose the task
  2. Workflow
  3. Technical reference routing
Original SKILL.md headings · 33 lines, 374 words
SKILL.md preview
---
name: csharp-zero-gc
description: C# zero-GC engineering plans. Use when the user asks to make a system allocation-free, or mentions zero-GC, zero allocation, GC spikes, per-frame allocation budgets, object pooling systems, or preventing GC regressions. Produces a plan with commitment levels, acceptance criteria and regression guards, not a one-off code fix. For general stutter or FPS problems, or a single allocation found while optimizing, use unity-performance instead.
---

# csharp-zero-gc

Use progressive disclosure: read the required workflow references at the stage where they apply, and only the technical references relevant to the task. Do not bulk-load this directory or sibling skills. References contain binding original rules, not optional background. Loading less must not omit an applicable requirement.

## Choose the task

- **Focused explanation of an allocation pattern, library or guardrail:** read only the corresponding technical reference below. For commitment tiers and acceptance criteria, read [commitment tiers](references/core-rules.md).
- **Allocation inventory, remediation or engineering plan:** follow the full workflow below. Narrow code fixes still require applicable evidence and guardrails.
- **Rough lead list:** follow inventory and validation requirements; [independent review](references/independent-review.md) defines the limited exception for this output.

Conceptual answers do not constitute project findings or acceptance. Do not initiate a project review for a conceptual question. Once making project-specific findings, proposing code changes or claiming a path is clean, apply the full relevant evidence, validation and reporting rules below.

## Workflow

1. Read [commitment tiers and rollout](references/core-rules.md) before choosing a scope. Declare L1, L2 or L3 and its acceptance boundary.
2. For an allocation inventory or remediation, read [allocation inventory](references/allocation-inventory.md) and [execution strategy](references/execution.md). Follow the committed call chain and classify every allocation site.
3. Read only the technical references needed for the current patterns, library choices or regression guards.
4. Before reporting findings, read the [pseudo-optimization checks](../unity-performance/references/finding-validation.md) (shared with unity-performance) and [output requirements](references/reporting.md).
5. Before delivering an engineering plan, read and execute [independent adversarial review](references/independent-review.md). Preserve its required independent reviewer and the explicit rough-lead-list exception. Guardrails and acceptance measurements remain part of delivery.

## Technical reference routing

Read a row when the task involves its topic. For broad reviews, select all implicated topics after reconnaissance; for a narrow question, select only that topic.

| Reference | Topic / when to read |
|---|---|
| [guardrails.md](references/guardrails.md) | Zero-GC guardrails: keeping the gains from being eaten by everyday commits |
| [zero-alloc-libraries.md](references/zero-alloc-libraries.md) | Choosing frontier zero-allocation libraries (2025–2026 ecosystem) |
| [zero-alloc-patterns.md](references/zero-alloc-patterns.md) | Zero-allocation architecture pattern library (structural replacement, cures rebound) |

Related skills: unity-performance covers bottlenecks and engine optimization; csharp-zero-gc covers system allocation commitments and regression guards; code-standards covers conventions, design and orchestrated reviews. Load a sibling only when that distinct workflow is needed.
Files in this package (10)
  • LICENSE 1 KB
  • SKILL.md 4 KB
  • references/allocation-inventory.md 11 KB
  • references/core-rules.md 5 KB
  • references/execution.md 3 KB
  • references/guardrails.md 6 KB
  • references/independent-review.md 2 KB
  • references/reporting.md 1 KB
  • references/zero-alloc-libraries.md 5 KB
  • references/zero-alloc-patterns.md 8 KB

Versions

The database has no other skills named csharp-zero-gc.

Database snapshot: 13.11.2026 · package version 145073029b01 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90unity-performance
    Unity performance optimization. Use when the user asks to optimize a class, view, function, folder or an entire module, or mentions stutter, lag, frame drops, low FPS, jank, overheating, battery drain, GC allocation, memory leaks, DrawCalls, batching, overdraw, slow loading,…
  • 84optimizing-memory-allocation
    Implements Zero Allocation patterns using Span, ArrayPool, and ObjectPool for memory efficiency in .NET. Use when reducing GC pressure or optimizing high-performance memory operations.
  • 100performance-optimization
    Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets.…
  • 100performance-optimization
    Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets.…
  • 100unity-csharp
    Use this skill when the user says 'unity dots', 'unity ecs', 'unity entities', 'ISystem', 'IJobEntity', 'burst compiler', 'unity job system', 'unity c# performance'. Covers Unity Entities (ECS), the C# Job System and Burst plus GC-free C# patterns for Unity gameplay code. Do NOT…
  • 100performance-optimization
    Find and fix game performance problems methodically — measure with the engine profiler first, reason about the frame-time budget, locate the CPU-vs-GPU bottleneck, then apply the right fix: object pooling, draw-call batching, fewer allocations/GC spikes, and asset budgets.…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.