These are required patterns that prevent bugs, ensure consistency, and maintain code quality.
When to Use
Use gold-standards when asking about best practices, standards, gold standards, mandatory rules, required patterns, absolute imports, testing policy, error handling standards, security best practices, documentation standards, or workflow design standards. Covers absolute imports, parameter passing, error handling, Tier 2/3 testing with real infrastructure (NO mocking per rules/testing.md), workflow design, custom node development, security, documentation, and test creation.
Release-blocking regression tier (W33b) — every public km.* surface has a fingerprint test + an e2e execute(...) pattern that round-trips from workflow → node → engine → registry. See skill 34-kailash-ml for the exact contract. Release PRs block on this tier independently of unit/integration status.
Error Handling
gold-error-handling - Explicit handling, no silent swallowing, actionable messages, cleanup in finally
Workflow & Node Design
gold-workflow-design - Always .build() before execute, string-based node API, single responsibility
gold-custom-nodes - Extend BaseNode, validate inputs, consistent output format
Security & Documentation
gold-security - No hardcoded secrets, env vars for credentials, input validation, injection prevention
gold-documentation - Document all public APIs, include examples, explain WHY not just WHAT
Quick Reference
All workflow patterns follow the canonical 4-parameter pattern from /01-core-sdk.
Standard
Correct
Wrong
Imports
from kailash.workflow.builder import WorkflowBuilder
