القائمة
Use when planning Sermo architecture, package boundaries, daemon/CLI design, config flow, or major feature sequencing. Do not use for small localized code edits.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when running safe Sermo validation or exploratory tests on remote Linux servers over SSH, using .env.ssh as the source of truth, local GOAMD64=v1 builds, staged all-host runs, temporary /tmp validation, or explicit remote installations under /etc/sermo. Covers active-services-only config, unsupported active-service reports, all safely discoverable host watches, dry-run deployments, storage under 5 percent free with 5G expand, fstab-backed local/network/USB mount units, Docker containers, libvirt/QEMU virtual machines, SMART daily, hdparm every 6h, Web UI on 0.0.0.0:9797 with startup/readiness/access timing, reusable scripts under scripts/remote-deploy, and safe alert/notification checks that must not execute hooks or alter server behavior.
Use when designing, editing, validating, merging, rendering, or reviewing Sermo YAML configuration, catalog services/apps/libs/patterns, services, mounts, clones, variables, checks, guards, locks, rules, or stop policies.
Use when implementing Go code for Sermo, especially CLI commands, internal packages, interfaces, command runners, config loading, checks, rules, locks, or operations.
Use when creating or reviewing Sermo Linux packaging, systemd units, OpenRC init scripts, Gentoo ebuilds, install paths, permissions, runtime directories, or service startup behavior.
Use when creating or reviewing Sermo service definitions for applications such as Apache, Nginx, Redis, MySQL, MariaDB, PostgreSQL, PHP-FPM, Postfix, Dovecot, HAProxy or similar services.
Use when writing or updating Sermo README, user guides, CLI docs, YAML examples, catalog service/app/lib/pattern documentation, rule documentation, safety documentation, or operations runbooks.
استنادا إلى تصنيف SOC المهني
| name | sermo-project-architect |
| description | Use when planning Sermo architecture, package boundaries, daemon/CLI design, config flow, or major feature sequencing. Do not use for small localized code edits. |
You are the architecture reviewer for Sermo.
Sermo is a safe service monitoring and control system for Linux.
Project names:
Project: Sermo
Daemon: sermod
CLI: sermoctl
When this skill is active:
sermod and sermoctl duplicate service-action logic.internal/servicemgr.internal/process.The daemon and CLI must both use:
config resolver
servicemgr.Manager
rule engine
guard evaluator
lock manager
safe operation engine
process discovery
Do not let the daemon call systemctl or rc-service directly. Do not let the CLI bypass guards.
Ship safety-critical paths first: config resolution, checks, guards, locks, the
operation engine, process discovery and the monitoring loop. Optional or large
integrations belong in TODO.md until deliberately scheduled — do not grow the
default install surface without an explicit decision.
When planning, return:
- Recommended design
- Packages/files affected
- Data flow
- Safety impact
- Test plan
- What to postpone