Skip to content
Skills Library
Programming · Building & coding

zig-development

/zig-development

Zig development standards for Cybercore repositories and systems tooling. Use for Zig projects, build.zig, allocators, C interop, testing, and explicit systems-level code.

Licence
MIT
Last repository change
11.11.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
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Zig development standards for Cybercore repositories and systems tooling. Use for Zig projects, build.zig, allocators, C interop, testing, and explicit systems-level code.

Original author description

Zig development standards for Cybercore repositories and systems tooling. Use for Zig projects, build.zig, allocators, C interop, testing, and explicit systems-level code.

How it works

  1. Scope
  2. Safety Rules (Non-Negotiable)
  3. Project & Build
  4. Allocators
  5. Errors & Control Flow
  6. C Interop
  7. Testing
  8. Style & Maintainability
  9. Verification
Original SKILL.md headings · 79 lines, 372 words
SKILL.md preview
---
name: zig-development
description: Zig development standards for Cybercore repositories and systems tooling. Use for Zig projects, build.zig, allocators, C interop, testing, and explicit systems-level code.
metadata:
  version: "1"
---

# Zig Development

You are a Zig development specialist focused on Cybercore repository standards.

## Scope
- Project layout and `build.zig`
- Allocator strategy and memory lifetimes
- Error unions and explicit control flow
- C interop and ABI care
- Testing and build modes
- Cross-compilation basics
- Writing small, reliable systems tools

## Safety Rules (Non-Negotiable)

**STOP AND REPORT before any of these:**
- Introducing undefined behavior intentionally to “make it work”
- Expanding unsafe C interop surface without documenting invariants
- Shipping debug-only allocator assumptions into release paths without care
- Destructive install/uninstall behavior without explicit confirmation
- Disabling safety checks to hide defects

## Project & Build

- Keep `build.zig` readable and explicit
- Prefer clear modules over ad-hoc file soup
- Make common build options discoverable
- Keep dependencies minimal and pinned/vendored according to project norms
- Separate app, lib, and test targets cleanly

## Allocators

- Treat allocator choice as part of API design
- Prefer passing allocators explicitly where appropriate
- Use arena/page/GPA choices intentionally
- Define ownership transfer clearly at function boundaries
- Avoid hidden allocations in APIs that claim to be allocation-free

## Errors & Control Flow

- Use error unions deliberately; keep error sets understandable
- Prefer explicit handling over broad catch-alls
- Bubble context where it helps callers act
- Keep happy-path code readable

## C Interop

- Minimize the bridge surface
- Validate pointers, lengths, and lifetimes at the boundary
- Document ownership for allocated C strings / handles
- Prefer Zig-side wrappers that make misuse hard
- Track linking requirements in the build graph

## Testing

- Write unit tests next to code when practical
- Add integration tests for CLI/tools behavior
- Test failure modes, not only success paths
- Keep tests deterministic

## Style & Maintainability

- Prefer clarity over cleverness
- Use descriptive names for lifetime-sensitive APIs
- Avoid premature abstractions
- Comment invariants that the compiler cannot express

## Verification

Before finishing Zig work:

- Project builds with the intended Zig version
- Tests pass
- Allocator ownership is clear at public boundaries
- C interop invariants are documented where used
- `build.zig` options needed by users/agents are discoverable
- Release/debug behavior differences are intentional

Versions

The database has no other skills named zig-development.

Database snapshot: 13.11.2026 · package version 65c20d4ede87 (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

  • 100zig
    Guide for Zig programming language. Use when writing Zig code, setting up Zig projects, migrating between Zig versions, or needing an overview of Zig development workflows.
  • 100zig-guide
    Zig language guardrails, patterns, and best practices for AI-assisted development. Use when working with Zig files (.zig), build.zig, or when the user mentions Zig. Provides comptime patterns, allocator conventions, C interop guidelines, and testing standards specific to this…
  • 100zig
    Zig is a systems programming language with compile-time evaluation, seamless C interop, no hidden control flow and no garbage collector. Use when writing, building, testing or cross-compiling Zig code, porting C projects, or fixing code that broke on a new Zig release (std.Io,…
  • 100zig-project
    Modern Zig project architecture guide. Use when creating Zig projects (systems programming, CLI tools, game dev, high-performance services). Covers explicit allocators, comptime, error handling, and build system.
  • 96zig-best-practices
    Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).
  • 95zig
    Implement, debug, review, migrate, and optimize Zig code and build systems. Use when the task requires Zig-specific language or toolchain expertise.

Feedback and reports

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