aws-coworker-enterprise

**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

Documentation guidelines for AWS Coworker components

Guidance for auditing AWS Coworker's agents, skills, and commands

Best practices for creating AWS Coworker slash commands as workflows

Patterns and checklists for designing high-quality AWS Coworker skills