SkillsSkill packagesb4pushRun comprehensive pre-push validation. Use when: (1) Completing a PR or feature implementation, (2) Before pushing significant changes, (3) After large refactors, (4) User says 'b4push', 'before push'...check-docsCheck documentation for broken links and formatting issuescolor-scheme-a11yWCAG-baseline contrast rules for zudo-doc's two ramp-native color schemes (Default Light, Default Dark — sharing one set of base/accent/state ramps). MUST be consulted before adding a new scheme, or e...l-generator-cli-testerTest a single create-zudo-doc CLI generation pattern. Scaffolds a project, builds it, starts dev server, and verifies expected features. Use when testing generator output for a specific pattern.l-lessons-wt-teams-orchestrationProject lessons learned for running /x-wt-teams multi-agent epics in this repo. Read PROACTIVELY before planning or implementing any multi-wave epic (e.g. the Theme Batch / Theme Finalize epics, or an...l-lessons-zfb-migration-parityProject lessons learned for the zfb migration parity work (zudo-doc Astro → zfb). Read PROACTIVELY before planning or implementing any Phase A/B/C/D/E work, harness changes, or per-page regression fix...l-make-releaseRelease the three lockstep packages (@takazudo/zudo-doc-history-server, @takazudo/zudo-doc, create-zudo-doc) by following RELEASE.md's release procedure with the repository helpers in scripts/release/...l-migrate-to-preset-styleMigrate an existing zudo-doc project to the MINIMAL SCAFFOLD shape (epic #2651): diff against the pinned ~5-file base template, DELETE files that match a known deleted-from-template legacy path (host ...l-run-generator-cli-whole-testRun all create-zudo-doc CLI generation tests and fix bugs. Invokes /l-generator-cli-tester for each pattern, collects results, fixes failures, and verifies all patterns pass. Use for comprehensive gen...l-update-generatorDetect and fix drift between the main zudo-doc project and the create-zudo-doc generator CLI. Use when adding/removing features, or to verify the generator stays in sync. Also triggered by "update gen...l-zfb-upstream-devRules for editing the zfb upstream framework (Takazudo/zudo-front-builder) from this consumer project. ALWAYS work in a git worktree — never touch the `../zfb` root checkout directly, because concurre...test-flow-html-preview-hydrationAI-judged verification that the HTML Preview component (`data-zfb-island="HtmlPreviewWrapperInner"`) hydrates into the correct vertical-stack layout — title bar on top, preview iframe below, code togg...test-flow-sidebar-width-restoreAI-judged verification that the docs-page sidebar's persisted drag-width is restored on page reload before first paint, with no visible flash to the CSS-default width. Use when /verify-ui-ai dispatche...zudo-doc-design-systemProject-specific CSS and component rules for zudo-doc. Must be consulted before writing or editing CSS, Wind classes, color tokens, or component markup in this project. Covers: component-first strateg...zudo-doc-navigation-designNavigation design rules for zudo-doc documentation sites. Consult before creating new pages, restructuring directories, or designing header navigation. Covers: the recommended 3-level hierarchy (heade...zudo-doc-translateTranslate zudo-doc documentation between English and Japanese with project-specific conventions.zudo-doc-version-bumpBump the lockstep monorepo version, author package-specific changelogs, commit, tag all three packages, and create distinct GitHub releases. Use when: (1) User says 'version bump', 'bump version', 're...zudo-doc-writing-rulesDoc-writing rules for zudo-doc content (mdx files under src/content/docs/ and src/content/docs-ja/). Consult before writing or editing doc content. Covers: no h1 in content, sidebar_position is mandat...Previoussrc/content/CLAUDE.mdNextb4push