From wolfram-hart
This skill should be used when the user asks to "configure Wolfram settings", "change Wolfram mode", or invokes /wolfram-hart:setup directly. It manages per-project wolfram-hart settings.
npx claudepluginhub james-traina/science-plugins --plugin wolfram-hartThis skill is limited to using the following tools:
Manage per-project wolfram-hart settings stored in `.claude/wolfram-hart.local.md`.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Manage per-project wolfram-hart settings stored in .claude/wolfram-hart.local.md.
If $ARGUMENTS is reset:
Delete .claude/wolfram-hart.local.md if it exists and recreate with defaults below.
If .claude/wolfram-hart.local.md does not exist (or argument is reset):
Create it with these defaults:
---
wolfram_mode: auto
default_timeout: 30
---
Tell the user:
.claude/wolfram-hart.local.mdwolfram_mode: auto (tries local, falls back to cloud), local, or clouddefault_timeout: seconds before computation times out (default 30)WOLFRAM_MODE, WOLFRAM_TIMEOUT) override these settingsIf .claude/wolfram-hart.local.md already exists (and argument is not reset):
Read the file using the Read tool and display the current settings in a readable format.
If $ARGUMENTS is show, stop after displaying.
Otherwise, ask which setting the user wants to change.
Editing settings: Use the Edit tool to modify individual YAML fields in the frontmatter. After editing, remind the user to restart Claude Code for changes to take effect.