Open content in VS Code for interactive editing before using it in the next step.
Opens content in VS Code for user review and editing before proceeding with the next step.
npx claudepluginhub bendrucker/claudeThis skill is limited to using the following tools:
scripts/edit.test.tsscripts/edit.tsOpen content in VS Code for the user to review and edit before proceeding.
Draft the content for the user's request, then pipe it to the edit script:
printf '%s' '<content>' | bun ${CLAUDE_SKILL_ROOT}/scripts/edit.ts --ext <ext>
The script opens VS Code with --wait, blocks until the tab is closed, then prints the edited content to stdout. Use the returned content for the next step (MCP call, file write, commit message, etc.).
Pass the file path directly:
bun ${CLAUDE_SKILL_ROOT}/scripts/edit.ts <file>
VS Code opens the file with --wait. The user edits and closes the tab. No stdout — the file is modified in place.
For multi-field content (issues, PRs, specs), use YAML front matter for structured fields and the body for prose. Parse the front matter from stdout to extract fields for API requests.
| Flag | Default | Purpose |
|---|---|---|
--ext <ext> | md | File extension for temp files (determines VS Code syntax highlighting) |
--no-wait | off | Open without blocking (fire-and-forget) |
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.