性能优化
io.github.addyosmani/agent-skills/performance-optimization
跨前端、后端、查询与数据库优化应用性能。在存在性能指标要求、怀疑性能回归、需要改善 Core Web Vitals 或加载时间、需要修复 N+1 查询模式,或剖析暴露瓶颈时使用。
“Frontend Development” 共 684 个结果
io.github.addyosmani/agent-skills/performance-optimization
跨前端、后端、查询与数据库优化应用性能。在存在性能指标要求、怀疑性能回归、需要改善 Core Web Vitals 或加载时间、需要修复 N+1 查询模式,或剖析暴露瓶颈时使用。
io.github.asgeirtj/system_prompts_leaks/control-browser
Use when opening, navigating, inspecting, testing, clicking, typing, filling, screenshotting, or verifying web pages and local HTTP targets (localhost, 127.0.0.1, ::1) inside ZCode, including browser/web-UI automation, rendered-page scraping, frontend checks, and visible page-state reading. Prefer this over Computer Use for anything that stays inside a web page, unless the user explicitly asks for Computer Use. Main agent only.
io.github.asgeirtj/system_prompts_leaks/web-gui-tester
Use the browser automation tooling available in the session to test web frontends interactively in a purely GUI-based, black-box manner: simulate real user clicks, text input, scrolling, and other actions; use screenshots for visual verification and read-only DOM inspection for cross-validation; and produce a final test report. Suitable for verifying whether web functionality works correctly, reproducing frontend bugs, checking interaction feedback and layout styling, or conducting exploratory testing of a page. Use this skill when the user asks to test a webpage/frontend feature, verify UI behavior, reproduce a page bug, or provides only a URL and asks you to "test it."
io.github.Stirling-Tools/Stirling-PDF/feature-walkthrough
端到端讲解当前分支的完整逻辑与流程,让毫无前置知识的人也能理解、审查并复现。从分支 diff 界定变更范围,追踪其触达的每一层流程(前端工具/hook/组件、Java controller/service/endpoint、Python 引擎、配置、i18n、测试),产出带 Mermaid 图(时序/流程/架构)、可点击引用的带注释文件地图、前后行为对比、涉及 UI 时的截图、「本地试跑」章节与边界情况/风险的自包含走查文档。当被要求做功能或分支走查、「解释这个分支做了什么」、设计/逻辑说明、PR 审查者上手或交接文档时使用。加 --html 可同时输出渲染的 HTML 版;--no-screens 跳过截图。
io.github.Stirling-Tools/Stirling-PDF/ui-walkthrough
对当前分支功能做完整的 UI 调查。枚举每个视图与状态(空态、有数据、加载、错误、每个对话框/菜单/面板、响应式断点、浅色+暗色+RTL),用内置 Playwright 工装捕获,汇总为带全局明暗切换滑杆的单图 HTML 走查,随后跑两轮审查:视觉/一致性(对齐、间距、专业感、明暗一致、对比度、截断)与 UX/易用性(流程、可发现性、可供性、空态/错误态、预期)。当被要求做 UI 走查、截图审查、设计或 QA 巡检、「找出可以更易用/更好的地方」或前端工作合并前使用。加 --fix 自动应用安全的前端修复并重新捕获;--theme 限定主题;--no-rtl 跳过 RTL。
io.github.alirezarezvani/claude-skills/engineering-skills
工程团队技能包的索引,支持 Claude Code、Codex、Gemini CLI、Cursor、OpenClaw 及另外 6 种工具。涵盖架构、前端、后端、QA、DevOps、安全、AI/ML、数据工程、Playwright、Stripe、AWS、MS365(仅 stdlib Python 工具)。用于浏览或选择工程团队角色技能——只加载所需的单个专家 SKILL.md,切勿批量加载整个技能包。
io.github.microsoft/vscode/project-setup-info-local
帮助用户在 VS Code 工作区中创建完整项目结构的全面设置步骤;本工具面向整体项目的初始化与脚手架搭建,而非创建单个文件。适用:用户要从零创建完整新项目;搭建整个项目框架(TypeScript 项目、React 应用、Node.js 服务等);初始化具备完整结构的 Model Context Protocol(MCP)服务器;按规范脚手架创建 VS Code 扩展;设置 Next.js、Vite 或其他框架项目;用户要求新项目、创建工作区或设置某框架项目;需要建立含依赖、配置文件与目录结构的完整开发环境。不适用:创建单个文件或少量代码片段;向已有项目添加单个文件;修改既有代码库;用户要求创建一个文件或添加一个组件;简单代码示例或演示;调试。
io.github.streamlit/streamlit/checking-changes
在提交前通过格式、lint、类型与单元测试检查来校验所有代码改动。在完成(Python)后端或(TypeScript)前端改动后、即将提交或结束工作会话前使用。
io.github.addyosmani/agent-skills/api-and-interface-design
指导稳定的 API 与接口设计。在设计 API、模块边界或任何公共接口时使用;在创建 REST 或 GraphQL 端点、定义模块间类型契约、确立前后端边界时使用。
io.github.rtk-ai/rtk/tdd-rust
RTK filter 开发的 TDD 流程,以 Rust 惯用法执行红-绿-重构。使用真实 fixture、token 节省断言和 insta 快照测试。新 filter 实现时自动触发。
io.github.affaan-m/ECC/docker-patterns
Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.
io.github.thedaviddias/Front-End-Checklist/contract-testing
为前后端 API 边界搭建集成测试、评估两个服务能否独立安全部署,或用契约测试替换缓慢的端到端测试时使用。
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.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.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.affaan-m/ECC/springboot-tdd
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
io.github.affaan-m/ECC/git-workflow
Git workflow patterns including branching strategies, commit conventions, keeping history clean and readable, tidying local commits before merging, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, cleaning up history before a pull request, deciding merge versus rebase, or resolving conflicts.
io.github.affaan-m/ECC/coding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.
io.github.affaan-m/ECC/contract-first
Coordinate frontend/backend or service-to-service work through one authoritative machine-checkable contract (OpenAPI, AsyncAPI, Protocol Buffers, or JSON Schema), with generated consumer types and contract-verified integration. Use when parallel consumer and provider work must evolve an API or event schema without field drift, mock/production shape mismatch, or one side silently redefining the interface.
io.github.affaan-m/ECC/quarkus-tdd
Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.
io.github.n8n-io/n8n/experiments
指导在 packages/frontend/editor-ui 中开展实验的工作。在创建、扩展、接线、测试、评审或下线 editor-ui 实验,以及 PostHog 特性开关、实验 key 索引、变体、store/composable、实验持久化状态或实验埋点时使用。
io.github.affaan-m/ECC/eval-harness
面向 Claude Code 会话的正式评估框架,落实评估驱动开发(EDD)原则。当 Claude Code 工作流在获得信任或被修改前需要正式评估时使用。
io.github.affaan-m/ECC/tdd-workflow
在编写新功能、修复 bug 或重构代码时使用此 skill。强制推行测试驱动开发,覆盖率不低于 80%,涵盖单元、集成与 E2E 测试。
io.github.affaan-m/ECC/contract-first
适用于多个消费方与提供方需要共同演进 API 或事件模式,且要避免字段漂移、集成意外,或某一侧擅自重新定义接口的场景。