GitHub
design
方案设计阶段详细规则；进入方案设计时读取；包含方案构思、任务拆解、风险评估、方案包创建
Skills IA DevOps
Découvrez les skills DevOps, comparez leurs dépôts et consultez leurs instructions.
Catégories: DevOps
DevOps Effacer les filtres
Explorer
GitHub
problem-solution-dialogue
Use when 需要讨论方案权衡/架构选型/需求澄清，且目标/约束/成功标准不清或存在多解权衡时。
GitHub
deep-analysis
Execute high-density analysis on complex ideas/tasks. Move from 'Vague' to 'Verified' by producing: constraints -> core modules -> facts vs assumptions -> ASCII flow maps (boundary + critical path) -> latticewo...
GitHub
helloagents
用于处理软件开发/维护类请求（常见说法包括但不限于：修改、修复 bug、新增功能、开发模块、重构/优化、补充/编写/运行测试、生成并执行计划）。会自动判定是问答/改动/命令（~auto/~plan/~exec/~init），并选择咨询问答/微调...
GitHub
decomposing-complex-problems
Deconstructs complex problems using the 'Polymath Investor' framework with a 5-step cognitive chain (First Principles → Modular Isolation → Pareto Filtering → Cross-Domain Mapping → Dynamic Zooming). Use when a...
GitHub
nexus-prompt-engineer
4-D prompt engineering assistant that transforms vague requirements into high-precision prompts through guided interaction. Trigger when users need to: (1) craft high-quality system prompts, (2) optimize existi...
GitHub
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
GitHub
hello-auditkit
Use this skill to audit, review, validate, or check the quality of AI assistant configurations including prompt text, prompt files, skills (SKILL.md), plugins, MCP servers, agents, hooks, memory files (AGENTS.m...
GitHub
analyze
需求分析阶段详细规则；进入需求分析时读取；包含需求评分、追问逻辑、代码分析步骤
GitHub
multi-lens-thinking
Use when facing complex problems, making decisions, seeking creative solutions, or when single-perspective thinking feels limiting. Triggers include "how should I think about this", "what am I missing", "need f...
GitHub
deep-analysis
Execute high-density architectural analysis on user ideas. Move from 'Vague' to 'Verified' using a 5-step logic chain: Calibration → Decomposition → Excavation → Re-Architecting → Inversion. This skill should b...
GitHub
develop
开发实施阶段详细规则；进入开发实施时读取；包含执行流程、代码规范、一致性审计、方案包迁移
GitHub
round-table-analysis
Deep pre-execution analysis framework using four philosophers (Socrates, Aristotle, Feynman, Drucker) for structured critical thinking before implementing plans. Use when users need to thoroughly understand a t...
GitHub
data-fetching
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, axios, React Query, SWR, error handling, caching strategies, offline support.
GitHub
upgrading-expo
Guidelines for upgrading Expo SDK versions and fixing dependency issues
GitHub
deployment
Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes
GitHub
cicd-workflows
Helps understand and write EAS workflow YAML files for Expo projects
GitHub
tailwind-setup
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
GitHub
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
GitHub
api-routes
Guidelines for creating API routes in Expo Router with EAS Hosting
GitHub
go-testing
Write unit and integration tests for Go services. Use when creating tests, test helpers, mocks, fuzz tests, or benchmarks in Go projects.
GitHub
go-api
Create a new Go API service. Use when starting a new Go service, API project, or microservice. Generates complete boilerplate with local development and observability.
GitHub
systematic-debugging
Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.
GitHub
project-plan
Creates project plan documents for tracking implementation work. Use when the user asks to create a project plan, implementation plan, or wants to document a new feature or refactoring task.
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é.