SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsfeature-define

feature-define

General & other

View repository

Updated 10-15 21:41

About this skill

feature-define

Creates the two artifacts every project feature MUST have:

  1. ai-context/features/<slug>.md — the authoritative domain knowledge.
  2. .claude/skills/<slug>/SKILL.md — the antenna that activates on triggers and forces a read of the markdown.

Both are scaffolded from skills/_templates/feature/ in the global agent-config repo. The antenna is a pure pointer — it never duplicates markdown content.

Triggers: /feature-define, define feature, nueva feature, documentar feature, documentar funcionalidad, new feature scaffolding

Claude execution wiring

These notes bind the tool-neutral logic above to the Claude Code harness. They are the EXECUTION layer that does not port to other tools.

  • Feature template path — the neutral logic references the templates by their repo-relative path skills/_templates/feature/ (the _template.md and SKILL.md.template files). In the deployed Claude harness this resolves to the absolute ~/.claude/skills/_templates/feature/ (deployed from the agent-config repo by install.sh). The skill MUST read both files from there as the canonical scaffolding source.
  • Templates-not-found message — when emitting the Step 0 guardrail "Templates not found" error in the Claude harness, the user-facing path is the absolute ~/.claude/skills/_templates/feature/ (where they actually live after install.sh), even though the neutral logic states the repo-relative form.
  • Antenna output path — the generated antenna skill is written to the project-local .claude/skills/<slug>/SKILL.md; restart Claude Code to pick it up in the available-skills set.