「reading」の検索結果

The sprint completeness oracle — a mechanical, exit-code-driven check that every feature in a sprint manifest is provably complete across three dimensions (a done-record reference, resolvable edge tests, and a resolvable wiring test). Fails loud with a per-feature gap list naming the missing dimension. Read-only. Use to gate a sprint before it is called done (Slice A of the sprint-mode epic), or any time you want a completeness reading.

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

Bring documentation prose down to a high-school reading level without losing precision. Runs after the content is written and before humanizer. Targets grade 9 on four measures — sentence length, vocabulary, clause load and jargon density — and carries the rewriting moves that actually shift them.

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

Use ane for ALL file exploration, discovery, reading, and editing unless the user states otherwise. `ane exec <file> --chord "<chord>"` handles reads (Yank), searches (List), and edits (Change, Delete, Replace, Append, Prepend, Insert). Prefer ane over builtin file tools and shell utilities like grep, sed, and cat.

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

Any live-web task via the Firecrawl CLI — including ordinary web research: searching the web, reading or extracting pages, gathering sources, discovering site URLs, bulk extraction, downloading a site, change alerts, or pages needing clicks/login — web only; local files route to firecrawl-parse. For US legal or regulatory questions use gov; for papers use firecrawl-research-index; for library, API, error, or bug questions use firecrawl-developer-index.

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

End-of-week reflection report. Mines your Claude Code transcripts from the last 7 days to produce a self-contained HTML file with (1) the topics/areas you explored, (2) distilled key learnings with live-searched further-reading links, and (3) a token/command/skill/ctx-stack usage summary. Use when the user says "week in review", "weekly review", "what did I learn this week", "my week", or runs /week-in-review.

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

Separates signal from noise in metrics you cannot observe directly, updating a belief from evidence instead of reacting to the latest reading - Bayesian updates over competing explanations, and a filter that says whether this week's move is real. Use when a metric moves and someone wants to act, when diagnosing why traffic or revenue changed, when a dashboard number contradicts intuition, or when deciding whether a trend is real yet.

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

Models what a competitor will do next and what happens if you respond - best response, equilibrium, and the difference between a rival who optimises perfectly and one who does not. Use before a price change or price war, when a competitor launches something, when deciding whether to match a rival's move, when analysing a market with few players, or when someone asks "what will they do if we do this".

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

Resolve repository documentation authority, repair reading paths and explanations, or shape a bounded public projection. Maintain docs after a bounded change when indirect reader promises, generated or paired sources, version/evidence boundaries, or unclear authority need attention. Ordinary known updates stay in normal development; not for isolated prose polishing, code review, or broad runtime audits.

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

Subagent flow for deep-reading GitHub issues + their linked/closing PRs to the bottom. Captures CURRENT state, maintainer status updates, reporter repro, blocking reviewer concerns, hidden second bugs, cross-repo duplicates. Invoked by weekly-report orchestrator; runs as a general-purpose subagent so the orchestrator's context stays small.

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

Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.

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

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

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

Map existing materials into a first knowledge record, or investigate a subject's history in depth. Use whenever the user asks to map, survey, go through, reconstruct or investigate what already exists - folders of documents, decision records, meeting notes, emails, exports, code - or wants a starting record built from existing materials, even when the word 'record' is never said: consult this before listing or reading the files yourself, because a map has an agreed scope, a protocol and a report. Also, once, at a suitable moment, to offer the starting choices where a workspace has no record and the work is clearly ongoing - never on a greeting. Learning while working needs no map. Requests come in any language.

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

Read the project's knowledge record before answering from memory or from the files. Use before answering about the project's state, a number, a date, a decision, a source, a deadline or what was agreed - even a casual 'what's the situation with X' or 'is that quote still current'; before changing a recorded value; and whenever the opener or a grounding line names entries. After finding relevant IDs, prefer kpop context to read them with their declared dependencies and checks. Uses pull for concise readings or when the checked reader is unavailable, affects for changed inputs, and search when no ID is known. A missing id is not absence. Not for showing the record's page (the hub skill). Requests come in any language.

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

Jev (TypeSafe System One) inner loop for ego-browser — one ~0.4 s typed decision per DOM step instead of an LLM turn. Use for multi-step clicking through a semantic page: fill known values into a form, set filters, open a row/card/menu by name, reach a page via nav or site search. Escalates login, payment, free text, canvas and content reading back to you.

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

Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary.

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

Use when reading a contract for risk and constraint — clause shape, redline priority, what the contract actually binds. Triggers on 'review this contract', 'what does this MSA constrain'.

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

Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.

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

Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).

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

Harness-first workflow for evaluating and improving terminal UIs through real interaction. Use this whenever the user wants to review a TUI experience, compare before/after behavior, identify UX friction, validate navigation or filtering flows, inspect visual stability, or turn observed interaction problems into concrete follow-up tests and improvement recommendations. Prefer this skill any time a TUI should be exercised through a reproducible PTY/session harness instead of only reading code.

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

Use this Canvas-owned clean-room skill for PDF work where layout, extraction, generation, forms, page operations, or visual verification matter. Trigger for reading PDFs beyond plain text, creating PDFs, merging, splitting, rotating, watermarking, extracting tables or images, filling forms, OCR handoff, and final PDF QA.

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

Gmail CLI for searching emails, reading threads, sending messages, managing drafts, and handling labels/attachments. Triggers: Gmail, send email, search email, read email, email thread, email draft, email labels, gmcli.

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

Use this Canvas-owned clean-room skill for creating, reading, editing, reviewing, redlining, commenting, or repairing Word `.docx` documents. Trigger for Word documents, DOCX files, memos, reports, letters, templates, tracked changes, comments, table of contents, headers, footers, page numbers, and Google Docs-targeted documents that should be authored as DOCX first.

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

Load this skill whenever the project involves writing, editing, or reviewing content for a general audience, including UI copy, help text, error messages, documentation, and instructions. Under no circumstances use jargon, complex sentence structures, or unexplained acronyms without providing plain alternatives. Absolutely always target a reading level accessible to the broadest possible audience. Load alongside content-design/SKILL.md for all content work.

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

[Content] Use when you need background HTTP server rendering markdown files with calm, book-like reading experience.

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