client-server-responsibility-splitter
Purpose
Decide which responsibilities belong on the client and which belong on the server including validation, orchestration, rendering, and persistence.
Expected inputs
- feature scope
- existing routes or pages
- data inputs/outputs
- constraints or stack context
Deliverables
- structured recommendation
- design notes
- risks or gaps
- recommended next artifact
Trigger this skill when
- You are designing or reviewing a web feature rather than a generic backend-only function.
- Request flow, form handling, rendering, state, or navigation decisions materially affect correctness.
- A feature needs clearer boundaries between route handling, server logic, and presentation.
Operating procedure
- Clarify the feature, request path, actors, and current or intended flow.
- Separate facts, assumptions, constraints, and unresolved web-specific risks.
- Prefer concrete request/response behavior over abstract framework talk.
- Explicitly handle invalid, missing, unauthorized, and degraded states where relevant.
- Recommend the next most useful web engineering or testing skill.
Quality gates
- The recommendation respects actual web request boundaries and browser behavior.
- Missing and invalid states are not ignored.
- Assumptions and unresolved decisions are visible.
- Output is specific enough to influence implementation or testing.
Output style
- Be concrete and structured.
- Separate findings, assumptions, and recommendations.
- Prefer explicit tradeoffs over single-answer absolutism.
- Use severity or priority where useful.
Failure modes to avoid
- Do not rely on client-side behavior as the only safeguard.
- Do not blur controller, rendering, validation, and persistence responsibilities.
- Do not describe happy-path behavior only.
- Do not hide uncertainty behind framework-specific jargon.
Minimum output skeleton
## Summary
## Findings or proposal
## Evidence vs assumptions
## Risks or tradeoffs
## Recommended next skill
Handoff targets
- mvc-boundary-checker
- session-state-strategy-reviewer
- progressive-enhancement-reviewer