fec-legacy-web-standard

Maintain legacy JavaScript, jQuery, and server-rendered HTML/CSS codebases.

21|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/bovinphang/frontend-craft --skill fec-legacy-web-standard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fec-legacy-web-standard
Source: https://github.com/bovinphang/frontend-craft/tree/main/localized/zh-CN/skills/fec-legacy-web-standard
Command: npx skills add https://github.com/bovinphang/frontend-craft --skill fec-legacy-web-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

传统前端项目通常包含原生 JavaScript、jQuery、HTML/CSS,以及多页应用与服务端模板。本技能提供安全的维护流程,帮助团队在不重构现有架构的前提下进行改动与修复,确保长期可维护性。

Core Features & Use Cases

  • 安全维护旧栈:限定改动范围,避免全局污染与破坏现有行为。
  • 指导性流程:提出分步维护与回退策略,兼容现有代码风格。
  • 参考清单与示例:提供 legacy-patterns、检查清单等参考材料,推动一致性。

Quick Start

运行维护工作流并按步骤执行改动,确保改动可回滚且符合现有标准。

Frequently Asked Questions about fec-legacy-web-standard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely maintain legacy jQuery and vanilla JavaScript codebases?

Safely maintaining legacy jQuery and vanilla JavaScript involves limiting change scope, enforcing coding conventions, and guarding against global scope pollution to prevent breaks in existing multi-page application behaviors.

What is the best way to patch server-rendered HTML and CSS without a full rewrite?

Patching server-rendered HTML and CSS without a full rewrite requires applying staged migration strategies that define safe-change requirements, ensuring updates remain compatible with long-lived plugins and existing server-side templates.

How do I prevent XSS risks when updating old frontend multi-page applications?

Preventing XSS risks when updating old frontend multi-page applications involves following defined safe-change requirements and checklists that explicitly guard against global scope pollution and insecure data handling in vanilla JavaScript.

Can I migrate legacy frontend code to modern standards without breaking existing plugins?

You can migrate legacy frontend code without breaking existing plugins by using a staged migration approach that restricts modifications to defined safe-change boundaries, preserving the behavior of long-lived dependencies.

What coding conventions should I follow for legacy frontend code maintenance?

Legacy frontend code maintenance requires following coding conventions that match existing styles, utilizing reference checklists to drive consistency and ensure changes are fully reversible during staged migrations.