---
source_keys:
  - apm-cli-0-28-0-experiments
---

# Verifying a file in a throwaway package

Reached from `SKILL.md` Step 3. Run step 2 outside the repo: `apm install` writes `apm_modules/`, `apm.lock.yaml` and a rules directory, and install overwrites hand-authored rule files without warning.

1. From the package root, a real compile, never `--validate`:

   ```bash
   apm compile --dry-run --target claude
   ```

   Resolve every warning it prints: missing `description`, missing `applyTo`, empty content, broken link, "Failed to parse".

2. For a scoped rule, deploy it where nothing else can be overwritten:

   ```bash
   d=$(mktemp -d)
   printf 'name: scratch\nversion: 0.1.0\ntype: instructions\ntargets:\n  - claude\n' > "$d/apm.yml"
   mkdir -p "$d/.apm/instructions"
   cp <package-root>/.apm/instructions/<name>.instructions.md "$d/.apm/instructions/"
   (cd "$d" && apm install && cat .claude/rules/<name>.md)
   ```

3. The deployed file must open with `paths:` listing the intended globs. No frontmatter block at all means `applyTo` was missing or did not parse: the rule would load in every session.

4. To check the compiled root file instead, compile in that same clean directory *before* installing, or pass `--force-instructions`; after an install, `--target claude` writes nothing.

Delete the directory afterwards. Report only what was observed; Cursor's list-form `globs` and the Windsurf, Kiro and Antigravity runtimes stay unverified.