update ui design for all pages

This commit is contained in:
2026-08-12 18:56:56 +05:30
parent 25c4ee4a6a
commit 3beb66059b
58 changed files with 7892 additions and 1891 deletions

View File

@@ -0,0 +1,27 @@
---
id: analytics-insights
name: Analytics Insights
description: Help Owliver explain the analytics shown on the current page.
pages:
- analytics
status: active
actions:
- navigate_to_analytics
---
# Analytics Insights
## Purpose
Explain the figures on the Analytics page — conversion, speed, department
performance — using the same records the page renders.
## Capabilities
- Explain hiring trend and conversion.
- Compare department performance.
- Identify where the funnel loses candidates.
## Actions
- navigate_to_analytics

View File

@@ -0,0 +1,29 @@
---
id: candidate-search
name: Candidate Search
description: Help Owliver search and summarize candidates.
pages:
- candidates
- candidates-analysis
status: active
actions:
- navigate_to_candidates
---
# Candidate Search
## Purpose
Read the candidate pipeline on the current page and answer questions about who
is waiting, who is strongest, and where screening is incomplete.
## Capabilities
- Summarize the candidate pipeline.
- Identify candidates waiting on a decision.
- Surface unscored or incomplete records.
- Compare candidates by screening score.
## Actions
- navigate_to_candidates

View File

@@ -0,0 +1,64 @@
---
id: forge-skill-management
name: Forge Skill Management
description: Create workforce skills, training and verification in KROW Forge.
pages:
- university
status: active
prompt: Create a skill
triggers:
- create a skill
- create skill
- create a new skill
- create a skill for *
- create a * skill
- new skill
- add a skill
- build a skill
- draft a skill
- create a skill training
- create skill training
- add skill training
- create training
- create a training for *
- create training for *
- create a * training
- add training
- add training to *
- build training
- write training
- create a challenge for *
- add a challenge for *
- review the * skill
- review skill
actions:
- open_create_skill_training
- open_create_training
- navigate_to_forge
---
# Forge Skill Management
## Purpose
Help an administrator build the workforce skill library: define what the
workforce must be able to do, write the training that teaches it, decide what
counts as proof, and say what the evaluation checks — using the Forge authoring
flow the page already has.
Owliver never publishes. It drafts, and hands the draft back to the existing
flow for review, which is the same rule Create Position follows.
## Capabilities
- Create workforce skills
- Create training
- Define verification
- Explain Forge skills
- Navigate Forge workflows
## Actions
- open_create_skill_training
- open_create_training
- navigate_to_forge

View File

@@ -0,0 +1,62 @@
---
id: create-position
name: Create Position
description: Create a position by answering a few questions in the chat.
pages:
- positions
status: active
prompt: Create a position
triggers:
- create a position
- create position
- create a * position
- create * position
- new position
- new * position
- post a job
- post a * job
- open a role
- open a * role
- add a position
- i want to hire
actions:
- create_position
---
# Create Position
## Purpose
Create a position without leaving the Positions page. Owliver asks for what it
does not already know, one question at a time, offers the answers as chips, then
reads the whole thing back before anything is written.
No form opens. No page is navigated to. The record created is the same
`JobPosting` the manual form writes, through the same create action.
## Capabilities
- Understand requests to create positions.
- Read the role, location, pay, experience, English level and certifications out
of a single sentence.
- Ask only for what the request did not already answer.
- Offer each answer as a suggestion, so the whole flow can be clicked.
- Read the position back for confirmation before creating it.
- Create the position on the page you are already on.
## Conversation
Each line is `field | question | suggestions | required?`. Suggestions beginning
with `@` come from the application's own data, so a role category added in the
form is offered here without this file changing.
- role_category | What role are you hiring for? | @roles | required
- location | Where will this role be based? | Chennai; Bengaluru; Coimbatore; Bay Area; Other | required
- pay | What is the pay range? | $18–$28/hr; $25–$35/hr; $30–$40/hr; Custom | required
- min_experience_years | Any minimum experience? | No minimum; 1 year; 2 years; 3+ years | optional
- english_required | What is the minimum English level? | @english | optional
- certifications_required | Any required certifications? | @certifications; None | optional
## Actions
- create_position