tapps-domain-frontend

name	tapps-domain-frontend
description	Frontend/UX TAPPS workflow: playbook, UI library docs, and quality gate on scored files. Use when building UI components, accessibility fixes, or client-side routing changes.
mcp_tools	["tapps_session_start","tapps_domain_playbook","tapps_lookup_docs","tapps_quick_check","tapps_validate_changed","tapps_checklist","tapps_score_file"]

Domain playbook workflow — same quality gate as the standard TAPPS pipeline.

1. Session bootstrap. Call session_start() if not already called this session.
2. Load playbook. Call domain_playbook(domain="user-experience") (or read bundled checklist from the response). Follow its workflow and checklist.
3. Library docs. For each entry in lookup_hints, call lookup_docs(library=..., topic=...) before using those APIs.
4. Domain tools. Run the tools listed in recommended_tools on changed files in scope.
5. Edit loop. After each Python file change, call quick_check(file_path=...).
6. Close out. Invoke /tapps-finish-task with the task_type=frontend. Do not declare done without validate + checklist.