frostney/known-good-route

react-stack

>- Applies the user's Bun-based React stack across Next.js web and Expo universal profiles, deferring backend and repository details to their domain skills. Use when scaffolding a React app, upgrading dependencies, choosing MVP tooling, or selecting a project profile.

First seen May 18, 2026

Installation

$ npx skills add frostney/known-good-route --skill react-stack

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from frostney/known-good-route · top by installs.

npx skills add frostney/known-good-route

Browse all from frostney/known-good-route

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseUnlicense OR MIT
CompatibilityAssumes a Bun-only TypeScript project using Next.js App Router or Expo Router, Convex, Clerk, Biome, and Lefthook.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,378 B
  • docs SUMMARY.md 284 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 13 installs

SKILL.md

React stack

Apply only decisions material to the requested work. Preserve valid project choices; do not turn a narrow change into a stack or layout migration.

Select the profile

Profile Use when
Web Next.js App Router; server-rendered/static web; SEO; Vercel
Universal Expo Router; mobile-first iOS, Android, and web

Document the choice in project context. If neither fits, follow the project's AGENTS.md instead of forcing this stack. Read the matching profile reference before scaffolding, routing, styling, deployment, or a framework upgrade:

  • [references/web.md](references/web.md)
  • [references/universal.md](references/universal.md)

Shared decisions

  • Bun is the only runtime/package manager; keep bun.lock and forbid other

package-manager lockfiles.

  • Use typescript-stack/SKILL.md for compiler configuration, type and API design,

module boundaries, language-level code style, and TypeScript validation.

  • Biome owns lint, format, and import ordering.
  • bun test unit tests are co-located with source. End-to-end tests live in

root e2e/.

  • Source lives under src/ by domain. src/app/ contains framework routes only.
  • Components use Atomic Design folders (atoms, molecules, organisms) with

downward-only dependencies and co-located companions.

  • Convex owns application data; Clerk owns identity. Use

convex-conventions/SKILL.md for backend policy.

  • Clerk Billing is the default; use Stripe only for a documented capability gap.
  • Vercel AI Gateway is the default AI lane. Use a native provider only for a

verified unsupported capability and isolate the exception.

  • Use Zod outside Convex and Convex validators inside it.
  • Knip checks dead code; Fallow reports complexity and churn hotspots.
  • Use Portless for stable worktree-aware local URLs.
  • Use .env.local for solo work and Doppler once a team shares secrets.

Read [references/shared-tooling.md](references/shared-tooling.md) when scaffolding layout, observability, generators, hooks, or package scripts. project-structure/SKILL.md owns language-neutral repository policy.

Evidence and boundaries

  • Verify dependency versions and release status live before adding or upgrading

them; read migration notes for framework, Convex, and Clerk version jumps.

  • Confirm Bun and framework/native-package compatibility on the deployment

target.

  • A single bun run check runs the project's format, lint, tests, typecheck,

dead-code/health checks, and build as applicable.

  • After dependency changes, run a frozen install plus the check and production

build on the target runtime.

  • If this skill does not prescribe a category, recommend a current

Vercel-friendly option with its version, fit, and tradeoffs. Wait for the user before adding that new product or service.

Do not claim completion without observing the relevant project gate.