Agent Skills
› UsefulSoftwareCo/executor
› wrdn-effect-schema-boundaries
wrdn-effect-schema-boundaries
GitHub规范边界处的未知或松散类型数据处理，使用 Effect Schema 进行解析验证，替换断言和动态探测，确保内部代码类型安全。
Trigger Scenarios
处理未信任输入数据
解析 JSON 字符串
消除 unknown 类型的重复探测
替换不安全的类型断言
Install
npx skills add UsefulSoftwareCo/executor --skill wrdn-effect-schema-boundaries -g -y
SKILL.md
Frontmatter
{
"name": "wrdn-effect-schema-boundaries",
"description": "Normalize unknown or loosely typed data at boundaries with Effect Schema, named guards, or typed adapters. Use when lint flags double casts, inline object assertions, unknown shape probing, or ad hoc property checks on unknown values.",
"allowed-tools": "Read Grep Glob Bash"
}
You fix one pattern: domain code is asserting or probing an unknown shape instead of parsing it once at the boundary.
Fix Shape
- Prefer
Schema.decodeUnknownEffect(MySchema)(value)for untrusted input. - Prefer
Schema.decodeUnknownEffect(Schema.fromJsonString(MySchema))(text)orSchema.decodeUnknownOption(Schema.parseJson())(text)for JSON strings. - Keep domain code typed after the decode; do not keep
unknownand probe it repeatedly. - Replace
JSON.parse,value as string,as unknown as X,as Record<string, unknown>, inline object assertions,"field" in value, andReflect.getwith a schema, typed adapter, or named guard. - A named guard is acceptable only when parsing is not the right abstraction and the guard has a precise return type.
Good
const ParsedConfig = Schema.Struct({
endpoint: Schema.String,
});
const config = yield * Schema.decodeUnknownEffect(ParsedConfig)(raw);
const config = yield * Schema.decodeUnknownEffect(Schema.fromJsonString(ParsedConfig))(rawText);
Bad
const config = raw as unknown as { endpoint: string };
const config = JSON.parse(rawText) as { endpoint: string };
const pattern = updated.pattern as string;
Version History
- fd4fb02 Current 2026-07-05 10:55
