Agent Skills
› UsefulSoftwareCo/executor
› wrdn-effect-schema-boundaries
wrdn-effect-schema-boundaries
GitHub在数据边界使用 Effect Schema 或类型适配器规范化未知数据，替代断言和探测。当出现双重类型转换、内联对象断言、未知形状探测或临时属性检查时触发。
Trigger Scenarios
代码中存在双重类型转换（如 as unknown as X）
对未知值进行内联对象断言
通过 in 操作符或 Reflect.get 探测未知数据结构
使用 JSON.parse 后直接进行类型断言
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
