aizxz-ai/splicing

★ 1TypeScriptAudience · developerComplexity · 2/5ActiveSetup · easy

Mindmap

mindmap
  root((Splicing))
    Inputs
      Image uploads
      User routes
    Outputs
      Stitched images
      JSON API responses
    Use Cases
      Image stitching demo
      Next.js starter
      shadcn UI scaffold
    Tech Stack
      Next.js
      shadcn
      Tailwind
      TypeScript
      Radix

mindmap root((Splicing)) Inputs Image uploads User routes Outputs Stitched images JSON API responses Use Cases Image stitching demo Next.js starter shadcn UI scaffold Tech Stack Next.js shadcn Tailwind TypeScript Radix

Things people build with this

USE CASE 1

Use the repo as a Next.js 16 plus shadcn/ui starter

USE CASE 2

Add static and dynamic routes following the README conventions

USE CASE 3

Build JSON API endpoints inside the app router

USE CASE 4

Build forms with react-hook-form and zod validation

Tech stack

Next.jsshadcn/uiTailwindTypeScriptRadix

Getting it running

Difficulty · easy Time to first run · 5min

Only pnpm is allowed; the preinstall script rejects npm or yarn.

In plain English

Splicing is described in the README as an image stitching tool, written in TypeScript. The repository is small and the README is a Chinese-language developer guide rather than a user-facing tour. It frames the project as a full-stack application built on top of two existing tools: Next.js 16, which is a popular framework for building websites, and shadcn/ui, which is a collection of pre-made interface pieces like buttons, cards, and dialogs. Most of the README is a quick-start and a set of house rules for anyone working on the code. It tells contributors to run "pnpm dev" to launch a local development server at port 3000, "pnpm build" to make a production version, and "pnpm start" to serve it. It insists that pnpm is the only allowed package manager and notes that the project is configured to reject npm or yarn through a preinstall script. The guide then walks through the project layout. The "src/app/" folder holds page routes, "src/components/ui/" holds the shadcn building blocks, "src/lib/" holds helper functions, and a separate "server/" folder holds a custom server entry point. Routes are added by creating new folders, and the README shows code snippets for static pages, dynamic pages with parameters, and small JSON API endpoints. The rest of the document covers conventions: build interfaces by composing shadcn components rather than starting from scratch, use Tailwind CSS v4 classes for styling, use react-hook-form together with zod for form validation, and prefer fetching data in server components when possible. A short list at the end names the stack: Next.js 16.1.1, shadcn/ui on Radix UI, Tailwind CSS v4, Lucide icons, Geist fonts, and TypeScript 5. The README does not describe the actual image-stitching feature itself, only how the project is set up.

Copy-paste prompts

Prompt 1

Clone Splicing and start the dev server with pnpm on port 3000

Prompt 2

Add a new dynamic route under src/app for stitching previews

Prompt 3

Compose a new admin page from shadcn components without any custom CSS

Prompt 4

Wire a Vitest test against the image-stitching helper in src/lib

Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.