AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
NextPressKit is an open-source full-stack starter kit with a Go backend and a modern web frontend.
Developer toolsTypeScript · CSSGitHub @nextpresskitOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
A modern open-source starter kit combining React.js and TanStack Start to help you build scalable web apps faster.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
NextPressKit is a PN Scripts product (product page): a starter kit for building modern web apps using TanStack Start, Tailwind CSS, and Shadcn UI.
The goal of this project is to give developers a strong starting point they can clone and build on, with common product needs already in place: authentication handling, blog post creation flows, and an administration area.
• Website: nextpresskit.com
• Backend API repository: nextpresskit/backendRead the full README ↗NextPressKit is a PN Scripts product (product page): a starter kit for building modern web apps using TanStack Start, Tailwind CSS, and Shadcn UI.
The goal of this project is to give developers a strong starting point they can clone and build on, with common product needs already in place: authentication handling, blog post creation flows, and an administration area.
This repository uses Bun only (lockfile bun.lock; CI pins Bun 1.3.9). Do not use npm, pnpm or yarn here: they would create a second lockfile. Install-script permissions live in package.json trustedDependencies (esbuild, lightningcss). Dependencies are pinned to exact versions or caret ranges, never latest.
Install dependencies and run the app locally:
bun install --frozen-lockfile
bun dev
Imports from src/ use the #/ alias only (package.json imports and tsconfig.json paths), for example import { Button } from "#/components/ui/button".
This is a one time setup to create certificates for the development server. If you don't have mkcert installed, you can install it with:
For Mac OS:
brew install mkcert
For Windows:
choco install mkcert
For Linux:
sudo apt install mkcert
Then run the following commands to create the certificates:
mkcert -install
mkcert localhost
The development server runs on https://localhost:3000.
bun --bun run dev
bun --bun run build
bun --bun run preview
bun --bun run test
bun --bun run lint
bun --bun run format
bun --bun run check
NextPressKit frontend is designed to work with the backend API project:
The app talks to the backend through VITE_API_URL (see .env.example):
cp .env.example .env.local # then edit VITE_API_URL if needed
VITE_API_URL falls back to http://localhost:9090, the backend's default APP_PORT.JWT_AUTH_SOURCE=cookie). Add this app's origin to the backend's CORS_ORIGINS (for example CORS_ORIGINS=http://127.0.0.1:3000,http://localhost:3000).POST /auth/login, POST /auth/logout, POST /auth/refresh, GET /auth/me.GET /admin/posts (+ GET|PUT|DELETE /admin/posts/{id}, PUT /admin/posts/{id}/seo) and GET /admin/users (backend permission users:read, granted to the admin role by the backend seed). Backend response shapes are mapped to the admin view models in one place, src/services/admin/adapters.ts.VITE_SITE_URL is this app's public origin; share tags such as og:image are built as absolute URLs from it (development default http://localhost:3000; production omits og:image until it is set).Sample blog covers and shop images in public/demo/ are abstract SVGs drawn by scripts/generate-demo-images.mjs (no photos, no third-party assets; same licence as this repository). Regenerate with bun scripts/generate-demo-images.mjs.
This project includes ParaglideJS for localized routing and message formatting.
messages/ (messages/{locale}.json, configured in project.inlang/settings.json).src/paraglide outputs.Use the latest Shadcn CLI to add components:
bunx --bun shadcn@latest add button