feat(kyberforge): add instructions-author skill for .apm/instructions files

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
This commit is contained in:
Defame1297andClaude Code committed 2026-10-01 06:46:39 +00:00
1 parent 529ed31cef
commit c52e351954
20 files changed
+719 -16

No files matched your search

@@ -4,12 +4,14 @@ source_keys:
- context7-websites-code-claude
---
# Routing a skill or agent to its author skill
# Routing a skill, agent or instructions file to its author skill
Reached from `SKILL.md` Step 2 when the classified artifact is a skill or an agent/subagent
definition. Route a skill to `skill-author` and an agent to `agent-author`. The two branches
differ on the author skill only — both verify the result with `factory-audit`, which detects the
artifact type itself — and everything below applies to both.
Reached from `SKILL.md` Step 2 when the classified artifact is a skill, an agent/subagent
definition or an instructions file. Route a skill to `skill-author`, an agent to `agent-author` and
an instructions file to `instructions-author`. The branches differ on the author skill only, and
everything below applies to all three — except that `factory-audit` has no instructions flow yet, so
an instructions file is verified by `instructions-author`'s own throwaway-package check and the
clean-context rerun below is skipped for it.
## Gotcha: `context: fork` is not `/fork`
@@ -7,8 +7,8 @@ source_keys:
Reached from `SKILL.md` Step 3 after a route has finished. A skill route always lands here:
`skill-author` moves only a skill's own `metadata.version`, which is not the package manifest's
number, so the package version is still behind when it reports done. `agent-author` bumps the
resolved package's `apm.yml` itself at plugin/APM scope, and `apm-workflow`'s configure flow
number, so the package version is still behind when it reports done. `agent-author` and `instructions-author` bump the
resolved package's `apm.yml` themselves (`agent-author` at plugin/APM scope), and `apm-workflow`'s configure flow
carries the same policy — read those routes' output before acting here, because a second bump for
one change is wrong.