清理注释 clean-up-comments
io.github.thedaviddias/Front-End-Checklist/clean-up-comments
审查与“在生产环境移除注释和调试代码”相关的模板、渲染 HTML 或共享组件时使用。校验最终面向浏览器的标记,而不只是框架侧的源码抽象。
“Python Code” 共 4,226 个结果
io.github.thedaviddias/Front-End-Checklist/clean-up-comments
审查与“在生产环境移除注释和调试代码”相关的模板、渲染 HTML 或共享组件时使用。校验最终面向浏览器的标记,而不只是框架侧的源码抽象。
io.github.thedaviddias/Front-End-Checklist/avoid-eval
审查与“绝不使用 eval() 或不安全的动态代码执行”相关的脚本、客户端组件、bundle 或运行时行为时使用。同时检查源码与浏览器执行路径,让修复命中真正的瓶颈或缺陷。
io.github.thedaviddias/Front-End-Checklist/back-forward-cache
审查导航性能、浏览器生命周期事件或内存恢复行为时使用。检查真实的浏览器生命周期与恢复路径,而不是只看静态代码模式。
io.github.thedaviddias/Front-End-Checklist/no-unchecked-indexed-access
审计 tsconfig.json 是否缺少安全标志、审查数据处理流水线中用到数组索引访问的代码,或排查 TypeScript 未捕获的运行时 undefined 错误时使用。
io.github.thedaviddias/Front-End-Checklist/no-explicit-any
审查 TypeScript 文件的类型安全回退、评审处理外部数据的函数,或代码库中存在 @typescript-eslint/no-explicit-any 的 ESLint 警告时使用。
io.github.thedaviddias/Front-End-Checklist/typescript-strict-mode
在新建 TypeScript 项目、审计已有 tsconfig.json,或审查存在空引用错误或隐式 any 类型的代码时使用。
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.QwikDev/qwik/qwik-core-development
用于修改或审阅 packages/qwik 下的 Qwik 核心包代码,尤其是响应式原语、信号、VNode、cursor 行为、QRL,以及面向 optimizer 的运行时行为,或 Qwik 核心测试。
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/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.addyosmani/agent-skills/security-and-hardening
加固代码以抵御漏洞。在审计输入处理逻辑、处理用户输入/认证/数据存储/外部集成,或检查登录流程是否符合 OWASP Top Ten 时使用。在构建任何接收不可信数据、管理用户会话或对接第三方服务的功能时使用。在审计依赖已知漏洞、分诊包管理器审计结果或评估新包供应链风险时使用。涉及个人数据或隐私合规(GDPR、CCPA)时使用。
io.github.Jeffallan/claude-skills/devops-engineer
编写 Dockerfile、配置 CI/CD 流水线、撰写 Kubernetes manifest,并生成 Terraform/Pulumi 基础设施模板。处理部署自动化、GitOps 配置、事故响应 runbook 与内部开发平台工具。在搭建 CI/CD 流水线、应用容器化、管理基础设施即代码、部署到 Kubernetes 集群、配置云平台、自动化发布或响应生产事故时使用。涉及流水线、Docker、Kubernetes、GitOps、Terraform、GitHub Actions、值班响应或平台工程时调用。
io.github.The-Vibe-Company/quivr/mermaid-diagrams
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
io.github.coreyhaines31/marketingskills/sms
当用户想规划、搭建或优化短信/MMS 营销时使用,包括欢迎流程、购物车挽回、购后触达、流失挽回、促销群发或验证码类事务短信。用户提到 SMS marketing、text message campaigns、SMS sequence、SMS automation、abandoned cart text、post-purchase SMS、Klaviyo SMS、Postscript、Attentive、Twilio、A2P 10DLC、TCPA、SMS compliance、short code、toll-free SMS、MMS campaign、“要不要做短信”或“SMS vs email”等场景时也适用。邮件序列见 emails,短信文案框架见 copywriting,采集手机号的弹窗见 popups。
io.github.moeru-ai/airi/stage-tamagotchi-godot-csharp
仅在 engines/stage-tamagotchi-godot 目录内工作时套用该引擎本地的 C# 开发方法与代码风格,包括其 .cs 文件、.csproj、引擎本地 .editorconfig 与 Godot 特有的 C# 结构决策。不用于 TypeScript、Electron、渲染层代码、共享工作区配置、仓库级 C# 约定,或 engines/stage-tamagotchi-godot 之外的任何文件。
io.github.deepseek-ai/deepseek-harness/dsh-find-simplifications
Find evidence-backed simplifications in DeepSeek Harness code, APIs, configuration, tests, and prose; write or consolidate proposals, identify small inline cleanups, or assess simplifications from another branch. Use for removing dead, duplicated, speculative, or unnecessarily maintained behavior and infrastructure.
io.github.coollabsio/coolify/infer-conventions
Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.
io.github.coollabsio/coolify/laravel-best-practices
在编写、审查或重构 Laravel PHP 代码时使用。包括创建或修改控制器、模型、迁移、表单请求、策略、任务、定时命令、服务类与 Eloquent 查询。涉及 N+1 与查询性能、缓存策略、授权与安全模式、校验、错误处理、队列与任务配置、路由定义和架构决策时触发。也用于 Laravel 代码审查及将现有 Laravel 代码重构至最佳实践。覆盖一切 Laravel 后端 PHP 代码模式的任务。
io.github.modelcontextprotocol/servers/local-dev
Install, build and run a server from this checkout. Use when starting a server locally over stdio, SSE or Streamable HTTP; when pointing npx, uvx or an MCP client config at the local build; when a running server still shows old code, or dist is missing; when setting up a git worktree; or when adding an overrides pin.
io.github.affaan-m/ECC/mybatis-patterns
MyBatis and MyBatis-Spring patterns for mapper design, XML and annotation SQL, result mapping, dynamic SQL safety, transactions, batching, pagination, and query performance. Use when building or reviewing Java persistence code with MyBatis, Spring Boot, MyBatis-Spring, or MyBatis-based legacy applications.
io.github.logseq/logseq/libs
使用 `@logseq/libs` SDK(TypeScript/JavaScript,iframe/shadow 沙箱)构建、调试或审查 Logseq 插件。适用于编写插件入口代码、注册 slash/命令/UI 项、provideUI/provideStyle/provideModel、设置 schema、macro renderer、DB 图的属性与标签、Datascript/DSL 查询、实验性 API、主题插件,或本包生成的 `logseq/*` CLJS facade。
io.github.affaan-m/ECC/kotlin-patterns
Idiomatic Kotlin patterns, best practices, and conventions for building robust, efficient, and maintainable Kotlin applications with coroutines, null safety, and DSL builders. Use when writing or reviewing Kotlin code and idiomatic structure or null safety is in question.
io.github.affaan-m/ECC/rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications. Use when writing or reviewing Rust code and ownership, error handling, traits, or concurrency is in question.
io.github.affaan-m/ECC/dotnet-patterns
Idiomatic C# and .NET patterns, conventions, dependency injection, async/await, and best practices for building robust, maintainable .NET applications. Use when writing or reviewing C# / .NET code — DI, async, or general conventions.