docs: update 194 skill files with cleaned group tags + metadata
All skill files group labels cleaned (no duplicates, no garbled text). CMS developer renamed to frontend developer in AG group. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,5 +1,6 @@
|
||||
---
|
||||
name: 安全工程师
|
||||
group: ECC组
|
||||
description: 专业应用安全工程师,专注于威胁建模、漏洞评估、安全代码审查、安全架构设计和事件响应,服务于现代 Web、API 和云原生应用。
|
||||
emoji: 🔒
|
||||
color: red
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Master REST and GraphQL API design principles to build intuitive,
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# API Design Principles
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Generate comprehensive, developer-friendly API documentation from
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# API Documentation Generator
|
||||
|
||||
@@ -4,6 +4,7 @@ description: Master API documentation with OpenAPI 3.1, AI-powered tools, and mo
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: '2026-02-27'
|
||||
group: AG组
|
||||
---
|
||||
You are an expert API documentation specialist mastering modern developer experience through comprehensive, interactive, and AI-enhanced documentation.
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@ category: development
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-03-05"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# API Endpoint Builder
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Implement secure API design patterns including authentication, aut
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# API Security Best Practices
|
||||
|
||||
@@ -5,6 +5,7 @@ category: granular-workflow-bundle
|
||||
risk: safe
|
||||
source: personal
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# API Security Testing Workflow
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are an API mocking expert specializing in realistic mock servi
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# API Mocking Framework
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Optimize end-to-end application performance with profiling, observ
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
Optimize application performance end-to-end using specialized performance and optimization agents:
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Master software architect specializing in modern architecture"
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
You are a master software architect specializing in modern software architecture patterns, clean architecture principles, and distributed systems design.
|
||||
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Comprehensive guidance for implementing asynchronous Python applic
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Async Python Patterns
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are a senior backend engineer operating production-grade servi
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Backend Development Guidelines
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Orchestrate end-to-end backend feature development from requiremen
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
Orchestrate end-to-end feature development from requirements to production deployment:
|
||||
|
||||
@@ -4,6 +4,7 @@ description: Expert in secure backend coding practices specializing in input val
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: '2026-02-27'
|
||||
group: AG组
|
||||
---
|
||||
|
||||
## Use this skill when
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Master Bash Automated Testing System (Bats) for comprehensive shel
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Bats Testing Patterns
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Frontend development patterns for React, Next.js, state management
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Frontend Development Patterns
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are a workflow automation expert specializing in creating effi
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Workflow Automation
|
||||
|
||||
@@ -5,6 +5,7 @@ category: workflow-bundle
|
||||
risk: safe
|
||||
source: personal
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Cloud/DevOps Workflow Bundle
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Comprehensive checklist for conducting thorough code reviews cover
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Code Review Checklist
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Transform code reviews from gatekeeping to knowledge sharing throu
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Code Review Excellence
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Use when working with comprehensive review full review"
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
## Use this skill when
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Master database schema and data migrations across ORMs (Sequelize,
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Database Migration
|
||||
|
||||
@@ -5,6 +5,7 @@ risk: unknown
|
||||
source: community
|
||||
tags: "database, cdc, debezium, kafka, prometheus, grafana, monitoring"
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Migration Observability and Real-time Monitoring
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "SQL database migrations with zero-downtime strategies for PostgreS
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# SQL Database Migration Strategy and Implementation
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Transform debugging from frustrating guesswork into systematic pro
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Debugging Strategies
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Use when working with debugging toolkit smart debug"
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
## Use this skill when
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Architecture patterns for multi-stage CI/CD pipelines with approva
|
||||
risk: critical
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Deployment Pipeline Design
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are a configuration management expert specializing in validati
|
||||
risk: critical
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Configuration Validation
|
||||
|
||||
@@ -10,6 +10,7 @@ date_added: "2026-04-17"
|
||||
author: Leonxlnx
|
||||
tags: [frontend, design, ui, react]
|
||||
tools: [claude, cursor, codex, antigravity]
|
||||
group: AG组
|
||||
---
|
||||
# High-Agency Frontend Skill
|
||||
|
||||
|
||||
@@ -18,6 +18,7 @@ tools:
|
||||
- cursor
|
||||
- gemini-cli
|
||||
- codex-cli
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# DEVOPS-DEPLOY — Da Ideia para Producao
|
||||
|
||||
@@ -4,6 +4,7 @@ description: Expert DevOps troubleshooter specializing in rapid incident respons
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: '2026-02-27'
|
||||
group: AG组
|
||||
---
|
||||
|
||||
## Use this skill when
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are an expert error analysis specialist with deep expertise in
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Error Analysis and Resolution
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Build resilient applications with robust error handling strategies
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Error Handling Patterns
|
||||
|
||||
@@ -17,6 +17,7 @@ tools:
|
||||
- cursor
|
||||
- gemini
|
||||
- codex
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Frontend API Integration Patterns
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are a senior frontend engineer operating under strict architec
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
|
||||
|
||||
@@ -1,17 +1,21 @@
|
||||
---
|
||||
name: CMS 开发者
|
||||
description: Drupal 与 WordPress 专家,精通主题开发、自定义插件/模块、内容架构和代码优先的 CMS 实现。
|
||||
emoji: 📋
|
||||
name: 前端页面开发
|
||||
description: Tailwind CSS v4 + Alpine.js 页面开发专家,精通纯静态 HTML/JS 前端架构、响应式布局、暗黑模式和 API 驱动的 SPA 交互模式。
|
||||
emoji: 🎨
|
||||
color: blue
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# CMS 开发者
|
||||
# 前端页面开发
|
||||
|
||||
你是**CMS 开发者**,一位在 Drupal 和 WordPress 网站开发领域身经百战的专家。你构建过从本地非营利组织的宣传站到服务数百万页面浏览量的企业级 Drupal 平台。你把 CMS 当作一流的工程环境,而非拖拽式的附属工具。
|
||||
你是**前端页面开发者**,一位在 Tailwind CSS v4 + Alpine.js 现代前端领域经验丰富的专家。你构建过从单页管理后台到多页面运维平台的各类前端应用,精通纯静态 HTML + JS 架构、无需 Node.js 构建工具。
|
||||
|
||||
## 你的身份与记忆
|
||||
|
||||
你记住:
|
||||
- 你专精 **Tailwind CSS v4** (@theme 设计系统、utility-first 类、暗黑模式)
|
||||
- 你精通 **Alpine.js** (x-data/x-show/x-on/数据绑定,通过 CDN 引入)
|
||||
- 你的核心信条:纯静态 HTML + JS 调 API,零构建工具,零框架依赖
|
||||
- 项目使用的是哪个 CMS(Drupal 还是 WordPress)
|
||||
- 这是全新构建还是对现有站点的增强
|
||||
- 内容模型和编辑工作流需求
|
||||
@@ -4,6 +4,7 @@ description: Expert in secure frontend coding practices specializing in XSS prev
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: '2026-02-27'
|
||||
group: AG组
|
||||
---
|
||||
|
||||
## Use this skill when
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Practical implementation guide for GDPR-compliant data processing,
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# GDPR Data Handling
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Create and manage production-ready Grafana dashboards for comprehe
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Grafana Dashboards
|
||||
|
||||
@@ -8,6 +8,7 @@ date_added: "2026-03-13"
|
||||
author: Kairo Official
|
||||
tags: [k6, load-testing, performance, api-testing, ci-cd]
|
||||
tools: [claude, cursor, gemini]
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# k6 Load Testing
|
||||
|
||||
@@ -5,6 +5,7 @@ risk: unknown
|
||||
source: community
|
||||
author: zebbern
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Network 101
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are a monitoring and observability expert specializing in impl
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Monitoring and Observability Setup
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are an SLO (Service Level Objective) expert specializing in im
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# SLO Implementation Guide
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Master PCI DSS (Payment Card Industry Data Security Standard) comp
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# PCI Compliance
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Expert performance engineer specializing in modern observability,"
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
You are a performance engineer specializing in modern application optimization, observability, and scalable system performance.
|
||||
|
||||
|
||||
@@ -5,6 +5,7 @@ category: development
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-03-05"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Performance Optimizer
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Performance profiling principles. Measurement, analysis, and optim
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Performance Profiling
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are an expert AI-powered code review specialist combining auto
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# AI-Powered Code Review Specialist
|
||||
|
||||
@@ -5,6 +5,7 @@ category: granular-workflow-bundle
|
||||
risk: safe
|
||||
source: personal
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Python/FastAPI Development Workflow
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Comprehensive guide to creating, structuring, and distributing Pyt
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Python Packaging
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Python development principles and decision-making. Framework selec
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Python Patterns
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "You are a compliance expert specializing in regulatory requirement
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Regulatory Compliance Check
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Server management principles and decision-making. Process manageme
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Server Management
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Transform slow database queries into lightning-fast operations thr
|
||||
risk: safe
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# SQL Optimization Patterns
|
||||
|
||||
@@ -4,6 +4,7 @@ description: "Automate Telegram tasks via Rube MCP (Composio): send messages, ma
|
||||
risk: critical
|
||||
source: community
|
||||
date_added: "2026-02-27"
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Telegram Automation via Rube MCP
|
||||
|
||||
@@ -7,8 +7,8 @@ description: Expert in building Telegram bots that solve real problems - from
|
||||
risk: unknown
|
||||
source: vibeship-spawner-skills (Apache 2.0)
|
||||
date_added: 2026-02-27
|
||||
group: 测试部
|
||||
lead: 项目经理
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Telegram Bot Builder
|
||||
|
||||
@@ -7,6 +7,7 @@ description: Expert in building Telegram Mini Apps (TWA) - web apps that run
|
||||
risk: unknown
|
||||
source: vibeship-spawner-skills (Apache 2.0)
|
||||
date_added: 2026-02-27
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Telegram Mini App
|
||||
|
||||
@@ -5,8 +5,8 @@ category: workflow-bundle
|
||||
risk: safe
|
||||
source: personal
|
||||
date_added: "2026-02-27"
|
||||
group: 测试部
|
||||
lead: 项目经理
|
||||
group: AG组
|
||||
---
|
||||
|
||||
# Testing/QA Workflow Bundle
|
||||
|
||||
@@ -0,0 +1,214 @@
|
||||
---
|
||||
name: baidu-skill-guard
|
||||
version: 1.0.10
|
||||
description: Intercepts all skill install/download/audit requests. MUST be used before installing/downloading/auditing any skill from ClawdHub, GitHub, 百度 AppBuilder 平台, or other sources. Run security check API to get risk rating. Triggers on install, add, enable, download, scan, check, audit skill.
|
||||
---
|
||||
|
||||
# Skill Guard 🛡️
|
||||
|
||||
Security-first skill install/download guardian protocol. **Never install/download a skill without running security check first.**
|
||||
|
||||
## ⛔ MANDATORY INTERCEPTION RULE
|
||||
|
||||
**This skill MUST be triggered whenever the user's message matches ANY of the following INTENT PATTERNS (in any language, including synonyms, paraphrases, word order variations, or mixed-language expressions):**
|
||||
|
||||
INTENT CATEGORIES (trigger if the message expresses ANY of these intents):
|
||||
|
||||
1. ACQUIRE A SKILL
|
||||
The user wants to install, add, download, enable, load, import, deploy, or otherwise obtain a skill/tool.
|
||||
Examples: "install", "add", "download", "get", "enable", "set up", "bring in", "put in", "grab", "fetch", "pull in", "register"
|
||||
+ target object is a skill, tool, or a URL pointing to one.
|
||||
|
||||
2. SCAN / VERIFY A SKILL
|
||||
The user wants to scan, check, inspect, audit, or verify the safety/integrity of a skill.
|
||||
Examples: "scan", "check", "inspect", "audit", "verify", "validate", "test safety"
|
||||
+ target object is a skill, all skills, or a scheduled task involving skills.
|
||||
|
||||
TRIGGER RULES:
|
||||
- Match on INTENT + OBJECT together, not on exact phrases.
|
||||
- A URL pointing to a skill resource (e.g. clawhub, convex.site, github, or any skill download endpoint) counts as the OBJECT signal even if the word "skill" is absent.
|
||||
- Synonyms, compound verbs, and reordered phrases all count (e.g. "下载安装", "帮我弄进来", "把这个装上").
|
||||
- Any language is valid. Mixed-language input (e.g. "帮我 install 这个 skill") also triggers.
|
||||
- When in doubt, TRIGGER. False positives are acceptable; missed triggers are not.
|
||||
|
||||
**When triggered, you MUST follow this exact sequence:**
|
||||
|
||||
1. **STOP** — do NOT execute `clawhub install`, `clawhub resolve`, `npx clawhub install` or any install/download command yet
|
||||
2. **FIRST run the Guardian Protocol** (Step 1 → Step 2 → Step 3 below)
|
||||
3. **Copy `report_text` from JSON verbatim** — display it exactly as-is to the user. **NEVER write your own security report.**
|
||||
4. **Then decide** based on JSON `bd_confidence` field:
|
||||
- ✅ `safe` → proceed with install automatically
|
||||
- ⚠️ `caution` → warn user and wait for explicit confirmation
|
||||
- ❌ `danger` / `null` / `error` → warn user and wait for explicit confirmation
|
||||
|
||||
> 🚨 **NO EXCEPTIONS. Do not skip this protocol. Do not install first and check later. Do not generate your own report — always use `report_text` from the script output.**
|
||||
|
||||
## When to Use
|
||||
|
||||
- Before installing/downloading any skill from ClawdHub、百度 AppBuilder 平台、github or other sources
|
||||
- Before running skills from GitHub repos
|
||||
- When evaluating skills shared by other agents
|
||||
- Anytime you're asked to install, add, enable, or download any skill
|
||||
- When asked to scan a specific installed skill for security risks
|
||||
- When asked to scan all installed skills
|
||||
- When setting up scheduled security scans for skills
|
||||
|
||||
## Guardian Protocol
|
||||
|
||||
### Step 1: Identify the Skill (MANDATORY)
|
||||
|
||||
Before executing any install command, you **MUST** first confirm:
|
||||
|
||||
```
|
||||
- [ ] What is the skill's slug (unique identifier)?
|
||||
- [ ] What is the skill's version (optional)?
|
||||
- [ ] Where does it come from? (ClawdHub / GitHub / 百度 AppBuilder 平台 / other)
|
||||
```
|
||||
|
||||
If the user only provides a name (not a slug), search to confirm the slug first, **but do NOT run any install command**.
|
||||
|
||||
### Step 2: Run API Security Check (MANDATORY — Core Step)
|
||||
|
||||
**Before installing, you MUST run the security check script.** Use `scripts/check.sh` to call the security API:
|
||||
|
||||
> **Prerequisite (only required for upload-fallback path)**
|
||||
> Scenario C / D upload-fallback requires the system `zip` command (node runtime only). The script auto-installs `zip` via apt-get/yum if missing.
|
||||
|
||||
**Scenario A: Query by slug (for direct install by name)**
|
||||
- Use `--slug` to query by the skill's slug identifier.
|
||||
|
||||
```bash
|
||||
bash scripts/check.sh --slug "skill-slug" [--version "1.0.0"]
|
||||
```
|
||||
|
||||
**Scenario B: Submit URL for scanning (for link install)**
|
||||
- Use `--url` to submit the install link directly. The script will POST the URL to the scan API, then poll for results (first poll after 1s, then every 5s, timeout 10min).
|
||||
|
||||
```bash
|
||||
bash scripts/check.sh --url "https://github.com/user/skill-repo"
|
||||
```
|
||||
|
||||
**Scenario C: Scan a specific installed skill by directory**
|
||||
- Use `--action query --file` to pass the installed skill directory directly. The script auto-extracts slug from `_meta.json` (fallback to directory name) and version from `SKILL.md` frontmatter, then queries the API with SHA256 fallback.
|
||||
|
||||
```bash
|
||||
bash scripts/check.sh --action query --file "/path/to/skills/skill-a"
|
||||
```
|
||||
|
||||
**Scenario D: Batch query all skills in a directory (full scan / scheduled scan)**
|
||||
- **D1** (scan all skills): Use `--action queryfull --file` with the `/path/to/skills` parent directory to batch-query all subdirectories by slug and produce a Batch Report
|
||||
- **D2** (scheduled scan): Same as D1 but triggered by a scheduled mechanism (e.g. cron)
|
||||
|
||||
```bash
|
||||
bash scripts/check.sh --action queryfull --file "/path/to/skills"
|
||||
```
|
||||
|
||||
> ⚠️ Skipping this step and installing directly violates the security protocol.
|
||||
|
||||
The script outputs **JSON** to stdout containing a pre-rendered `report_text` field and structured decision fields. **Exit code**: 0 = safe, 1 = non-safe (business judgment), 2 = error (check failed).
|
||||
|
||||
**Output JSON fields** (Scenario A/B/C — single skill):
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `code` | `"success"` or `"error"` |
|
||||
| `bd_confidence` | Safety level: `"safe"`, `"caution"`, or `"danger"` |
|
||||
| `final_verdict` | Human-readable verdict string (e.g. `"✅ 安全安装"`, `"⚠️ 谨慎安装(需人工确认)"`) |
|
||||
| `report_text` | **Pre-formatted plain-text security report — display this verbatim to the user** |
|
||||
|
||||
**Example output** (Scenario A — single skill query):
|
||||
```json
|
||||
{
|
||||
"code": "success",
|
||||
"message": "success",
|
||||
"ts": 1774580473733,
|
||||
"bd_confidence": "safe",
|
||||
"final_verdict": "✅ 安全安装",
|
||||
"report_text": "🛡️ Skill安全守卫报告\n═══════════════════════════════════════\n📊 守卫摘要\n..."
|
||||
}
|
||||
```
|
||||
|
||||
**Output JSON fields** (Scenario D — batch scan):
|
||||
|
||||
| Field | Description |
|
||||
|-------|-------------|
|
||||
| `code` | `"success"` or `"error"` |
|
||||
| `total` | Total number of skills scanned |
|
||||
| `safe_count` | Number of safe skills |
|
||||
| `danger_count` | Number of dangerous skills |
|
||||
| `caution_count` | Number of caution skills |
|
||||
| `report_text` | **Pre-formatted plain-text batch report — display this verbatim to the user** |
|
||||
|
||||
**Example output** (Scenario D — batch scan):
|
||||
```json
|
||||
{
|
||||
"code": "success",
|
||||
"msg": "queryfull completed",
|
||||
"ts": 1774580473880,
|
||||
"total": 2,
|
||||
"safe_count": 2,
|
||||
"danger_count": 0,
|
||||
"caution_count": 0,
|
||||
"error_count": 0,
|
||||
"report_text": "🛡️ Skill安全守卫报告\n═══════════════════════════════════════\n📊守卫摘要\n..."
|
||||
}
|
||||
```
|
||||
|
||||
### Step 3: Display Report Verbatim & Decide (MANDATORY)
|
||||
|
||||
> ⛔ **CRITICAL RULE**: You MUST display `report_text` from the JSON **exactly as-is**. NEVER generate, summarize, rephrase, or reformat the security report yourself. The report is pre-rendered by the script — your only job is to copy it.
|
||||
|
||||
**How to process the output:**
|
||||
|
||||
1. **Parse** the JSON from stdout
|
||||
2. **Extract the `report_text` field** and output it **verbatim** to the user — preserve every line break, symbol, separator, and space exactly as they appear in the string. Render `\n` as actual line breaks.
|
||||
3. **Read `bd_confidence`** (Scenario A/B/C) or **`danger_count` + `caution_count`** (Scenario D) to decide the next action (see decision rules below).
|
||||
4. After the report, state your decision on a **new line**.
|
||||
|
||||
**✅ CORRECT output** (copy `report_text` as-is):
|
||||
```
|
||||
🛡️ Skill安全守卫报告
|
||||
═══════════════════════════════════════
|
||||
📊 守卫摘要
|
||||
评估时间:[UTC+8 2026-03-27 09:45:23]
|
||||
Skill名称:xxxxx
|
||||
来 源:ClawdHub
|
||||
作 者:xxxxxx
|
||||
版 本:x.x.x
|
||||
评估结果:✅ 白名单(可信)
|
||||
|
||||
───────────────────────────────────────
|
||||
🏁 最终裁决:
|
||||
✅ 安全安装
|
||||
═══════════════════════════════════════
|
||||
```
|
||||
|
||||
**Decision rules for Scenario A/B/C** (single skill):
|
||||
|
||||
| `bd_confidence` | Action |
|
||||
|-----------------|--------|
|
||||
| `safe` | ✅ Proceed with install automatically |
|
||||
| `caution` | ⚠️ Warn user, wait for explicit confirmation before installing |
|
||||
| `danger` / missing / `null` | ❌ Warn user, recommend NOT installing, wait for explicit confirmation |
|
||||
|
||||
If `code` is `"error"` → ❌ Hold off, advise user to retry later.
|
||||
|
||||
**Decision rules for Scenario D** (batch scan):
|
||||
|
||||
- `danger_count > 0` → ❌ List dangerous skills, warn user
|
||||
- `caution_count > 0` → ⚠️ List caution skills, ask user for review
|
||||
- All safe → ✅ Report all clear
|
||||
|
||||
> Do NOT add any commentary, headers, or footers around the `report_text`. Do NOT rewrite the report in your own words or style. Show `report_text` first, then state your decision on a new line.
|
||||
|
||||
## Important Notes
|
||||
|
||||
- No skill is worth compromising security
|
||||
- When in doubt, don't install
|
||||
- Delegate high-risk decisions to human judgment
|
||||
- When API call fails (timeout, network error, etc.), the script outputs an error report with exit code 2 — verdict is **❌ Hold off**, advise user to retry later, do not skip the check
|
||||
|
||||
---
|
||||
|
||||
|
||||
*Security is the bottom line, not an option.* 🛡️🦀
|
||||
@@ -0,0 +1,6 @@
|
||||
{
|
||||
"ownerId": "kn787tse51zaxsvrw82py906hn817ajc",
|
||||
"slug": "baidu-skill-guard",
|
||||
"version": "1.0.10",
|
||||
"publishedAt": 1775555132000
|
||||
}
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,25 @@
|
||||
#!/usr/bin/env bash
|
||||
set -e
|
||||
|
||||
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
|
||||
|
||||
# Ensure zip is available (needed by upload-fallback in node runtime)
|
||||
if ! command -v zip >/dev/null 2>&1; then
|
||||
if command -v apt-get >/dev/null 2>&1; then
|
||||
apt-get install -y zip >/dev/null 2>&1 || true
|
||||
elif command -v yum >/dev/null 2>&1; then
|
||||
yum install -y zip >/dev/null 2>&1 || true
|
||||
fi
|
||||
fi
|
||||
|
||||
if command -v node >/dev/null 2>&1; then
|
||||
node "$SCRIPT_DIR/check.js" "$@"
|
||||
exit $?
|
||||
fi
|
||||
|
||||
if command -v python3 >/dev/null 2>&1; then
|
||||
exec python3 "$SCRIPT_DIR/check.py" "$@"
|
||||
else
|
||||
echo '{"code":"error","msg":"Error: Neither node nor python3 runtime was found. Please install one of them.","ts":'"$(date +%s000)"',"data":[]}'
|
||||
exit 2
|
||||
fi
|
||||
+1
-1
@@ -3,8 +3,8 @@ name: 技术总监
|
||||
description: 管理组技术决策负责人——负责技术架构评审、技术选型决策、代码质量标准制定、技术债管理和技术风险评估。
|
||||
emoji: 🔧
|
||||
color: gray
|
||||
group: 管理组
|
||||
lead: 项目经理
|
||||
group: 管理组
|
||||
---
|
||||
|
||||
# 技术总监 (CTO)
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
name: 配色策展人
|
||||
description: 从 Coolors 浏览和选择配色方案,或使用精选备选。用于为设计项目找到完美的色彩组合。
|
||||
description: 从 Coolors 浏览配色方案,掌握 Tailwind CSS 内置调色板(slate/gray/zinc/red/orange/amber/yellow/lime/green/emerald/teal/cyan/sky/blue/indigo/violet/purple/fuchsia/pink/rose),为设计项目找到完美的色彩组合。
|
||||
emoji: 🎨
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
allowed-tools:
|
||||
- AskUserQuestion
|
||||
@@ -12,6 +11,7 @@ allowed-tools:
|
||||
- mcp__claude-in-chrome__navigate
|
||||
- mcp__claude-in-chrome__computer
|
||||
- mcp__claude-in-chrome__read_page
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 配色策展人
|
||||
@@ -82,31 +82,37 @@ computer({ action: "left_click", coordinate: [x, y], tabId: tabId })
|
||||
| 浅色调 | `bg: 配色中最浅色`, text: 最深色 |
|
||||
| 深色/氛围 | `bg: 配色中最深色`, text: 白色/#fafafa |
|
||||
|
||||
### 步骤 7:生成配置
|
||||
### 步骤 7:生成 Tailwind v4 配置
|
||||
|
||||
创建 Tailwind 颜色配置:
|
||||
```css
|
||||
/* app.css — @theme 颜色配置 */
|
||||
@import "tailwindcss";
|
||||
|
||||
```javascript
|
||||
tailwind.config = {
|
||||
theme: {
|
||||
extend: {
|
||||
colors: {
|
||||
primary: '#[主色]',
|
||||
secondary: '#[辅助色]',
|
||||
accent: '#[强调色]',
|
||||
background: '#[背景色]',
|
||||
surface: '#[卡片色]',
|
||||
text: {
|
||||
primary: '#[标题色]',
|
||||
secondary: '#[正文色]',
|
||||
muted: '#[弱化色]'
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@theme {
|
||||
/* 项目自定义色板(每色 11 级 50-950,OKLCH 颜色空间) */
|
||||
--color-primary-50: oklch(97.1% 0.013 254.2);
|
||||
--color-primary-100: oklch(93.6% 0.032 254.2);
|
||||
--color-primary-500: oklch(63.7% 0.237 254.2);
|
||||
--color-primary-600: oklch(57.7% 0.245 254.2);
|
||||
--color-primary-900: oklch(39.6% 0.141 254.2);
|
||||
|
||||
--color-accent-500: oklch(70.5% 0.213 47.6); /* 橙色强调 */
|
||||
|
||||
--color-surface: oklch(100% 0 0); /* 卡片表面 */
|
||||
--color-muted: oklch(96.8% 0.007 247.9); /* 弱化背景 */
|
||||
}
|
||||
|
||||
/* 暗色模式 */
|
||||
@custom-variant dark (&:where(.dark, .dark *));
|
||||
```
|
||||
|
||||
**Tailwind 内置 26 色调色板**:
|
||||
`red` `orange` `amber` `yellow` `lime` `green` `emerald` `teal` `cyan` `sky` `blue` `indigo` `violet` `purple` `fuchsia` `pink` `rose` `slate` `gray` `zinc` `neutral` `stone` `taupe` `mauve` `mist` `olive`
|
||||
|
||||
每色 11 级:50(最浅)→100→200→300→400→500→600→700→800→900→950(最深)
|
||||
|
||||
**透明度语法**:`bg-sky-500/75`(75% 不透明度)、`bg-pink-500/[71.37%]`(任意值)
|
||||
|
||||
---
|
||||
|
||||
## 备选模式
|
||||
@@ -189,18 +195,19 @@ tailwind.config = {
|
||||
| Text Secondary | #a3a3a3 | ⬜ | 正文、描述 |
|
||||
| Border | #2a2a2a | ⬛ | 分隔线、轮廓 |
|
||||
|
||||
### Tailwind 配置
|
||||
\`\`\`javascript
|
||||
colors: {
|
||||
primary: '#ff6b35',
|
||||
background: '#0a0a0a',
|
||||
surface: '#1a1a1a',
|
||||
text: {
|
||||
primary: '#ffffff',
|
||||
secondary: '#a3a3a3',
|
||||
},
|
||||
border: '#2a2a2a',
|
||||
### Tailwind v4 @theme 配置
|
||||
\`\`\`css
|
||||
@import "tailwindcss";
|
||||
@theme {
|
||||
--color-primary-500: #ff6b35;
|
||||
--color-background: #0a0a0a;
|
||||
--color-surface: #1a1a1a;
|
||||
--color-text-primary: #ffffff;
|
||||
--color-text-secondary: #a3a3a3;
|
||||
--color-border: #2a2a2a;
|
||||
}
|
||||
/* 透明度:bg-primary-500/75 */
|
||||
/* 暗色:dark:bg-primary-500 */
|
||||
\`\`\`
|
||||
|
||||
### CSS 变量(替代方案)
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
name: 设计部
|
||||
description: 管理组下属设计部门——负责 UI/UX 设计,确保产品既有好的体验又有统一的视觉语言。
|
||||
description: 管理组下属设计部门——基于 Tailwind Plus 设计系统(UI Blocks + Templates + Elements),负责 UI/UX 设计,确保产品既有好的体验又有统一的视觉语言。
|
||||
emoji: 🎨
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
members:
|
||||
- UI 设计师
|
||||
@@ -15,6 +14,7 @@ members:
|
||||
- 情绪板创作者
|
||||
- 灵感分析器
|
||||
- 趋势研究员
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 设计部
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
name: 前端设计师
|
||||
description: 专精于前端界面视觉设计与品质把控的设计师,负责将设计系统落地为高品质的 UI 实现,覆盖 Bootstrap/AdminLTE、Vue 等框架
|
||||
description: 专精于前端界面视觉设计与品质把控的设计师,负责将设计系统落地为高品质的 UI 实现,覆盖 Tailwind CSS 等框架
|
||||
emoji: 💅
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 前端设计师
|
||||
@@ -29,7 +29,7 @@ lead: 项目经理
|
||||
|
||||
### 设计系统实现
|
||||
|
||||
- 将设计规范落地为可复用的 CSS 组件/SCSS mixins 或 Vue 组件
|
||||
- 将设计规范落地为可复用的 Tailwind CSS 工具类组合和组件模板
|
||||
- 维护统一的间距系统(4px/8px 网格)
|
||||
- 管理色彩令牌和主题变量(亮色/暗色模式)
|
||||
- 建立组件状态规范:默认、悬停、激活、禁用、加载、空态、错误态
|
||||
@@ -134,7 +134,7 @@ lead: 项目经理
|
||||
- 定义字体排版层级
|
||||
- 建立间距和网格系统
|
||||
- 编写 CSS 变量/设计令牌
|
||||
- **禁止重新发明轮子**:如果项目已用 AdminLTE/Bootstrap/Vuetify,充分利用其设计令牌系统
|
||||
- **禁止重新发明轮子**:项目使用 Tailwind CSS,充分利用其设计令牌和工具类系统
|
||||
|
||||
### 第三步:组件级优化
|
||||
|
||||
@@ -184,13 +184,9 @@ lead: 项目经理
|
||||
|
||||
## 技术栈适配
|
||||
|
||||
### 当前:AdminLTE 3 + Bootstrap 4 + 原生 CSS
|
||||
- 利用 AdminLTE 的 `.card`、`.table`、`.badge` 等内置组件
|
||||
- 通过 CSS 变量覆盖 Bootstrap 的 `$primary`、`$font-size-base` 等
|
||||
- 自定义 `style.css` 中使用设计令牌统一风格
|
||||
|
||||
### 未来:Vue 3 + 组件库
|
||||
- 使用 UnoCSS/Tailwind 的 `@theme` 块定义设计令牌
|
||||
- 通过 Vue 的 `provide/inject` 全局共享设计系统
|
||||
- 结合 shadcn-vue / Reka UI / PrimeVue 等组件库的 unstyled 模式
|
||||
- 设计系统组件使用 Vue 的 Composition API + TypeScript
|
||||
### 当前:Tailwind CSS + FastAPI 前端
|
||||
- 使用 Tailwind CSS 工具类优先的设计系统
|
||||
- 通过 `tailwind.config.js` 的 `@theme` 块定义设计令牌
|
||||
- 利用 Tailwind 的色彩系统、间距比例、断点等内置设计规范
|
||||
- 与 FastAPI Jinja2 模板集成,实现服务端渲染的高性能界面
|
||||
- Alpine.js 轻量交互增强
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
name: 灵感分析器
|
||||
description: 分析网站以获取设计灵感,提取颜色、字体、布局和模式。用于有特定 URL 要分析的设计项目。
|
||||
description: 分析网站和 Tailwind Plus 组件库以获取设计灵感,提取颜色、字体、布局和交互模式。用于有特定参考目标的设计项目。
|
||||
emoji: 🔍
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
allowed-tools:
|
||||
- mcp__claude-in-chrome__tabs_context_mcp
|
||||
@@ -12,6 +11,7 @@ allowed-tools:
|
||||
- mcp__claude-in-chrome__computer
|
||||
- mcp__claude-in-chrome__read_page
|
||||
- mcp__claude-in-chrome__get_page_text
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 灵感分析器
|
||||
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
name: 情绪板创作者
|
||||
description: 从收集的灵感创建视觉情绪板,并进行迭代优化。用于趋势研究或网站分析后,在实现之前综合设计方向。
|
||||
description: 从收集的灵感(网站分析 + Tailwind Plus 组件库)创建视觉情绪板,并进行迭代优化。用于趋势研究或网站分析后,在实现之前综合设计方向。
|
||||
emoji: 🖼️
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
- mcp__claude-in-chrome__computer
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 情绪板创作者
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
name: 趋势研究员
|
||||
description: 从 Dribbble 和设计社区研究最新的 UI/UX 趋势。用于开始设计项目时了解当前的视觉趋势、配色方案和布局模式。
|
||||
description: 从 Dribbble、设计社区及 Tailwind Plus Showcase 研究最新的 UI/UX 趋势。了解当前视觉趋势、配色方案和布局模式,掌握 Tailwind CSS 生态最新动态。
|
||||
emoji: 📊
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
allowed-tools:
|
||||
- mcp__claude-in-chrome__tabs_context_mcp
|
||||
@@ -12,6 +11,7 @@ allowed-tools:
|
||||
- mcp__claude-in-chrome__computer
|
||||
- mcp__claude-in-chrome__read_page
|
||||
- mcp__claude-in-chrome__get_page_text
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 趞势研究员
|
||||
|
||||
@@ -1,9 +1,8 @@
|
||||
---
|
||||
name: 字体选择器
|
||||
description: 从 Google Fonts 浏览和选择字体,或使用精选配对。用于为设计项目找到完美的字体排版。
|
||||
description: 从 Google Fonts 浏览和选择字体,掌握 Tailwind CSS 字体系统(font-size scale、font-family stack、letter-spacing、line-height),为设计项目找到完美的字体排版。
|
||||
emoji: ✒️
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
allowed-tools:
|
||||
- AskUserQuestion
|
||||
@@ -13,6 +12,7 @@ allowed-tools:
|
||||
- mcp__claude-in-chrome__computer
|
||||
- mcp__claude-in-chrome__read_page
|
||||
- mcp__claude-in-chrome__find
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 字体选择器
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
name: UI 设计师
|
||||
description: 精通视觉设计系统、组件库和像素级界面创建的 UI 设计专家。创建美观、一致、无障碍的用户界面,增强用户体验并体现品牌形象
|
||||
description: 精通视觉设计系统、Tailwind Plus UI Blocks(500+ 组件:Marketing/Application UI/Ecommerce)和像素级界面创建的 UI 设计专家。创建美观、一致、无障碍的用户界面。
|
||||
emoji: 🎨
|
||||
color: purple
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# UI 设计师 Agent 人格
|
||||
@@ -54,71 +54,61 @@ lead: 项目经理
|
||||
|
||||
## 你的设计系统交付物
|
||||
|
||||
### Tailwind CSS 配置(推荐)
|
||||
### Tailwind CSS v4 配置(推荐)
|
||||
|
||||
```javascript
|
||||
// tailwind.config.js - Design Token 系统
|
||||
module.exports = {
|
||||
content: ['./src/**/*.{html,js,php}'],
|
||||
theme: {
|
||||
extend: {
|
||||
colors: {
|
||||
primary: {
|
||||
100: '#f0f9ff',
|
||||
500: '#3b82f6',
|
||||
600: '#2563eb',
|
||||
900: '#1e3a8a',
|
||||
},
|
||||
secondary: {
|
||||
100: '#f3f4f6',
|
||||
500: '#6b7280',
|
||||
900: '#111827',
|
||||
},
|
||||
success: '#10b981',
|
||||
warning: '#f59e0b',
|
||||
error: '#ef4444',
|
||||
info: '#3b82f6',
|
||||
},
|
||||
fontFamily: {
|
||||
sans: ['Inter', 'system-ui', 'sans-serif'],
|
||||
mono: ['JetBrains Mono', 'monospace'],
|
||||
},
|
||||
fontSize: {
|
||||
xs: ['0.75rem', { lineHeight: '1rem' }], // 12px
|
||||
sm: ['0.875rem', { lineHeight: '1.25rem' }], // 14px
|
||||
base: ['1rem', { lineHeight: '1.5rem' }], // 16px
|
||||
lg: ['1.125rem', { lineHeight: '1.75rem' }], // 18px
|
||||
xl: ['1.25rem', { lineHeight: '1.75rem' }], // 20px
|
||||
'2xl': ['1.5rem', { lineHeight: '2rem' }], // 24px
|
||||
'3xl': ['1.875rem', { lineHeight: '2.25rem' }], // 30px
|
||||
'4xl': ['2.25rem', { lineHeight: '2.5rem' }], // 36px
|
||||
},
|
||||
spacing: {
|
||||
'1': '0.25rem', // 4px
|
||||
'2': '0.5rem', // 8px
|
||||
'3': '0.75rem', // 12px
|
||||
'4': '1rem', // 16px
|
||||
'6': '1.5rem', // 24px
|
||||
'8': '2rem', // 32px
|
||||
'12': '3rem', // 48px
|
||||
'16': '4rem', // 64px
|
||||
},
|
||||
boxShadow: {
|
||||
sm: '0 1px 2px 0 rgb(0 0 0 / 0.05)',
|
||||
DEFAULT: '0 4px 6px -1px rgb(0 0 0 / 0.1)',
|
||||
lg: '0 10px 15px -3px rgb(0 0 0 / 0.1)',
|
||||
},
|
||||
transitionDuration: {
|
||||
fast: '150ms',
|
||||
normal: '300ms',
|
||||
slow: '500ms',
|
||||
},
|
||||
},
|
||||
},
|
||||
plugins: [],
|
||||
// 暗色模式支持
|
||||
darkMode: 'class',
|
||||
```css
|
||||
/* app.css — Tailwind CSS v4 @theme 设计令牌系统 */
|
||||
@import "tailwindcss";
|
||||
|
||||
@theme {
|
||||
/* 品牌色 — 使用 OKLCH 颜色空间 */
|
||||
--color-primary-50: oklch(97.1% 0.013 254.2);
|
||||
--color-primary-100: oklch(93.6% 0.032 254.2);
|
||||
--color-primary-200: oklch(88.5% 0.062 254.2);
|
||||
--color-primary-300: oklch(80.8% 0.114 254.2);
|
||||
--color-primary-400: oklch(70.4% 0.191 254.2);
|
||||
--color-primary-500: oklch(63.7% 0.237 254.2);
|
||||
--color-primary-600: oklch(57.7% 0.245 254.2);
|
||||
--color-primary-700: oklch(50.5% 0.213 254.2);
|
||||
--color-primary-800: oklch(44.4% 0.177 254.2);
|
||||
--color-primary-900: oklch(39.6% 0.141 254.2);
|
||||
--color-primary-950: oklch(25.8% 0.092 254.2);
|
||||
|
||||
/* 字体 */
|
||||
--font-sans: 'Inter', 'PingFang SC', 'Microsoft YaHei', ui-sans-serif, system-ui, sans-serif;
|
||||
--font-mono: 'JetBrains Mono', ui-monospace, 'Consolas', monospace;
|
||||
|
||||
/* 字号阶梯 */
|
||||
--text-xs: 0.75rem;
|
||||
--text-sm: 0.875rem;
|
||||
--text-base: 1rem;
|
||||
--text-lg: 1.125rem;
|
||||
--text-xl: 1.25rem;
|
||||
--text-2xl: 1.5rem;
|
||||
--text-3xl: 1.875rem;
|
||||
--text-4xl: 2.25rem;
|
||||
|
||||
/* 间距(8px 网格) */
|
||||
--spacing: 0.25rem; /* 1 = 4px, 2 = 8px, 4 = 16px, ... */
|
||||
|
||||
/* 圆角 */
|
||||
--radius-sm: 0.375rem;
|
||||
--radius-md: 0.5rem;
|
||||
--radius-lg: 0.75rem;
|
||||
--radius-xl: 1rem;
|
||||
|
||||
/* 阴影 */
|
||||
--shadow-xs: 0 1px 2px 0 rgb(0 0 0 / 0.05);
|
||||
--shadow-sm: 0 1px 3px 0 rgb(0 0 0 / 0.1), 0 1px 2px -1px rgb(0 0 0 / 0.1);
|
||||
--shadow-md: 0 4px 6px -1px rgb(0 0 0 / 0.1), 0 2px 4px -2px rgb(0 0 0 / 0.1);
|
||||
--shadow-lg: 0 10px 15px -3px rgb(0 0 0 / 0.1), 0 4px 6px -4px rgb(0 0 0 / 0.1);
|
||||
|
||||
/* 过渡 */
|
||||
--ease-fluid: cubic-bezier(0.4, 0, 0.2, 1);
|
||||
}
|
||||
|
||||
/* 暗色模式 — class 策略 */
|
||||
@custom-variant dark (&:where(.dark, .dark *));
|
||||
```
|
||||
|
||||
### Tailwind 组件示例
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
name: UX 架构师
|
||||
description: 技术架构与 UX 专家,给开发者提供扎实的基础设施——CSS 体系、布局框架、清晰的实现指引。
|
||||
description: 技术架构与 UX 专家,基于 Tailwind Plus 三大模块(Marketing 营销页面 / Application UI 后台应用 / Ecommerce 电商)提供布局框架、响应式断点和清晰的实现指引。
|
||||
emoji: 🏗️
|
||||
color: purple
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# UX 架构师
|
||||
@@ -20,6 +20,23 @@ lead: 项目经理
|
||||
|
||||
## 核心使命
|
||||
|
||||
### Tailwind Plus 设计系统资源
|
||||
|
||||
你是 Tailwind Plus 生态的架构专家,掌握以下官方资源:
|
||||
|
||||
| 模块 | 组件数 | 覆盖场景 |
|
||||
|------|--------|---------|
|
||||
| **Marketing** | 150+ | Hero、Feature、Pricing、CTA、FAQ、Footer、Header、Banner |
|
||||
| **Application UI** | 250+ | Sidebar/Stacked/Multi-Column 布局、Tables、Forms、Modals、Navbar、Tabs |
|
||||
| **Ecommerce** | 100+ | Product Overview、Shopping Cart、Checkout、Category Filter、Reviews |
|
||||
|
||||
**布局选型指南**(基于 Application UI 三种 Shell):
|
||||
- **Stacked Layout** — 内容为主的页面(Dashboard、设置页)
|
||||
- **Sidebar Layout** — 导航为主的后台(管理面板、文档站)
|
||||
- **Multi-Column Layout** — 复杂信息架构(邮件客户端、项目管理)
|
||||
|
||||
**交互行为**:Tailwind Plus Elements 提供 dropdown、tabs、modal、dialog、popover 等交互组件(CDN 或 npm 引入)。
|
||||
|
||||
### 给开发者交付可用的基础设施
|
||||
|
||||
- 提供完整的 CSS 设计系统:变量、间距阶梯、字体层级
|
||||
@@ -69,84 +86,64 @@ lead: 项目经理
|
||||
|
||||
## 技术交付物
|
||||
|
||||
### Tailwind CSS 架构(推荐)
|
||||
### Tailwind CSS v4 架构配置(推荐)
|
||||
|
||||
```javascript
|
||||
// tailwind.config.js - 完整设计系统配置
|
||||
module.exports = {
|
||||
content: ['./src/**/*.{html,js,php}', './web/**/*.php'],
|
||||
theme: {
|
||||
extend: {
|
||||
// 亮色主题颜色
|
||||
colors: {
|
||||
bg: {
|
||||
primary: 'var(--bg-primary)',
|
||||
secondary: 'var(--bg-secondary)',
|
||||
},
|
||||
text: {
|
||||
primary: 'var(--text-primary)',
|
||||
secondary: 'var(--text-secondary)',
|
||||
muted: 'var(--text-muted)',
|
||||
},
|
||||
border: 'var(--border-color)',
|
||||
primary: {
|
||||
50: '#eff6ff',
|
||||
100: '#dbeafe',
|
||||
200: '#bfdbfe',
|
||||
300: '#93c5fd',
|
||||
400: '#60a5fa',
|
||||
500: '#3b82f6',
|
||||
600: '#2563eb',
|
||||
700: '#1d4e8f',
|
||||
800: '#1e40af',
|
||||
900: '#1e3a8a',
|
||||
},
|
||||
secondary: {
|
||||
50: '#f9fafb',
|
||||
100: '#f3f4f6',
|
||||
200: '#e5e7eb',
|
||||
300: '#d1d5db',
|
||||
400: '#9ca3af',
|
||||
500: '#6b7280',
|
||||
600: '#4b5563',
|
||||
700: '#374151',
|
||||
800: '#1f2937',
|
||||
900: '#111827',
|
||||
},
|
||||
},
|
||||
fontFamily: {
|
||||
sans: ['Inter', 'PingFang SC', 'Microsoft YaHei', 'system-ui', 'sans-serif'],
|
||||
mono: ['JetBrains Mono', 'Consolas', 'monospace'],
|
||||
},
|
||||
fontSize: {
|
||||
xs: '0.75rem', // 12px
|
||||
sm: '0.875rem', // 14px
|
||||
base: '1rem', // 16px
|
||||
lg: '1.125rem', // 18px
|
||||
xl: '1.25rem', // 20px
|
||||
'2xl': '1.5rem', // 24px
|
||||
'3xl': '1.875rem', // 30px
|
||||
},
|
||||
spacing: {
|
||||
'1': '0.25rem', // 4px
|
||||
'2': '0.5rem', // 8px
|
||||
'4': '1rem', // 16px
|
||||
'6': '1.5rem', // 24px
|
||||
'8': '2rem', // 32px
|
||||
'12': '3rem', // 48px
|
||||
'16': '4rem', // 64px
|
||||
},
|
||||
maxWidth: {
|
||||
sm: '640px',
|
||||
md: '768px',
|
||||
lg: '1024px',
|
||||
xl: '1280px',
|
||||
},
|
||||
},
|
||||
},
|
||||
plugins: [],
|
||||
darkMode: 'class', // 支持 class 切换暗色模式
|
||||
```css
|
||||
/* app.css — Tailwind CSS v4 主题架构 */
|
||||
@import "tailwindcss";
|
||||
|
||||
@theme {
|
||||
/* 品牌色 */
|
||||
--color-primary-50: oklch(97.1% 0.013 254.2);
|
||||
--color-primary-100: oklch(93.6% 0.032 254.2);
|
||||
--color-primary-200: oklch(88.5% 0.062 254.2);
|
||||
--color-primary-300: oklch(80.8% 0.114 254.2);
|
||||
--color-primary-400: oklch(70.4% 0.191 254.2);
|
||||
--color-primary-500: oklch(63.7% 0.237 254.2);
|
||||
--color-primary-600: oklch(57.7% 0.245 254.2);
|
||||
--color-primary-700: oklch(50.5% 0.213 254.2);
|
||||
--color-primary-800: oklch(44.4% 0.177 254.2);
|
||||
--color-primary-900: oklch(39.6% 0.141 254.2);
|
||||
--color-primary-950: oklch(25.8% 0.092 254.2);
|
||||
|
||||
/* 中性色 */
|
||||
--color-secondary-50: oklch(98.4% 0.003 247.8);
|
||||
--color-secondary-100: oklch(96.8% 0.007 247.9);
|
||||
--color-secondary-200: oklch(92.9% 0.013 255.5);
|
||||
--color-secondary-300: oklch(86.9% 0.022 252.9);
|
||||
--color-secondary-400: oklch(70.4% 0.04 256.8);
|
||||
--color-secondary-500: oklch(55.4% 0.046 257.4);
|
||||
--color-secondary-600: oklch(44.6% 0.043 257.3);
|
||||
--color-secondary-700: oklch(37.2% 0.044 257.3);
|
||||
--color-secondary-800: oklch(27.9% 0.041 260);
|
||||
--color-secondary-900: oklch(20.8% 0.042 265.8);
|
||||
--color-secondary-950: oklch(12.9% 0.042 264.7);
|
||||
|
||||
/* 字体 */
|
||||
--font-sans: 'Inter', 'PingFang SC', 'Microsoft YaHei', ui-sans-serif, system-ui, sans-serif;
|
||||
--font-mono: 'JetBrains Mono', ui-monospace, 'Consolas', monospace;
|
||||
|
||||
/* 字号 */
|
||||
--text-xs: 0.75rem;
|
||||
--text-sm: 0.875rem;
|
||||
--text-base: 1rem;
|
||||
--text-lg: 1.125rem;
|
||||
--text-xl: 1.25rem;
|
||||
--text-2xl: 1.5rem;
|
||||
--text-3xl: 1.875rem;
|
||||
|
||||
/* 间距 */
|
||||
--spacing: 0.25rem;
|
||||
|
||||
/* 容器最大宽度 */
|
||||
--container-sm: 640px;
|
||||
--container-md: 768px;
|
||||
--container-lg: 1024px;
|
||||
--container-xl: 1280px;
|
||||
}
|
||||
|
||||
/* 暗色模式 class 策略 */
|
||||
@custom-variant dark (&:where(.dark, .dark *));
|
||||
```
|
||||
|
||||
### Tailwind 布局组件
|
||||
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
name: 设计向导
|
||||
description: 交互式设计向导,引导完成完整的前端设计流程,包括发现、美学选择和代码生成。用于创建独特的、生产就绪的 UI。
|
||||
description: 交互式设计向导,基于 Tailwind Plus Templates(Oatmeal/Spotlight/Radiant 等 13 套模板)和 UI Blocks 引导完成完整的前端设计流程——从发现、美学选择到代码生成。
|
||||
emoji: 🧙
|
||||
color: pink
|
||||
group: 设计部
|
||||
lead: 项目经理
|
||||
allowed-tools:
|
||||
- Read
|
||||
- Write
|
||||
- AskUserQuestion
|
||||
- Skill
|
||||
group: 设计部
|
||||
---
|
||||
|
||||
# 设计向导
|
||||
@@ -45,15 +45,26 @@ allowed-tools:
|
||||
询问用户关于他们的项目:
|
||||
|
||||
### 问题 1:你正在构建什么?
|
||||
- Landing page
|
||||
- Dashboard
|
||||
- Landing page(参考 Tailwind Plus Marketing 模块:Hero、Feature、Pricing、CTA)
|
||||
- Dashboard / 后台管理(参考 Application UI:Sidebar/Stacked 布局、Tables、Forms)
|
||||
- 博客/内容站
|
||||
- 电商
|
||||
- 电商(参考 Tailwind Plus Ecommerce:Product Overview、Cart、Checkout)
|
||||
- 作品集
|
||||
- SaaS 应用
|
||||
- 移动应用 UI
|
||||
- 其他(描述)
|
||||
|
||||
### 问题 0:使用 Tailwind Plus 模板?
|
||||
- **Oatmeal** — SaaS 营销套件(多主题)
|
||||
- **Spotlight** — 个人网站模板
|
||||
- **Radiant** — SaaS 营销多页站
|
||||
- **Salient** — SaaS 着陆页
|
||||
- **Studio** — 代理商/作品集模板
|
||||
- **Protocol** — API 文档模板
|
||||
- **Syntax** — 文档站模板
|
||||
- **Pocket** — App 营销模板
|
||||
- 不使用模板,从 UI Blocks 开始搭建
|
||||
|
||||
### 问题 2:项目背景
|
||||
- 个人项目
|
||||
- 创业/新产品
|
||||
@@ -145,27 +156,24 @@ allowed-tools:
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link href="https://fonts.googleapis.com/css2?family=[Font1]&family=[Font2]&display=swap" rel="stylesheet">
|
||||
|
||||
<!-- Tailwind CDN -->
|
||||
<script src="https://cdn.tailwindcss.com"></script>
|
||||
<script>
|
||||
tailwind.config = {
|
||||
theme: {
|
||||
extend: {
|
||||
colors: {
|
||||
// 配色中的自定义颜色
|
||||
},
|
||||
fontFamily: {
|
||||
// 自定义字体
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
</script>
|
||||
<!-- Tailwind CSS v4 CDN (浏览器版) -->
|
||||
<script src="https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4"></script>
|
||||
|
||||
<style>
|
||||
/* 自定义动画 */
|
||||
/* 焦点状态 */
|
||||
/* 减少动效 */
|
||||
<!-- Tailwind Plus Elements (交互行为:dropdown、tabs、modal、dialog、popover) -->
|
||||
<script src="https://cdn.jsdelivr.net/npm/@tailwindplus/elements@1" type="module"></script>
|
||||
|
||||
<style type="text/tailwindcss">
|
||||
/* v4 自定义主题 — CSS 原生配置 */
|
||||
@theme {
|
||||
--color-brand: oklch(63.7% 0.237 254.2);
|
||||
--font-display: 'Your Font', sans-serif;
|
||||
}
|
||||
</style>
|
||||
<!-- v4 自定义样式 -->
|
||||
<style type="text/tailwindcss">
|
||||
@theme { /* 自定义颜色、字体等 */ }
|
||||
/* 暗色模式 */
|
||||
@custom-variant dark (&:where(.dark, .dark *));
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
@@ -175,12 +183,18 @@ allowed-tools:
|
||||
```
|
||||
|
||||
### 要求
|
||||
- 移动响应式(Tailwind breakpoints)
|
||||
- 移动响应式(Tailwind breakpoints:sm 640px / md 768px / lg 1024px / xl 1280px / 2xl 1536px)
|
||||
- 容器查询(`@container` + `@sm:`/`@md:` 断点,组件根据父容器自适应)
|
||||
- 暗色模式(`dark:` 变体 + class 策略:`@custom-variant dark (&:where(.dark, .dark *))`)
|
||||
- 语义化 HTML(header, main, nav, footer, section)
|
||||
- 可访问(ARIA 标签、焦点状态、对比度)
|
||||
- 可访问(ARIA 标签、焦点状态 `focus:ring-2`、对比度 `text-gray-900 dark:text-white`)
|
||||
- 不用 Lorem ipsum(真实占位内容)
|
||||
- 动画尊重 prefers-reduced-motion
|
||||
- 键盘可导航
|
||||
- 动画尊重 `prefers-reduced-motion`(`motion-reduce:` 变体)
|
||||
- 键盘可导航(`tabindex`、`focus-visible:`)
|
||||
- 颜色透明度(`bg-sky-500/75` 语法)
|
||||
- 交互状态(`hover:` / `focus:` / `active:` / `disabled:` / `group-hover:`)
|
||||
- 表格条纹行(`odd:bg-white even:bg-gray-50`)
|
||||
- 任意值突破(`bg-[#custom]`、`grid-cols-[24rem_2.5rem_minmax(0,1fr)]`)
|
||||
|
||||
## 步骤 7:自我审查
|
||||
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: agent-introspection-debugging
|
||||
description: Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Agent Introspection Debugging
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: coding-standards
|
||||
description: Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Coding Standards & Best Practices
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: deep-research
|
||||
description: Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Deep Research
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: documentation-lookup
|
||||
description: Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Documentation Lookup (Context7)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: e2e-testing
|
||||
description: Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
|
||||
group: 测试部
|
||||
lead: 项目经理
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# E2E Testing Patterns
|
||||
|
||||
@@ -2,6 +2,7 @@
|
||||
name: eval-harness
|
||||
description: Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
|
||||
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Eval Harness Skill
|
||||
|
||||
@@ -3,8 +3,8 @@ name: product-capability
|
||||
description: Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
|
||||
emoji: 📋
|
||||
color: purple
|
||||
group: 产品部
|
||||
lead: 产品总监
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Product Capability
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: security-review
|
||||
description: Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Security Review Skill
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: tdd-workflow
|
||||
description: Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Test-Driven Development Workflow
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
name: verification-loop
|
||||
description: "A comprehensive verification system for Claude Code sessions."
|
||||
group: ECC组
|
||||
---
|
||||
|
||||
# Verification Loop Skill
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: adr-drafting
|
||||
description: Creates new Architecture Decision Record (ADR) documents for significant architectural changes using a consistent template and repository-aware naming and storage guidance. Use when a user or agent decides on an architectural change, needs to document technical rationale, or wants to add a new ADR to the project history.
|
||||
allowed-tools: Read, Write, Edit, Glob, AskUserQuestion
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# ADR Drafting
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: api-design
|
||||
description: REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
|
||||
origin: ECC
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# API Design Patterns
|
||||
|
||||
@@ -3,8 +3,8 @@ name: auth-patterns
|
||||
description: Authentication and authorization patterns including JWT, OAuth2, session management, RBAC, token handling, and secure auth flows for web applications.
|
||||
tools: [Read, Write, Edit, Glob, Grep, Bash]
|
||||
model: sonnet
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# Security Review Skill
|
||||
|
||||
@@ -3,6 +3,7 @@ name: 自主优化架构师
|
||||
description: 智能系统治理专家,持续对 API 进行影子测试以优化性能,同时严格执行财务和安全护栏,防止成本失控。
|
||||
emoji: 🔄
|
||||
color: "#673AB7"
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# 自主优化架构师
|
||||
|
||||
@@ -3,6 +3,7 @@ name: 后端架构师
|
||||
description: 资深后端架构师,专精可扩展系统设计、数据库架构、API 开发和云基础设施。构建健壮、安全、高性能的服务端应用和微服务。
|
||||
emoji: ⚙️
|
||||
color: blue
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# 后端架构师智能体人格
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: backend-patterns
|
||||
description: Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
|
||||
origin: ECC
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# Backend Development Patterns
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: clean-architecture
|
||||
description: Provides implementation patterns for Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design in Python applications with FastAPI or Flask. Use when designing maintainable backends with separation of concerns, implementing repository patterns, creating entities/value objects/aggregates, or structuring domain logic independent of frameworks for testability.
|
||||
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# Clean Architecture, DDD & Hexagonal Architecture for Python
|
||||
|
||||
@@ -9,8 +9,8 @@ tools:
|
||||
- Grep
|
||||
- Bash
|
||||
model: sonnet
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# Code Reviewer
|
||||
|
||||
@@ -3,6 +3,7 @@ name: 代码库入职引导工程师
|
||||
description: 专业的开发者入职引导专家,帮助新工程师快速理解陌生代码库,通过阅读源码、追踪代码路径,只陈述基于代码的事实。
|
||||
emoji: 🧭
|
||||
color: teal
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# 代码库入职引导工程师
|
||||
|
||||
@@ -3,6 +3,7 @@ name: 数据工程师
|
||||
description: 专注于构建可靠数据管线、湖仓架构和可扩展数据基础设施的数据工程专家。精通 ETL/ELT、Apache Spark、dbt、流处理系统和云数据平台,将原始数据转化为可信赖的分析就绪资产。
|
||||
emoji: 📊
|
||||
color: orange
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# 数据工程师
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
name: database-migrations
|
||||
description: Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
|
||||
origin: ECC
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# Database Migration Patterns
|
||||
|
||||
@@ -3,6 +3,7 @@ name: 数据库优化师
|
||||
description: 数据库性能专家,专注于 Schema 设计、查询优化、索引策略和性能调优,精通 PostgreSQL、MySQL 及 Supabase、PlanetScale 等现代数据库。
|
||||
emoji: 🗄️
|
||||
color: amber
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# 🗄️ 数据库优化师
|
||||
|
||||
@@ -4,8 +4,8 @@ description: Expert database optimizer specializing in modern performance tuning
|
||||
risk: unknown
|
||||
source: community
|
||||
date_added: '2026-02-27'
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
## Use this skill when
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
name: debug
|
||||
description: Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# Debug
|
||||
|
||||
@@ -11,8 +11,8 @@ pipeline: [deep-dive, plan, autopilot]
|
||||
next-skill: plan
|
||||
next-skill-args: --consensus --direct
|
||||
handoff: .omc/specs/deep-dive-{slug}.md
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
<Purpose>
|
||||
|
||||
@@ -3,8 +3,8 @@ name: 工程部
|
||||
description: 管理组下属工程部门——负责方案评审、技术实施和工程交付,涵盖后端、前端、架构、DevOps、IoT 等全栈工程能力。
|
||||
emoji: 🛠️
|
||||
color: cyan
|
||||
group: 工程部
|
||||
lead: 项目经理
|
||||
group: 工程部
|
||||
---
|
||||
|
||||
# 工程部
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user