simple-typescript
Apply direct, functional TypeScript and JavaScript coding style preferences. Use when writing, editing, reviewing, or refactoring TS/JS code; deciding whether to introduce classes, factories, helpers, wrappers, utilities, shared modules, types vs interfaces, validation boundaries, or recoverable error handling; or when the user asks for code that matches these personal style preferences.
92
88%
Does it follow best practices?
Impact
100%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
5%User Profile Fetcher
Tagged discriminated union error handling
Tagged union result type
80%
100%
No null/undefined failure
100%
100%
No throw at boundary
100%
100%
type keyword for result
100%
100%
Caller branches on tag
86%
100%
No trivial wrappers
100%
100%
Named function exports
100%
100%
Parse once at edge
100%
100%
100%
19%Product Catalogue API Module
Named exports and module boundaries
No factory function
100%
100%
No class
100%
100%
Optional params with defaults
100%
100%
Shared infrastructure extracted
100%
100%
Feature file stays focused
100%
100%
Optional grouped export
0%
100%
No trivial helpers
100%
100%
type keyword for shapes
0%
100%
Named function declarations
100%
100%
100%
26%Order Intake Processor
Schema/type file organization and boundary validation
schemas.ts exists
66%
100%
types.ts exists
100%
100%
Reusable items in dedicated files
100%
100%
Local-only items co-located
100%
100%
type not interface for domain shapes
0%
100%
No interface for local/non-extensible shapes
0%
100%
Validate at boundary
100%
100%
Normalize at boundary
100%
100%
Parse once principle
100%
100%
Feature-local schema files
100%
100%
- Repository
- idrevnii/perks
- Commit
51dd9ad
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.