jason-c-dev

**AWS Coworker Development Guardrails** - MANDATORY when extending or modifying AWS Coworker itself. TRIGGERS (use this skill when ANY of these apply): - User asks to add new skills, agents, or commands to AWS Coworker - User asks to modify existing AWS Coworker components - User asks about AWS Coworker architecture or design - User wants to add support for new AWS services - Discussion involves directory structure or file organization - User mentions "extending", "customizing", or "adding to" AWS Coworker - Creating or modifying files in: skills/, .claude/agents/, .claude/commands/, config/ NOT for: Using AWS Coworker to interact with AWS (that's CLAUDE.md's domain)

Canonical AWS CLI patterns for discover, plan, deploy, validate, and rollback

AWS Well-Architected Framework alignment for planning and review

Organization governance policies - never do, always do, and compliance rules

Git and GitHub best practices for AWS Coworker change management

Multi-account and OU strategy, landing zone patterns, and workload placement

Cost-aware AWS interaction and optimization patterns

Standard patterns for CloudWatch, CloudTrail, Config, logging, and alerting

Track tasks and todos in the vault. Use when the user says 'add this to my todo', 'add this as a task', 'put this on my list', 'put this on the backlog', 'let's circle back to this later', 'don't let me forget', 'note for later', 'park this', 'we should come back to this', 'remind me to X', 'I need to do X later', or any phrase that implies queuing an action for future pickup. Also fires when the user wants to see pending tasks, check progress on multi-day work, or mark tasks complete. IMPORTANT: Do NOT fire on 'remember this', 'remember that X is Y', 'save this fact', 'store this about me' — those are memory actions, not task actions (see Task vs Memory Disambiguation below).

Wiki audit and lint — review the wiki for quality, consistency, and completeness. Use when the user says 'audit', 'lint', 'review the wiki', 'check for issues', 'check wiki health', or wants to assess the knowledge base quality. Also handles staleness checks and cross-link verification.

Wiki intake and compilation — process new content into the knowledge base. Use when the user says 'compile', 'add this to the wiki', 'process raw files', drops content in raw/, shares a URL to capture, or wants to ingest new material into the wiki. Also use when new raw files need processing or the user mentions intake, ingestion, or web clipping.

Telegram communication protocol — how to handle messages from Telegram. Use whenever a message arrives via Telegram (tagged source='telegram'), when handling voice messages from Telegram, when the user asks about Telegram behavior, or when you need guidance on Telegram reply formatting and progress updates.

Wiki compilation — spawns a subagent with fresh context to compile raw/ sources into wiki articles. Reports result to Telegram.

Memory consolidation — spawns a subagent with fresh context to review and consolidate session memories. Reports result to Telegram.