「repo」の検索結果

コンペ開始時の7項目チェックリストを対話的に埋め、survey/competition/overview.md として保存する。新しいコンペに着手するときに最初に使う。

新しい実験フォルダを reference/ から雛形コピーして作成する。SESSION_NOTES.md と run.sh も自動生成。Claude用は expA00, A01, ...、人間用は exp200, 201, ... の連番で命名する。

Run pre-submission validation. Handles 5 formats — Kaggle CSV / Kaggle Code Competition / prediction-file zip / Docker container / Simulation agent. Delegates to the submission-validator agent for mechanical checks. Use right before any submission.

日本語の概要は準備中です。原文の説明を表示しています。

Create a new experiment folder by copying reference/ as a template. Auto-generates SESSION_NOTES.md and run.sh. Claude experiments use expA00, A01, ...; human experiments use exp200, 201, ... in sequential numbering.

日本語の概要は準備中です。原文の説明を表示しています。

Walks through the 7-item competition onboarding checklist interactively and saves it to survey/competition/overview.md. Use first when starting a new competition.

日本語の概要は準備中です。原文の説明を表示しています。

Invoke only when the user explicitly asks to review code through the "single level of abstraction / layered error handling" lens — a function does only its own layer's business logic while errors are handled above or below. The agent reports detections, raw-count measurements, and move directions. Apply only when the user explicitly requests this lens.

日本語の概要は準備中です。原文の説明を表示しています。

Use when generating changesets in the pythinker-code repository — deciding whether to write one, which package to list, the bump level, the wording, and the confirmation workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Use when cutting, debugging, or verifying a pythinker-code (TSC monorepo) release — changesets flow, the ci release-packages version PR, release.yml anatomy, npm Trusted Publishing OIDC, native assets, brew tap, CDN redeploy, and their failure modes. Invoked by /release.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing or building any terminal user interface — choosing a layout paradigm, keybindings/interaction model, color system, data visualization, or motion. Framework-agnostic universal patterns that work with Ratatui, Ink, Textual, Bubbletea, or any TUI toolkit. For the repo's own pythinker-code TUI, use write-tui instead.

日本語の概要は準備中です。原文の説明を表示しています。

Use when reviewing a pull request in this repository — check the description against the PR template section by section, then run a separate regression and user-impact pass that produces impact levels and a review summary.

日本語の概要は準備中です。原文の説明を表示しています。

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating or updating a pull request in this repository — how to fill in each section of the PR template with concise, reviewer-friendly content, including the behavior-change table.

日本語の概要は準備中です。原文の説明を表示しています。

Three-phase code review. Investigates internally, verifies findings, then reports only confirmed issues.

日本語の概要は準備中です。原文の説明を表示しています。

Use when analyzing an existing TypeScript or JavaScript codebase to decide where and how to introduce Inngest. Covers repository discovery, framework and package detection, finding durability gaps in HTTP handlers, webhooks, cron jobs, queues, long-running jobs, AI agents, Agent Evals, polling loops, eval loops, and side-effect-heavy code, then producing and implementing an incremental integration plan.

日本語の概要は準備中です。原文の説明を表示しています。

Show a team skill's eval history — committed receipts per version and this machine's local runs — as a Markdown board from the terum-skills CLI, without fetching. Use when the user asks how a shared skill scored, which version passed, or what its receipts say.

日本語の概要は準備中です。原文の説明を表示しています。

Show one skill in full — its team record or Library folder, versions, installs, health, and its eval report when it is a team skill — as Markdown boards from the terum-skills CLI. Use when the user names a skill and asks what it is, who installed it, how it scored, or what its receipt says.

日本語の概要は準備中です。原文の説明を表示しています。

chrome-devtools-mcp launcher — a single bash script that resolves Playwright's bundled Chrome-for-Testing and Node.js directly through Nix. See repo README for usage, override mechanisms, and version compatibility.

日本語の概要は準備中です。原文の説明を表示しています。

Use this when setting up a GitHub repo to push its Nix builds to Juspay's shared OSS Attic cache (cache.nixos.asia/oss) — adds the substituter to flake.nix, a nix-cache.yml GitHub Actions workflow, and prompts for the ATTIC_TOKEN secret.

日本語の概要は準備中です。原文の説明を表示しています。

Enter talk mode — conversation and research, no repo changes. ONLY invoke when the user explicitly types `/talk` or `$talk`; never auto-select from a natural-language question or design discussion.

日本語の概要は準備中です。原文の説明を表示しています。

odu MCP server launcher — drive CI from a coding agent. `bin/serve` resolves odu via Nix and runs `odu mcp` in the cwd. See the repo README for the tools/resources and override knobs.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.

日本語の概要は準備中です。原文の説明を表示しています。

Generate PDFs from LaTeX (.tex) or Markdown (.md) using Tectonic, a self-contained TeX engine. Use whenever the user wants a PDF, whether converting markdown, compiling existing LaTeX, writing a document from scratch (reports, resumes, letters, CVs), or live-rebuilding while the user edits. Trigger on words like "make a PDF", "convert to PDF", "render this markdown", "compile this tex", "latex", "tectonic", "typeset" — even when the tool is never named.

日本語の概要は準備中です。原文の説明を表示しています。

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.

日本語の概要は準備中です。原文の説明を表示しています。

DECIDE-phase doctrine for an Arbor research run: when to merge, prune, combine, or finalize; how the held-out merge gate works; and the rule that the final report uses TEST scores. Load before deciding what to do with completed experiments.

日本語の概要は準備中です。原文の説明を表示しています。