skills/context/SKILL.md
Load relevant ADRs, patterns, and memory before implementation
npx skillsauth add petcom/ai_team_config contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pre-implementation context loading. Combines ADR lookup, pattern loading, and memory recall.
/context # Auto-detect work type from conversation
/context quick # Quick orientation (memory + recent activity only)
/context new-endpoint # Explicit work type
/context certificates # Search by topic
/context quick)Fast orientation for session start or context recovery:
memory/memory-log.md for recent activitymemory/context/project-overview.mdmemory/ for keywords## Context Loaded
**Recent Activity:** [from memory-log]
**Relevant:** [matching entities/patterns]
Detect Work Type from conversation keywords: | Work Type | Keywords | |-----------|----------| | new-endpoint | route, endpoint, api, controller | | new-model | model, schema, collection, mongoose | | bug-fix | fix, bug, issue, broken, error | | auth-change | auth, permission, access, role | | testing | test, spec, vitest, coverage | | ui-component | component, widget, page, layout |
Load ADRs (max 3) from dev_communication/shared/architecture/decisions/ — decision section only, skip rationale unless requested
Load Patterns (max 4) from memory/patterns/ matching work type
Load Memory — search memory/entities/ and memory/context/ for topic keywords
Load Backend Context Packs (backend only) — if team.json indicates backend team, load relevant notes from memory/context/backend/ (for example restart checklist or backend issue snapshots)
Load Role Guidance — read the role guidance file for the active sub-team from dev_communication/shared/guidance/
Output:
## Context for: {work-type}
### ADRs
- **{ID}**: {one-line decision}
### Patterns
- **{name}**: {summary}
### Memory
- **{entity/context}**: {relevant notes}
### Role Guidance
- **{key points from role guidance}**
### Checklist
- [ ] {applicable checklist items}
Target: <2000 tokens per invocation
tools
Manage inter-team communication, issues, and coordination
testing
Manage architecture decisions, gaps, and suggestions
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------