メニュー
Ensure skills are created in `.agents/skills` and `.cursor/skills` is a symlink to that directory. Use when the user asks to create/update a skill, mentions skills location, or asks about the `.agents`/`.cursor/skills` symlink.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-skill-augment |
| description | Ensure skills are created in `.agents/skills` and `.cursor/skills` is a symlink to that directory. Use when the user asks to create/update a skill, mentions skills location, or asks about the `.agents`/`.cursor/skills` symlink. |
~/.cursor/skills-cursor/create-skill/SKILL.md and follow its structure..agents/skills/<skill-name>/SKILL.md..cursor/skills directly..cursor/skills is a symlink to .agents/skills..cursor/skills exists and is not a symlink, move it aside before linking..cursor/skills is a symlink to the wrong location, replace it.Use:
if [ -e ".cursor/skills" ] && [ ! -L ".cursor/skills" ]; then
mv ".cursor/skills" ".cursor/skills.bak"
fi
if [ -L ".cursor/skills" ] && [ "$(readlink ".cursor/skills")" != "../.agents/skills" ]; then
rm ".cursor/skills"
fi
if [ ! -L ".cursor/skills" ]; then
ln -s "../.agents/skills" ".cursor/skills"
fi
Debug and repair code using minimal, reviewable patches instead of full-file rewrites. Use this whenever the user is fixing a bug, iterating on failing tests, asks for a surgical code change, wants a minimal diff, or is in a tight debug loop where output size and token cost matter. Prefer this even if the user does not explicitly say "patch."
Build or use a tight automated test-fix loop that repairs one failing test at a time with minimal patches and narrow context. Use whenever the user wants a repair harness, constrained bug-fixing loop, failing-test repair workflow, or a prompt that turns the model into a surgical fix engine instead of a general coding assistant.
Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome)
Reduce cognitive load when implementing or refactoring code for readability.
Use Conventional Commits when creating reviewing or fixing commit messages.
Audit and refactor React UI components to match DataConnect UI implementation rules (Text component, tokens, Tailwind, naming) and Vercel React/composition guidance. Use when the user asks for a UI audit, React audit, composition review, or to fix UI implementation issues in components.