platform-engineer

Implements PaasFabric platform changes across Python core, Terraform provisioning, and Ansible service roles.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill platform-engineer-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-engineer
Source: https://github.com/lfuuu/claude-rules/tree/main/shared-skills/roles/platform-engineer
Command: npx skills add https://github.com/lfuuu/claude-rules --skill platform-engineer-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It enforces disciplined, architecture-compliant changes to the PaasFabric platform codebase by routing every task through defined ownership zones, mandatory patterns (Hexagonal, Strategy, Repository, Factory, DI, Specification), and a review pipeline, preventing ad-hoc edits and architectural drift. ## Core Features & Use Cases - Zone-scoped editing: Defines exactly which paths the engineer may modify (Python core, prov-driver, Terraform modules, Ansible roles, tests) and which are forbidden (infra, CI, docs). - Pattern enforcement: Requires Hexagonal dependency rules, Protocol-based ports, Specification objects for domain rules, and idempotent Ansible with handlers and check_mode support. - Service scaffolding: Provides a complete procedure to scaffold a new managed service (shims, Ansible role skeleton, playbooks, scenarios, config registration) modeled on service-compute and service-k8s. - Use Case: Ask it to add an HAQuorumSpec specification for a 3-node k8s-ha cluster; it reads the pattern docs, creates the spec with is_satisfied_by and find_violations, adds unit tests, runs ruff, and hands off to reviewer and techwriter. ## Quick Start Invoke the platform-engineer skill with a task such as adding a new domain specification or updating an Ansible role, and it will analyze, implement, verify, and route the change through review.

Frequently Asked Questions about platform-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new domain rule to a Hexagonal Python project?

Create a Specification class in the domain specifications module implementing is_satisfied_by and find_violations methods. Domain code must never import adapters or infrastructure; all external access goes through Protocol ports, with wiring done in the DI container.

How do I scaffold a new managed service with Ansible and Terraform?

Copy the shim scripts from a reference service, create a vms.d config template, build an Ansible role skeleton with defaults, tasks, and handlers, add a setup playbook, symlink shared roles, register the service in config.yaml, then delegate docs and tests to the appropriate roles.

What makes an Ansible role idempotent?

Idempotent roles use correct changed_when and failed_when conditions, support check_mode, and trigger restarts only through handlers rather than direct systemctl commands in tasks. Tags for install, configure, and verify phases make partial runs safe.

Which files should a platform engineer never edit?

Install scripts, packaging, CI workflows, hooks, and the root Makefile belong to the devops zone, and documentation belongs to the techwriter role. Terraform state files must never be committed, and the prov-driver JSON protocol cannot change without approval.

Why must domain code not import adapters in Hexagonal architecture?

The dependency rule keeps business logic independent of infrastructure so adapters can be swapped without touching the domain. Violations couple domain rules to specific technologies, breaking testability and the Strategy pattern used for provisioners and inventories.