Skills de Claude Code · página 69

>

>

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree. Use when user wants to write or refine a specification document using adversarial development.

|

系统架构设计方法论，包含架构模式选择、系统分层、目录结构设计

数据模型和API设计方法论，包含ERD设计、数据字典、RESTful API规范

技术调研方法论，通过系统性调研和对比分析，为技术选型提供数据支持

后端API开发方法论，包括RESTful/GraphQL设计、请求验证、错误处理和安全实现

后端测试编写指南，包括单元测试、集成测试和E2E测试的编写方法和最佳实践

|

自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范

部署流程和CI/CD配置，确保安全可靠的部署

监控告警配置，确保系统稳定运行

前端组件开发方法论，包括组件设计原则、状态管理、样式实现和性能优化

前端测试编写指南，包括单元测试、集成测试和E2E测试的编写方法和最佳实践

竞品调研和分析方法，通过系统性分析竞品的功能、体验和策略，发现差异化机会

产品需求文档(PRD)的标准编写格式和内容要求，确保输出完整、清晰、可执行的产品文档

深度挖掘用户需求的方法论，通过5W2H追问和需求分层模型，识别显性、隐性、潜在和惊喜需求

从CEO/战略视角进行商业价值评审，评估市场契合度、ROI、竞争优势、风险和战略对齐

用户研究方法，通过用户画像和用户旅程图，深入理解目标用户的特征、需求和行为

Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧

测试执行方法，包含测试框架检测、测试运行、结果解析

测试策略和测试金字塔原则，定义单元测试、集成测试、E2E测试的分布和覆盖要求

风险评估方法，识别项目风险并制定应对策略

任务拆解方法，将需求拆解为可执行的开发任务

检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链

代码审查方法，包含审查清单、常见问题、最佳实践

技术规范和最佳实践，确保代码质量和一致性

UI组件规范，定义按钮、输入框、卡片等基础组件的变体、尺寸、状态

设计系统规范，包含颜色、字体、间距、圆角、阴影、动效等基础设计token

设计变体模式，产出2-3个设计方案及 tradeoff 分析，供用户选择后确定最终方案

交互规范，定义加载状态、空状态、反馈机制、动效、无障碍等交互细节

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

Comprehensive architecture patterns, methodologies, quality frameworks, and evaluation methods for solution architects. Load when designing system architecture or selecting patterns.

Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.

Domain-specific authoritative source databases, search strategies by topic category, and source freshness rules

BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation