| name | my-skill |
| description | PLACEHOLDER — do not invoke. This folder exists only so `apm install` has something to resolve during workshop setup. Your real skill belongs in a NEW folder under .apm/skills/<your-skill>/, generated by your harness from a Genesis design. See docs/tracks/. |
| license | UNLICENSED |
| allowed-tools | [] |
my-skill — placeholder (do NOT edit)
🚫 Don't fill this file in. It's a marker, not a skeleton.
Why this folder exists
apm install needs a real folder under .apm/skills/ to bootstrap the
workshop. That's it. The skill you ship in this workshop is a new
folder you'll create — .apm/skills/test-improver/, .apm/skills/docs-generator/,
etc. You will not edit this file.
The discipline this enforces
The workshop's hardest lesson: don't open a text editor and start typing
SKILL.md while squinting at Genesis's prose output. That's how every
"failed to ship" skill is born. The discipline is:
-
Design with Genesis. In your harness, run /genesis with your
chosen track's prompt. Genesis returns an
ASCII architecture diagram + an interface spec. Read it. That's
your contract.
-
Generate the skill from the design. Paste Genesis's design back
into chat, then instruct your harness:
Generate the <your-skill> skill at .apm/skills/<your-skill>/
following the Genesis design above. Use the SKILL.md frontmatter
conventions from .github/instructions/prose-style.md (installed
by apm install from code-kit).
Your harness writes SKILL.md (and any references) into the new
folder. You review the output, you don't author it line-by-line.
-
Iterate on the design, not the implementation. Don't like the
output? Tweak the Genesis prompt (narrow the inputs, add a
constraint), regenerate, re-ask the harness to regenerate the skill.
The implementation is a function of the design — keep the design
sharp and the implementation follows.
Why this matters in production
In a real codebase you will redesign skills as your team's conventions
evolve. If the implementation is hand-typed, every redesign is a
rewrite-from-scratch. If the implementation is generated from a
persisted design, every redesign is one Genesis tweak + one regenerate
prompt. That's the loop you're learning here.
See your chosen track guide for the exact
Genesis prompt + the reference ASCII diagram you should expect to get
back.
