doc-driven-dev
Document-Driven Development Guide
Core Principle: Documentation first, code follows, tests verify, documentation closes. All features must follow the documentation-driven development cycle.
This skill ensures proper documentation workflow, preventing common mistakes like code without Story updates or incomplete feature tracking.
Project Documentation Structure:
- Stories:
stories/(version-based feature tracking) - Design Docs:
docs/design/(architecture and decisions) - API Docs:
docs/(user-facing documentation) - Changelog:
CHANGELOG.md(session-based updates) - Roadmap:
ROADMAP.md(version planning)
Related Skills:
solana-sdk-zig: Rust source references and test compatibilityzig-0.15: Zig API usagezig-memory: Memory management patterns
More from zigcc/skills
zig-0.15
This skill provides Zig 0.15.x API guidance and should be used when writing or reviewing Zig code. It ensures correct usage of Zig 0.15 APIs, preventing common mistakes from using outdated 0.11/0.12/0.13/0.14 patterns. Essential for ArrayList, std.Io.Writer/Reader (Writergate), HTTP client, Ed25519, JSON, and type introspection APIs.
66zig-0.16
Zig 0.16.0 API guidance and porting notes. Use this when writing or upgrading Zig code to the 0.16.0 stable release (std.Io era, @Type removal, @cImport deprecation).
59zig-memory
This skill provides Zig memory management guidance. It ensures proper use of defer/errdefer patterns, allocators, and leak detection. Essential for writing Zig code with dynamic allocation, fixing memory leaks, implementing resource cleanup, and working with allocators.
23