devops-platform-patterns

Name: devops-platform-patterns
Author: majesticlabs-dev

github.com/majesticlabs-devCloud & DevOps5065 installsUpdated 7w ago

About devops-platform-patterns

DevOps Platform Patterns is a reference skill with verification checklists and infrastructure practices for DigitalOcean, Hetzner, AWS, and Cloudflare. It helps developers review infrastructure code against platform-specific and cross-platform checks.

Key features

01DigitalOcean infrastructure checks
02Hetzner infrastructure checks
03AWS security and configuration checks
04Cloudflare protection checks
05Cross-platform infrastructure checks

Use cases

01Reviewing Terraform for DigitalOcean deployments
02Checking network and firewall setup on Hetzner
03Auditing AWS IAM, encryption, and logging
04Verifying Cloudflare API token and SSL settings

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill devops-platform-patterns

After installing, type/devops-platform-patternsin Claude Code to confirm it loaded.

Details

From the project README

DevOps Platform Patterns

Platform-specific verification checklists for infrastructure code.

DigitalOcean

Check	Pass	Fail
VPC used for private networking	Private network configured	Public networking only
Reserved IPs for production	Static IPs assigned	Ephemeral IPs for critical services
Managed database in same region	Co-located DB	Cross-region latency
Spaces for state backend	Remote state in Spaces	Local state only
Firewall attached to all droplets	Firewall rules applied	No firewall

Best Practices:

Use digitalocean_vpc for internal communication
Attach firewalls via digitalocean_firewall with inbound rules
Store Terraform state in DigitalOcean Spaces with versioning

Hetzner

Check	Pass	Fail
Private network configured	Network created	No private networking
Firewall rules defined	Rules restrict access	Open to internet
SSH keys managed via resource	`hcloud_ssh_key` used	Keys in user_data only
Placement groups for HA	Servers distributed	Single point of failure

Best Practices:

Use hcloud_network + hcloud_network_subnet for internal traffic
Apply hcloud_firewall to all servers
Use placement groups with spread type for critical workloads

AWS

Check	Pass	Fail
VPC with private subnets	Multi-AZ VPC	Default VPC usage
Security groups least-privilege	Specific ports/IPs	0.0.0.0/0 ingress
IAM roles over access keys	Instance profiles	Hardcoded credentials
KMS encryption for data	Customer-managed keys	No encryption
CloudTrail enabled	Audit logging on	No audit trail

Best Practices:

Never use default VPC for production
Prefer aws_iam_role with instance profiles over access keys
Enable S3 bucket versioning and encryption by default
Use aws_kms_key for sensitive data encryption

Cloudflare

Check	Pass	Fail
API tokens over global key	Scoped tokens	Global API key
WAF rules configured	Protection enabled	No WAF
SSL mode is strict	Full (strict) mode	Flexible SSL
Rate limiting on endpoints	Rules applied	No rate limiting

Best Practices:

Create scoped API tokens per environment/purpose
Set SSL mode to strict for origin protection
Apply rate limiting to authentication endpoints
Enable Bot Management if available

Cross-Platform Checks

Check	Applies To	Verification
Private networking	All	Internal services not exposed
Firewall/security groups	All	Explicit allow rules only
State backend remote	All	Not in local tfstate
Encryption at rest	All	Data encrypted
Audit logging	AWS, Cloudflare	Activity tracked

Comments

Markdown supported

Details

Author: majesticlabs-dev
Repository: majesticlabs-dev/majestic-marketplace
Category: Cloud & DevOps
Installs: 65
GitHub stars: 50

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.