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.zipInstalls 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.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
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 deprecatedbd/cassreferences. - Stay within assigned files; reserve before edits with
ttl_seconds; release reservations on done; finish swarm work withswarm_complete. - Use
TaskCreate/TaskUpdatefor visible progress in Claude Code UI alongsidehive_*for git-backed persistence. - When
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSis enabled, preferTeammateToolfor real-time coordination andswarmmail_*for persistence. swarmmail_release_allis 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
EnterPlanModefor 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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| always-on-guidance (this skill) | 0 | 6mo | No flags | Intermediate |
| workflow-tdd-plan | 1 | 3mo | Review | Intermediate |
| bmad-agent-dev | 0 | 4mo | No flags | Advanced |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by joelhooks
View all by joelhooks →You might also like
workflow-tdd-plan
catlog22
TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, cycle tracking, and post-execution compliance verification. Triggers on "workflow:tdd-plan", "workflow:tdd-verify".
bmad-agent-dev
pplancq
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
vitest
antfu
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.