docs

Automate Clapse documentation authoring and validate executable code fences against the wasm compiler.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mewhhaha/clapse --skill docs-mewhhaha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/mewhhaha/clapse/tree/main/docs
Command: npx skills add https://github.com/mewhhaha/clapse --skill docs-mewhhaha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation in Clapse often drifts from the current compiler/runtime, making it hard to trust examples and workflows. This skill standardizes authoring, validation, and maintenance of docs, references, tutorials, and validation workflows by tying executable snippets to the live toolchain.

Core Features & Use Cases

  • Executable snippets: ensure code fences labeled clapse compile against the current wasm compiler unless explicitly marked skip.
  • Structured docs validation: automate docs/test alignment, validate LSP formatter expectations, and keep clapse.json plugin and tooling references in sync.
  • Documentation workflow: support reference edits, tutorial snippets, and docs validation tasks with a clear maintenance path and change-tracking hooks.
  • Use Case: when introducing a new language feature, update the docs snippets and run the docs-validate flow to confirm end-to-end correctness.

Quick Start

Run the docs validation workflow to verify all executable snippets compile against the current wasm compiler.

Frequently Asked Questions about docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate executable code snippets in documentation against a wasm compiler?

To validate executable code snippets, run a docs validation workflow that compiles code fences against the current wasm compiler. Snippets explicitly marked skip bypass compilation, ensuring docs stay synchronized with the live toolchain.

What is docs validation for executable examples and when do I need it?

Docs validation for executable examples is a process that checks if code fences compile with the current toolchain. You need it when documentation drifts from the compiler runtime, making examples and workflows hard to trust.

How to update tutorials and reference edits when introducing a new language feature?

Update tutorial snippets and reference edits with the new feature, then run the docs-validate flow to confirm end-to-end correctness. This coordinates refresh scripts and LSP formatter tests to keep references in sync.

Does the docs validation workflow support LSP formatter tests and clapse.json references?

Yes, the docs validation workflow validates LSP formatter expectations and keeps clapse.json plugin and tooling references in sync. It automates docs and test alignment within the repository maintenance path.

Can I skip compilation for certain code fences in documentation?

Yes, you can skip compilation for certain code fences by explicitly marking them skip. This bypasses the wasm compiler check for examples that are illustrative or incomplete, while unmarked snippets must compile.