Backend Architecture
Software development skill, available on Zeplik
Backend Architecture is a ready-to-run software development skill on Zeplik. Not for whole-system design docs (use system-design) or service decomposition (use microservices-patterns). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The Backend Architecture skill loads automatically when your request matches it, or you can invoke it directly by typing /backend-architecture in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Backend Architecture skill can do
- Design clean, hexagonal, and DDD-layered service architectures
- Scaffold CQRS, event sourcing, and projection based read models
- Model sagas and durable Temporal workflows with state and determinism
- Apply language specific backend patterns for Go, Rust, C#, and Bash
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Backend Architecture skill works
/backend-architecture
Umbrella skill for designing and implementing backend services: architecture patterns (clean, hexagonal, DDD), CQRS and event sourcing, sagas and durable workflow orchestration, API scaffolding, and language-specific backend patterns in Go, Rust, C#/.NET, and shell. The body is a dispatch table; the depth lives in references/. Pick the matching reference(s), read them, then answer. This lane covers the internals of services and their patterns -- a whole-system design document belongs to system-design, and carving a monolith into services belongs to microservices-patterns.
Dispatch table
| Intent | Reference |
|---|---|
| FastAPI project scaffolding, async patterns, dependency injection | references/fastapi-templates.md (+ --details) |
| Clean / hexagonal architecture, DDD layering in services | references/architecture-patterns.md (+ --details, --advanced-patterns) |
| CQRS: separating read and write models | references/cqrs-implementation.md (+ --details) |
| Event store design, event sourcing infrastructure | references/event-store-design.md (+ --details) |
| Read models, projections, materialized views from event streams | references/projection-patterns.md (+ --details) |
| Sagas, distributed transactions, cross-aggregate workflows | references/saga-orchestration.md (+ --details, --advanced-patterns) |
| Testing Temporal workflows: pytest, time-skipping, replay | references/temporal-python-testing.md (+ --unit-testing, --integration-testing, --replay-testing, --local-setup) |
| Durable workflow design with Temporal, determinism, state | references/workflow-orchestration-patterns.md (+ --details) |
| C#/.NET backend patterns, EF Core, Dapper, DI | references/dotnet-backend-patterns.md (+ --ef-core-best-practices, --dapper-patterns) |
| Defensive Bash for production scripts and pipelines | references/bash-defensive-patterns.md (+ --details) |
| Bats testing for shell scripts | references/bats-testing-patterns.md (+ --details) |
| ShellCheck configuration and shell script linting | references/shellcheck-configuration.md (+ --details) |
| Go concurrency: goroutines, channels, worker pools, context | references/go-concurrency-patterns.md (+ --details) |
| Memory safety: RAII, ownership, smart pointers (Rust/C++/C) | references/memory-safety-patterns.md (+ --details) |
| Async Rust with Tokio, async traits, concurrent patterns | references/rust-async-patterns.md (+ --details) |
How to work
- Read the matching reference file(s) before answering; load the
--companion files when the base reference points to them. - If the language, framework, or persistence layer is ambiguous (for example "add CQRS" without knowing the stack, or "orchestrate this workflow" without knowing whether Temporal is in play), ask ONE clarifying question before designing.
- Produce concrete artifacts: layered project skeletons, aggregate and event definitions, saga step tables, full code in the user's language. When validation needs the user's environment, walk them through what to run and ask them to paste results back.
- Combine references when a design spans patterns -- an event-sourced service typically needs event-store-design plus projection-patterns plus cqrs-implementation.
- Redirect out-of-lane asks: full-system design documents go to system-design; deciding service boundaries and decomposition goes to microservices-patterns.
Usage
/backend-architecture $ARGUMENTS
How to use the Backend Architecture skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Backend Architecture skill right away.
Describe your software development task
Ask in plain language, or type /backend-architecture to invoke the skill directly. Zeplik recognizes the Backend Architecture skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- anthropic
- License
- MIT
Adapted from the open-source wshobson/agents project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Backend Architecture skill?
- Backend Architecture is a ready-to-run software development skill on Zeplik. Not for whole-system design docs (use system-design) or service decomposition (use microservices-patterns). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use Backend Architecture on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /backend-architecture in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Backend Architecture skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Backend Architecture skill runs on your preferred model for the task.
- Where does the Backend Architecture skill come from?
- The Backend Architecture skill is adapted from the open-source wshobson/agents project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Backend Architecture skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related software development skills
- .NET BackendBuild ASP.NET Core 8+ backends with EF Core: auth, background jobs, production API patterns
- Advanced Git WorkflowsUse for advanced Git surgery: interactive rebase, cherry-pick, bisect, reflog recovery, and history cleanup before merging. Not for parallel worktree workflows (use using-git-worktrees).
- Adversarial Code ReviewHunt for bugs in code the user shares by assuming defects exist and attacking the code through several distinct lenses, then report severity-ranked findings with evidence. Use for "review this", "what could go wrong", "bug hunt", or pre-merge scrutiny of a change. Read-only, it reports problems and does not rewrite the code. Not for style cleanup (use simplify-code) or for writing new code.
- AI Agent FrameworksUse when building multi-agent systems or agent orchestration -- LangChain/LangGraph, agent team design, task coordination, pipelines. Not for authoring a Zeplik skill (use skill-creator).
- Algolia SearchAdd Algolia search: indexing strategies, React InstantSearch, relevance tuning, search-as-you-type
- Android CI/CDAutomate Android CI/CD to Google Play: keystore, GitHub Secrets, multi-stage release workflow for RN, Flutter, native
More on Zeplik
Try Backend Architecture on Zeplik
Every model, one chat. Bring the Backend Architecture skill into your next conversation and let the assistant do the work.