๐Ÿ“ฆ

next

์ฝ˜ํ…์ธ  ๋ฆฌ๋น„์ „ r1 ์•ˆ์ „ โš™๏ธ ์™ธ๋ถ€ ๋ช…๋ น์–ด

Build Next.js Apps from JSON Specifications

Connecting JSON specifications to Next.js routes, layouts, and server rendering requires several integration steps. This skill guides AI assistants through the documented json-render setup.

์ง€์›: Claude Codex Code(CC)
Maintain this Skill? Claim it ๐Ÿฅ‰ 78 ๋ธŒ๋ก ์ฆˆ

๋‚ด ์—์ด์ „ํŠธ๋กœ ์„ค์น˜

์ด ์š”์ฒญ์„ ์—์ด์ „ํŠธ์— ๋ณต์‚ฌํ•˜์„ธ์š”. ๊ณต์‹ Skill ํŽ˜์ด์ง€์™€ ๋งค๋‹ˆํŽ˜์ŠคํŠธ๊ฐ€ ํฌํ•จ๋˜์–ด ์žˆ์Šต๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ ์š”์ฒญ
Review the Skillstore skill "next" from https://skillstore.io/skills/vercel-labs-next.md and its manifest at https://skillstore.io/api/skills/vercel-labs-next/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

์—์ด์ „ํŠธ๋Š” ๊ณ„์†ํ•ด์„œ ๊ณ„ํš์„ ํ‘œ์‹œํ•˜๊ณ  ๋ณด์•ˆ ์ •์ฑ…์—์„œ ์š”๊ตฌํ•˜๋Š” ํ™•์ธ์„ ์š”์ฒญํ•ด์•ผ ํ•ฉ๋‹ˆ๋‹ค.

์—์ด์ „ํŠธ๊ฐ€ ์ฝ๊ธฐ ์‰ฌ์šด ๋ฆฌ์†Œ์Šค

AI ์—์ด์ „ํŠธ, ํฌ๋กค๋Ÿฌ, ์Šคํฌ๋ฆฝํŠธ๊ฐ€ ์ „์ฒด ํŽ˜์ด์ง€ ๋Œ€์‹  ์ •๋ฆฌ๋œ ์ปจํ…์ŠคํŠธ๋งŒ ํ•„์š”ํ•  ๋•Œ ์ด ๋งํฌ๋ฅผ ์‚ฌ์šฉํ•˜์„ธ์š”.

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"next" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Outline a home and about application with a shared layout.

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • The specification defines home and about routes with separate page titles.
  • Both routes reference one layout containing navigation and a Slot for page content.
  • The component registry must supply the custom components used by the specification.

"next" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Explain how a dynamic blog page loads data before rendering.

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • The dynamic route uses a slug segment to identify the requested page.
  • An asynchronous server loader retrieves the post and returns page state.
  • The server component runs loaders and generates metadata before passing the resolved specification to the client renderer.
  • The application must implement its data access function and choose which fields may reach the client.

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „

All 40 static findings are false positives caused by Markdown fences or inline code formatting, not Ruby or shell backtick execution. The source documents routine dependency installation and Next.js integration examples. No evidence found of prompt injection, credential theft, or malicious data transfer; dependency implementations were not included in this review.

1
์Šค์บ”๋œ ํŒŒ์ผ
195
๋ถ„์„๋œ ์ค„ ์ˆ˜
0
๊ฒ€ํ†  ํ•ญ๋ชฉ
0
์˜คํƒ ๋ฌด์‹œ๋จ
๊ฐ€์žฅ ์ตœ๊ทผ์— ์™„๋ฃŒ๋œ ์ •์ ยท์˜๋ฏธ๋ก ์  ๊ฐ์‚ฌ์—์„œ ํ™•์ธ๋œ ๋ณด์•ˆ ๋ฐœ๊ฒฌ ์‚ฌํ•ญ์ด ๊ฐ์ง€๋˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค. ์ด๋Š” ์Šคํ‚ฌ์— ๋ถ€์ž‘์šฉ์ด ์—†์Œ์„ ์ฆ๋ช…ํ•˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค.
๊ฐ์‚ฌ์ž: codex
์ด ๋ณด๊ณ ์„œ ๊ณต์œ  ๋ฐ ์ธ์šฉ

๋ฒ„์ „์ด ์ง€์ •๋œ ํ‰๊ฐ€ ๋ณด๊ณ ์„œ, ์ค‘๋ฆฝ ๋ฐฐ์ง€, ์ž„๋ฒ ๋“œ ์นด๋“œ ๋ฐ ์ธ์šฉ์„ ๊ณต์œ ํ•˜์„ธ์š”. Skillstore๋Š” ๊ทผ๊ฑฐ๋ฅผ ๋ณด๊ณ ํ•˜์ง€๋งŒ ์ด Skill์˜ ์•ˆ์ „ ์—ฌ๋ถ€๋ฅผ ํŒ๋‹จํ•˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค.

๋ฒ„์ „๋ณ„ ๋ณด๊ณ ์„œ ์—ด๊ธฐ
๋ณด์•ˆ ํ‰๊ฐ€

๋ณด๊ณ ์„œ ๋งํฌ ๋ณต์‚ฌ

https://skillstore.io/skills/vercel-labs-next/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown ๋ฐฐ์ง€

[![Skillstore security assessment](https://skillstore.io/badges/skills/vercel-labs-next/security.svg)](https://skillstore.io/skills/vercel-labs-next?utm_source=security_passport_badge)

HTML ๋ฐฐ์ง€

<a href="https://skillstore.io/skills/vercel-labs-next?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/vercel-labs-next/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

์ž„๋ฒ ๋“œ ์นด๋“œ

<iframe src="https://skillstore.io/embed/skills/vercel-labs-next.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
ํ•™์ˆ  ์ธ์šฉ (APA ยท BibTeX ยท CFF)

APA ์ธ์šฉ

vercel-labs. (2026). next security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/vercel-labs-next/audits/1

BibTeX ์ธ์šฉ

@techreport{vercel-labs-vercel-labs-next-2026, author = {vercel-labs}, title = {next security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/vercel-labs-next/audits/1}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "next security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "vercel-labs" date-released: "2026-09-29" url: "https://skillstore.io/skills/vercel-labs-next/audits/1" identifiers: - type: other value: "skillstore:vercel-labs-next:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore ์ ์ˆ˜

์ด ์ ์ˆ˜์˜ ์ด์œ  ์ฆ๊ฑฐ ์‹ ๋ขฐ๋„: ์ค‘๊ฐ„
55
์•„ํ‚คํ…์ฒ˜
85
์œ ์ง€๋ณด์ˆ˜์„ฑ
87
์ฝ˜ํ…์ธ 
65
์ปค๋ฎค๋‹ˆํ‹ฐ
91
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Connect a JSON-driven frontend

Build shared layouts and route definitions, then connect the specification to Next.js page exports and a component registry.

Prototype multiple application pages

Translate a small application outline into JSON specifications with consistent navigation, page metadata, and shared layouts.

Integrate server-loaded page data

Plan asynchronous loaders, route matching, server rendering, and client hydration for pages backed by existing data services.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Understand the setup
Explain the minimum setup for using @json-render/next in my existing Next.js project. Identify required packages and missing application components.
Define a two-page specification
Draft a NextAppSpec for home and about pages using my existing registry. Include shared navigation, a layout Slot, and page metadata.
Connect server rendering
Integrate my specification with createNextApp and NextAppProvider. Show the catch-all route exports and identify any missing registry or handler definitions.
Review a dynamic content integration
Review my dynamic blog specification and server loader design. Check route patterns, metadata, static parameters, and layout Slots. Identify sensitive fields before client hydration.

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Include a Slot in every shared layout and verify that referenced components exist in your registry.
  • Keep server utilities and client components in their documented entry points.
  • Review loader return values for sensitive data before they become page state, and test dynamic routes in your application.

ํ”ผํ•˜๊ธฐ

  • Copying examples without implementing the referenced registry, handlers, and data access functions.
  • Defining shared layouts without a Slot for page content.
  • Assuming server-loaded data remains private after it is passed to the client renderer.

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

What does this skill provide?
It provides instructions and examples for integrating @json-render/next with a Next.js application. It does not bundle the renderer or a complete project.
Which AI tools can use it?
The marketplace lists support for Claude, Codex, and Claude Code.
What dependencies are required?
The quick start installs @json-render/core, @json-render/react, and @json-render/next. You also need a Next.js project and your application components.
Does it cover dynamic routes?
Yes. It documents static paths, dynamic segments, catch-all segments, and optional catch-all segments using Next.js route conventions.
How does server rendering work?
The documented Page component matches routes, runs server loaders, generates metadata, and passes the resolved specification to the client renderer for hydration.
Why is page content missing from my layout?
Check that the layout includes a Slot component. Also verify that the route references the intended layout and the registry supplies its custom components.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

vercel-labs

๋ผ์ด์„ ์Šค

MIT

Skillstore ๋ฆฌ๋น„์ „

r1

๋ฒ„์ „ ์•ˆ๋‚ด

์ž‘์„ฑ์ž๊ฐ€ ๋ฒ„์ „์„ ์„ ์–ธํ•˜์ง€ ์•Š์•˜์Šต๋‹ˆ๋‹ค.

์ฐธ์กฐ

bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2

์œ ์ง€๋ณด์ˆ˜ ์ตœ์‹ ์„ฑ

2026. 9. 30.

์‚ฌ์šฉ๋Ÿ‰

0 ๋‹ค์šด๋กœ๋“œ ยท 0 ์กฐํšŒ

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md