gold-standards
Skill0 starsChanged 8 months agoApache-2.0View on GitHub
Mandatory best practices and gold standards for Kailash SDK development including absolute imports, parameter passing, error handling, testing policies (Real infrastructure recommended in Tiers 2-3), workflow design, custom node development, security, documentation, and test creation. Use when asking about 'best practices', 'standards', 'gold standards', 'mandatory rules', 'required patterns', 'absolute imports', 'Real infrastructure recommended', 'testing policy', 'error handling standards', 'security best practices', 'documentation standards', or 'workflow design standards'.
- Reads credentials
In this repository37 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- .claude/guides/claude-code/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- core-sdkSkill
- dataflowSkill
- nexusSkill
- kaizenSkill
- kailash-mcpSkill
- cheatsheetsSkill
- development-guidesSkill
- nodes-referenceSkill
- workflow-patternsSkill
- deployment-gitSkill
- frontend-integrationSkill
- testing-strategiesSkill
- architecture-decisionsSkill
- code-templatesSkill
- enterprise-infrastructureSkill
- validation-patternsSkill
- security-patternsSkill
- flutter-patternsSkill
- interactive-widgetsSkill
- enterprise-ai-uxSkill
- conversation-uxSkill
- uiux-design-principlesSkill
- value-auditSkill
- ai-interaction-patternsSkill
- eatp-referenceSkill
- coc-referenceSkill
- 29-pactSkill
- claude-code-patternsSkill
- error-troubleshootingSkill
- kailash-mlSkill
- kailash-alignSkill
- co-referenceSkill
- managementSkill
- projectSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
[gold-absolute-imports](gold-absolute-imports.md): - ALWAYS absolute, NEVER relative
- Very specific: line 33
[gold-workflow-design](gold-workflow-design.md): - Always .build() before execute, string-based node API, single responsibility
- Distinctive: line 38
[gold-security](gold-security.md): - No hardcoded secrets, env vars for credentials, input validation, injection prevention
- Distinctive: line 39
[gold-documentation](gold-documentation.md): - Document all public APIs, include examples, explain WHY not just WHAT
- Very specific: line 43
All workflow patterns follow the canonical 4-parameter pattern from /01-core-sdk.
- Distinctive: line 59
All connections use 4 parameters
- Distinctive: line 64
No mocking in Tier 2-3 tests
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Kailash Gold Standards - Mandatory Best Practices
These are required patterns that prevent bugs, ensure consistency, and maintain code quality.
Sub-File Index
Code Organization
- gold-absolute-imports - ALWAYS absolute, NEVER relative
from kailash.workflow.builder import WorkflowBuilder(notfrom ..workflow import builder)
- gold-parameter-passing - 4-parameter connections + dict result access
workflow.add_connection(source_id, source_param, target_id, target_param)results["node_id"]["result"](notresults["node_id"].result)
Testing
- gold-mocking-policy - Real infrastructure in Tiers 2-3
- Mocking ONLY in Tier 1 unit tests; Tiers 2-3 use real databases, APIs, infrastructure
- gold-testing - 3-tier strategy, deterministic tests, resource cleanup
- gold-test-creation - TDD, one assertion focus, AAA pattern
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 | from ..workflow.builder import WorkflowBuilder |
| Connections | workflow.add_connection("n1", "result", "n2", "input_data") | workflow.add_connection("n1", "n2") |
| Execution | runtime.execute(workflow.build()) | runtime.execute(workflow) |
| Results | results["node_id"]["result"] | results["node_id"].result |
| Secrets | os.environ["API_KEY"] | api_key = "sk-..." |
| Testing | Real DB in Tier 2-3 | Mock(spec=DataFlow) in Tier 2-3 |
| Errors | except WorkflowExecutionError as e: logger.error(...) | except: pass |
| Development | Write test first, then implement | Implement first, add tests later |
Before Every Commit
- All imports absolute
- All connections use 4 parameters
.build()called before execute- No hardcoded secrets
- Error handling present
- Tests written (TDD)
- No mocking in Tier 2-3 tests
- Documentation updated
Related Skills
- 16-validation-patterns - Validation tools
- 31-error-troubleshooting - Error patterns
- 12-testing-strategies - Testing strategies
- 01-core-sdk - Core patterns
Support
gold-standards-validator- Automated compliance checkingpattern-expert- Pattern validationtesting-specialist- Testing compliance
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

