User-invocable: true
npx claudepluginhub hay-kot/scaffoldThis skill inherits all available tools. When active, it can use any tool Claude has access to.
cli-reference.mdvariable-syntax.mdUser-invocable: true Auto-triggerable: true
Triggers when: User wants to run a scaffold, generate a project, create files from a template, or use the scaffold CLI.
scaffold list --json
Lists all scaffolds: aliases (from scaffoldrc), local (in .scaffold/), and system (cached remote repos). Use --json for programmatic output.
scaffold inspect <name-or-path>
Outputs JSON with questions (name, type, default, options), presets, computed values, features, and messages. Use this to understand what variables a scaffold expects.
scaffold new <scaffold>
Launches an interactive prompt for project name and all questions. The scaffold argument can be:
gh:org/repo)https://github.com/org/repo)--scaffold-dir directories, default .scaffold/)scaffold new --no-prompt --preset <preset-name> <scaffold> [key=value ...]
Use --no-prompt to skip all interactive prompts. Provide variables via:
--preset <name> — loads a named preset from the scaffold's configkey[:type]=value arguments — override or supplement preset valuesCLI arguments take precedence over preset values.
If no Project variable is set in non-interactive mode, a random name scaffold-test-NNNN is auto-generated.
scaffold new --dry-run --no-prompt --preset default <scaffold>
Renders the scaffold fully but writes nothing to disk. Outputs JSON:
{
"files": [{ "path": "path/to/file", "action": "create" }],
"errors": [],
"warnings": []
}
scaffold new --output-dir :memory: --no-prompt --preset default --snapshot stdout <scaffold>
Renders entirely in memory and outputs a full AST with file contents to stdout. Ideal for CI/CD validation and diffing.
Variables use key[:type]=value syntax. See variable-syntax.md for the full type reference.
Common examples:
scaffold new --no-prompt my-scaffold \
Project=MyApp \
description="A web service" \
port:int=8080 \
debug:bool=true \
features:[]string=auth,api
scaffold new| Flag | Default | Description |
|---|---|---|
--no-prompt | false | Disable interactive prompts |
--preset | — | Preset name for variable values |
--output-dir | . | Output directory (:memory: for in-memory) |
--dry-run | false | Show what would be created (JSON) |
--snapshot | — | Output AST to path or stdout |
--overwrite | false | Overwrite existing files |
--force | true | Allow dirty git working tree |
scaffold inspect first to understand a scaffold's variables and presets--dry-run before real runs to verify output paths--output-dir :memory: with --snapshot stdout for zero-disk testing--no-prompt is active, hooks with run_hooks=prompt are skipped--no-prompt modeExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.