adding-a-feature

To ensure UI and agent parity, apply a four-area checklist that synchronizes UI components, agent actions, skill documentation, and app-state navigation. This workflow guarantees end-to-end parity between UI capabilities and agent actions during feature development.

The four-area checklist is a governance workflow for feature development that requires updating UI components, defining actions, documenting skills in AGENTS.md, and syncing app-state navigation to maintain complete UI and agent parity.

Document agent behavior by adding explicit guidance in SKILL.md frontmatter and recording instructions in AGENTS.md. Alternatively, add a dedicated skill file in the .agents/skills directory with appropriate visibility settings.

No, you should avoid raw API routes. To maintain UI-agent parity, introduce and align actions using defineAction to cover both reads and writes, ensuring the UI and agent share the same action-driven state changes.

Render real-time agent-driven state changes in the UI component by using useActionQuery and useActionMutation hooks. This ensures the UI accurately reflects state updates triggered by the agent during feature operation.

When adding a new feature, update the app-state navigation state and view-screen data to reflect the new functionality. This ensures the agent and UI share synchronized navigation context and maintain end-to-end parity.