Document the FC onboarding workflow state machine and access control gates.
npx skills add https://github.com/jj8127/Appointment-Process --skill fc-workflow
Please help me install this Agent Skill. Skill: fc-workflow Source: https://github.com/jj8127/Appointment-Process/tree/main/.claude/skills/fc-workflow Command: npx skills add https://github.com/jj8127/Appointment-Process --skill fc-workflow
This skill provides a clear blueprint for FC onboarding workflow and state management, helping admins and developers coordinate roles, permissions, and status transitions in a structured way.
Explain the FC onboarding workflow, its state transitions, and how identity and phone verification gates control UI access.
High-intent search queries and answers about installing and using this skill.
The workflow uses a state machine tracking transitions: draft → temp_id_issued → consent_approved → docs_approved → appointed → completed. This structured progression ensures each onboarding phase is validated before moving forward.
Identity and phone verification gates control UI access by checking identity_completed and phone_verified statuses. These gates restrict screen access and feature availability until the FC successfully passes the required verification steps.
The FC onboarding state management references core data tables including fc_profiles, fc_identity_secure, and fc_credentials. These tables store the necessary fields for tracking onboarding progress, identity data, and access credentials.
Admins have full permissions to approve onboarding steps, while Manager accounts are restricted to a read-only mode. FCs progress through the onboarding steps based on these role-based access control rules.
You can implement UI gating logic by referencing app/index.tsx and app/identity.tsx. These components provide the implementation reference for screen access control and feature availability based on the workflow state definitions.
Yes, the FC onboarding workflow blueprint provides a clear structure for coordinating roles, permissions, and status transitions. It satisfies requirements for workflow state definitions, access rules, and UI gating suitable for structured implementations.
windyskyEstablish domain UI/UX foundations with design tokens and theming for React and Vue.
orthogonal-shVerify identities and screen AML risks via the Didit API.
caffeinelabsApprove or reject user access requests to control application functionality.
Venkateshvenki404224Generate state machine logic for Frappe DocTypes with transition validation and hooks.
