Defame1297andClaude Code
c52e351954
Scaffolds and revises apm instructions files, with a throwaway-package verification recipe because `apm compile --validate` always exits 0 and Claude Code drops `description`. Routed from forge and linked from apm-workflow's compile reference. Bumps kyberforge to 2.1.0 and the catalog to 0.5.2. Fixes #148 Co-Authored-By: Claude Code <[email protected]> Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi
1.4 KiB
source_keys
| source_keys | |
|---|---|
|
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.
-
From the package root, a real compile, never
--validate:apm compile --dry-run --target claudeResolve every warning it prints: missing
description, missingapplyTo, empty content, broken link, "Failed to parse". -
For a scoped rule, deploy it where nothing else can be overwritten:
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) -
The deployed file must open with
paths:listing the intended globs. No frontmatter block at all meansapplyTowas missing or did not parse: the rule would load in every session. -
To check the compiled root file instead, compile in that same clean directory before installing, or pass
--force-instructions; after an install,--target claudewrites nothing.
Delete the directory afterwards. Report only what was observed; Cursor's list-form globs and the Windsurf, Kiro and Antigravity runtimes stay unverified.