원클릭으로 Manus에서 모든 스킬 실행

legacy-conventions

스타4

포크0

업데이트2026년 3월 28일 18:14

MUST consult before writing any code related to Svelte 4 legacy features. Contains mandatory naming conventions, doc-comment format, and isolation rules for legacy code. Use this skill whenever touching on:directive, bind:this legacy syntax, Svelte 4 deprecated features, code marked LEGACY(svelte4), or when porting/implementing any feature that has both a Svelte 5 and a Svelte 4 variant. Failure to follow these conventions creates tech debt that blocks future cleanup.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

MrWaip

MrWaip/svelte-rs-2

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Legacy Feature Conventions (Svelte 4)

Legacy Svelte 4 syntax (deprecated in Svelte 5, scheduled for removal in Svelte 6) is ported with isolation in mind so it can be cleanly deleted later.

Conventions

Legacy suffix in all type/function names: OnDirectiveLegacy, gen_on_directive_legacy, build_legacy_event_handler.
LEGACY(svelte4): doc-comment on every struct, enum variant, and top-level function:
```
/// LEGACY(svelte4): on:directive syntax. Deprecated in Svelte 5, remove in Svelte 6.
pub struct OnDirectiveLegacy { ... }
```
Short inline comments use the same tag: // LEGACY(svelte4): on:directive handled separately.
Easy removal — keep legacy code in self-contained blocks/functions. Avoid mixing legacy logic into non-legacy code paths. Ideal: grep LEGACY(svelte4) -> delete all hits -> compile -> done.

이 저장소의 다른 Skills

같은 저장소

add-test

MrWaip/svelte-rs-2

Use whenever adding an e2e compiler-output test (our JS vs the reference compiler) — a new cluster case under `tasks/compiler_tests/`.

2026-07-064

dig-better

MrWaip/svelte-rs-2

🧩 PARITY · Turn one divergence from the Original into a test per affected case (does not fix).

2026-07-064

required

MrWaip/svelte-rs-2

Use when starting any compiler task or session before touching parser/analyze/transform/ast/codegen/css/diagnostics code, before proposing a design or writing code, and when the task grows into a new layer and you need its PRD invariants.

2026-07-064

verdict-directed

MrWaip/svelte-rs-2

🔪 SDT · verdict-directed review of backend codegen/transform. Use when auditing codegen/transform for smart-analyzer / dumb-codegen violations, or when porting a transform/codegen visitor from the Original.

2026-07-064

write-unit-test

MrWaip/svelte-rs-2

The required unit-test format for `crates/**/src/**` — use when writing or reviewing a Rust `#[test]`, a test helper, or an `assert_*`. Not for `tasks/compiler_tests/` (use add-test) or `tasks/diagnostic_tests/` (use add-diagnostic-test).

2026-07-064

writing-docs

MrWaip/svelte-rs-2

PRD editorial standard for docs/. Use when writing a new PRD, extending one, or reviewing changes under docs/ — and when another skill needs the PRD rules.

2026-07-064

name	legacy-conventions
description	MUST consult before writing any code related to Svelte 4 legacy features. Contains mandatory naming conventions, doc-comment format, and isolation rules for legacy code. Use this skill whenever touching on:directive, bind:this legacy syntax, Svelte 4 deprecated features, code marked LEGACY(svelte4), or when porting/implementing any feature that has both a Svelte 5 and a Svelte 4 variant. Failure to follow these conventions creates tech debt that blocks future cleanup.
paths	["*/.rs"]

Legacy Feature Conventions (Svelte 4)

Legacy Svelte 4 syntax (deprecated in Svelte 5, scheduled for removal in Svelte 6) is ported with isolation in mind so it can be cleanly deleted later.

Conventions

Legacy suffix in all type/function names: OnDirectiveLegacy, gen_on_directive_legacy, build_legacy_event_handler.
LEGACY(svelte4): doc-comment on every struct, enum variant, and top-level function:
```
/// LEGACY(svelte4): on:directive syntax. Deprecated in Svelte 5, remove in Svelte 6.
pub struct OnDirectiveLegacy { ... }
```
Short inline comments use the same tag: // LEGACY(svelte4): on:directive handled separately.
Easy removal — keep legacy code in self-contained blocks/functions. Avoid mixing legacy logic into non-legacy code paths. Ideal: grep LEGACY(svelte4) -> delete all hits -> compile -> done.