Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Reflection-first problem solving methodology for Convex development.
Install Help
$ npx skills add waynesutton/markdown-site --skill help -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install waynesutton/markdown-site help --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/waynesutton/markdown-site.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/help .claude/skills/help && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "help" agent skill from https://github.com/waynesutton/markdown-site/tree/main/.claude/help into .claude/skills/help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "help", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/waynesutton/markdown-site/tree/main/.claude/helpType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add waynesutton/markdown-site --skill help -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install waynesutton/markdown-site help --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/markdown-site.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/help .agents/skills/help && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "help" agent skill from https://github.com/waynesutton/markdown-site/tree/main/.claude/help into .agents/skills/help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "help", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add waynesutton/markdown-site --skill help -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install waynesutton/markdown-site help --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/markdown-site.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/help .cursor/skills/help && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "help" agent skill from https://github.com/waynesutton/markdown-site/tree/main/.claude/help into .cursor/skills/help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "help", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/waynesutton/markdown-site.git --path .claude/help--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add waynesutton/markdown-site --skill help -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install waynesutton/markdown-site help --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/markdown-site.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/help .gemini/skills/help && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "help" agent skill from https://github.com/waynesutton/markdown-site/tree/main/.claude/help into .gemini/skills/help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "help", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install waynesutton/markdown-site helpInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add waynesutton/markdown-site --skill help -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/waynesutton/markdown-site.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/help .github/skills/help && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "help" agent skill from https://github.com/waynesutton/markdown-site/tree/main/.claude/help into .github/skills/help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "help", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add waynesutton/markdown-site --skill help -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install waynesutton/markdown-site help --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/waynesutton/markdown-site.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/help .opencode/skills/help && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "help" agent skill from https://github.com/waynesutton/markdown-site/tree/main/.claude/help into .opencode/skills/help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "help", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
help- GitHub stars
- 628
- Token cost
- ~1.1k tokens
- SKILL.md length
- 484 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reflection-first problem solving methodology for Convex development.
- Works in 6 steps: Reflect deeply before acting → Convex implementation guidelines → Change scope and restrictions → …
- Tasks that involve Root cause analysis
- SKILL.md covers 1. Reflect deeply before acting, 2. Convex implementation…, 3. Change scope and restrictions and 4. UI/UX guidelines, plus 3 more sections
- Calls git
What it does
Help is an agent skill from waynesutton/markdown-site. Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Root cause analysis. It works with WorkOS. The repository describes itself as: An open-source publishing framework built for AI agents and developers to ship websites, docs, or blogs. Write markdown, sync from the terminal. Your content is instantly… The licence is MIT.
When your agent uses it
- Tasks that involve Root cause analysis
Example prompts
- “/help”
Requirements
- Node.js
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3872c59. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.convex.devworkos.comraw.githubusercontent.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Help loads about 1.1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 484 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from waynesutton/markdown-site at commit 3872c59, republished under its MIT licence (© waynesutton). 484 words, ~1,111 tokens.
Download SKILL.mdSave it as
.claude/skills/help/SKILL.md (or your agent's skills folder).- name
- help
- description
- Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.
Core Development Guidelines Skill
Deep reflection and problem-solving methodology for full-stack Convex development.
1. Reflect deeply before acting
Before implementing any solution, follow this process:
- Reflect: Carefully consider why the current implementation may not be working
- Identify: What's missing, incomplete, or incorrect based on the request
- Theorize: Different possible sources of the problem or areas requiring updates
- Distill: Narrow down to 1-2 most probable root causes or solutions
- Proceed: Only move forward after clear understanding
Never assume. If anything is unclear, ask questions and clarify.
2. Convex implementation guidelines
Core principles
Direct mutation pattern:
- Use direct mutation calls with plain objects
- Create dedicated mutation functions that map form fields to database fields
- Form field names should exactly match database field names when applicable
Best practices:
- Patch directly without reading first
- Use indexed queries for ownership checks (not
ctx.db.get()) - Make mutations idempotent with early returns
- Use timestamp-based ordering for new items
- Use
Promise.all()for parallel independent operations to avoid write conflicts
Essential documentation
Functions:
- Mutations: https://docs.convex.dev/functions/mutation-functions
- Queries: https://docs.convex.dev/functions/query-functions
- Validation: https://docs.convex.dev/functions/validation
- General: https://docs.convex.dev/functions
Core concepts:
- Zen of Convex: https://docs.convex.dev/understanding/zen
- TypeScript best practices: https://docs.convex.dev/understanding/best-practices/typescript
- Best practices: https://docs.convex.dev/understanding/best-practices/
- Schema validation: https://docs.convex.dev/database/schemas
Authentication:
- WorkOS AuthKit: https://workos.com/docs/authkit/vanilla/nodejs
- WorkOS docs: https://workos.com/docs
- Convex + WorkOS setup: https://docs.convex.dev/auth/authkit/
3. Change scope and restrictions
What to update
- Update Convex schema if needed
- Only update files directly necessary to fix the original request
- When tasks touch changelog.md, changelog page, or files.md:
- Run
git log --date=shortto check commit history - Set release dates to match real commit timeline
- No placeholders or future months
- Run
What NOT to change
- Do not change UI, layout, design, or color styles unless specifically instructed
- Preserve all admin dashboard sections and frontend components unless explicitly told to update
- Never remove sections, features, or components unless directly requested
Show full SKILL.md (191 more words)Show less
4. UI/UX guidelines
Design system compliance
For pop-ups, alerts, modals, warnings, notifications, and confirmations:
- Always follow the site's existing design system
- Never use browser default pop-ups
- Use site design system components only
Follow Vercel guidelines
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/refs/heads/main/AGENTS.md
5. Documentation policy
IMPORTANT: Do NOT create documentation files unless explicitly instructed.
Banned unless requested:
- README.md
- CONTRIBUTING.md
- SUMMARY.md
- USAGE_GUIDELINES.md
You may include a brief summary in responses, but don't create separate documentation files.
Formatting rules:
- Never use emojis in readme or app unless instructed
6. Code confidence requirement
98% confidence rule:
Don't write any code until you're very confident (98% or more) in what needs to be done.
If unclear, ask for more information.
Quick reference checklist
Before writing code:
- Have I reflected on the root cause?
- Do I understand what's actually broken?
- Am I 98% confident in the solution?
- Am I only changing files that need to change?
- Am I preserving existing UI/features not mentioned?
- Am I using the site's design system (not browser defaults)?
- Am I following Convex mutation best practices?
- Have I checked the relevant docs?
When uncertain:
- Ask clarifying questions
- Don't assume
- Reference documentation
- Narrow down to 1-2 most likely solutions
© waynesutton, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/help of waynesutton/markdown-site.
Open the folder on GitHubat commit 3872c59
Compare with similar skills
Help next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Help this skillwaynesutton/markdown-site | 628 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graph-Based Bug Tracingtirth8205/code-review-graph | 32k | 1 repos | ~287 | Automated safety check: Pass | MIT |
Similar skills
- Official
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
Om Auto Fix Issue
go-musicfox/go-musicfox
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain…
More from waynesutton/markdown-site
All 17 skills in this repoConvex Self Hosting
waynesutton/markdown-site
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time.
Robel Auth
waynesutton/markdown-site
Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation.
Migration Helper
waynesutton/markdown-site
Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations.
Convex Return Validators
waynesutton/markdown-site
Guide for when to use and when not to use return validators in Convex functions.
Convex Doctor
waynesutton/markdown-site
Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories.
Convex Quickstart
waynesutton/markdown-site
Initialize a new Convex project from scratch or add Convex to an existing app.
Related
Works with
Categories
Questions about Help
What does Help do?
Reflection-first problem solving methodology for Convex development. Help is an agent skill from waynesutton/markdown-site. Reflection-first problem solving methodology for Convex development.
When should I use Help?
Help fits situations like: tasks that involve Root cause analysis.
How do I install Help in Claude Code?
Run `npx skills add waynesutton/markdown-site --skill help -a claude-code`. Or copy the skill folder (.claude/help in waynesutton/markdown-site) into .claude/skills/help in your project. Claude Code loads it when a task matches its description.
How do I install Help in Codex?
Run `npx skills add waynesutton/markdown-site --skill help -a codex`. Or copy the skill folder (.claude/help in waynesutton/markdown-site) into .agents/skills/help in your project. Codex loads it when a task matches its description.
Can I use Help in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add waynesutton/markdown-site --skill help -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/help, .gemini/skills/help, .github/skills/help and .opencode/skills/help in your project.
What does Help need to run?
Going by SKILL.md and its folder, Help needs the command-line tools its instructions call (git). Our summary lists: Node.js.
Does Help access the network?
SKILL.md names 3 domains. As links in the text: docs.convex.dev, workos.com and raw.githubusercontent.com. This is read from the text; nothing was executed.
Is Help safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Help use?
Help is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Help use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Help?
Skills that share tags, products or a category with Help: Code Design Rationale Investigator (cursor/plugins, 10k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Help?
waynesutton (a GitHub user) maintains it in waynesutton/markdown-site, which has 628 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on May 20, 2026.
Source: waynesutton/markdown-site on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.