home / skills / williamzujkowski / standards / infrastructure

infrastructure skill

/skills/devops/infrastructure

This skill helps you establish secure, maintainable infrastructure practices for devops, applying patterns, testing, and observability across projects.

npx playbooks add skill williamzujkowski/standards --skill infrastructure

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.9 KB
---
name: infrastructure
description: Infrastructure standards for infrastructure in Devops environments. Covers
---

# Infrastructure

> **Quick Navigation:**
> Level 1: [Quick Start](#level-1-quick-start) (5 min) → Level 2: [Implementation](#level-2-implementation) (30 min) → Level 3: [Mastery](#level-3-mastery-resources) (Extended)

---

## Level 1: Quick Start

### Core Principles

1. **Best Practices**: Follow industry-standard patterns for devops
2. **Security First**: Implement secure defaults and validate all inputs
3. **Maintainability**: Write clean, documented, testable code
4. **Performance**: Optimize for common use cases

### Essential Checklist

- [ ] Follow established patterns for devops
- [ ] Implement proper error handling
- [ ] Add comprehensive logging
- [ ] Write unit and integration tests
- [ ] Document public interfaces

### Quick Links to Level 2

- [Core Concepts](#core-concepts)
- [Implementation Patterns](#implementation-patterns)
- [Common Pitfalls](#common-pitfalls)

---

## Level 2: Implementation

### Core Concepts

This skill covers essential practices for devops.

**Key areas include:**

- Architecture patterns
- Implementation best practices
- Testing strategies
- Performance optimization

### Implementation Patterns

Apply these patterns when working with devops:

1. **Pattern Selection**: Choose appropriate patterns for your use case
2. **Error Handling**: Implement comprehensive error recovery
3. **Monitoring**: Add observability hooks for production

### Common Pitfalls

Avoid these common mistakes:

- Skipping validation of inputs
- Ignoring edge cases
- Missing test coverage
- Poor documentation

---

## Level 3: Mastery Resources

### Reference Materials

- [Related Standards](../../docs/standards/)
- [Best Practices Guide](../../docs/guides/)

### Templates

See the `templates/` directory for starter configurations.

### External Resources

Consult official documentation and community best practices for devops.

Overview

This skill defines infrastructure standards for DevOps environments to get projects production-ready fast. It provides battle-tested patterns, secure defaults, and checklists to start any project correctly. The guidance emphasizes maintainability, security, testing, and performance so teams can deliver reliable systems.

How this skill works

The skill inspects common infrastructure concerns and prescribes concrete patterns for architecture, error handling, observability, and testing. It provides a short quick-start checklist, implementation patterns, and links to templates and reference materials. Use the guidance to validate designs, add required hooks (logging, monitoring, retries), and avoid common pitfalls.

When to use it

  • Bootstrapping a new DevOps or infrastructure project
  • Designing system architecture or selecting deployment patterns
  • Adding or auditing production readiness features (monitoring, logging, retries)
  • Preparing infrastructure for security review or compliance
  • Creating templates and starter configurations for teams

Best practices

  • Adopt secure defaults and validate all inputs at boundaries
  • Choose architecture patterns that match scale and failure characteristics
  • Implement comprehensive error handling and graceful recovery
  • Instrument systems with observability hooks before production launch
  • Write unit and integration tests for infrastructure code and document public interfaces

Example use cases

  • Create a starter repo with templates for CI/CD, IaC, and monitoring integrations
  • Perform a production-readiness audit using the essential checklist
  • Design retry and backoff strategies and add centralized error handling
  • Integrate structured logging and metrics to improve debugging and SLO tracking
  • Standardize testing and documentation practices across multiple services

FAQ

How long does it take to apply the quick-start checklist?

The quick-start level is designed to be actionable in about five minutes to set core guardrails and a 30-minute follow-up for implementation basics.

Does this skill include code templates?

Yes. It points to a templates directory with starter configurations for CI/CD and infrastructure patterns, plus links to deeper references and best-practice guides.