Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

solution-architect

Étoiles5

Forks0

Mis à jour24 mai 2026 à 08:11

Solution architect for event-driven systems, distributed processes, and Event Sourcing patterns. Helps structure components using Saga, Process Manager, Choreography, and Outbox patterns.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

hpcsc

hpcsc/dotfiles

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	solution-architect
description	Solution architect for event-driven systems, distributed processes, and Event Sourcing patterns. Helps structure components using Saga, Process Manager, Choreography, and Outbox patterns.

Solution Architect

Guidance for implementing distributed processes without distributed transactions.

Quick Reference

Replace distributed transactions with local transactions + events
Each step is independently retryable and compensatable
Saga for simple workflows, Process Manager for complex state machines
Use Outbox pattern for reliable event delivery

Pattern Selection

Pattern	Best For	State
Saga	Simple workflows, most cases	Stateless
Process Manager	Complex, multi-step decisions	Stateful
Choreography	Decentralized, no coordinator	Distributed

Checklist

Before implementing:

Each operation has local transaction scope
Compensation actions defined for critical steps
Internal events separated from external events
Transient errors handled with retry policies
Dead letter queues configured

Key Anti-Patterns

Distributed Transaction: Trying ACID across services
Missing Compensation: No rollback for failures
Synchronous Dependencies: Direct service-to-service calls
Unreliable Messaging: Fire-and-forget event publishing
God Process Manager: All logic in coordinator

Common Pitfalls

Trying to coordinate distributed transactions
Publishing internal events directly to other services
Not defining compensation for all failure scenarios
Services calling each other synchronously

For Full Details

See: ~/.config/ai/guidelines/architecture/implementation/event-driven-patterns.md

Plus depuis ce dépôt

même dépôt

implement-flow

hpcsc/dotfiles

Implement a feature fully autonomously in the background as a Workflow — decompose, then run each task through test-design → implement → refactor → review → verify, closing on executed evidence instead of human approval gates. Use when you want unattended end-to-end implementation on a branch and will review the result as a diff/PR afterward.

2026-07-215

deliver-story

hpcsc/dotfiles

Deliver a large user story as multiple parallel PRs. On first run it decomposes the story into PR-sized slices with a dependency DAG (decompose-to-prs) and, after you review the plan, scaffolds a git worktree per slice and launches implement-flow in each via workmux. Re-run it to deliver later waves — it adopts the existing plan instead of re-planning. Use when a story is too big for one PR.

2026-07-215

implement-auto

hpcsc/dotfiles

Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, pausing only for plan approval and pre-commit approval.

2026-07-195

implement

hpcsc/dotfiles

Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, running independent tasks in parallel (isolated git worktrees) and pausing only for plan approval and pre-commit approval.

2026-07-195

verify-run

hpcsc/dotfiles

Post-run verification of an autonomous implementation run (implement-flow / implement-auto / implement). Runs the run-verifier agent to catch the failure modes the evidence gate can't see — staged tails, dead code, vacuous receipts, collapsed commits — and, with --fix, remediates them. Use after an unattended run, before trusting its "done".

2026-07-195

write

hpcsc/dotfiles

Write or edit an article or note. Follows writing style guidelines for clarity and consistency.

2026-07-085

name	solution-architect
description	Solution architect for event-driven systems, distributed processes, and Event Sourcing patterns. Helps structure components using Saga, Process Manager, Choreography, and Outbox patterns.

Solution Architect

Guidance for implementing distributed processes without distributed transactions.

Quick Reference

Replace distributed transactions with local transactions + events
Each step is independently retryable and compensatable
Saga for simple workflows, Process Manager for complex state machines
Use Outbox pattern for reliable event delivery

Pattern Selection

Pattern	Best For	State
Saga	Simple workflows, most cases	Stateless
Process Manager	Complex, multi-step decisions	Stateful
Choreography	Decentralized, no coordinator	Distributed

Checklist

Before implementing:

Each operation has local transaction scope
Compensation actions defined for critical steps
Internal events separated from external events
Transient errors handled with retry policies
Dead letter queues configured

Key Anti-Patterns

Distributed Transaction: Trying ACID across services
Missing Compensation: No rollback for failures
Synchronous Dependencies: Direct service-to-service calls
Unreliable Messaging: Fire-and-forget event publishing
God Process Manager: All logic in coordinator

Common Pitfalls

Trying to coordinate distributed transactions
Publishing internal events directly to other services
Not defining compensation for all failure scenarios
Services calling each other synchronously

For Full Details

See: ~/.config/ai/guidelines/architecture/implementation/event-driven-patterns.md