# Layerkit Deletion First

> Deletion-first change discipline for Layerkit work. Use before adding code, files, exports, docs, tests, or abstractions; during heal/integration updates; and whenever Codex should prefer modifying or deleting existing code over additive implementation.

- **Type:** Skill
- **Install:** `agentstack add skill-hariharapanigrahy-layerkit-layerkit-deletion-first`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [hariharapanigrahy](https://agentstack.voostack.com/s/hariharapanigrahy)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [hariharapanigrahy](https://github.com/hariharapanigrahy)
- **Source:** https://github.com/hariharapanigrahy/layerkit/tree/main/skills/layerkit-deletion-first

## Install

```sh
agentstack add skill-hariharapanigrahy-layerkit-layerkit-deletion-first
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# layerkit-deletion-first

Use this skill before implementation work, especially before `layerkit-source-edit-client` edits production datalayer code.

Before adding code, identify existing code, docs, tests, fixtures, and package surfaces that can be removed or rewritten.

Before a large deletion/rewrite or strategic redirect, prove the new direction with one small passing gate: an eval, end-to-end QA check, contract-heal case, or before/after acceptance test.

## Protocol

1. Identify existing code, docs, tests, fixtures, scripts, exports, commands, and shims that can be removed or rewritten.
2. Prefer modifying or deleting existing code over adding files.
3. Do not add a new abstraction until the existing abstraction has been inspected and cannot reasonably change.
4. For every new file, function, export, command, fixture, or skill, state what it replaces.
5. If it replaces nothing, justify why the expansion is necessary.
6. Target net-negative or near-neutral LOC unless functionality truly expands.
7. Before a strategic redirect or large deletion/rewrite, define what must pass, the proof artifact, and the fallback if validation fails; record the proof step before continuing.
8. Keep tests proportional to the implementation size; release hardening must cover client-package edit paths, mapping semantics, deletion-first behavior, and CI/eval gates touched by the change.

## Deletion Pass

Check these surfaces before adding:

- stale demos, design notes, launch scripts, sample-only assets
- legacy wrappers and compatibility aliases not required by public API
- tests for removed behavior
- duplicated command paths or old workflow names
- unused exports, fixtures, scripts, generated output, and package contents
- docs that describe non-current product paths

For heal/integration work, preserve only the spine:

`API spec/doc -> contract drift -> map/proposal update -> privacy/checker -> production datalayer integration -> client package verification`

Move required examples into `evals/fixtures`; delete demo/docs packaging around them.

## Final Report

Report:

- lines added/deleted and net delta
- files deleted
- new files/functions/exports and what each replaces
- legacy surfaces intentionally kept and why
- outcome checkpoints: what passed, proof artifact, fallback used or available
- tests/gates run, including any package-level fixture, judge, release checklist, or before/after behavior used as proof
- proof step for any strategic redirect

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [hariharapanigrahy](https://github.com/hariharapanigrahy)
- **Source:** [hariharapanigrahy/layerkit](https://github.com/hariharapanigrahy/layerkit)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-hariharapanigrahy-layerkit-layerkit-deletion-first
- Seller: https://agentstack.voostack.com/s/hariharapanigrahy
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.