How this skill is triggered — by the user, by Claude, or both
Slash command
/arato-simulate:setup-appThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Walk the user through onboarding a new application for simulation testing. This is a sequential, multi-step process.
Walk the user through onboarding a new application for simulation testing. This is a sequential, multi-step process.
Create the application. Ask for the app name and URL. Call create_application to create it.
Generate the application brief. Call regenerate_brief to auto-analyze the chat interface. The brief defines what should be tested and why. Wait for generation to complete, then call get_brief to show the result. Ask if the user wants to refine it — if so, use comment_on_brief with their feedback, then regenerate_brief again.
Generate virtual users. Call generate_virtual_users to create AI personas that will test the chat. These personas are based on the brief. Show the generated users with list_virtual_users.
Review available skills. Call list_skills to show testing capabilities (security checks, compliance rules, custom validations). Help the user understand which skills are relevant for their application.
Run the first simulation. Call list_test_suites to find the right suite, then launch_run to start. Suggest starting with a small run (1–3 parallel conversations) for the first test.
npx claudepluginhub aratoai/claude-code-plugin --plugin arato-simulateProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.