Results for “poka-yoke”

Guides incremental code improvements, error-proofing through types and validation, and standardization to raise code quality and prevent defects.

Play Yoink, an onchain capture-the-flag game on Base. Yoink the flag from the current holder, check game stats and leaderboards, view player scores, and compete for the trophy. Uses Bankr for transaction execution.

Write, review, debug, test, and optimize Python Polars code with version-grounded object types, schemas, and execution boundaries.

Play Pokemon via headless emulator + RAM reads.

Server-side JavaScript hooks for PocketBase (pb_hooks). Use when writing custom routes, event hooks, cron jobs, sending emails, making HTTP requests, querying the database, or extending PocketBase with server-side logic. Covers the goja ES5 runtime, routing, middleware, all event hooks, DB queries, record operations, and global APIs.

Automates the entire software development lifecycle from PRD to production with zero human intervention, using multi-agent orchestration and memory systems.

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Synthesize source-indexed proof-material items into the final proof-usage playbook. Use when Codex needs to cluster proof items by proof shape, de-duplicate across sources, design reusable taxonomy entries, update proof-usage indexes and source maps, or preserve material-ID links from cooked proof entries.

Use the status-briefing skill to run `pk-reconcile session-start`, then

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Write unit tests with table-driven patterns and interface mocking in Go. Use when writing Go unit tests, table-driven tests, or using mock interfaces.

Play Pokemon games autonomously via headless emulation. Starts a game server, reads structured game state from RAM, makes strategic decisions, and sends button inputs — all from the terminal.

Police the project's vocabulary — bust vague terms, keep the CONTEXT.md glossary sharp, and lock in decisions worth remembering as ADRs. Use when the user debates naming, says "what should we call this", asks to pin down terminology, wants a decision recorded, or when another skill (hot-seat, whiteboard) surfaces a decision that clears the ADR bar. Just reading the glossary for vocabulary is NOT this skill — trigger only when the words or decisions are being changed.

Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".

PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.

Start voice calls via the OpenClaw voice-call plugin.

波总个人财务中枢 v2.0 — 债务追踪 + 消费分析 + 还款日预测 + 暴力催收。当你收到"还了XX YY元""花呗清了""我的债务""截图""消费"等财务相关指令时使用。

Configures autonomous heartbeat and cron-based proactive routines (e.g., morning briefing setup, unanswered-message scan cadence). Invoke when user is SETTING UP or MODIFYING a proactive routine, not when the routine itself fires. Cron crons execute their own logic — they do NOT load this skill. Triggers: "set up proactive check", "configure heartbeat", "add morning briefing", "tune cron cadence".

Applies four disciplined mindsets—audit, debt, help, review—to cut complexity, track deferrals, surface reference, and catch over-engineering in codebases.

波总口语输入 → 结构化任务记录 → 同步到副官系统。当波总说"记一下""记录下来""有个任务"或描述要做的事时使用。

日本語の生産性コーチングモード。明示的な依頼、反復失敗、受け身、検証不足、品質不満のときに、構造化トラブルシューティングと証拠ベースの完了確認を促す。

PUA Shot — compact all-in-one PUA reference for explicit injection into sub-agents or short sessions. Strong flavor, same evidence-first behavior.

五条悟（少年漫）认知与表达框架（压缩蒸馏）：无敌教师、眼罩梗、领域展开爽点 触发：咒术回战 等。虚构；非暴力细节

Challenge decisions, surface counter-arguments, flag assumptions. Trigger: 'should I', 'is this right', 'critique', 'poke holes', 'second opinion', 'devil's advocate'. Auto-fired by ijfw-intent-router.

PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Play an onchain capture-the-flag game on Base by yoinking the flag from the current holder, checking game stats and leaderboards, and competing for the trophy using Bankr for transaction execution.

PUA Shot — compact all-in-one PUA reference for explicit injection into sub-agents or short sessions. Strong flavor, same evidence-first behavior.

Detect monorepo structure, identify shared chokepoints, and generate safe parallel lane specs aligned to package boundaries

Logic (akao-logic)

PUA Loop — guided iterative development with recurring checks, completion evidence, and pause/abort markers. Use only when the user explicitly asks for loop/自动迭代 mode.

Rule (agak-rule)

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher quality and fewer defects.

Guide for continuous improvement, error proofing, and standardization in code and processes. Use when improving code quality, refactoring, or discussing process improvements.