User-invocable: false
npx claudepluginhub hay-kot/scaffoldThis skill inherits all available tools. When active, it can use any tool Claude has access to.
scaffoldrc-reference.mdUser-invocable: false Auto-triggerable: true
Triggers when: User asks about scaffoldrc setup, scaffold resolution, environment variables, authentication, or how scaffold finds templates.
The scaffoldrc file is resolved in this order:
--scaffoldrc CLI flagSCAFFOLDRC environment variable~/.scaffold/scaffoldrc.yml (legacy, only if it exists on disk)$XDG_CONFIG_HOME/scaffold/scaffoldrc.yml (default: ~/.config/scaffold/scaffoldrc.yml)If the file doesn't exist, it's created automatically as an empty file. An empty file is valid and uses all defaults.
Use scaffold dev migrate to move legacy ~/.scaffold/ paths to XDG locations.
When scaffold new <ref> is called, the reference resolves through:
aliases keys → replaced with alias valuegh:org/repo) expanded via scaffoldrc shorts → URL/) — joined with current working directory--scaffold-dir directories (default: .scaffold/)If resolution fails interactively, fuzzy matching runs against all known scaffolds with a "did you mean?" prompt. In --no-prompt mode, the error is returned directly.
For private repositories, configure auth in scaffoldrc. If no auth is configured and a remote requires it, the CLI prompts interactively (unless --no-prompt).
See scaffoldrc-reference.md for the auth section schema.
| Variable | Maps to | Description |
|---|---|---|
SCAFFOLDRC | --scaffoldrc | ScaffoldRC file path |
SCAFFOLD_DIR | --scaffold-dir | Template search directories |
SCAFFOLD_CACHE | --cache | Cache directory for remote scaffolds |
SCAFFOLD_LOG_LEVEL | --log-level | Log level (debug, info, warn, error) |
SCAFFOLD_SETTINGS_LOG_LEVEL | --log-level | Log level (alt) |
SCAFFOLD_SETTINGS_LOG_FILE | --log-file | Log file path |
SCAFFOLD_SETTINGS_THEME | --theme | UI theme |
SCAFFOLD_THEME | --theme | UI theme (alt) |
SCAFFOLD_SETTINGS_RUN_HOOKS | --run-hooks | Hook execution policy |
SCAFFOLD_OVERWRITE | --overwrite | Overwrite existing files |
SCAFFOLD_FORCE | --force | Allow dirty git tree |
SCAFFOLD_OUT | --output-dir | Output directory |
CLI flags take precedence over environment variables, which take precedence over scaffoldrc settings.
| Purpose | XDG Path | Legacy Path |
|---|---|---|
| ScaffoldRC | $XDG_CONFIG_HOME/scaffold/scaffoldrc.yml | ~/.scaffold/scaffoldrc.yml |
| Cache | $XDG_DATA_HOME/scaffold/templates | ~/.scaffold/cache |
Legacy paths are used if they exist. XDG defaults: ~/.config/ for config, ~/.local/share/ for data.
Remote scaffolds (URLs, shorts) are cloned to the cache directory. Use scaffold update to pull latest for all cached scaffolds. The cache directory can be overridden with --cache or SCAFFOLD_CACHE.
Expert 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.