gold-standards

Enforce Kailash SDK best practices for code design, testing, security, and documentation.

Updated Aug 23, 2026

Search Tags:#security #NO MOCKING #best-practices #gold-standard #Kailash SDK #testing-policy #absolute-imports

Ready to run

npx skills add https://github.com/esperie/new-project --skill gold-standards-esperie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gold-standards
Source: https://github.com/esperie/new-project/tree/main/.claude/skills/17-gold-standards
Command: npx skills add https://github.com/esperie/new-project --skill gold-standards-esperie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies mandatory best practices for Kailash SDK development, ensuring consistency, reliability, and security across projects.

Core Features & Use Cases

Enforces absolute imports, parameter passing conventions, and error handling strategies.
Provides NO MOCKING policy guidance for Tier 2-3 tests, plus testing and workflow design standards.
Supports security, documentation, and test creation guidelines.

Use cases include guiding code reviews, audits, and compliance verification across teams, and serving as a reference during design and implementation to uphold quality standards.

Quick Start

Invoke the gold-standards skill to review a project and generate a compliance checklist aligned with the defined standards.

Frequently Asked Questions about gold-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce SDK best practices for code reviews and compliance audits?▼

You can enforce SDK best practices by applying a codified standards skill that checks absolute imports, parameter passing conventions, and error handling to generate a compliance checklist for project reviews and audits.

What is the NO MOCKING policy for integration testing in the Kailash SDK?▼

The NO MOCKING policy for Kailash SDK testing prohibits the use of mocks in Tier 2-3 tests, requiring real component interactions to validate integration reliability and workflow design without simulated dependencies.

How do I set up mandatory secure coding and testing standards for Kailash SDK development?▼

To set up secure coding and testing standards for Kailash SDK development, invoke a best practices skill to review your project and generate a compliance checklist covering security requirements, testing policies, and documentation guidelines.

Does the Kailash SDK require absolute imports and specific connection parameters?▼

Yes, Kailash SDK development mandates absolute imports and enforces 4-parameter connections to ensure consistent module resolution, explicit parameter passing, and reliable workflow design across all projects.

What is the best way to verify workflow design and security compliance in SDK projects?▼

The best way to verify workflow design and security compliance is to evaluate your project against codified SDK standards, checking for absolute imports, 4-parameter connections, and secure coding requirements during design and implementation reviews.

Can I use these best practices standards for both code design and documentation workflows?▼

Yes, these SDK best practices standards apply to code design, testing, security, and documentation workflows, serving as a reference during implementation and guiding teams through reviews and compliance verification.