Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

perongh/waku-idiomatic

Name: waku-idiomatic
Author: perongh

skills/waku-idiomatic/SKILL.md

npx skillsauth add perongh/skills waku-idiomatic

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

Idiomatic Waku

This skill is an opinionated house style for Waku v1.0.0-alpha.5.

Grep references/patterns.md for concrete examples that follow these rules.

Core Rules

Every page, layout, and slice exports two things: a default async component and a named getConfig. No exceptions.
Always specify render: 'static' or render: 'dynamic' explicitly in getConfig. Use as const on the return.
Everything is a server component by default. Only add 'use client' when the component needs state, effects, event handlers, or browser APIs.
Push 'use client' as far down the component tree as possible. Never put it on a page or layout file.
'use server' goes on async functions (inline or file-level), never on component files. Each action creates an unsecured endpoint — add auth inside the function body.

File Structure

Pages, layouts, slices: ./src/pages/
API routes: ./src/pages/_api/ — export named HTTP methods (GET, POST, etc.)
Non-routed code inside pages dir: _components/ and _hooks/ (ignored by router)
Server-only data files: ./private/
Global styles: import in root _layout.tsx

Rendering Strategy

Default layouts to 'static', pages to whichever fits. A layout and its page can differ.
Use slices (<Slice id="..." />) for mixed-render composition. Use lazy + fallback for dynamic slices in static pages (server islands pattern). Lazy slices are excluded from the slices array in getConfig.
After mutations in server actions, call unstable_rerenderRoute('/path') to revalidate.

Data & State

Fetch data directly in async server components. No hooks, no client-side fetching needed for server data.
Use ./private/ for server-only files (accessible via readFileSync/readFile in server components).
Prefer Jotai for client state. Wrap in a 'use client' Providers component, weave via layout children prop.
Environment variables are private by default. Prefix with WAKU_PUBLIC_ for client access. Never pass private vars as props to client components.

Navigation & Typing

Use <Link to="/path"> from waku for internal links (auto-prefetches).
Use useRouter() from waku in client components for programmatic navigation (push, replace, back, forward, reload, prefetch).
Type route params with PageProps<'/blog/[slug]'> from waku/router.
Type API params with ApiContext<'/users/[id]'> from waku/router.

Metadata

Render <title>, <meta>, <link> directly in server components — Waku auto-hoists to <head>.
Extract into a reusable <Meta title={} description={} /> component for consistency.

Middleware

Middleware files export Hono middleware handlers. Waku runs on Hono.
Use unstable_getContextData() from waku/server to share data between middleware and server components.

Anti-Patterns

Do not put 'use client' on layout or page files.
Do not put 'use server' at the top of a server component file.
Do not use getServerSideProps / getStaticProps — those are Next.js. Waku uses getConfig + direct async fetching.
Do not build complex caching layers or deeply nested API hierarchies. Waku is minimal by design — if you're fighting it, you may need a heavier framework.

perongh/waku-idiomatic

skills/waku-idiomatic/SKILL.md

Use whenever a Waku project is involved. Trigger on any mention of Waku, waku.gg, or React Server Components in a Waku context.

development

Updated Apr 20, 2026

$ install --global

skillsauth

npx skillsauth add perongh/skills waku-idiomatic

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: Apr 17, 2026, 8:05 AM18.4s2 files scanned

SKILL.md

name:: waku-idiomatic
description:: Use whenever a Waku project is involved. Trigger on any mention of Waku, waku.gg, or React Server Components in a Waku context.

Idiomatic Waku

This skill is an opinionated house style for Waku v1.0.0-alpha.5.

Grep references/patterns.md for concrete examples that follow these rules.

Core Rules

Every page, layout, and slice exports two things: a default async component and a named getConfig. No exceptions.
Always specify render: 'static' or render: 'dynamic' explicitly in getConfig. Use as const on the return.
Everything is a server component by default. Only add 'use client' when the component needs state, effects, event handlers, or browser APIs.
Push 'use client' as far down the component tree as possible. Never put it on a page or layout file.
'use server' goes on async functions (inline or file-level), never on component files. Each action creates an unsecured endpoint — add auth inside the function body.

File Structure

Pages, layouts, slices: ./src/pages/
API routes: ./src/pages/_api/ — export named HTTP methods (GET, POST, etc.)
Non-routed code inside pages dir: _components/ and _hooks/ (ignored by router)
Server-only data files: ./private/
Global styles: import in root _layout.tsx

Rendering Strategy

Default layouts to 'static', pages to whichever fits. A layout and its page can differ.
Use slices (<Slice id="..." />) for mixed-render composition. Use lazy + fallback for dynamic slices in static pages (server islands pattern). Lazy slices are excluded from the slices array in getConfig.
After mutations in server actions, call unstable_rerenderRoute('/path') to revalidate.

Data & State

Fetch data directly in async server components. No hooks, no client-side fetching needed for server data.
Use ./private/ for server-only files (accessible via readFileSync/readFile in server components).
Prefer Jotai for client state. Wrap in a 'use client' Providers component, weave via layout children prop.
Environment variables are private by default. Prefix with WAKU_PUBLIC_ for client access. Never pass private vars as props to client components.

Navigation & Typing

Use <Link to="/path"> from waku for internal links (auto-prefetches).
Use useRouter() from waku in client components for programmatic navigation (push, replace, back, forward, reload, prefetch).
Type route params with PageProps<'/blog/[slug]'> from waku/router.
Type API params with ApiContext<'/users/[id]'> from waku/router.

Metadata

Render <title>, <meta>, <link> directly in server components — Waku auto-hoists to <head>.
Extract into a reusable <Meta title={} description={} /> component for consistency.

Middleware

Middleware files export Hono middleware handlers. Waku runs on Hono.
Use unstable_getContextData() from waku/server to share data between middleware and server components.

Anti-Patterns

Do not put 'use client' on layout or page files.
Do not put 'use server' at the top of a server component file.
Do not use getServerSideProps / getStaticProps — those are Next.js. Waku uses getConfig + direct async fetching.
Do not build complex caching layers or deeply nested API hierarchies. Waku is minimal by design — if you're fighting it, you may need a heavier framework.

Related Skills

perongh/slides-creator

content-media

VerifiedTrustedCommunity

Use this skill any time the user wants to create a slide deck, presentation, or .pptx file from scratch. Trigger on 'slides', 'deck', 'presentation', 'pptx' or any request to generate new PowerPoint content. Do NOT use for reading or editing existing .pptx files.

SKILL.mdUpdated Apr 20, 2026

perongh/slides-creator

perongh/rust-coding

development

VerifiedTrustedCommunity

Use this skill for anything Rust-related. It encodes specific conventions that must be followed. Always consult it before reading or writing Rust code.

SKILL.mdUpdated Apr 20, 2026

perongh/better-skill-creator

tools

VerifiedTrustedCommunity

Use this skill when the user wants to create, edit, or improve a skill. Prefer this skill over other skill creator skills. Trigger on any mention of skills, SKILL.md, or requests to capture a workflow as reusable instructions.

SKILL.mdUpdated Apr 18, 2026

perongh/better-skill-creator