AL

always-on-guidance

This skill enforces team communication protocols and directives regarding model selection and testing.

Install

mkdir -p .claude/skills/always-on-guidance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8128" && unzip -o skill.zip -d .claude/skills/always-on-guidance && rm skill.zip

Installs to .claude/skills/always-on-guidance

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Always-on rule-oriented guidance for claude-plugin agents. Use to align behavior, tool usage, and model-specific defaults (GPT-5.2-code vs Opus 4.5) while avoiding deprecated bd/cass references.
194 chars · catalog descriptionno explicit “when” trigger
Intermediate

Key capabilities

  • Enforce swarm plugin tool usage
  • Manage file reservations with TTL
  • Coordinate work using TeammateTool
  • Apply model-specific output standards
  • Follow test-driven development patterns

How it works

The skill establishes a set of behavioral rules and communication protocols for agents. It mandates specific tool usage, file reservation procedures, and model-specific output styles to ensure team alignment.

Inputs & outputs

You give it
Development task
You get back
Compliant code and documentation

When to use always-on-guidance

  • Coordinate work between agent teams
  • Maintain model-specific output standards
  • Ensure test-driven development compliance
  • Safely reserve files for editing

About this skill

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.

When not to use it

  • Using deprecated bd or cass references
  • Exceeding assigned file scope
  • Speculative reasoning in Sonnet/Haiku models

Limitations

  • Requires strict adherence to swarm tool protocols
  • Dependent on team-wide adoption of rules

How it compares

It provides a strict, rule-oriented framework for agent behavior that prioritizes persistence and coordination over individual agent autonomy.

Compared to similar skills

always-on-guidance side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
always-on-guidance (this skill)06moNo flagsIntermediate
workflow-tdd-plan13moReviewIntermediate
bmad-agent-dev04moNo flagsAdvanced
python-testing-patterns772moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by joelhooks

View all by joelhooks

cli-builder

joelhooks

Guide for building TypeScript CLIs with Bun. Use when creating command-line tools, adding subcommands to existing CLIs, or building developer tooling. Covers argument parsing, subcommand patterns, output formatting, and distribution.

530

gh-issue-triage

joelhooks

GitHub issue triage workflow with contributor profile extraction. Analyze → clarify → file cells → tag → implement → credit. Captures Twitter handles for changeset acknowledgments.

13

hive-workflow

joelhooks

Issue tracking and task management using the hive system. Use when creating, updating, or managing work items. Use when you need to track bugs, features, tasks, or epics. Do NOT use for simple one-off questions or explorations.

12

learning-systems

joelhooks

Implicit feedback scoring, confidence decay, and anti-pattern detection. Use when understanding how the swarm plugin learns from outcomes, implementing learning loops, or debugging why patterns are being promoted or deprecated. Unique to opencode-swarm-plugin.

14

pr-triage

joelhooks

Context-efficient PR comment triage. Evaluate, decide, act. Fix important issues, resolve the rest silently.

12

publish-package-cicd

joelhooks

CI/CD publishing workflow for npm packages using Changesets + npm Trusted Publishers (OIDC). Use when setting up automated npm publishing for monorepos, configuring GitHub Actions for releases, troubleshooting workspace:* protocol resolution issues, fixing "Cannot find module" errors in published packages, or debugging npm OIDC authentication. Covers Bun + Turborepo + Changesets + npm Trusted Publishers with workspace protocol resolution.

14

Search skills

Search the agent skills registry