Nextjs Nextra Starter Distill

Community

pdsuwwz

nextjs-nextra-starter-distill

Distill and apply this repository's Next.js Nextra starter architecture, implemented features, extension points, and migration patterns. Use when Codex needs to understand this project, continue second-stage development, add or change docs/landing/i18n/theme/auth/UI behavior, or reuse these Next.js 16 + Nextra 4 + Tailwind CSS 4 patterns in another project.

Overview

Publisher	pdsuwwz
Repository	`nextjs-nextra-starter`
Skill name	`nextjs-nextra-starter-distill`
Stars	318
Forks	54
Bundled files	6
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
6 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by pdsuwwz on GitHub. Read the source before you install it.

Installation

Install the Nextjs Nextra Starter Distill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/pdsuwwz/nextjs-nextra-starter/tree/main/.agents/skills/nextjs-nextra-starter-distill
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/pdsuwwz/nextjs-nextra-starter/tree/main/.agents/skills/nextjs-nextra-starter-distill

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/pdsuwwz/nextjs-nextra-starter.git /tmp/nextjs-nextra-starter
mkdir -p .claude/skills
cp -r /tmp/nextjs-nextra-starter/.agents/skills/nextjs-nextra-starter-distill .claude/skills/nextjs-nextra-starter-distill

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Nextjs Nextra Starter Distill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Nextjs Nextra Starter Distill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Nextjs Nextra Starter Distill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Next.js Nextra Starter Distill

Use this project-local Skill to understand, extend, or selectively migrate the nextjs-nextra-starter implementation. Treat the reference files as distilled guidance, then inspect the current source before editing because the repository may have changed.

Reference Router

Architecture or ownership questions: read references/architecture.md.
Feature inventory or product capability questions: read references/feature-map.md.
Implementation pattern reuse questions: read references/implementation-patterns.md.
Second-stage development tasks in this repo: read references/extension-guide.md.
Borrowing these patterns in another repo: read references/migration-notes.md.

Read only the references needed for the user request. Load multiple files when a task crosses boundaries, such as adding a localized landing page section.

Workflow

Classify the request as understanding, extension, migration, or review.
Read the relevant reference file(s).
Inspect live source paths cited by the references before making claims or edits.
Preserve the Nextra, locale, theme, and MDX integration points unless the user asks to replace them.
Treat the current auth flow as a front-end demo unless real backend/session code has been added.
For runtime changes, verify with the narrowest useful command, usually pnpm lint or pnpm build.

Operating Notes

This starter combines docs, product landing pages, i18n, theme controls, and UI primitives. Avoid treating it as a generic Next.js app.
The src/content/zh and src/content/en trees are content sources, while src/i18n stores reusable UI copy.
_meta.tsx files control Nextra navigation and page-level layout behavior.
Client widgets often adapt Nextra-rendered DOM. Recheck selectors when upgrading Nextra.
Do not copy demo auth, placeholder analytics, static metadata, or product copy into production without replacing them.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
references/architecture.md4 KB
references/extension-guide.md5 KB
references/feature-map.md4 KB
references/implementation-patterns.md4 KB
references/migration-notes.md3 KB

Frequently asked questions

What does the Nextjs Nextra Starter Distill AI skill do?

Why use Nextjs Nextra Starter Distill on TypingMind?

Because you install it once and use it with any model. Nextjs Nextra Starter Distill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Nextjs Nextra Starter Distill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pdsuwwz/nextjs-nextra-starter/tree/main/.agents/skills/nextjs-nextra-starter-distill. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Nextjs Nextra Starter Distill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Nextjs Nextra Starter Distill?

As many as you like. As long as a model supports skills, you can use Nextjs Nextra Starter Distill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Nextjs Nextra Starter Distill AI skill free?

Yes. It is published on GitHub by pdsuwwz under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Ui Styling

nextlevelbuilder

OrganizationPopular

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user…

Landing Report

Read-only queue dashboard for workspace-aware ship. (gstack)

Gstack Openclaw Ceo Review

garrytan

CommunityPopular

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

Caveman Stats

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Next.js Nextra Starter Distill

Reference Router

Workflow

Operating Notes

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now