Pipeline run
25c3b6e4-7473-441e-a1fa-506408b58b20
Client output enrichment
v2 Skill cluster · Nature of work · AI index · Tech stack maturity · Evidence · KRA descriptionvocab breakdown (legacy)
Signals
Post-classification
Captured for admin review
1 POST /skills/extract-from-jd
2 POST /skills/extract-details
3 POST /skills/final-role-output
Frontend Engineer
CASE Aslug: frontend-engineer · id: 7 · source: db
The primary skills strongly align with the responsibilities of a Frontend Engineer.
Resolution:
in_db
— role exists in library; skill↔dim and role↔dim links saved when applicable.
Job description
Frontend Engineer — Job Description Job Title: Frontend Engineer Experience: 4+ Years Location: Remote / Hybrid / Onsite About the Role We are seeking a talented Frontend Engineer to build modern, scalable, and high-performing web applications. The ideal candidate should have strong expertise in frontend technologies, responsive design, and performance optimization while collaborating closely with product, design, and backend teams. Key Responsibilities Develop and maintain user-facing features for web applications Collaborate with UI/UX designers to translate designs into responsive interfaces Ensure technical feasibility of UI/UX designs Write reusable, scalable, and maintainable frontend code Optimize applications for maximum speed and scalability Ensure cross-browser compatibility and responsive behavior across devices Work closely with backend engineers for API integrations Improve SEO performance and web analytics implementation Break down business requirements into smaller technical features and tasks Participate in code reviews and frontend architecture discussions Requirements and Qualifications • Bachelor’s or master degree in engineering • 4+ years of work experience. • Proficient understanding of HTML, CSS, and Javascript • Proficient understanding of ReactJs or similar library • Good understanding of responsive web development • Good understanding of SEO and analytics • Ability to break the business problem into smaller features • Ability to access the technical feasibility of UI/UX designs • Build reusable code and libraries for future use • Optimize application for maximum speed and scalability • Proficient understanding of cross-browser compatibility
Skills from this JD
Each row merges API 1 extraction, API 2 library match / v3 orchestration (dimensions + locked dims), and API 3 persistence tags.
Skill enrichment (orchestrator / LLM)
UI/UX appears in a large share of product/design job descriptions across industries and is a standard hiring requirement, with strong demand on major job boards and design-tool ecosystems.
(0.90)
UI/UX is a fairly specific domain term; typical JDs won’t confuse it with other distinct catalog skills.
Not versioned
Domain ·ui_ux_design confidence 0.96
UI/UX is a vertical body of knowledge about designing user interfaces and experiences, so it fits the Domain type rather than a tool, framework, or methodology.
- Category
- Domain
- Sub-category
- ui_ux_design
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Version strategy
- NOT_APPLICABLE
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
Locked dimensions (v3 placement)
-
UI and UX Design
Pipeline tentative id
Designing user interfaces and shaping user experience across screens, flows, and interactions. This fits UI/UX because it covers how products look, feel, and behave from the user's perspective.
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- API (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Concept
- Sub-category
- Application Programming Interface
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: APIs are a core requirement in most software engineering JDs and underpin common integrations across cloud, mobile, and web stacks; major vendors like AWS, Stripe, and Google Cloud center products on API-first usage.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 2
- Sub-category id
- 1174
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
API Integration and Data Fetching Catalog dimension db id 127
Library dimension (catalog)
Roles linked in library: Frontend Engineer, Full Stack Engineer
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved |
Aliases — catalog
- SEO (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Domain
- Sub-category
- Search Engine Optimization
- Confidence
- 0.98
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: SEO appears in large volumes of marketing, content, and growth job descriptions across industries; Google Search Central and major CMS vendors continue to publish active guidance, indicating broad ongoing demand.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 37
- Sub-category id
- 1251
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Web Analytics (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- Domain
- Sub-category
- Web Analytics
- Confidence
- 0.93
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Web analytics is a common requirement in marketing, product, and e-commerce JDs, with tools like GA4, Adobe Analytics, and Tag Manager widely listed across roles.
Skill profile (library / DB)
- Skill nature
- CONCEPT
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 37
- Sub-category id
- 1252
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Aliases — catalog
- Code Review (CANONICAL)
Context tags (catalog)
Stored enrichment (catalog DB)
- Category
- SoftSkill
- Sub-category
- Code Review
- Confidence
- 0.96
- Version strategy
- NOT_APPLICABLE
Maturity reasoning: Code review is a standard hiring-pipeline requirement in engineering JDs and is built into major platforms like GitHub/GitLab pull-request workflows, indicating broad adoption.
Skill profile (library / DB)
- Skill nature
- PRACTICE
- Volatility
- STABLE
- Typical lifespan
- EVERGREEN
- Category id
- 58
- Sub-category id
- 364
- Extractable
- True
- Also category
- False
Dimensions (API 2 worklist)
-
React Frontend Development Catalog dimension db id 96
Library dimension (catalog)
API 3 link attempts (this skill)
| Dimension | Skill↔dim | Role↔dim | Outcome |
|---|---|---|---|
|
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
All API 3 persistence rows
Same grid as the skill-extractor “Persistence items” table: one row per (skill × dimension) work item.
| Skill | Tag | Dimension | Skill↔dim | Role↔dim | Outcome | Notes |
|---|---|---|---|---|---|---|
| API | in_db |
API Integration and Data Fetching
api-integration-and-data-fetching
|
✓ | ✓ | Existing dimension (library) · Role↔dimension saved | |
| SEO | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Web Analytics | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| Code Review | in_db |
React Frontend Development
d_init_01
|
✓ | — | Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) | |
| UI/UX | in_db |
React Frontend Development
d_init_01
|
✓ | — | New skill saved · Existing dimension (library) · Role↔dimension skipped (dimension not under chosen role) |
Library artifacts (this run)
| Kind | Detail | DB id |
|---|---|---|
| canonical_skill_added | UI/UX | 1662 |
| dimension_skill_link | UI/UX ↔ React Frontend Development | 96 |
nano JD Parser — gpt-4.1-nano click to toggle
Show raw JSON
{
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"SaaS",
"Software Products"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Engineering",
"raw": "Bachelor\u2019s or master degree in engineering",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 4,
"raw": "4+ Years"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "hybrid"
}
],
"role": "Frontend Engineer",
"role_aliases": [
"Frontend Developer",
"UI Engineer",
"Web Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Develop and maintain user-facing features",
"last_5_words": "frontend architecture discussions"
},
"text": "Develop and maintain user-facing features for web applications\nCollaborate with UI/UX designers to translate designs into responsive interfaces\nEnsure technical feasibility of UI/UX designs\nWrite reusable, scalable, and maintainable frontend code\nOptimize applications for maximum speed and scalability\nEnsure cross-browser compatibility and responsive behavior across devices\nWork closely with backend engineers for API integrations\nImprove SEO performance and web analytics implementation\nBreak down business requirements into smaller technical features and tasks\nParticipate in code reviews and frontend architecture discussions",
"word_count": 109
}
],
"urls": []
}
API 1 — extract-from-jd click to toggle
{
"final_skills": [
{
"is_primary": true,
"skill_name": "UI/UX"
},
{
"is_primary": true,
"skill_name": "API"
},
{
"is_primary": true,
"skill_name": "SEO"
},
{
"is_primary": true,
"skill_name": "Web Analytics"
},
{
"is_primary": true,
"skill_name": "Code Review"
}
],
"jd_role": {
"display_name": "Frontend Engineer",
"rationale": null,
"role_aliases": [
"Frontend Developer",
"UI Engineer",
"Web Developer"
],
"role_archetype": "Engineering",
"slug": ""
},
"nano_parsed": {
"JD_type": "pass",
"about_company": null,
"certifications": [],
"company_name": null,
"ctc": null,
"domain": {
"primary": {
"aliases": [
"SaaS",
"Software Products"
],
"domain": "Software \u0026 SaaS Products"
},
"secondary": null
},
"education": [
{
"level": "Bachelor\u0027s",
"qualification": "BTECH/BE - Engineering",
"raw": "Bachelor\u2019s or master degree in engineering",
"requirement": "required"
}
],
"experience": {
"max": null,
"min": 4,
"raw": "4+ Years"
},
"job_locations": [
{
"aliases": [],
"city": null,
"country": null,
"state": null,
"work_mode": "hybrid"
}
],
"role": "Frontend Engineer",
"role_aliases": [
"Frontend Developer",
"UI Engineer",
"Web Developer"
],
"role_archetype": "Engineering",
"roles_and_responsibilities": [
{
"bullet_count": 10,
"heading": "Key Responsibilities",
"heading_was_present": true,
"source_marker": {
"first_5_words": "Develop and maintain user-facing features",
"last_5_words": "frontend architecture discussions"
},
"text": "Develop and maintain user-facing features for web applications\nCollaborate with UI/UX designers to translate designs into responsive interfaces\nEnsure technical feasibility of UI/UX designs\nWrite reusable, scalable, and maintainable frontend code\nOptimize applications for maximum speed and scalability\nEnsure cross-browser compatibility and responsive behavior across devices\nWork closely with backend engineers for API integrations\nImprove SEO performance and web analytics implementation\nBreak down business requirements into smaller technical features and tasks\nParticipate in code reviews and frontend architecture discussions",
"word_count": 109
}
],
"urls": []
},
"rejected": false,
"rejection_reason": null,
"run_id": "25c3b6e4-7473-441e-a1fa-506408b58b20",
"stage3_signals": {
"alias_found": true,
"alias_match_roles": [
{
"display_name": "Frontend Engineer",
"matched_count": null,
"role_id": 7,
"score": 1.0,
"slug": "frontend-engineer",
"total_count": null
}
],
"kra_match_roles": [
{
"display_name": "Frontend Engineer",
"matched_count": null,
"role_id": 7,
"score": 0.4734,
"slug": "frontend-engineer",
"total_count": null
},
{
"display_name": "Data Engineer",
"matched_count": null,
"role_id": 2,
"score": 0.4058,
"slug": "data-engineer",
"total_count": null
},
{
"display_name": "DevOps Engineer",
"matched_count": null,
"role_id": 10,
"score": 0.4009,
"slug": "devops-engineer",
"total_count": null
},
{
"display_name": "Backend Engineer",
"matched_count": null,
"role_id": 1,
"score": 0.3938,
"slug": "backend-engineer",
"total_count": null
},
{
"display_name": "Full Stack Engineer",
"matched_count": null,
"role_id": 15,
"score": 0.3618,
"slug": "full-stack-engineer",
"total_count": null
}
],
"skill_match_roles": [
{
"display_name": "Frontend Engineer",
"matched_count": 1,
"role_id": 7,
"score": 0.2,
"slug": "frontend-engineer",
"total_count": 5
},
{
"display_name": "Full Stack Engineer",
"matched_count": 1,
"role_id": 15,
"score": 0.2,
"slug": "full-stack-engineer",
"total_count": 5
}
]
},
"stage4_decision": {
"alias_collision_detected": false,
"case": "A",
"chosen_role": {
"display_name": "Frontend Engineer",
"matched_count": null,
"role_id": 7,
"score": 1.0,
"slug": "frontend-engineer",
"total_count": null
},
"confidence": 0.4734,
"llm2_fired": false,
"llm2_reasoning": null,
"queued": false,
"reasoning": "Stage 1 title \u0027Frontend Engineer\u0027 (name match, sim 1.00); KRA agrees (0.47)"
},
"stage5_updates": {
"centroid_n_after": 17,
"centroid_updated": true,
"collision_log_id": null,
"new_kra_attached": null,
"new_skills_attached": [
{
"is_primary": true,
"queue_id": 1539,
"role_display_name": "Frontend Engineer",
"role_slug": "frontend-engineer",
"skill_name": "UI/UX",
"status": "pending"
}
],
"queue_entry_id": null,
"v3_pipeline_triggered": false,
"v3_role_slug": null,
"v3_run_id": null
}
}
API 2 — extract-details
{
"alias_matches": [
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2514,
"existing_alias_text": "API",
"input_term": "API",
"matched_canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2628,
"existing_alias_text": "SEO",
"input_term": "SEO",
"matched_canonical": {
"category_id": 37,
"display_name": "SEO",
"id": 1658,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "seo",
"sub_category_id": 1251,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 2629,
"existing_alias_text": "Web Analytics",
"input_term": "Web Analytics",
"matched_canonical": {
"category_id": 37,
"display_name": "Web Analytics",
"id": 1659,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "web-analytics",
"sub_category_id": 1252,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
},
{
"alias_persist_skipped_reason": "alias_text already exists for this canonical skill",
"alias_persisted": false,
"existing_alias_id": 864,
"existing_alias_text": "Code Review",
"input_term": "Code Review",
"matched_canonical": {
"category_id": 58,
"display_name": "Code Review",
"id": 516,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PRACTICE",
"slug": "code-review",
"sub_category_id": 364,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"matched_via": "alias"
}
],
"candidate_roles": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"chosen_role": {
"display_name": "Frontend Engineer",
"id": 7,
"rationale": "The primary skills strongly align with the responsibilities of a Frontend Engineer.",
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "SEO",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Web Analytics",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Code Review",
"llm_role": null,
"roles_from_db": []
},
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "UI/UX",
"llm_role": null,
"roles_from_db": []
}
],
"input_final_skills": [
"UI/UX",
"API",
"SEO",
"Web Analytics",
"Code Review"
],
"input_llm_skills": [
"UI/UX",
"API",
"SEO",
"Web Analytics",
"Code Review"
],
"new_aliases_persisted": 0,
"run_id": "25c3b6e4-7473-441e-a1fa-506408b58b20",
"skills_detail": [
{
"aliases_in_db": [],
"canonical": null,
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "UI/UX",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "UI/UX",
"matched_via": null,
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": {
"derived": {
"category": "Domain",
"skill_nature": "CONCEPT",
"sub_category": "ui_ux_design",
"typical_lifespan": "EVERGREEN",
"version_strategy": "NOT_APPLICABLE",
"volatility": "STABLE"
},
"enrichment": {
"ambiguity": {
"ambiguity_flag": false,
"confused_with": [],
"reasoning": "UI/UX is a fairly specific domain term; typical JDs won\u2019t confuse it with other distinct catalog skills."
},
"context_keywords": {
"context_keywords": [
"user research",
"wireframing",
"prototyping",
"usability testing",
"interaction design",
"visual hierarchy",
"information architecture",
"user personas",
"A/B testing",
"responsive design",
"design systems",
"Figma",
"Adobe XD",
"Sketch",
"user journey"
]
},
"maturity": {
"confidence": 0.93,
"maturity": "well_known",
"reasoning": "UI/UX appears in a large share of product/design job descriptions across industries and is a standard hiring requirement, with strong demand on major job boards and design-tool ecosystems."
},
"skill_id": "ui-ux",
"vendor_license": {
"confidence": 0.9,
"license": null,
"vendor": null,
"year_introduced": null
},
"versioning": {
"current_version": null,
"version_aliases": {},
"versioned": false
}
},
"keep_log": [],
"locked_dimensions": [
{
"description": "Designing user interfaces and shaping user experience across screens, flows, and interactions. This fits UI/UX because it covers how products look, feel, and behave from the user\u0027s perspective.",
"exemplar_skills": [
"UI/UX",
"wireframing",
"mockups",
"interaction design",
"information architecture",
"user flows",
"usability testing",
"accessibility"
],
"in_scope": "UI/UX, wireframes, mockups, interaction design, information architecture, user flows, usability heuristics, accessibility basics, visual hierarchy, responsive layouts, design systems",
"name": "UI and UX Design",
"out_of_scope": "CSS implementation and styling details, client routing and navigation mechanics, form validation logic, backend API integration, these belong to separate frontend engineering dimensions",
"overlap_flags": [
{
"reason": "Visual presentation and layout implementation often overlap with UI design, but this dimension focuses on styling code rather than design decisions.",
"with_dim_id": "css-architecture-and-styling",
"with_dim_name": null,
"with_role": "Frontend Engineer, Full Stack Engineer"
},
{
"reason": "Navigation structure is part of UX flows, but route implementation and URL handling belong to the routing dimension.",
"with_dim_id": "client-routing-and-navigation",
"with_dim_name": null,
"with_role": "Frontend Engineer"
},
{
"reason": "Error states and recovery flows are UX concerns, but the validation logic itself is owned by the form handling dimension.",
"with_dim_id": "form-validation-and-error-recovery",
"with_dim_name": null,
"with_role": "Frontend Engineer"
}
],
"tentative_id": "d_init_01"
}
],
"merge_log": [],
"placed": {
"name": "UI/UX",
"placement_confidence": 0.92,
"primary_dimension": "d_init_01",
"reasoning": "Deterministic JD placement: locked_dimensions has 1 dimension(s) from skill-driven dimension generation after reconciliation; primary_dimension is the first locked dim.",
"secondary_dimensions": [],
"skill_id": "ui-ux"
},
"relationships": {
"child_skills": [],
"parent_skills": [],
"related_to": [
"responsive-web-development",
"design-patterns",
"a-b-testing",
"web-analytics",
"widget-testing",
"evaluation",
"technical-writing",
"api-integration"
],
"requires": [],
"skill_id": "ui-ux",
"suppress_on_match": []
},
"skill_id": "ui-ux",
"split_log": [],
"typed": {
"alternatives_considered": [],
"confidence": 0.96,
"name": "UI/UX",
"reasoning": "UI/UX is a vertical body of knowledge about designing user interfaces and experiences, so it fits the Domain type rather than a tool, framework, or methodology.",
"skill_id": "ui-ux",
"subtype": "ui_ux_design",
"type": "Domain"
},
"warnings": []
},
"source_tag": "llm",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "API",
"alias_type": "CANONICAL",
"id": 2514,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 2,
"display_name": "API",
"id": 1568,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "api",
"sub_category_id": 1174,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"input_skill": "API",
"llm_role": null,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
]
}
],
"input_skill": "API",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "SEO",
"alias_type": "CANONICAL",
"id": 2628,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 37,
"display_name": "SEO",
"id": 1658,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "seo",
"sub_category_id": 1251,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "SEO",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "SEO",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Web Analytics",
"alias_type": "CANONICAL",
"id": 2629,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 37,
"display_name": "Web Analytics",
"id": 1659,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "CONCEPT",
"slug": "web-analytics",
"sub_category_id": 1252,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Web Analytics",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Web Analytics",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
},
{
"aliases_in_db": [
{
"alias_text": "Code Review",
"alias_type": "CANONICAL",
"id": 864,
"is_primary": false,
"match_strategy": "CASE_INSENSITIVE"
}
],
"canonical": {
"category_id": 58,
"display_name": "Code Review",
"id": 516,
"is_also_category": false,
"is_extractable": true,
"skill_nature": "PRACTICE",
"slug": "code-review",
"sub_category_id": 364,
"typical_lifespan": "EVERGREEN",
"volatility": "STABLE"
},
"dimensions": [
{
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"input_skill": "Code Review",
"llm_role": null,
"roles_from_db": []
}
],
"input_skill": "Code Review",
"matched_via": "alias",
"new_alias_persisted": false,
"new_alias_text": null,
"new_skill_meta": null,
"source_tag": "db",
"was_in_llm_skills": true
}
],
"unmatched_skills": [
"UI/UX"
]
}
API 3 — final-role-output
{
"chosen_role": {
"display_name": "Frontend Engineer",
"id": 7,
"rationale": "The primary skills strongly align with the responsibilities of a Frontend Engineer.",
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
"chosen_role_resolution": "in_db",
"final_input_skills": [
{
"skill": "UI/UX",
"tag": "new"
},
{
"skill": "API",
"tag": "in_db"
},
{
"skill": "SEO",
"tag": "in_db"
},
{
"skill": "Web Analytics",
"tag": "in_db"
},
{
"skill": "Code Review",
"tag": "in_db"
}
],
"llm_cost_api1_usd": null,
"llm_cost_api2_usd": null,
"llm_cost_api3_usd": null,
"llm_cost_total_usd": null,
"persistence": {
"items": [
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "API Integration and Data Fetching",
"id": 127,
"rationale": "Client-side integration with backend endpoints and third-party services, including request shaping, response handling, and synchronization with UI state. This is central to frontend work because most screens depend on remote data.",
"slug": "api-integration-and-data-fetching",
"source": "db"
},
"dimension_id": 127,
"input_skill": "API",
"llm_role": null,
"matched_chosen_role": true,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension saved",
"role_dimension_saved": true,
"roles_from_db": [
{
"display_name": "Frontend Engineer",
"id": 7,
"rationale": null,
"role_archetype": null,
"slug": "frontend-engineer",
"source": "db"
},
{
"display_name": "Full Stack Engineer",
"id": 15,
"rationale": null,
"role_archetype": null,
"slug": "full-stack-engineer",
"source": "db"
}
],
"skill_dimension_saved": true,
"skill_id": 1568,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "SEO",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 1658,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Web Analytics",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 1659,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "Code Review",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 516,
"skill_tag": "in_db",
"skipped_reason": null
},
{
"chosen_role_id": 7,
"dimension": {
"difficulty_hint": "well_known",
"display_name": "React Frontend Development",
"id": 96,
"rationale": "Building interactive web user interfaces with React.js, including component composition, state management, hooks, and rendering patterns. React.js belongs here because it is a core library for client-side UI development in modern web applications.",
"slug": "d_init_01",
"source": "db"
},
"dimension_id": 96,
"input_skill": "UI/UX",
"llm_role": null,
"matched_chosen_role": false,
"outcome_line": "New skill saved \u00b7 Existing dimension (library) \u00b7 Role\u2194dimension skipped (dimension not under chosen role)",
"role_dimension_saved": false,
"roles_from_db": [],
"skill_dimension_saved": true,
"skill_id": 1662,
"skill_tag": "in_db",
"skipped_reason": null
}
],
"new_skills_created": 1,
"role_dimension_saved": 0,
"skill_dimension_saved": 1,
"skipped": 0
},
"planner_output": null,
"run_id": "25c3b6e4-7473-441e-a1fa-506408b58b20"
}
LLM Calls
Every model call made for this run, in pipeline order. Click a card to see the model's response.