t1k:web:core:frameworks
| Field | Value |
|---|---|
| Module | core |
| Version | 1.26.1 |
| Effort | high |
| Tools | — |
Keywords: App Router, caching, Cloudflare, deploy, monorepo, Next.js, Pages, React, RSC, SSR, Turborepo, web
How to invoke
Section titled “How to invoke”/t1k:web:core:frameworks[framework] [feature]Web Frameworks Skill Group
Section titled “Web Frameworks Skill Group”Comprehensive guide for building modern full-stack web applications using Next.js, Turborepo, and RemixIcon.
Overview
Section titled “Overview”This skill group combines three powerful tools for web development:
Next.js - React framework with SSR, SSG, RSC, and optimization features Turborepo - High-performance monorepo build system for JavaScript/TypeScript RemixIcon - Icon library with 3,100+ outlined and filled style icons
When to Use This Skill Group
Section titled “When to Use This Skill Group”- Building new full-stack web applications with modern React
- Setting up monorepos with multiple apps and shared packages
- Implementing server-side rendering and static generation
- Optimizing build performance with intelligent caching
- Creating consistent UI with professional iconography
- Managing workspace dependencies across multiple projects
- Deploying production-ready applications with proper optimization
Stack Selection Guide
Section titled “Stack Selection Guide”Single Application: Next.js + RemixIcon
Section titled “Single Application: Next.js + RemixIcon”Use when building a standalone application:
- E-commerce sites
- Marketing websites
- SaaS applications
- Documentation sites
- Blogs and content platforms
Setup:
bunx create-next-app@latest my-appcd my-appbun install remixiconMonorepo: Next.js + Turborepo + RemixIcon
Section titled “Monorepo: Next.js + Turborepo + RemixIcon”Use when building multiple applications with shared code:
- Microfrontends
- Multi-tenant platforms
- Internal tools with shared component library
- Multiple apps (web, admin, mobile-web) sharing logic
- Design system with documentation site
Setup:
bunx create-turbo@latest my-monorepo# Then configure Next.js apps in apps/ directory# Install remixicon in shared UI packagesFramework Features Comparison
Section titled “Framework Features Comparison”| Feature | Next.js | Turborepo | RemixIcon |
|---|---|---|---|
| Primary Use | Web framework | Build system | UI icons |
| Best For | SSR/SSG apps | Monorepos | Consistent iconography |
| Performance | Built-in optimization | Caching & parallel tasks | Lightweight fonts/SVG |
| TypeScript | Full support | Full support | Type definitions available |
Quick Start
Section titled “Quick Start”Next.js Application
Section titled “Next.js Application”# Create new projectbunx create-next-app@latest my-appcd my-app
# Install RemixIconbun install remixicon
# Import in layout# app/layout.tsximport 'remixicon/fonts/remixicon.css'
# Start developmentbun run devTurborepo Monorepo
Section titled “Turborepo Monorepo”# Create monorepobunx create-turbo@latest my-monorepocd my-monorepo
# Structure:# apps/web/ - Next.js application# apps/docs/ - Documentation site# packages/ui/ - Shared components with RemixIcon# packages/config/ - Shared configs# turbo.json - Pipeline configuration
# Run all appsbun run dev
# Build all packagesbun run buildRemixIcon Integration
Section titled “RemixIcon Integration”// Webfont (HTML/CSS)<i className="ri-home-line"></i><i className="ri-search-fill ri-2x"></i>
// React componentimport { RiHomeLine, RiSearchFill } from "@remixicon/react"<RiHomeLine size={24} /><RiSearchFill size={32} color="blue" />Reference Navigation
Section titled “Reference Navigation”Next.js References:
- App Router Architecture (
./references/nextjs-app-router.md) - Routing, layouts, pages, parallel routes - Server Components (
./references/nextjs-server-components.md) - RSC patterns, client vs server, streaming - Data Fetching (
./references/nextjs-data-fetching.md) - fetch API, caching, revalidation, loading states - Optimization (
./references/nextjs-optimization.md) - Images, fonts, scripts, bundle analysis, PPR
Turborepo References:
- Setup & Configuration (
./references/turborepo-setup.md) - Installation, workspace config, package structure - Task Pipelines (
./references/turborepo-pipelines.md) - Dependencies, parallel execution, task ordering - Caching Strategies (
./references/turborepo-caching.md) - Local cache, remote cache, cache invalidation
RemixIcon References:
- Integration Guide (
./references/remix-icon-integration.md) - Installation, usage, customization, accessibility
Deployment References:
- Cloudflare Pages Deploy Gotchas (
./references/cloudflare-pages-deploy.md) - EXISTING Pages projects only (new work uses Workers, see devops:deploy); Access.pages.devcoverage, reservedASSETSbinding, committed configvars(a legacywranglerconfig is not viable:wrangleris RETIRED — the studio never runs it, and the repo’s cf-only guard blocks it; see thedevops:deployreference above)
Common Patterns & Workflows
Section titled “Common Patterns & Workflows”Full patterns and workflows (CI/CD, auth, API, state management): see references/patterns-and-workflows.md.
Utility Scripts
Section titled “Utility Scripts”Python utilities in scripts/ directory:
nextjs_init.py - Initialize Next.js project with best practices turborepo_migrate.py - Convert existing monorepo to Turborepo
Usage examples:
# Initialize new Next.js app with TypeScript and recommended setuppython scripts/nextjs_init.py --name my-app --typescript --app-router
# Migrate existing monorepo to Turborepo with dry-runpython scripts/turborepo_migrate.py --path ./my-monorepo --dry-run
# Run testscd scripts/testspytestBest Practices
Section titled “Best Practices”Next.js:
- Default to Server Components, use Client Components only when needed
- Implement proper loading and error states
- Use Image component for automatic optimization
- Set proper metadata for SEO
- Leverage caching strategies (force-cache, revalidate, no-store)
Turborepo:
- Structure monorepo with clear separation (apps/, packages/)
- Define task dependencies correctly (^build for topological)
- Configure outputs for proper caching
- Enable remote caching for team collaboration
- Use filters to run tasks on changed packages only
RemixIcon:
- Use line style for minimal interfaces, fill for emphasis
- Maintain 24x24 grid alignment for crisp rendering
- Provide aria-labels for accessibility
- Use currentColor for flexible theming
- Prefer webfonts for multiple icons, SVG for single icons
Resources
Section titled “Resources”- Next.js: https://nextjs.org/docs/llms.txt
- Turborepo: https://turborepo.dev/docs
- RemixIcon: https://remixicon.com
Implementation Checklist
Section titled “Implementation Checklist”Full implementation checklist: see references/implementation-checklist.md.
Hard rules
Section titled “Hard rules”- App Router soft navs silently become full document reloads in production — render-time
useSearchParams()(prerender bailout), first query-onlyrouter.replaceon a static page, and iframes under a suspendeduseSearchParams()are the four triggers; none reproduce innext dev. Seereferences/nextjs-app-router.md→ “Production-Only Hard-Reload Triggers”. - SvelteKit
+page.server.ts↔+page.tsconfusion — server-only is.server.ts; client-shared is.ts. Mixing leaks server data to bundle. - Cloudflare Access on a Pages custom domain does NOT gate the default
<project>.pages.devURL — the admin shell loads there unauthenticated; add.pages.dev(or*.pages.dev) to the SAME Access app. Also:ASSETSis a reserved Pages binding name (useGAME_ASSETS/etc.), and dashboard-set env vars are wiped on the next legacy Pages deploy (declare them in the committed configvars— a legacywranglerconfig is not viable,wrangleris RETIRED andcf-only-guardblocks it;cf pages deploycannot ship a legacy Pages project: GAP). Both surface only at deploy/runtime, not typecheck. Seereferences/cloudflare-pages-deploy.md.