Help
SkillFiles & storageThink before typing. Root cause first, two candidate fixes, pick one, ask if still unclear, then change only the files the request needs. Edit the confidence bar and scope rules to fit the project. Use when a bug report comes in, when a previous fix did not work, or when the request is vague.
Use Help in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Help and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Help skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by waynesutton/convexskills in templates/skills/help/SKILL.md and read by Ahel’s review.
Slow down for thirty seconds before the first edit. It saves an hour later.
Reflect before acting
- Why does the current code not do what the user wants? Read it. Do not guess.
- What is missing, wrong, or incomplete relative to the request?
- List two or three candidate causes.
- Pick the most likely one and say why.
- If the answer to "what is unclear" is not empty, ask one question and stop.
Never assume. A wrong assumption costs more than a question.
Confidence bar
Do not write code below [98]% confidence in what needs to change. Below that: read more, ask, or propose a plan instead of a diff.
Convex rules
- Mutations map form fields to document fields one to one. Field names match.
- Patch without reading when possible. Indexed queries for ownership. Idempotent with early returns.
Promise.allfor independent writes. - Load the matching
convex-*skill for anything deeper.
Scope
Change:
- Files the request needs.
- The schema, if the request needs it.
changelog.md,files.md,task.mdafter the change lands. Dates fromgit log --date=short, never invented.
Do not change:
- UI, layout, colors, or copy that the request did not mention.
- Existing sections, features, or components. Nothing gets removed without being asked.
- [Add project specific protected areas: admin dashboard, billing flow, etc.]
UI
- Site design system for every popup, alert, modal, toast, confirmation. Never the browser default.
- Vercel Web Interface Guidelines: https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/refs/heads/main/AGENTS.md
Docs policy
Do not create README, CONTRIBUTING, SUMMARY, or USAGE files unless asked. A short summary in the reply is enough.
Git
Load git-safety before any git command that could discard work. Short version: git status first, git diff before discarding, edit files by hand to undo, never reset --hard / checkout -- . / clean -fd / stash drop without the user saying yes to that exact command.
Checklist
Before the first edit:
- I can name the root cause
- I considered at least two fixes and picked one for a reason
- I am at or above the confidence bar
- I know which files change and which do not
- Anything unclear has been asked
Before saying done:
- The fix was verified, not just written
- Nothing outside the request changed
- Docs synced if the change was non trivial
Signals
- GitHub stars
- 405
- Forks
- 32
- Last commit
- Sep 2026
Ahel recommends instead
Advanced
- Item type
- skill
- Key
help-2- Source
- github.com/waynesutton/convexskills
github.com/waynesutton/convexskills