Run any Skill in Manus with one click

legacy-conventions

Stars4

Forks0

UpdatedMarch 28, 2026 at 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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

MrWaip

MrWaip/svelte-rs-2

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.

More from this repository

same repository

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.