Beads Documentation Style Guide
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
$ npx skills add leonardomso/33-js-concepts --skill concept-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install leonardomso/33-js-concepts concept-workflow --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/leonardomso/33-js-concepts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/concept-workflow .claude/skills/concept-workflow && 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 "concept-workflow" agent skill from https://github.com/leonardomso/33-js-concepts/tree/master/.claude/skills/concept-workflow into .claude/skills/concept-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concept-workflow", 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/leonardomso/33-js-concepts/tree/master/.claude/skills/concept-workflowType 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 leonardomso/33-js-concepts --skill concept-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install leonardomso/33-js-concepts concept-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leonardomso/33-js-concepts.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/concept-workflow .agents/skills/concept-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "concept-workflow" agent skill from https://github.com/leonardomso/33-js-concepts/tree/master/.claude/skills/concept-workflow into .agents/skills/concept-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concept-workflow", 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 leonardomso/33-js-concepts --skill concept-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install leonardomso/33-js-concepts concept-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leonardomso/33-js-concepts.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/concept-workflow .cursor/skills/concept-workflow && 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 "concept-workflow" agent skill from https://github.com/leonardomso/33-js-concepts/tree/master/.claude/skills/concept-workflow into .cursor/skills/concept-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concept-workflow", 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/leonardomso/33-js-concepts.git --path .claude/skills/concept-workflow--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 leonardomso/33-js-concepts --skill concept-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install leonardomso/33-js-concepts concept-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leonardomso/33-js-concepts.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/concept-workflow .gemini/skills/concept-workflow && 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 "concept-workflow" agent skill from https://github.com/leonardomso/33-js-concepts/tree/master/.claude/skills/concept-workflow into .gemini/skills/concept-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concept-workflow", 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 leonardomso/33-js-concepts concept-workflowInstalls 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 leonardomso/33-js-concepts --skill concept-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/leonardomso/33-js-concepts.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/concept-workflow .github/skills/concept-workflow && 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 "concept-workflow" agent skill from https://github.com/leonardomso/33-js-concepts/tree/master/.claude/skills/concept-workflow into .github/skills/concept-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concept-workflow", 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 leonardomso/33-js-concepts --skill concept-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install leonardomso/33-js-concepts concept-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leonardomso/33-js-concepts.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/concept-workflow .opencode/skills/concept-workflow && 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 "concept-workflow" agent skill from https://github.com/leonardomso/33-js-concepts/tree/master/.claude/skills/concept-workflow into .opencode/skills/concept-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "concept-workflow", 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.
concept-workflowOrchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO.
The skill runs the full pipeline for a new or fully rewritten concept page in the 33 JavaScript concepts repository. Five specialized skills run in order: resource curation, concept writing, test writing for the code examples, fact checking and an SEO review. For partial jobs it points to the matching single skill, such as resource-curator, write-concept, test-writer, fact-check or seo-review.
Each phase has a goal, steps, deliverables and quality gates that must pass before moving on. Resource curation, for example, targets 4-6 articles, 3-4 videos and 2-4 MDN links, verifies that every link responds, requires JavaScript-focused resources with specific descriptions and formats them as Card components ready to paste. Concept writing starts with category selection and frontmatter fields such as title, sidebarTitle and description.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 16d0d95. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
JavaScript Concept Page Workflow loads about 3.9k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 1,138 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.
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.
The full file from leonardomso/33-js-concepts at commit 16d0d95, republished under its MIT licence (© leonardomso). 1,138 words, ~3,937 tokens.
.claude/skills/concept-workflow/SKILL.md (or your agent's skills folder).Use this skill to create a complete, high-quality concept page from start to finish. This skill orchestrates all five specialized skills in the optimal order:
For partial tasks, use individual skills instead:
resource-curatorwrite-concepttest-writerfact-checkseo-review┌─────────────────────────────────────────────────────────────────────────────┐
│ COMPLETE CONCEPT WORKFLOW │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ INPUT: Concept name (e.g., "hoisting", "event-loop", "promises") │
│ │
│ ┌──────────────────┐ │
│ │ PHASE 1: RESEARCH │ │
│ │ resource-curator │ Find MDN refs, articles, videos │
│ └────────┬─────────┘ │
│ ▼ │
│ ┌──────────────────┐ │
│ │ PHASE 2: WRITE │ │
│ │ write-concept │ Create the documentation page │
│ └────────┬─────────┘ │
│ ▼ │
│ ┌──────────────────┐ │
│ │ PHASE 3: TEST │ │
│ │ test-writer │ Generate tests for all code examples │
│ └────────┬─────────┘ │
│ ▼ │
│ ┌──────────────────┐ │
│ │ PHASE 4: VERIFY │ │
│ │ fact-check │ Verify accuracy, run tests, check links │
│ └────────┬─────────┘ │
│ ▼ │
│ ┌──────────────────┐ │
│ │ PHASE 5: OPTIMIZE│ │
│ │ seo-review │ SEO audit and final optimizations │
│ └────────┬─────────┘ │
│ ▼ │
│ OUTPUT: Complete, tested, verified, SEO-optimized concept page │
│ │
└─────────────────────────────────────────────────────────────────────────────┘Skill: resource-curator
Goal: Gather high-quality external resources before writing
Before moving to Phase 2:
Skill: write-concept
Goal: Create the full documentation page
.mdx file at /docs/concepts/{concept-name}.mdxdocs.json navigation (if new)Before moving to Phase 3:
Skill: test-writer
Goal: Create comprehensive tests for all code examples
tests/{category}/{concept}/{concept}.test.jstests/{category}/{concept}/{concept}.dom.test.jstests/{category}/{concept-name}/{concept-name}.test.jstests/{category}/{concept-name}/{concept-name}.dom.test.jsBefore moving to Phase 4:
npm test -- tests/{category}/{concept}/Skill: fact-check
Goal: Verify technical accuracy of all content
Verify code examples:
npm test -- tests/{category}/{concept}/Verify MDN/spec claims:
Verify external resources:
Audit technical claims:
Generate fact-check report
Before moving to Phase 5:
Skill: seo-review
Goal: Optimize for search visibility
Audit title tag:
Audit meta description:
Audit keyword placement:
Audit content structure:
Audit featured snippet optimization:
Audit internal linking:
Calculate score and fix any issues
Before marking complete:
Use this master checklist to track progress through all phases.
# Concept Workflow: [Concept Name]
**Started:** YYYY-MM-DD
**Target Category:** {category}
**File Path:** `/docs/concepts/{concept-name}.mdx`
**Test Path:** `/tests/{category}/{concept-name}/`
---
## Phase 1: Resource Curation
- [ ] MDN references found (2-4)
- [ ] Articles found (4-6)
- [ ] Videos found (3-4)
- [ ] All links verified working
- [ ] Descriptions written (specific, 2 sentences)
- [ ] Resources formatted as Cards
**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete
---
## Phase 2: Concept Writing
- [ ] Frontmatter complete
- [ ] Opening hook written
- [ ] Opening code example added
- [ ] "What you'll learn" box added
- [ ] Main content sections written
- [ ] Key Takeaways added
- [ ] Test Your Knowledge added
- [ ] Related Concepts added
- [ ] Resources pasted from Phase 1
- [ ] Added to docs.json (if new)
**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete
---
## Phase 3: Test Writing
- [ ] Code examples extracted and categorized
- [ ] Test file created
- [ ] DOM test file created (if needed)
- [ ] All testable examples have tests
- [ ] Source line references added
- [ ] Tests run and passing
**Test Results:** X passing, X failing
**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete
---
## Phase 4: Fact Checking
- [ ] All tests passing
- [ ] Code examples verified accurate
- [ ] MDN links checked (X/X valid)
- [ ] External resources checked (X/X valid)
- [ ] Technical claims audited
- [ ] No misconceptions found
- [ ] Issues fixed
**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete
---
## Phase 5: SEO Review
- [ ] Title tag optimized (50-60 chars)
- [ ] Meta description optimized (150-160 chars)
- [ ] Keywords placed correctly
- [ ] Content structure verified
- [ ] Featured snippet optimized
- [ ] Internal links complete
**SEO Score:** X/27 (X%)
**Status:** ⬜ Not Started | 🟡 In Progress | ✅ Complete
---
## Final Status
**All Phases Complete:** ⬜ No | ✅ Yes
**Ready to Publish:** ⬜ No | ✅ Yes
**Completed:** YYYY-MM-DDWhen executing this workflow, follow these steps:
Starting concept workflow for: [CONCEPT NAME]
Category: [fundamentals/functions-execution/web-platform/etc.]
File: /docs/concepts/[concept-name].mdx
Tests: /tests/[category]/[concept-name]/For each phase:
Announce the phase:
## Phase X: [Phase Name]
Using skill: [skill-name]Load the skill to get detailed instructions
Execute the phase following the skill's methodology
Report completion:
Phase X complete:
- [Deliverable 1]
- [Deliverable 2]
- Quality gates: ✅ All passedMove to next phase only after quality gates pass
After all phases complete:
# Workflow Complete: [Concept Name]
## Summary
- **Concept Page:** `/docs/concepts/[concept-name].mdx`
- **Test File:** `/tests/[category]/[concept-name]/[concept-name].test.js`
- **Word Count:** X,XXX words
- **Code Examples:** XX (XX tested)
- **Resources:** X MDN, X articles, X videos
## Quality Metrics
- **Tests:** XX passing
- **Fact Check:** ✅ All verified
- **SEO Score:** XX/27 (XX%)
## Files Created/Modified
1. `/docs/concepts/[concept-name].mdx` (created)
2. `/docs/docs.json` (updated navigation)
3. `/tests/[category]/[concept-name]/[concept-name].test.js` (created)
## Ready to Publish: ✅ YesSome phases can be partially parallelized, but the general flow should be:
Phase 1 (Resources) ──┐
├──► Phase 2 (Writing) ──► Phase 3 (Tests) ──┐
│ │
│ ┌───────────────────────────────────┘
│ ▼
└──► Phase 4 (Fact Check) ──► Phase 5 (SEO)| Phase | Skill | Purpose |
|---|---|---|
| 1 | resource-curator | Find and evaluate external resources |
| 2 | write-concept | Write the documentation page |
| 3 | test-writer | Generate tests for code examples |
| 4 | fact-check | Verify technical accuracy |
| 5 | seo-review | Optimize for search visibility |
Each skill has detailed instructions in its own SKILL.md file. Load the appropriate skill at each phase for comprehensive guidance.
| Phase | Estimated Time | Notes |
|---|---|---|
| Phase 1: Resources | 15-30 min | Depends on availability of quality resources |
| Phase 2: Writing | 1-3 hours | Depends on concept complexity |
| Phase 3: Tests | 30-60 min | Depends on number of code examples |
| Phase 4: Fact Check | 15-30 min | Most automated via tests |
| Phase 5: SEO | 15-30 min | Mostly checklist verification |
| Total | 2-5 hours | For a complete concept page |
To start the workflow for a new concept:
1. Determine the concept name and category
2. Load this skill (concept-workflow)
3. Execute Phase 1: Load resource-curator, find resources
4. Execute Phase 2: Load write-concept, write the page
5. Execute Phase 3: Load test-writer, create tests
6. Execute Phase 4: Load fact-check, verify accuracy
7. Execute Phase 5: Load seo-review, optimize SEO
8. Generate final report
9. Commit changesExample prompt to start:
"Create a complete concept page for 'hoisting' using the concept-workflow skill"
This will trigger the full end-to-end workflow, creating a complete, tested, verified, and SEO-optimized concept page.
© leonardomso, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/concept-workflow of leonardomso/33-js-concepts.
Open the folder on GitHubat commit 16d0d95
JavaScript Concept Page Workflow 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 |
|---|---|---|---|---|---|---|
| JavaScript Concept Page Workflow this skillleonardomso/33-js-concepts | 67k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Beads Documentation Style Guidegastownhall/beads | 28k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Technical Writing Standardcursor/plugins | 10k | 10 repos | ~2.4k | Automated safety check: Pass | None | |
| Heym Documentation Articlesheymrun/heym | 1.4k | — | ~780 | Automated safety check: Pass | Custom licence | |
| Technical Writing Workflowtokenbender/agent-guides | 367 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Developer Docs Technical Writervercel-labs/github-tools | 131 | — | ~3.9k | Automated safety check: Pass | MIT |
gastownhall/beads
Sets the house style for the beads user docs: the canonical concept model, required terminology, prose and diagram conventions, and checks before docs work is done.
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
heymrun/heym
Creates and updates documentation articles for the Heym platform: category choice, manifest entry, markdown file and cross-links from existing pages.
tokenbender/agent-guides
A skill your agent uses for planning, researching, drafting, revising, or auditing technical write-ups, textbooks, papers, reports, READMEs, research notes, PR narratives, and public technical prose.
vercel-labs/github-tools
Writes, reviews and edits developer documentation for SDKs, libraries and frameworks, from getting-started guides and API references to migration guides.
manycoretech/aholo-viewer
Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.
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.
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.
leonardomso/33-js-concepts
Runs a five-step SEO audit on JavaScript concept pages: keyword clusters, on-page checks, featured snippets, internal links and a written report.
leonardomso/33-js-concepts
Generates Vitest tests for every runnable code example on a JavaScript concept documentation page, following a four-phase extraction and conversion process.
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.
Works with
Categories
Orchestrates five skills to produce a complete JavaScript concept documentation page, from resource curation through writing, tests, fact-checking and SEO. The skill runs the full pipeline for a new or fully rewritten concept page in the 33 JavaScript concepts repository. Five specialized skills run in order: resource curation, concept writing, test writing for the code examples, fact checking and an SEO review.
JavaScript Concept Page Workflow fits situations like: creating a new JavaScript concept page from scratch with all quality checks; completely rewriting an existing concept page; running research, writing, tests, fact-checking and SEO as one workflow.
Run `npx skills add leonardomso/33-js-concepts --skill concept-workflow -a claude-code`. Or copy the skill folder (.claude/skills/concept-workflow in leonardomso/33-js-concepts) into .claude/skills/concept-workflow in your project. Claude Code loads it when a task matches its description.
Run `npx skills add leonardomso/33-js-concepts --skill concept-workflow -a codex`. Or copy the skill folder (.claude/skills/concept-workflow in leonardomso/33-js-concepts) into .agents/skills/concept-workflow in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add leonardomso/33-js-concepts --skill concept-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/concept-workflow, .gemini/skills/concept-workflow, .github/skills/concept-workflow and .opencode/skills/concept-workflow in your project.
Going by SKILL.md and its folder, JavaScript Concept Page Workflow needs the command-line tools its instructions call (npm). Our summary lists: The resource-curator, write-concept, test-writer, fact-check and seo-review skills.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
JavaScript Concept Page Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with JavaScript Concept Page Workflow: Beads Documentation Style Guide (gastownhall/beads, 28k stars), Technical Writing Standard (cursor/plugins, 10k stars), Heym Documentation Articles (heymrun/heym, 1.4k stars) and Technical Writing Workflow (tokenbender/agent-guides, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
leonardomso (a GitHub user) maintains it in leonardomso/33-js-concepts, which has 66,531 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 10, 2026.
Source: leonardomso/33-js-concepts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.