zig-build-and-memory
Maintain version-sensitive Zig build graphs, allocator ownership, buffered I/O, tests and fuzz targets, especially zig-playground's Zig 0.15.2 minimum API contract. Use when editing build.zig, allocator or I/O code, or tests in a Zig project.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- zig-build-and-memory
- license
- MIT
- description
- Maintain version-sensitive Zig build graphs, allocator ownership, buffered I/O, tests and fuzz targets, especially zig-playground's Zig 0.15.2 minimum API contract. Use when editing build.zig, allocator or I/O code, or tests in a Zig project.
02 资源文件 2
- 许可证LICENSE1.3 KB
- 参考文档references/build-memory-io.md3.6 KB
03 SKILL.md 正文
Zig build and memory contracts
Read build.zig.zon and build.zig before choosing snippets or commands. Confirm actual compiler version and supported floor. Minimum 0.15.2 is not an exact compiler pin, nor proof every future standard library is compatible. Preserve module names, package fingerprint and dependency hashes unless deliberately changing package identity or dependencies.
Read build-memory-io.md for repository's module/test graph, unmanaged containers, allocation failure, writer flush and fuzz semantics. Match official docs and std source to compiler in use.
For a change, state who owns allocated bytes and when slices become invalid. Run relevant module and executable tests through existing build graph, then format/build checks fitting the change. Keep deterministic regression results, fuzz duration/corpus findings and cross-target compile results distinct.
04 同仓库更多 Skills
wiki-builder
Create and maintain a local Markdown research wiki (sources with provenance, compiled concept/source pages, index, maintenance log) driven by a per-wiki config. Use when the user wants to start a wiki or knowledge base, ingest sources into one, or query and update it; use wiki-page-writer for a single code deep-dive page.
refactoring-guru
Diagnose a named code smell and apply the smallest behavior-preserving refactoring, with verification before and after and an explicit stop condition. Use for structural refactors (extract, move, consolidate, change ownership), not for feature or bug work; for readability cleanup of recent changes use code-simplification.
legacy-seams
When changing untested legacy code, pin the observed results with characterization tests and open the smallest seam that substitutes only the blocking dependency, separate from any later logic change. Use when a clock, random source, I/O, global, or hidden constructor blocks a test or a safe edit. Use test-driven-development for a new behavior or a bug, refactoring-guru for one named structural refactor after the seam exists, and code-refactoring-tech-debt to choose which legacy to replace.
idea-refine
Refine a raw idea into a one-page brief (problem statement, recommended direction, assumptions to validate, MVP scope, not-doing list) through divergent then convergent thinking. Use when an idea is still vague or you want options and a stress test before committing; use interview-me when the goal itself is unclear and spec-driven-development once the direction is chosen.
code-review-and-quality
Review rubric and approval standard for any change before merge, including code written by you, another agent, or a human: five axes (correctness, readability, architecture, security, performance), change sizing, structural remedies, severity labels, and feedback technique. Use to judge whether a change is fit to merge; use code-review to run a PR or diff review end to end.
code-perfection
Smell and style gate for code you write or change. Bans known code smells (long method, large class, primitive obsession, long parameter list, data clumps, duplicate code, dead code, feature envy, shotgun surgery, flag arguments, message chains) and enforces behavior-preserving structure. On Scala files, enforces worxbend style. Use while implementing, reviewing a diff for smells, or when a smell or style violation is suspected. Routine construction stays with code-complete. SOLID and DRY stay with clean-code-guard. One named structural refactor stays with refactoring-guru.