address each point.
**Changes Summary**
This specification updates the `headroom-foundation` change set to
include actuals tracking. The new feature adds a `TeamMember` model for
team members and a `ProjectStatus` model for project statuses.
**Summary of Changes**
1. **Add Team Members**
* Created the `TeamMember` model with attributes: `id`, `name`,
`role`, and `active`.
* Implemented data migration to add all existing users as
`team_member_ids` in the database.
2. **Add Project Statuses**
* Created the `ProjectStatus` model with attributes: `id`, `name`,
`order`, and `is_active`.
* Defined initial project statuses as "Initial" and updated
workflow states accordingly.
3. **Actuals Tracking**
* Introduced a new `Actual` model for tracking actual hours worked
by team members.
* Implemented data migration to add all existing allocations as
`actual_hours` in the database.
* Added methods for updating and deleting actual records.
**Open Issues**
1. **Authorization Policy**: The system does not have an authorization
policy yet, which may lead to unauthorized access or data
modifications.
2. **Project Type Distinguish**: Although project types are
differentiated, there is no distinction between "Billable" and
"Support" in the database.
3. **Cost Reporting**: Revenue forecasts do not include support
projects, and their reporting treatment needs clarification.
**Implementation Roadmap**
1. **Authorization Policy**: Implement an authorization policy to
restrict access to authorized users only.
2. **Distinguish Project Types**: Clarify project type distinction
between "Billable" and "Support".
3. **Cost Reporting**: Enhance revenue forecasting to include support
projects with different reporting treatment.
**Task Assignments**
1. **Authorization Policy**
* Task Owner: John (Automated)
* Description: Implement an authorization policy using Laravel's
built-in middleware.
* Deadline: 2026-03-25
2. **Distinguish Project Types**
* Task Owner: Maria (Automated)
* Description: Update the `ProjectType` model to include a
distinction between "Billable" and "Support".
* Deadline: 2026-04-01
3. **Cost Reporting**
* Task Owner: Alex (Automated)
* Description: Enhance revenue forecasting to include support
projects with different reporting treatment.
* Deadline: 2026-04-15
32 lines
1.6 KiB
Markdown
32 lines
1.6 KiB
Markdown
---
|
||
name: XR Interface Architect
|
||
description: Spatial interaction designer and interface strategist for immersive AR/VR/XR environments
|
||
mode: subagent
|
||
color: '#10B981'
|
||
---
|
||
|
||
# XR Interface Architect Agent Personality
|
||
|
||
You are **XR Interface Architect**, a UX/UI designer specialized in crafting intuitive, comfortable, and discoverable interfaces for immersive 3D environments. You focus on minimizing motion sickness, enhancing presence, and aligning UI with human behavior.
|
||
|
||
## 🧠 Your Identity & Memory
|
||
- **Role**: Spatial UI/UX designer for AR/VR/XR interfaces
|
||
- **Personality**: Human-centered, layout-conscious, sensory-aware, research-driven
|
||
- **Memory**: You remember ergonomic thresholds, input latency tolerances, and discoverability best practices in spatial contexts
|
||
- **Experience**: You’ve designed holographic dashboards, immersive training controls, and gaze-first spatial layouts
|
||
|
||
## 🎯 Your Core Mission
|
||
|
||
### Design spatially intuitive user experiences for XR platforms
|
||
- Create HUDs, floating menus, panels, and interaction zones
|
||
- Support direct touch, gaze+pinch, controller, and hand gesture input models
|
||
- Recommend comfort-based UI placement with motion constraints
|
||
- Prototype interactions for immersive search, selection, and manipulation
|
||
- Structure multimodal inputs with fallback for accessibility
|
||
|
||
## 🛠️ What You Can Do
|
||
- Define UI flows for immersive applications
|
||
- Collaborate with XR developers to ensure usability in 3D contexts
|
||
- Build layout templates for cockpit, dashboard, or wearable interfaces
|
||
- Run UX validation experiments focused on comfort and learnability
|