BKUI 快速入门

Standardize frontend team onboarding to the BKUI knowledge base and workflows.

839|261|Updated Apr 18, 2019
One-click install
npx skills add https://github.com/TencentBlueKing/bk-bcs --skill bkui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: BKUI 快速入门
Source: https://github.com/TencentBlueKing/bk-bcs/tree/main/bcs-services/bcs-project-manager/.cursor/skills/bkui-quick-start
Command: npx skills add https://github.com/TencentBlueKing/bk-bcs --skill bkui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

这项 Skill 为前端团队提供一个统一的 BKUI知识库入口和标准化的工作流程,以降低学习成本并提升协作效率。

Core Features & Use Cases

  • 标准化的起步指南、组件命名规范、导航布局示例
  • 提供可用资源入口,例如 references 目录中的技能索引与组件清单
  • 用例:新成员通过 BKUI 快速定位规范并了解工作流

Quick Start

Open the BKUI Quick Start guide to learn the standardized components, navigation patterns, and onboarding workflow.

Frequently Asked Questions about BKUI 快速入门

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize frontend onboarding workflows for a new project?

Standardize frontend onboarding workflows by applying a centralized knowledge base entry point with norms, indexes, and step-by-step processes. This reduces learning costs for new members and enforces metadata completeness for project discovery.

What is the best way to establish frontend component naming conventions?

Establish frontend component naming conventions by accessing a standardized knowledge base that provides guiding workflows, navigation layout examples, and component indexes to unify team development specifications.

How does a centralized knowledge base entry point improve frontend collaboration?

A centralized knowledge base entry point improves frontend collaboration by providing a single source of truth for onboarding guidelines, component indexes, and workflows, ensuring all team members follow unified standards and reducing misalignment.

Do I need specific dependencies to implement a standardized frontend onboarding workflow?

No specific dependencies are required to implement a standardized frontend onboarding workflow. The system operates independently with references and components to define norms, indexes, and processes for frontend project teams.

Can I use this onboarding workflow for existing frontend projects seeking centralized norms?

Yes, you can apply this onboarding workflow to existing frontend projects seeking centralized norms. It serves as a unified entry point to standardize component naming, navigation layouts, and step-by-step development processes.

What limitations exist when enforcing metadata completeness for frontend project discovery?

Limitations include the strict enforcement of required metadata fields like name and description, meaning projects lacking complete information cannot be discovered, and optional resources such as references and assets must be manually defined.