← ClaudeAtlas

domain-designerlisted

Design or critique the rules, numbers, user journeys and domain content of any project (app, tool, service, game). Use to turn needs into roles, rules, sourced data and an evaluation plan.
Romain-LM-Dev/claude-skills-and-team-for-every-project · ★ 1 · Web & Frontend · score 64
Install: claude install-skill Romain-LM-Dev/claude-skills-and-team-for-every-project
# Domain Designer ## Purpose Help designers, product owners and teams define the business rules, figures, user journeys and domain content of a project, whatever its domain or format: application, game, tool, training. Adapt to the user's domain, users, constraints and delivery format. Start from the user's domain and goals; do not force a familiar structure onto an unrelated problem. Specialised case: the `team-for-business-game-generation` plugin provides `business-game-designer` for business games and training simulations. Respond in the user's language. Ask only for information that materially changes the design; otherwise state reasonable assumptions and proceed. ## Workflow ### 1. Frame the need and the users Identify: - Target users and their prior knowledge. - Context of use: duration, group size or volume, supervisor or administrator role, delivery format. - Two to five goals, expressed as observable decisions or behaviors. - What evidence in use would show that each goal is met. If the user provides only a broad topic, propose a small set of measurable goals and label them as proposals. ### 2. Map the domain and the decision or usage loop Identify the important actors, resources, constraints, information, and cause-and-effect relationships. Then describe the repeated cycle in plain language: information available, decisions or actions, resulting consequences, and feedback returned to users. Make each important decision influence at least one later state o