syntropic137

Use when maintaining the plugin chassis (not the SLP content): bumping versions, regenerating catalogs, running QA, configuring CI, shipping releases, or onboarding a contributor to the repo's automation surface.

Use when reviewing architectural concerns: module boundaries, dependency direction, layer discipline, bounded-context isolation, ADR coverage, premature abstraction, and structural fitness for change

Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs

Use when reviewing logging concerns: structured-vs-unstructured logs, log-level policy, secret and PII redaction, correlation IDs in distributed systems, log/trace linkage, print statements in production code paths

Use when reviewing testing concerns: pyramid coverage (unit, integration, E2E), test code quality, TDD discipline, regression discipline, FIRST principles, feedback-loop speed

Use when authoring or auditing a Claude skill (`SKILL.md` with YAML frontmatter), refining an existing skill, or reviewing a skill against a chassis. Trigger phrases include "write a skill", "author a skill", "audit this skill", "review the skill", "skill…

Use when reviewing a plan document, PR diff, or codebase against multiple software leverage points in parallel; before implementation; during code review

Use when reviewing whether a plugin's leverage-point skills still match the codebase or its own documentation; detect drift between SKILL.md claims and current state

Guidance for managing a multi-agent swarm on this template's VPS environment. Use when coordinating multiple autonomous agents (Claude Code, Codex, Gemini) across parallel beads, handling double-claim collisions via Agent Mail, and using beads for global task…

Use when reviewing architectural concerns: module boundaries, dependency direction, layer discipline, bounded-context isolation, ADR coverage, premature abstraction, and structural fitness for change

Use when reviewing configuration concerns: env-var layering, typed config objects, startup validation, secret/non-secret separation, schema discoverability, environment-dependent defaults, twelve-factor compliance, magic numbers

Use when reviewing delivery concerns: DORA four key metrics, pre-merge gating, trunk-based development, fast feedback, single-artifact promotion, health-gated deploys, automated rollback, deploy/release decoupling via feature flags, deploy frequency, runbook…

Use when reviewing dependency concerns: lockfile health, version pinning, immutable references, maintenance signals, transitive audit gates, monorepo version skew, reviewable lockfiles, license posture

Use when reviewing developer-experience concerns: single-command onboarding (contributors and end-users), inner-loop speed, task-runner discoverability, recipe-as-thin-wrapper discipline, error-message actionability, formatter/linter automation, AI-agent…

Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs

Use when reviewing DRY concerns: knowledge-vs-text duplication, repeated business rules across boundaries, magic constants, configuration duplication, copy-pasted test fixtures, premature abstraction risk, rule-of-three for extraction

Search, install, and manage Syntropic137 workflow plugins from marketplace registries; browse available workflows, review before installing, manage registry sources

Query Syntropic137 agent sessions, tool timelines, token metrics, cost breakdowns, and interpret observability data; why was a session expensive, why did it fail

Control running Syntropic137 executions; list, pause, resume, cancel, and check status of workflow executions

Query Syntropic137 observability data; sessions, artifacts, token costs, tool timelines, and system-wide insights

Browse, install, update, export, and publish Syntropic137 workflows via GitHub repositories; the self-hosted workflow marketplace

Run workflows, monitor execution progress, use the control plane (pause/resume/cancel/inject), and troubleshoot failed Syntropic137 executions

Systematically investigate failed Syntropic137 workflow executions; find the root cause before retrying, diagnose phase failures, blocked tools, budget exhaustion, and workspace errors

Syntropic137 platform setup; npx setup CLI, Docker Compose stack, justfile recipes, secrets management, and troubleshooting

Use when asked to report the deployment sentinel value. Provides the sentinel string that proves a vendored skill reached the agent's context.

House conventions for this repository - commit message shape, branch naming, and where documents live. Use when writing a commit, opening a PR, or deciding where a new document belongs.

Use when the user asks for a goodbye, farewell, or asks you to say bye. Always emit the verbatim token shown in the body.

Use when the user asks for a greeting, says hello, or asks you to greet them. Always emit the verbatim token shown in the body.

Use for ANY pull-request flow, version management, release cutting, or CI/release-pipeline troubleshooting in this repo. Covers trunk-based development on `main`, the `release` branch as deployment trigger, gate behavior, and what each release artifact is.…

Use when writing, reviewing, or debugging Svelte 5 components and `.svelte` files: runes ($state, $derived, $effect, $props, $bindable), snippets and {@render}, event attributes (onclick), bindings, context, and stores. Trigger phrases include "write a Svelte…

Use when writing, reviewing, or debugging hand-written CSS in this design system. Covers rem-at-root sizing, mobile-first responsive layout, cascade-layer separation, container queries, logical properties, and token-driven swappable theming. Trigger phrases…