parse-boundary

Parse external data into typed structures using Schema.decodeUnknown.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aitchwhy/dotfiles --skill parse-boundary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parse-boundary
Source: https://github.com/aitchwhy/dotfiles/tree/main/config/quality/generated/skills/parse-boundary
Command: npx skills add https://github.com/aitchwhy/dotfiles --skill parse-boundary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parse external data at boundaries, trust internal types.

Core Features & Use Cases

  • DecodeUnknown at boundary
  • Transform at boundary
  • No runtime checks in domain

Quick Start

Parse input at boundary using Schema.decodeUnknownSync.

Frequently Asked Questions about parse-boundary

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

FAQPage Schema
How do I parse external data into typed data structures?

Parse external data at API, file, and environment boundaries using Schema.decodeUnknown to decode unknown inputs into strongly typed objects. This ensures type safety before data reaches your domain logic, eliminating runtime type checks inside your application.

Why should I parse at the boundary instead of in my domain code?

Boundary parsing separates concerns: external data validation happens once at entry points (HTTP requests, config files, environment variables), while your domain code works exclusively with trusted, pre-validated typed data. This reduces errors and simplifies internal logic.

Can I transform data while parsing at boundaries?

Yes. Boundary parsing supports both decoding unknown inputs into typed structures and transforming them simultaneously. This consolidates validation and shape conversion at entry points before data enters your domain.

What formats does boundary parsing work with?

Boundary parsing applies to HTTP requests, configuration from environment variables, and file contents. You decode any unknown external input against known schemas to produce strongly typed objects for internal consumption.

Do I need a schema to parse external data?

Yes. Boundary parsing requires defining known schemas upfront. You validate incoming external data against these schemas using decodeUnknown, which either produces typed data or fails validation, ensuring type safety.