Takazudo

Get a second opinion from OpenAI Codex CLI on a plan or approach. Use when: (1) During planning phase of /x-as-pr or /x-wt-teams to validate the approach, (2) User says 'codex 2nd', 'second opinion', or 'codex opinion', (3) Wanting an alternative perspective…

Generate or redesign raster images (PNG mockups, illustrations, photos, UI design polish) from inside Claude Code by driving Codex CLI's built-in $imagegen, billed to ChatGPT-included usage instead of per-image OpenAI API charges. Use whenever the user wants…

Web research using OpenAI Codex CLI (codex exec). PREFERRED over general web research. Use when: (1) User says 'research', 'codex research', 'look up', or 'investigate', (2) Researching libraries, APIs, best practices, or technical topics, (3) Gathering…

Code review using OpenAI Codex CLI (codex exec review). PREFERRED over /light-review for code review. Use when: (1) User says 'review', 'code review', or 'codex review', (2) After implementation when quality check is needed, (3) Child agents self-reviewing.…

Translation using OpenAI Codex CLI (codex exec). PREFERRED for translation. Use when: (1) User says 'translate', 'codex translate', 'translation', or 'codex translator', (2) Translating between languages (Japanese, English, etc.), (3) Translating…

Document writing using OpenAI Codex CLI (codex exec). PREFERRED over general writing tasks. Use when: (1) User says 'write document', 'write docs', 'codex write', or 'codex writer', (2) Writing README, documentation, or technical content, (3) Drafting text…

Deep code quality review focused on structure, refactoring, and best practices. Use when: (1) User says 'review', 'deep review', or 'code review', (2) After implementation when a quality check is needed, (3) Before marking a PR as ready. Default backend is…

Sync the user's Claude Code workflow skills into the OpenAI Codex CLI settings repo ($HOME/.codex) as Codex-native ports, fix the Codex .gitignore for new local state, then commit and push. Use when: (1) user says '/dev-codex-sync-settings-from-claude', 'sync…

Audit exact electronic-component identities and run the end-to-end workflow for adding or replacing a BOM part. Use whenever circuit, schematic, PCB, BOM, firmware, bring-up, substitution, or related documentation could depend on a component rating, pin,…

Resolve exact EXAMPLE-MPN component limits and application constraints. Use whenever EXAMPLE-MPN, its LCSC ID, manufacturer, function, pins, package, substitution, bring-up, or firmware behavior is relevant.

Navigation design rules for the zudo-led-lamp doc site (zudo-doc). Consult before creating new pages, restructuring directories, or changing header navigation. Covers: 3-level hierarchy (header → sidebar → nested), file-structure-is-navigation principle,…

Audit cross-component circuit behavior, evidence chains, substitutions, startup, rails, protection, sensing, firmware assumptions, thermal limits, and as-built state. Use whenever a question spans multiple exact component skills or changes USB-PD/NVM, either…

Audit the exact AL8860MP-13 LED-driver stage and its RLP25FEER200 sense resistor, FXL0630-330-M inductor, and R+O SS26 catch diode. Use for Board L LED current, CTRL/PWM behavior, pins, thermal/layout limits, faults, substitutions, bring-up, or power-stage…

Resolve the exact ALPS EC11L1525G01 rotary encoder used on Board L. Use for quadrature phase order, detents, switch terminals, mechanical drawing, soldering, lifetime, lifecycle uncertainty, and encoder-interface questions.

Audit the exact AP63203WU-7 3.3 V synchronous buck and its FNR4030S4R7MT inductor and CL21A226MAQNNNE output capacitors. Use for Board L V3P3 startup, EN-open behavior, pins, switching/fault timing, L/C stability, thermal/layout work, substitutions, or…

Audit the exact BHFUSE BSMD1206-075-30V resettable input PPTC on Board L. Use for C976305/F1 identity, hold/trip behavior, V15 input protection, time-current response, ambient derating, resistance, cycling/reset, package, layout, substitution, fault analysis,…

Project-specific CSS and component rules for zudo-doc. Must be consulted before writing or editing CSS, Tailwind classes, color tokens, or component markup in this project. Covers: component-first strategy, design token system, three-tier color architecture,…

Translate zudo-doc documentation between English and Japanese with project-specific conventions.

Bump package version, generate changelog docs, commit, tag, and create GitHub release. Use when: (1) User says 'version bump', 'bump version', 'release', or 'zudo-doc-version-bump', (2) User wants to create a new release of this project.

Writing and formatting rules for MDX articles in zcss. Use when: (1) Writing or editing MDX docs in src/content/docs/, (2) Creating new articles, (3) User says 'writing rules' or 'article format'. Auto-load when working on MDX content.

Run before-push quality checks for the zudo-css project. Use when: (1) User says 'b4push', 'before push', or 'run checks', (2) Before pushing to remote, (3) After completing implementation work.

Create or convert CSS best-practices articles into "deep articles" with sub-pages in the zcss Astro site. Use when: (1) An article topic has enough depth to warrant "see more" reference sub-pages, (2) Converting a flat .mdx article into a category with index…

Translate English docs to Japanese for the Astro i18n locale. Use when: (1) User wants to translate en docs to ja, (2) User says 'translate', 'ja version', 'Japanese translation', (3) User wants to check for missing ja docs.

Guidance for using CssPreview component in zcss documentation articles. Use when: (1) Writing or editing CssPreview demos in MDX articles, (2) Deciding whether to use defaultOpen={true} or false, (3) User asks about demo component usage patterns.

Verify committed manual PDFs against the revision each manufacturer currently publishes, and propose (or run) refreshes for stale ones. Use when: (1) User says 'check stale manuals', 'verify manuals', 'manual sweep', 'staleness check', or asks whether any…

Run the complete PDF processing pipeline to convert the manual PDF into Next.js application data. This command executes all steps automatically: split, render, extract, translate, build, and manifest.

Run comprehensive pre-push validation covering code quality, build, production server, and smoke e2e tests. Use when: (1) Completing a PR or feature implementation, (2) Before pushing significant changes, (3) After large refactors, (4) User says 'b4push',…

Capture screenshots of all manual pages at high resolution for translation verification. Use when verifying that translations match page images, checking layout correctness, or inspecting for content mismatches.

Capture all manual pages and verify translations match page images using AI-powered checking. Identifies extraction failures and can regenerate extracted text from images.

Datasheet-aware schematic review for this USB-PD power-supply board. Exports the KiCad schematic to a compact netlist, walks a power-supply checklist (VBUS sense paths, regulator EN/feedback dividers, dropout headroom, polarity, decoupling, abs-max), and…

Bump the X digit of this project's X.Y.Z version — a real product release. Use when the user says 'bump version x', 'product release', 'l-bump-version-x'. Resets Z to 0, KEEPS Y (lifetime JLCPCB-order counter), commits, tags, and creates a GitHub release.

Bump the Y digit of this project's X.Y.Z version — a new JLCPCB PCBA order. Use when the user says 'bump version y', 'new JLCPCB order', 'l-bump-version-y', or is placing the next PCB order. Resets Z to 0, commits, tags, and creates a GitHub release.

Bump the Z digit of this project's X.Y.Z version — a local checkpoint tag. Use when the user says 'bump version z', 'tag a checkpoint', 'l-bump-version-z'. Commits and creates a git tag ONLY (no GitHub release).

Browser automation with two efficiency tiers. Tier 1: headless-check.js for quick health checks, screenshots, error detection (JSON output). Tier 2: Playwright CLI (@playwright/cli via npx) for interactive automation — click, fill, navigate, snapshots with…

Verify CSS/UI changes match what the user asked for. Uses deterministic computed style checks to avoid LLM confirmation bias. Use when: (1) After CSS or layout changes the user asks to verify, (2) User says 'verify ui', 'check the result', 'confirm it works',…

AI-based visual confirmation that a problem is resolved — Level 6 (final-resort) testing. Use ONLY when /verify-ui (mechanical computed-styles or screenshot pixel-diff) cannot reach the assertion AND writing an E2E (Playwright) is intractable — e.g.…

Project lessons learned for the zfb dev-server watcher and tick narrowing (zfb-watcher ChangeKind coalescing, zfb-build orchestrator fan_out_safe gate, commands/dev.rs tick-candidate derivation, the PageSelection::All fallback, the dependency graph's Content…

Project lessons learned for client bundling (zfb-build bundler, bundle.exclude, shadow staging, esbuild resolution) and for running autonomous review→fix loops on this area. Read PROACTIVELY before planning or implementing work touching…

Search and reference documentation from the zfb (zudo-front-builder) project. Use when answering questions about zfb features, CLI usage, configuration, content collections, routing, build pipeline, or architecture decisions.

Project-specific CSS and component rules for zudo-doc, including the Composer Polish epic's non-negotiables — accent budget (≤2-3 accent elements per viewport, hover always neutral), border ladder, 14px functional-text floor. Must be consulted before writing…

Bump package version, generate changelog docs, commit, tag, and create GitHub release. Use when: (1) User says 'version bump', 'bump version', 'release', or 'zudo-doc-version-bump', (2) User wants to create a new release of this project.

Translate zudo-doc documentation between English and Japanese with project-specific conventions.

Build, verify, and install CCResDoc.app locally for testing. Use when: (1) User says 'build ccresdoc', 'rebuild ccresdoc', 'install ccresdoc', 'ccresdoc-build', (2) User wants a fresh CCResDoc.app after Rust, app/, or src-tauri changes, (3) After Rust or…

Run comprehensive pre-push validation covering Rust formatting, Clippy lints, Rust tests, and the zfb app build. Use when: (1) Completing a PR or feature implementation, (2) Before pushing significant changes, (3) After large refactors or multi-file edits,…

Develop, build, or fix the upstream zfb crate without disturbing $HOME/repos/myoss/zfb's working tree. Use when: (1) Editing zfb source as part of a ccresdoc task, (2) Filing a zfb PR / merging zfb fixes, (3) Bumping pinned versions (esbuild, tailwindcss,…

Design system reference for the mdx-formatter doc site (zudo-doc based). Use PROACTIVELY when: (1) Writing or modifying any CSS/styling in doc/, (2) Creating or editing React components in doc/src/components/, (3) Adding new pages or layouts to the doc site,…

Run comprehensive pre-push validation covering code quality, builds, tests, and doc site. Use when: (1) Completing a PR or feature implementation, (2) Before pushing significant changes, (3) After large refactors or multi-file edits, (4) User says 'b4push',…

Refresh every zfb example site to a clean, up-to-date main: checkout main and git pull (fast-forward only) for each. Never touches a repo that has meaningful uncommitted changes -- reports it instead. Use when the user types /l-sync, or asks to…

Run one task across every zfb example site (the zfb-example-* siblings of zfbex-tweaker) so it doesn't have to be repeated by hand in each one. Use when the user types /l-each, or asks to apply a change, fix, dependency bump, or any dev task "to each / across…

Refresh every wisdom repo to a clean, up-to-date main: checkout main and git pull (fast-forward only) for each. Never touches a repo that has meaningful uncommitted changes -- reports it instead. Use when the user types /l-sync, or asks to…

Run one task across every wisdom repo (the *-wisdom siblings of wisdom-tweaker) so it doesn't have to be repeated by hand in each one. Use when the user types /l-each, or asks to apply a change, fix, dependency bump, or any dev task "to each / across all /…