native-firstlisted

Per-stack cheatsheet for "what does the platform already give me?" — reach for the built-in before a dependency, an abstraction, or a custom layer; also carries the smallest validation command per stack. Use BEFORE installing a package, writing a util/wrapper/abstraction, hand-rolling auth/cache/date/validation, or choosing how to verify. Covers Next.js/React, Astro, Node/TS, Cloudflare Workers, Vercel, Postgres+Drizzle+better-auth, Shopify (Liquid/Storefront/CLI), self-host (Docker/Coolify/Vultr). Triggers: "perlu install apa", "pakai library apa", "npm i", "pnpm add", "bikin helper/wrapper/abstraction", "cara validasi", "gimana cek ini jalan", over-engineering, bloat, dependency baru. NOT a general dev-task router.
ongkipro/dotfiles · ★ 0 · Web & Frontend · score 53

Install: claude install-skill ongkipro/dotfiles

# Native-first The ladder lives in `AGENTS.md` (always on). This skill is rung 3–5 made concrete: **what does this specific stack already give me, before I add anything?** Read only the reference for the stack you're in. Don't load them all. | Stack | Reference | |---|---| | Next.js App Router / React | `references/next-react.md` | | Astro | `references/astro.md` | | Node / TypeScript | `references/node-ts.md` | | Cloudflare Workers | `references/cloudflare.md` | | Vercel | `references/vercel.md` | | Postgres + Drizzle + better-auth | `references/data.md` | | Shopify (Liquid / Storefront / CLI) | `references/shopify.md` | | Self-host (Docker / Coolify / Vultr) | `references/selfhost.md` | | Browser (HTML / CSS / JS — any framework) | `references/browser.md` | ## The dependency test Before `npm i` / `pnpm add`, answer all four. Any "no" → don't install. 1. **Does the runtime already do it?** (`fetch`, `URL`, `Intl`, `crypto`, `structuredClone`, CSS, a DB constraint) 2. **Does an already-installed dep do it?** Check `package.json` first — you probably have it. 3. **Does it remove enough maintained code to earn its cost?** Line count is a heuristic, not a gate; include bundle, supply-chain, upgrade, and API surface. 4. **Is it healthy for this project?** Check compatibility, releases, unresolved breakage, security advisories, license, and maintenance signals. Adding it anyway is a legitimate call — but say in one line what you skipped and why. ## Validation — small