免费在 GitHub 公开

zig-best-practices

Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).

中文简介正在准备中。当前显示原文说明。

aiskillstore/marketplace

查看安装方法

包含的文件（5）

SKILL.md3.3 KB
C-INTEROP.md2.0 KB
DEBUGGING.md1.6 KB
GENERICS.md1.7 KB
skill-report.json31.9 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Zig Best Practices

Follows type-first, functional, and error handling patterns from CLAUDE.md. This skill covers Zig-specific idioms only.

Type System Patterns

Tagged unions for mutually exclusive states — prevents invalid combinations that a struct with multiple nullable fields would allow:

const RequestState = union(enum) {
    idle,
    loading,
    success: []const u8,
    failure: anyerror,
};

Explicit error sets — documents exactly what can fail; anyerror hides failure modes:

const ParseError = error{ InvalidSyntax, UnexpectedToken, EndOfInput };
fn parse(input: []const u8) ParseError!Ast { ... }

Distinct types for domain IDs — compiler prevents mixing up different ID types:

const UserId = enum(u64) { _ };
const OrderId = enum(u64) { _ };

Comptime validation — catch invalid configurations at compile time, not runtime:

fn Buffer(comptime size: usize) type {
    if (size == 0) @compileError("buffer size must be greater than 0");
    return struct { data: [size]u8 = undefined, len: usize = 0 };
}

Memory Management

Pass allocators explicitly to every function that allocates; no global allocator state.
Place defer resource.deinit() immediately after acquisition — keeps cleanup co-located with creation.
Use errdefer for cleanup on error paths; defer for unconditional cleanup.
Use arena allocators for batch/temporary work; they free everything at once.
Use std.testing.allocator in tests — reports leaks with stack traces.

fn createResource(allocator: std.mem.Allocator) !*Resource {
    const resource = try allocator.create(Resource);
    errdefer allocator.destroy(resource);  // runs only on error
    resource.* = try initializeResource();
    return resource;
}

Key Conventions

Prefer const over var; prefer slices over raw pointers.
Prefer comptime T: type over anytype; explicit types produce clearer errors. Use anytype only for genuinely polymorphic cases (callbacks, std.debug.print-style).
Exhaustive switch: include an else returning an error or unreachable for truly impossible cases.
Use std.log.scoped(.module_name) for namespaced logging; define a module-level const log constant.
Larger cohesive files are idiomatic — tests alongside implementation, comptime generics at file scope.

Advanced Topics

Generic containers (queues, stacks, trees): See GENERICS.md
C library interop (raylib, SDL, curl): See C-INTEROP.md
Debugging memory leaks (GPA, stack traces): See DEBUGGING.md

Tooling

zigdoc — browse std library and dependency docs:

zigdoc std.mem.Allocator   # std lib symbol
zigdoc vaxis.Window        # project dependency
zigdoc @init               # create AGENTS.md with API patterns

ziglint — static analysis with .ziglint.zon config:

ziglint                    # lint current directory
ziglint --ignore Z001      # suppress specific rule

References

Language Reference: https://ziglang.org/documentation/0.15.2/
Standard Library: https://ziglang.org/documentation/0.15.2/std/
Zig Guide: https://zig.guide/

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

academy-guide

免费

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

中文简介正在准备中。当前显示原文说明。