Tiny Wasm
Official@tinywasm · Chile
The Fullstack Go framework
Agent Skills by Tiny Wasm
Showing 10 vetted skills indexed across 1 GitHub repositories.
form-codegen
Generate schema-driven forms with shared validation across WASM and backend services.
documentation
Define unified documentation standards for ARCHITECTURE.md, PLAN.md, DESIGN.md, SPECS.md, SKILL.md, diagrams, and README indexing.
agent-workflow
Coordinate multi-agent workflows via PLAN.md and modular PLAN_STAGE_ files.
wasm
Standardize tinywasm MCP server and frontend Go compatibility guidelines.
testing
Automate Go test workflows from running tests to publishing results.
components
Define TinyWasm component structure, embedding, CSS tokens, SSR, and PLAN.md workflow.
tinywasm-app
Orchestrate a persistent MCP daemon with REST/SSE endpoints for tinywasm projects.
llmskill
Synchronize skill definitions from a source repository to installed LLM agent configurations.
core-principles
Apply Go development principles for maintainable, testable codebases.
dev-protocols
Plan and document AI workflows with explicit execution gates.
Frequently Asked Questions About Tiny Wasm
FAQPage SchemaWhat specific tasks does Tiny Wasm enable for developers?▼
Tiny Wasm enables the generation of schema-driven forms with shared validation, the orchestration of persistent MCP daemons, and the standardization of component structures including SSR and CSS tokens. It facilitates unified documentation standards across project architecture files and ensures Go-based compatibility for WebAssembly environments.
Which personas benefit most from using Tiny Wasm?▼
Fullstack Go developers and systems architects benefit most from Tiny Wasm. It is designed for engineers building high-performance web interfaces who require strict schema synchronization between frontend WebAssembly modules and backend services, as well as those managing complex project documentation and modular component lifecycles.
What are the prerequisites for implementing Tiny Wasm?▼
Implementation requires a Go development environment and familiarity with WebAssembly compilation targets. Users must adopt the framework's specific documentation standards, including PLAN.md and DESIGN.md files, to manage component structures and execution gates within their project repository.