pricing-governance
Use to run pricing councils, track decisions, and enforce approval workflows.
Découvrez les skills Blockchain, comparez leurs dépôts et consultez leurs instructions.
Use to run pricing councils, track decisions, and enforce approval workflows.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web appl...
Systematically investigate user-reported bugs and issues, generating detailed reports with root cause analysis, recommended fixes, symptom details, flow diagrams, error message mappings, code analysis, and prio...
在写作前验证选题是否值得写。当用户说"帮我调研这个选题""这个话题值得写吗""分析一下这个选题"时调用。提供热点扫描、爆款拆解、痛点验证和选题打分,确保不写"自嗨式"文章。
在文章发布前进行最终评审。当主编审稿完成后、文章准备发布时调用。通过"发布前5问"评审清单,从读者视角验证文章是否值得发布,给出通过/不通过的结论和具体修改建议。
深入互联网搜集与写作主题相关的素材、数据、案例、前沿动态及多元视角。为创作提供扎实的事实支撑,辅助写作需求澄清及大纲构建。
模拟今日头条读者测试文章。作为最后的守门员,在发布前评审通过后使用。当用户说"模拟读者"、"今日头条测试"、"最终检验"、"读者会怎么看"时调用。
当用户需要学习某种风格、提取写作配方、建立风格库或模仿特定作者时调用。深度解构文本的15个维度,包括作者画像、思维内核、创作路径、互动设计等,建模为可精准复制的风格文件。触发词:风格建模、提取风格、学习风格、模仿...
当用户完全没有写作灵感、不知道写什么时调用。通过热点扫描、个人资产盘点、竞品分析生成候选选题,并进行五问验证和具象化,最终输出可立即动笔的选题执行方案。触发词:不知道写什么、帮我想个选题、有什么值得写的、给我推...
Comprehensive PR analysis with security review, code quality assessment, and automatic improvements. Use when reviewing PRs for security issues, performance optimizations, or best practices violations. Provides...
Create or update Pull Requests with AI-generated descriptions, mermaid diagrams, and file walkthroughs. Integrates with SDD specs. Use --update flag to modify existing PRs.
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs qualit...
Use when writing database access code, creating schemas, or managing transactions with PostgreSQL - enforces transaction safety with TX_ naming, read-write separation, type safety for UUIDs/JSONB, and snake_cas...
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following brainstorming before coding, and creating TodoWrit...
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skil...
Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation
Use when writing TypeScript code, reviewing TS implementations, or making decisions about type declarations, function styles, or naming conventions - comprehensive house style covering type vs interface rules,...
Use when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakiness
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists; when design makes assumptions about file locations, struct...
Use when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testing
Use when invalid data causes failures deep in execution - validates at every layer data passes through to make bugs structurally impossible rather than temporarily fixed
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.