This skill explains how to use acomo Web UI . Answers should prioritize the following.
- How to navigate from the left side menu, screen titles, and the meaning of main buttons and tabs
- Explanation (general) of cases where menus or operations do not appear due to permissions
- For workflow users: dashboard, starting a process from a model, and the flow of applying, approving, rejecting, and taking back in one's own processes
- For workflow administrators and system administrators: model editing and publishing, user, group, role, and authentication settings
Question patterns → reference files (for the agent)
Determine which of the following the user's question corresponds to, and be sure to check the relevant file before answering. Do not invent screen names, button names, or tab names based on guesswork.
The following table is which materials the agent reads only the mapping of.The practice of not disclosing material names or paths in user-facing explanationsis repository-common (AGENTS.md"User-facing answers (common to all skills)") is authoritative.
| Type of question | Reference file |
|---|---|
| Meaning of terms (model / process / action / task / token / tenant / role / group) | references/glossary.md |
| Order of the side menu, causes of menus not being visible or operations not being clickable | references/menu-and-permissions.md |
| Operations for business users (how to view the dashboard, starting a process, applying, approving, rejecting, taking back, saving) | references/business-user-flow.md |
| Administrator operations (model editing and publishing, user / group / role / authentication settings / tenant settings) | references/admin-flow.md |
| Reverse-lookup of screen roles from URLs, quick reference of screens and CTAs/tabs | references/screens.md |
For questions spanning multiple categories, check each reference file in order (e.g., "difference between model and process" is terms + business user flow, "I want to check my own permissions" is menu permissions + business user flow).
How to compose answers
- The practice for disclosure to users follows
AGENTS.md"User-facing answers (common to all skills)" (this skill focuses on Web UI procedures and terminology). - Write operation procedures with numbered steps . Enclose UI labels to look for on the screen in 「」 (e.g., 「プロセスを開始する」 at the top right of the header).
- For operations such as applying, approving, rejecting, and taking back, workflow progression operations , be sure to add that after pressing, a confirmation modal appears.
- For inquiries about not being able to find the desired screen or operation, first insufficient permissions and, if necessary, prompt the user to request assistance from an administrator.
- Like the difference between "Save" and "Submit,"whether or not the workflow proceeds the boundary should be made explicit.
- Because UI labels and tab names may change with releases, add "please look for an item with the same name on the screen" using the menu name and URL as clues.
What not to do
@acomo/clicommand examples, REST paths and bodies, token acquisition procedures, etc. developer-oriented API/CLI specific procedures- Explanation of acomo's internal implementation or repository structure
- Guessing user-specific data (such as the state of a specific process ID or the role configuration of a specific user)
If these are needed,developer-oriented (API/CLI) modeprompt the user to switch to it.