CSS 自定义属性 css-custom-properties
SkillSkillsMP
io.github.thedaviddias/Front-End-Checklist/css-custom-properties
审查样式表、组件样式与响应式行为，落实“用 CSS 自定义属性承载设计令牌”这一规则时使用。提出修复前要在各断点和交互状态下检查实际渲染布局。
source
“filesystem github context7 playwright” 共 6,480 个结果
io.github.thedaviddias/Front-End-Checklist/css-custom-properties
审查样式表、组件样式与响应式行为，落实“用 CSS 自定义属性承载设计令牌”这一规则时使用。提出修复前要在各断点和交互状态下检查实际渲染布局。
io.github.thedaviddias/Front-End-Checklist/css-grid
审查样式表、组件样式与响应式行为，落实“用 CSS Grid 做二维布局”这一规则时使用。提出修复前要在各断点和交互状态下检查实际渲染布局。
io.github.thedaviddias/Front-End-Checklist/css-print
审查样式表、组件样式与响应式行为，落实“包含打印样式表”这一规则时使用。提出修复前要在各断点和交互状态下检查实际渲染布局。
io.github.thedaviddias/Front-End-Checklist/css-file-size
排查页面加载缓慢、资源过大或渲染延迟，落实“优化 CSS 文件体积”时使用。在 DevTools、Lighthouse 或真实数据中确认实际瓶颈后再提改动建议。
io.github.thedaviddias/Front-End-Checklist/css-containment
审查样式表、组件样式与响应式行为，落实“用 CSS containment 限制重绘范围”这一规则时使用。提出修复前要在各断点和交互状态下检查实际渲染布局。
io.github.thedaviddias/Front-End-Checklist/css-at-property
实现动画渐变、涉及自定义属性取值的复杂 CSS transition，或构建类型化设计令牌系统（希望自定义属性误用能直接报错）时使用。
io.github.thedaviddias/Front-End-Checklist/mobile-testing
审查与“在真实移动设备和视口上测试”相关的 CI 覆盖、自动化检查或测试策略时使用。重点看规则是否被持续验证，而不只是写在文档里。
io.github.thedaviddias/Front-End-Checklist/typescript-strict-mode
在新建 TypeScript 项目、审计已有 tsconfig.json，或审查存在空引用错误或隐式 any 类型的代码时使用。
io.github.nodejs/node/v8-regression-testing
Use this skill when designing, writing, or minimizing regression tests (e.g., mjsunit) for V8 bug fixes
io.github.nodejs/node/workflow-gerrit-fix
Workflow for automatically fixing errors or addressing comments on a Gerrit CL requested by the user.
io.github.nodejs/node/v8-understanding
Guides the methodology for investigating V8 concepts, codebase structure, performance, memory, and architecture. MANDATORY to use whenever triaging bugs, investigating crashes, reading C++ files, analyzing compiler optimizations (Ignition, Maglev, TurboFan, Turboshaft), or doing static research on V8 subsystems. Essential for locating high-level design documents in the local docs/ directory before reading C++ code. Do not use for raw build commands or Git workflows.
io.github.nodejs/node/v8-workflow
Manages git task isolation and environment setup in V8. Use at the start of any new task or bug fix. Do not use for general C++ editing.
io.github.nodejs/node/trace_processor
Managing and querying Perfetto traces using the trace_processor MCP server.
io.github.nodejs/node/clangd-setup
Handles installation and configuration of clangd-mcp for V8. Use when clangd-mcp is missing or needs configuration for the current workspace. Do not use for general C++ editing.
io.github.wshobson/agents/k8s-manifest-generator
遵循最佳实践与安全标准，为 Deployment、Service、ConfigMap 与 Secret 生成生产就绪的 Kubernetes manifest。在生成 Kubernetes YAML 清单、创建 K8s 资源或实施生产级 Kubernetes 配置时使用。
io.github.wshobson/agents/gitops-workflow
使用 ArgoCD 与 Flux 实现 GitOps 工作流，达成自动化、声明式的 Kubernetes 部署与持续调谐。在落地 GitOps 实践、自动化 Kubernetes 部署或配置声明式基础设施管理时使用。
io.github.heygen-com/hyperframes/hyperframes-keyframes
当 HyperFrames 合成需要推近、拉出、缩放、改构图、Ken Burns 效果、运镜、视觉匹配/甩镜交接，或其他 seek-safe 的 2D/3D 关键帧时使用；也用于 GSAP、CSS keyframes、Anime.js、WAAPI、FLIP、路径、遮罩、SVG morph/draw、文字拖尾、3D 纵深，或 `hyperframes keyframes` 诊断。不要用于宽泛的场景策略、品牌设计、素材获取、字幕或一般视频规划。
io.github.affaan-m/ECC/mcp-dependency-review
Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers.
io.github.affaan-m/ECC/mcp-dependency-review
Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or other repo-scoped MCP config.
io.github.affaan-m/ECC/mcp-dependency-review
Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or other repo-scoped MCP config.
io.github.NousResearch/hermes-agent/unreal-mcp
自动化 Unreal Engine 编辑器的场景、Actor 与渲染操作。
io.github.asgeirtj/system_prompts_leaks/durable-test-collateral
Load the body before the first implementation edit for a bug fix or behavior change, or when the user or governing specification makes reusable tests a deliverable. It keeps the smallest focused test with the delivered project and updates coverage when behavior changes. Do not load for greenfield work unless reusable tests are explicitly required, behavior-preserving refactors, verification-only work, plan/review/explanation/documentation/formatting/generated-output-only work, explicit no-change or no-tool work, or when the user declines tests.
io.github.asgeirtj/system_prompts_leaks/plan
On an explicit planning request, always call `read_skill` for this skill before answering. Research first, then return one concise inline plan; do not create a plan file unless the user explicitly asks or a governing workflow requires one. Start and end the reply by saying this is not a special mode and `go` executes the plan; do not implement in the planning turn. For ordinary implement, build, fix, debug, or refactor requests, work directly. When an explicit plan divides work into separate diffs, commits, or PRs and the user asks to publish, preserve that split and tell the user before deviating.
io.github.asgeirtj/system_prompts_leaks/requirements-clarification
Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask one blocking outcome question or at most three coupled questions; wait. After the answer, load the body before write or delegation. Do not use for implement/build/fix/debug/refactor work when expected behavior is settled, plan/design deliverables owned by Plan, complexity/greenfield/integration alone, agent-owned technical choices, locally discoverable facts, reversible defaults, permission to begin, or stop/no-tool turns. Never re-ask supplied facts or turn clarification into refusal.