gate-3-implementation

Enforce Gate 3 type-safety and boilerplate compliance in TypeScript connectors.

6|Updated Feb 20, 2025
One-click install
npx skills add https://github.com/zerobias-org/module --skill gate-3-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate-3-implementation
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/gate-3-implementation
Command: npx skills add https://github.com/zerobias-org/module --skill gate-3-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce Gate 3 validation to guarantee implementation quality and type safety across connector components.

Core Features & Use Cases

  • Verifies that no 'any' types appear in signatures and that generated types are used.
  • Ensures ConnectorImpl extends only the generated interface and adheres to boilerplate metadata and isSupported patterns.
  • Provides guidance for mapper usage and runtime validation to catch missing fields early.

Quick Start

Audit your ConnectorImpl and Mapper implementations to confirm adherence to Gate 3 boilerplate and runtime validation.

Frequently Asked Questions about gate-3-implementation

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

FAQPage Schema
How do I enforce type safety and prevent Promise<any> in TypeScript connector code?

Type safety in TypeScript connector code is enforced by auditing signatures to eliminate 'any' types and requiring the use of generated API types across all ConnectorImpl implementations.

What is the correct way to implement ConnectorImpl boilerplate and isSupported patterns?

ConnectorImpl boilerplate requires extending only the generated interface and strictly adhering to defined metadata and isSupported patterns to validate implementation quality.

How do I use mapper patterns for runtime validation to catch missing fields?

Mapper runtime validation catches missing fields by applying mapper patterns that verify data structure completeness, ensuring zero missing fields during connector data processing.

Does Gate 3 validation require generated API types for connectionState and producer parameters?

Gate 3 validation requires generated API types to properly check connectionState and producer parameter context, ensuring strict type safety across connector components.

What are common type-safety limitations when implementing ConnectorImpl extensions?

Limitations arise when ConnectorImpl extensions deviate from the generated interface or fail to use strict mapper runtime validation, resulting in missing fields and unsafe 'any' types.