envapt

Use this when writing or reviewing any prose in a repo - reference docs, conceptual guides, READMEs, code comments, commit messages, or PR descriptions. Defines a precise, anti-marketing voice - a ban-list of hype words (powers, seamless, loudly, robust, leverage, easy, ...), an anthropomorphism verb-swap, before/after rewrites, worked comment and commit examples, and a one-line test for whether a sentence states a behavior or just sells one.

Reads typed, validated config from process.env, .env files, or any bound source for TypeScript and JavaScript with the envapt library, on Node, Bun, Deno, Cloudflare Workers, and the browser. Use when the project imports from 'envapt' or 'envapt/config', when the user mentions envapt, Envapter, @Envapt, or the @EnvNum/@EnvStr/@EnvBool/@EnvUrl/@EnvTime sugar decorators, or when the task involves reading typed environment variables, loading .env files, validating env with zod/valibot/arktype, binding config on Cloudflare Workers or in the browser, or migrating off dotenv or the removed 'envapt/workerd' / 'envapt/browser' subpaths.

Use this when writing, refactoring, or reviewing TypeScript code. Defines when comments are required, when they are noise, and how to document guardrails, invariants, and non-obvious logic without bloating the codebase.

Release envapt through changesets pre mode. Cut a prerelease from the long-lived `next` branch, graduate it to a stable release on `main`, then re-sync `next`. Use for any envapt release on the `next` line.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Use this when asked to write code, or audit, sweep, or fix code quality in the envapt repo (incl. the apps/guide Fumadocs docs app). Covers React 19 + Tailwind v4 antipattern categories as a manual review checklist, TS/OOP/fail-fast rules, and when to parallelize with subagents. Also use when onboarding any agent to this repo's quality standards.

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

Use when building or refactoring user-facing UI components. Encodes the dev-page checkpoint loop, mock-fidelity discipline, and animation principles. Each component lands through a structured build → preview → end-turn → user-feedback → iterate cycle, NOT a single shot.