Always-on rule-oriented guidance for claude-plugin agents. Use to align behavior, tool usage, and model-specific defaults while avoiding deprecated bd/cass references. Related skills: swarm-coordination, testing-patterns.
Enforces consistent agent behavior and tool usage with model-specific defaults and coordination rules.
npx claudepluginhub joelhooks/swarm-toolsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
hive_*, swarm_*, swarmmail_*, hivemind_*); avoid deprecated bd/cass references.ttl_seconds; release reservations on done; finish swarm work with swarm_complete.TaskCreate/TaskUpdate for visible progress in Claude Code UI alongside hive_* for git-backed persistence.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is enabled, prefer TeammateTool for real-time coordination and swarmmail_* for persistence.swarmmail_release_all is coordinator-only for stale/orphaned reservations.Use model aliases (inherit, opus, sonnet, haiku) instead of version numbers.
EnterPlanMode for test-driven planning before implementation.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.