JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
Patchies documentation style guide. An agent skill from heypoom/patchies.
Install Docs Style
$ npx skills add heypoom/patchies --skill docs-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install heypoom/patchies docs-style --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/heypoom/patchies.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/docs-style .claude/skills/docs-style && 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 "docs-style" agent skill from https://github.com/heypoom/patchies/tree/main/.agents/skills/docs-style into .claude/skills/docs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style", 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/heypoom/patchies/tree/main/.agents/skills/docs-styleType 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 heypoom/patchies --skill docs-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install heypoom/patchies docs-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/heypoom/patchies.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/docs-style .agents/skills/docs-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs-style" agent skill from https://github.com/heypoom/patchies/tree/main/.agents/skills/docs-style into .agents/skills/docs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style", 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 heypoom/patchies --skill docs-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install heypoom/patchies docs-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/heypoom/patchies.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/docs-style .cursor/skills/docs-style && 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 "docs-style" agent skill from https://github.com/heypoom/patchies/tree/main/.agents/skills/docs-style into .cursor/skills/docs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style", 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/heypoom/patchies.git --path .agents/skills/docs-style--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 heypoom/patchies --skill docs-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install heypoom/patchies docs-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/heypoom/patchies.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/docs-style .gemini/skills/docs-style && 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 "docs-style" agent skill from https://github.com/heypoom/patchies/tree/main/.agents/skills/docs-style into .gemini/skills/docs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style", 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 heypoom/patchies docs-styleInstalls 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 heypoom/patchies --skill docs-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/heypoom/patchies.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/docs-style .github/skills/docs-style && 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 "docs-style" agent skill from https://github.com/heypoom/patchies/tree/main/.agents/skills/docs-style into .github/skills/docs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style", 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 heypoom/patchies --skill docs-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install heypoom/patchies docs-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/heypoom/patchies.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/docs-style .opencode/skills/docs-style && 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 "docs-style" agent skill from https://github.com/heypoom/patchies/tree/main/.agents/skills/docs-style into .opencode/skills/docs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-style", 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
docs-style- GitHub stars
- 209
- Token cost
- ~1k tokens
- SKILL.md length
- 365 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Patchies documentation style guide. An agent skill from heypoom/patchies.
- Works in 7 steps: H1 title — one sentence intro explaining… → Screenshot or image (if available) —… → ✨ Try-it link — > ✨ Try this patch —… → …
- Writing & Content work in your project
- SKILL.md covers Voice & Tone, Page Structure (Topic Docs), Formatting Rules and Content Principles, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docs Style is an agent skill from heypoom/patchies. Patchies documentation style guide. Load when writing or editing topic docs in ui/static/content/topics/ or ui/static/content/objects/. Describes the voice, structure, and formatting conventions for all Patchies docs.
Its SKILL.md is about 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 Writing & Content. It works with JavaScript. The repository describes itself as: Write small programs with tools & libraries you know and patch 'em together. Make interactive widgets, visuals, sounds, and play with computation on the web. The licence is AGPL-3.0.
When your agent uses it
- Writing & Content work in your project
Example prompts
- “Use the docs-style skill to patchy documentation style guide. An agent skill from heypoom/patchies”
- “/docs-style”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- H1 title — one sentence intro explaining what this topic is and why it matters
- Screenshot or image (if available) — with a caption or context sentence below
- ✨ Try-it link — > ✨ Try this patch — brief description.
- How It Works — the mental model first, before any API or steps. Use analogies (e.g. "like a hardware signal chain")
- Try It — hands-on exercises. Use ### sub-headings per exercise.
- Feature sections — one ## section per major concept, separated by ---
- See Also — links with one-line descriptions
What it can do on your machine
Read from SKILL.md and the folder at commit dd38c74. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and javascript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Docs Style loads about 1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 365 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 heypoom/patchies at commit dd38c74, republished under its AGPL-3.0 licence (© heypoom). 365 words, ~1,041 tokens.
Download SKILL.mdSave it as
.claude/skills/docs-style/SKILL.md (or your agent's skills folder).- name
- docs-style
- description
- Patchies documentation style guide. Load when writing or editing topic docs in ui/static/content/topics/ or ui/static/content/objects/. Describes the voice, structure, and formatting conventions for all Patchies docs.
- paths
- ui/static/content/**/*.md
Patchies Documentation Style Guide
Use this guide whenever writing or editing documentation in ui/static/content/.
Voice & Tone
- Friendly but concise — welcoming like P5.js docs, not terse like a man page
- Write for someone who knows how to code but is new to Patchies
- Lead with the concept ("what it is and why you'd use it"), then the how
- Use "you" to address the reader directly
- Avoid filler phrases: "Note that", "It's worth mentioning", "Simply", "Just"
Page Structure (Topic Docs)
Follow this order — omit sections that don't apply:
- H1 title — one sentence intro explaining what this topic is and why it matters
- Screenshot or image (if available) — with a caption or context sentence below
- ✨ Try-it link —
> ✨ [Try this patch](/?id=...) — brief description. - How It Works — the mental model first, before any API or steps. Use analogies (e.g. "like a hardware signal chain")
- Try It — hands-on exercises. Use
###sub-headings per exercise. - Feature sections — one
##section per major concept, separated by--- - See Also — links with one-line descriptions
Formatting Rules
Headings
- Use
##for major sections - Use
###for sub-sections and exercises - Never use bold text as a heading — always use a proper
#heading
<!-- WRONG -->
**Exercise — Simple tone**
<!-- RIGHT -->
### Exercise — Simple toneCallouts
Use blockquote callouts for tips, warnings, and try-it links:
> ✨ [Try this patch](/?id=abc123) — brief description.
> **Tip**: Use the `logger.js` preset to inspect messages.
> **Note**: Objects like `expr` use hot and cold inlets.
> **Important**: Always connect to `out~` to hear audio.Show full SKILL.md (162 more words)Show less
Code Examples
- Every API function must have a runnable example, not just a signature
- Add inline comments explaining why, not just what
- Show realistic values (use
440notn, use0.3notvalue)
// WRONG — too abstract
setInterval(callback, ms)
// RIGHT — copy-pasteable and clear
setInterval(() => {
send({type: 'bang'})
}, 500)Tables
Always include a spaced separator row:
| Column A | Column B | Column C |
| -------- | -------- | -------- |
| value | value | value |Lists
Prefer numbered lists for sequential steps, bullets for unordered options. Keep bullets short — one line each when possible.
Code Diagrams
Use plain text for signal flow — it's clear and universal:
[osc~ 440] → [gain~ 0.5] → [out~]Content Principles
Concept Before API
Always explain the mental model before listing functions:
<!-- WRONG — starts with API -->
Use `setPortCount(inletCount, outletCount)` to set inlets.
<!-- RIGHT — concept first -->
Each js object starts with one inlet and one outlet.
Use `setPortCount()` to add more when your logic needs them:Avoid Duplication
- If a concept is fully covered in another doc, link to it — don't repeat it
- A brief one-example intro + "See [X] for the full API" is the right pattern
message-passing.mdowns message concepts;javascript-runner.mdowns the JS API
Exercises
Every topic doc should have at least one hands-on exercise. Format:
### Exercise — Descriptive name
1. Create a `foo` object (`Enter` → type `foo`)
2. Connect it to a `bar` object
3. Do something — you should see/hear the resultSee Also
End every topic doc with a See Also section. Format:
## See Also
- [Page Title](/docs/slug) — one-line description of what it covers
- [Object Name](/docs/objects/name) — what the object doesFile Locations
- Topic docs:
ui/static/content/topics/<slug>.md - Object docs:
ui/static/content/objects/<name>.md - Register new topic docs in
ui/src/routes/docs/docs-nav.ts
© heypoom, AGPL-3.0. 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 .agents/skills/docs-style of heypoom/patchies.
Open the folder on GitHubat commit dd38c74
Compare with similar skills
Docs Style 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 |
|---|---|---|---|---|---|---|
| Docs Style this skillheypoom/patchies | 209 | — | ~1k | Automated safety check: Pass | AGPL-3.0 | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| Install Anti Sloptrycompai/crm | 11k | 1 repos | ~881 | Automated safety check: Pass | MIT | |
| JavaScript Concept Page Workflowleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| JS Concept Resource Curatorleonardomso/33-js-concepts | 67k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Translatetagspaces/tagspaces | 5.3k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Install Anti Slop
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
JavaScript Concept Page Workflow
leonardomso/33-js-concepts
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
JS Concept Resource Curator
leonardomso/33-js-concepts
Finds, vets, writes up and maintains external articles, videos and courses for JavaScript concept pages, including audits for broken and outdated links.
Translate
tagspaces/tagspaces
Translate new or untranslated i18n strings from the English locale files (core.json + peri.json) into all other locales, maintaining consistency with each language's existing translations.
JavaScript Concept Page Writer
leonardomso/33-js-concepts
Writes or reviews documentation pages for the 33 JavaScript Concepts project, following its structure, a beginner-friendly voice and rules against AI-sounding language.
More from heypoom/patchies
All 8 skills in this repoPatchies Audio
heypoom/patchies
A skill your agent uses when adding, migrating, or changing Patchies Audio V2 nodes, native DSP worklet nodes, audio object docs, audio packs, or AudioService integration.
Patchies Frontend
heypoom/patchies
A skill your agent uses when editing Patchies Svelte components, UI state, styling, buttons, persistence, or frontend implementation patterns.
Patchies Objects
heypoom/patchies
A skill your agent uses when adding, editing, or migrating Patchies nodes, objects, handles, object modules, schemas, object docs, AI prompts, file drag/drop support, or node data settings.
Patchies Workflow
heypoom/patchies
A skill your agent uses when working in Patchies on tests, specs, reflections, verification scope, or commits, especially before changing product behavior or when the user explicitly asks to commit.
Patchies Assembly Module
heypoom/patchies
A skill your agent uses when changing Patchies assembly VM code, VASM Rust sources, wasm-pack output, machine WASM assets, asm object behavior, or modules/vasm build/link steps.
Patchies Rendering
heypoom/patchies
A skill your agent uses when changing Patchies rendering pipeline, render graph, image generation preview capture, GLSystem, render workers, FBO rendering, output sizing, render-node types, or video…
Related
Works with
Categories
Questions about Docs Style
What does Docs Style do?
Patchies documentation style guide. An agent skill from heypoom/patchies. Docs Style is an agent skill from heypoom/patchies. Patchies documentation style guide.
When should I use Docs Style?
Docs Style fits situations like: writing & Content work in your project.
How do I install Docs Style in Claude Code?
Run `npx skills add heypoom/patchies --skill docs-style -a claude-code`. Or copy the skill folder (.agents/skills/docs-style in heypoom/patchies) into .claude/skills/docs-style in your project. Claude Code loads it when a task matches its description.
How do I install Docs Style in Codex?
Run `npx skills add heypoom/patchies --skill docs-style -a codex`. Or copy the skill folder (.agents/skills/docs-style in heypoom/patchies) into .agents/skills/docs-style in your project. Codex loads it when a task matches its description.
Can I use Docs Style 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 heypoom/patchies --skill docs-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-style, .gemini/skills/docs-style, .github/skills/docs-style and .opencode/skills/docs-style in your project.
What does Docs Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs Style is instructions for the agent only.
Does Docs Style access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Docs Style 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 Docs Style use?
Docs Style is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docs Style use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Docs Style?
Skills that share tags, products or a category with Docs Style: JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars), Install Anti Slop (trycompai/crm, 11k stars), JavaScript Concept Page Workflow (leonardomso/33-js-concepts, 67k stars) and JS Concept Resource Curator (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs Style?
heypoom (a GitHub user) maintains it in heypoom/patchies, which has 209 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: heypoom/patchies on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.