원클릭으로 Manus에서 모든 스킬 실행

boilerplate

스타47

포크8

업데이트2026년 2월 7일 13:13

Generate project scaffolds from descriptions. Use when starting a new project, scaffolding, or creating "CLI in Go", "React app with auth", or similar from a short description.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

lvndry

lvndry/jazz

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Boilerplate

Generate minimal project scaffolds from short descriptions. Turn "CLI in Go with cobra" or "React app with auth" into a runnable structure with the right files and commands.

When to Use

User wants to start a new project from a description
User asks for a scaffold, boilerplate, or starter
User says "create a X that does Y" and expects a project layout

Workflow

Parse request: Language, framework, key features (auth, DB, API, CLI)
Choose stack: Specific tools (e.g. cobra for Go CLI, Vite+React for frontend)
Design layout: Directories, main entry, config, README
Generate: Minimal files to run (main, config, one example)
Ask for clarifications, personalisation if needed

Scaffold Rules

Minimal: Only what's needed to run and one clear path (e.g. one command, one route).
Conventional: Standard layout (e.g. cmd/ for Go, src/ for TS/JS).
Runnable: User can install deps and run with 1–2 commands.
Documented: README with install, run, and (if applicable) env vars.

README for Scaffolds

# [Project Name]

[One-line description]

## Setup

\`\`\`bash
[install deps: npm install, go mod download, etc.]
\`\`\`

## Run

\`\`\`bash
[npm run dev, go run ., etc.]
\`\`\`

## [Optional: Env / Config]

What to Generate

Always: Entry point, dependency file (package.json, go.mod, Cargo.toml, etc.), README
When relevant: Config (e.g. .env.example), one test, .gitignore
Avoid: Full app logic; keep to minimal “hello world” or one feature

Ambiguity

If the request is vague:

Pick one reasonable stack and say what you chose: "Using Vite + React; say if you want Next.js instead."
Default to TypeScript for Node/React unless they say "JavaScript".

Anti-Patterns

❌ Huge template with many options; keep it small
❌ Unrunnable (missing deps, wrong paths)
❌ No README or run instructions
❌ Over-engineered (e.g. full DDD for a tiny CLI)

이 저장소의 다른 Skills

같은 저장소

github-action

lvndry/jazz

Set up Jazz as a GitHub Action for automated PR code review and on-demand /jazz PR assistance. Use when the user asks to add Jazz to CI, create a GitHub Action workflow, set up PR review automation, enable /jazz commands on PRs, or integrate Jazz with GitHub. Triggers on "github action", "github actions", "ci", "pr review", "pr assistant", "jazz in ci", "/jazz".

2026-06-1947

defuddle

lvndry/jazz

Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

2026-03-0147

obsidian

lvndry/jazz

Use the official Obsidian CLI (v1.12+) to manage vaults, notes, daily notes, search, tasks, tags, properties, links, templates, sync, publish, and workspaces. Use when the user mentions Obsidian, vaults, notes, or wants to automate note-taking and knowledge base workflows.

2026-03-0147

persona

lvndry/jazz

Help users create, manage, and refine custom personas for Jazz agents. Use when the user wants to define a new communication style, character, or identity for an agent.

2026-02-1847

skill-creator

lvndry/jazz

Create new Jazz skills for automating workflows. Use when the user asks to create a skill, make a skill, or wants to define custom automation behavior.

2026-02-1747

todo

lvndry/jazz

Create and track task lists for complex multi-step work. Use when planning projects, breaking down work, tracking progress, or when a task has 3+ steps. Triggers on "plan", "todo", "task list", "break down", "step by step", or complex requests requiring multiple actions.

2026-02-1747

Boilerplate

Generate minimal project scaffolds from short descriptions. Turn "CLI in Go with cobra" or "React app with auth" into a runnable structure with the right files and commands.

When to Use

User wants to start a new project from a description

User asks for a scaffold, boilerplate, or starter

User says "create a X that does Y" and expects a project layout

Workflow

Parse request: Language, framework, key features (auth, DB, API, CLI)

Choose stack: Specific tools (e.g. cobra for Go CLI, Vite+React for frontend)

Design layout: Directories, main entry, config, README

Generate: Minimal files to run (main, config, one example)

Ask for clarifications, personalisation if needed

Scaffold Rules

Minimal: Only what's needed to run and one clear path (e.g. one command, one route).

Conventional: Standard layout (e.g. cmd/ for Go, src/ for TS/JS).

Runnable: User can install deps and run with 1–2 commands.

Documented: README with install, run, and (if applicable) env vars.

README for Scaffolds

# [Project Name] [One-line description] ## Setup \`\`\`bash [install deps: npm install, go mod download, etc.] \`\`\` ## Run \`\`\`bash [npm run dev, go run ., etc.] \`\`\` ## [Optional: Env / Config]

What to Generate

Always: Entry point, dependency file (package.json, go.mod, Cargo.toml, etc.), README

When relevant: Config (e.g. .env.example), one test, .gitignore

Avoid: Full app logic; keep to minimal “hello world” or one feature

Ambiguity

If the request is vague:

Pick one reasonable stack and say what you chose: "Using Vite + React; say if you want Next.js instead."

Default to TypeScript for Node/React unless they say "JavaScript".

Anti-Patterns

❌ Huge template with many options; keep it small

❌ Unrunnable (missing deps, wrong paths)

❌ No README or run instructions

❌ Over-engineered (e.g. full DDD for a tiny CLI)

name	boilerplate
description	Generate project scaffolds from descriptions. Use when starting a new project, scaffolding, or creating "CLI in Go", "React app with auth", or similar from a short description.