Skill

always-on-guidance

Provides rules for Claude plugin agents on swarm tool usage, model behaviors, file reservations, task coordination, and TDD. Useful in multi-agent Claude Code workflows.

developer-tools

code-quality

From swarm

Install

Run in your terminal

npx claudepluginhub imbios/swarm-tools --plugin swarm

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

cost-optimization

1 file

Optimizes cloud costs on AWS, Azure, GCP via rightsizing, tagging strategies, reserved instances, spot usage, and spending analysis. Use for expense reduction and governance.

cloud-infrastructure

33.0k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitFeb 6, 2026

Actions

View Source View Plugin View on GitHub View README

Always-On Guidance

Global Rules

Follow instruction priority: system → developer → user → AGENTS.
Use swarm plugin tools (hive_*, swarm_*, swarmmail_*, hivemind_*); avoid deprecated bd/cass references.
Stay within assigned files; reserve before edits with ttl_seconds; release reservations on done; finish swarm work with swarm_complete.
Use TaskCreate/TaskUpdate for visible progress in Claude Code UI alongside hive_* for git-backed persistence.
When 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.
Keep outputs concise and action-oriented.

Model Defaults

Use model aliases (inherit, opus, sonnet, haiku) instead of version numbers.

Opus

Allow brief rationale (1–2 sentences) for decisions.
Use sections when work has multiple phases.
Suggest alternatives only when risk is high, then choose one.
Stay compact; avoid long exposition.

Sonnet/Haiku

Prefer strict checklists and short imperatives.
Ask a single clarifying question if blocked; otherwise proceed.
Avoid speculative reasoning; state decisions plainly.
Keep outputs minimal and non-narrative.

Testing Discipline

Use red → green → refactor when tests cover the touched area.
Use EnterPlanMode for test-driven planning before implementation.
If tests are absent or out of scope, state that explicitly.