搜索「3」的结果

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.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.

io.github.asgeirtj/system_prompts_leaks/taste

Mandatory preflight for web frontend visual design. If available, call read_skill for bundled:taste before the first frontend create or edit tool call whenever creating or visually styling a human-viewed web page, component, app, dashboard, or interactive report. Do not load it for non-visual frontend logic or machine-only HTML. If unavailable, continue without warning. Negative constraints only; user requests and other explicit styles still win.

io.github.asgeirtj/system_prompts_leaks/python-env

Setting up or installing into a Python environment. One rule applies whether or not you read the body - the environment belongs with the project, so create it inside the project directory (.venv) or let uv manage it, and never in a scratch directory like /tmp and never by forcing an install into the system interpreter. Load the body before creating a virtualenv, choosing an installer, or writing run instructions for a Python project.

io.github.asgeirtj/system_prompts_leaks/forget

Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely means cancel the current task.

io.github.asgeirtj/system_prompts_leaks/pdf

Build, revise, or manipulate a fixed-layout PDF (report, guide, one-pager, printable document). Use whenever a build task's artifact kind is pdf, a document build's output format is pdf, or the task reads, merges, splits, crops, or fills an existing PDF, including fillable AcroForms. Covers authoring the print-CSS HTML source, rendering, the geometry and validation gates, existing-PDF manipulation and form filling, and delivery under workspace/your_files.

io.github.asgeirtj/system_prompts_leaks/granola

Search and read Granola meeting notes and transcripts through Granola's OAuth-backed MCP server.

io.github.asgeirtj/system_prompts_leaks/muse_db

Inspect database-backed Muse records for diagnosis and cross-table tracing when purpose-built product tools do not expose the needed state.

io.github.asgeirtj/system_prompts_leaks/lovable

Read, create, edit, and deploy web apps and projects in Lovable. Use to turn a product brief into a working website or prototype, inspect existing project code, update pages and features, and publish changes through Lovable's official MCP server.

io.github.asgeirtj/system_prompts_leaks/vercel

Inspect and manage the user's Vercel websites, web apps, projects, and deployments. Use to read build and runtime logs, investigate production errors and failed deployments, check deployment status, and deploy projects through Vercel's official MCP server.

io.github.asgeirtj/system_prompts_leaks/document

Create, read, edit, or manipulate Word documents (.docx) and Word templates (.dotx). Use whenever a build task's artifact kind is document with the default docx output, or the task mentions a Word doc, .docx, or .dotx, extracts or reorganizes content from one, inserts or replaces images, does find-and-replace in one, or works with tracked changes (redlines) or comments. Covers python-docx generation, raw OOXML editing of existing files, document structure and formatting, and render verification. Not for PDFs, spreadsheets, or Google Docs.

io.github.pytorch/pytorch/scrub-issue

获取、分析、复现并精简 GitHub issue 的复现步骤。仅在用户要求验证某个 GitHub issue 是否可复现、精简其复现用例、分析 bug 报告，或为可复现性对 issue 做审查/分诊时使用。不适用于没有对应 GitHub issue 的独立复现请求。

io.github.pytorch/pytorch/ci-metrics

查询 PyTorch CI、GitHub Actions、HUD、Grafana 与基础设施指标。当用户询问 CI 耗时、任务失败、排队时长、工作流趋势、runner 健康度、看板数据或 PyTorch 基础设施指标时使用。

io.github.pytorch/pytorch/fix-issue

复现并定位 PyTorch GitHub issue 报告的 bug，在本地工作区实现修复。当用户要求修复 PyTorch GitHub issue 时使用。

io.github.pytorch/pytorch/triaging-issues

对 GitHub issue 进行分诊：路由到值班团队、打标签并关闭咨询类问题。在处理新的 PyTorch issue 或被要求分诊 issue 时使用。