Loading...
Loading...
Found 11 Skills
Vue 2 项目从规范到业务开发的完整工作流程，包括创建新业务模块、开发CRUD页面、实现业务功能、遵循项目规范等。适用于开发新功能、创建新模块、实现业务需求等场景。
Systematic approach to implementing new features in the Rust memory system following project conventions. Use when adding new functionality with proper testing and documentation, maintaining code quality and test coverage.
This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It checks epic parent relationships and validates description completeness for coding assistants, developers, and stakeholders.
Embedded C Code Style Assistant, based on the code specifications of 51 MCU teaching projects. Uses snake_case as the default naming convention, with camelCase as an option. It is used to create project structures that comply with embedded development specifications, optimize code style, and provide hardware driver templates. Suitable for embedded C project development such as 51 MCU and STM32.
Guidelines for executing commands and running scripts. Follow when running shell commands, installing packages, or using project scripts.
Go implementation guide for PMA-managed service and CLI projects. Covers project layout (cmd/internal), strict linting with golangci-lint v2, database access (sqlc + pgx or GORM), HTTP patterns (stdlib + Chi or Gin), layered config with koanf, structured logging with slog, OpenTelemetry observability, and CI quality gates.
Check and configure Justfile with standard recipes for project standards
Check and configure Sentry error tracking for project standards
Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding.
Write Project Guardrails, i.e. project engineering specifications. Applicable scenarios: when you need to define frontend, backend, API, data, security, operation and maintenance, and release standards during new project launch, tech stack change, multi-team collaboration, incident review, or code specification drift.
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.