coding

Enforce Guardian Core TypeScript coding standards and Effect service patterns.

Updated Aug 27, 2026

Search Tags:#architecture #TypeScript #migration #coding #Effect #Guardian Core

Ready to run

npx skills add https://github.com/guardian-intelligence/guardian-core --skill coding-guardian-intelligence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding
Source: https://github.com/guardian-intelligence/guardian-core/tree/main/.claude/skills/coding
Command: npx skills add https://github.com/guardian-intelligence/guardian-core --skill coding-guardian-intelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill defines and enforces Guardian Core TypeScript coding standards, ensuring consistency across services and migration efforts by aligning with the Effect TypeScript approach.

Core Features & Use Cases

Unified coding standards for Guardian Core TypeScript projects using Effect TS.
Enforces the Effect-first architecture, typed error handling, service patterns, testing standards, and migration conventions.
Use when writing new services, porting legacy modules, or performing code reviews to ensure conformity with the established patterns.

Quick Start

Follow the references in the repository to implement new services using the canonical Effect service pattern, review existing modules for pattern conformance, and adopt the migration protocol when porting legacy code.

Frequently Asked Questions about coding

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

FAQPage Schema

How do I structure TypeScript services using the Effect service pattern?▼

To structure TypeScript services using the Effect service pattern, follow the five-part canonical architecture enforced by Guardian Core, ensuring centralized errors, schemas, and consistent runtime expectations across all new and updated modules.

What is the best way to migrate legacy TypeScript modules to Effect?▼

Migrating legacy TypeScript modules to Effect requires following the established migration protocols and references, ensuring ported code conforms to Effect-first architecture, runtime expectations, and centralized error handling standards.

Does Guardian Core TypeScript coding require specific runtime and import configurations?▼

Guardian Core TypeScript coding requires specific runtime configurations, enforcing bun and NodeNext imports to ensure consistent module resolution and runtime behavior across all Effect-based services and ported legacy code.

How do I ensure consistent architecture during TypeScript code reviews?▼

To ensure consistent architecture during TypeScript code reviews, check for conformance to the five-part Effect service pattern, centralized schemas, typed error handling, and the established migration conventions documented in the references.

Why do I need centralized errors and schemas in Effect TypeScript services?▼

Centralized errors and schemas in Effect TypeScript services are required to enforce type-safe runtime validation and consistent error handling, ensuring all Guardian Core modules conform to the unified Effect-first coding standards.

When should I apply Effect-first TypeScript coding standards?▼

Apply Effect-first TypeScript coding standards when writing new services, porting legacy modules, or performing code reviews within Guardian Core to ensure architecture consistency, proper typed error handling, and adherence to testing standards.