「context」の検索結果

Decide when to delegate to Honey's read-only subagents (hive-scout, hive-reviewer) instead of working inline, so the expensive tokens — large file reads and review passes injected back into the orchestrator's context — come back compressed (Honey Lever 3). Use when a task is search-heavy or review-heavy, spans many files, or you want to keep the orchestrator's context small. Not for trivial one-file work.

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

Rewrite a memory or context file (CLAUDE.md, AGENTS.md, a todo or notes file) into Honey-terse form so it costs fewer input tokens every session, without losing meaning. Backs up the original first. Use when asked to shrink or compress context files, trim CLAUDE.md, or cut per-session input cost. Prose only — never code, config, or data.

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

Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.

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

OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.

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

Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.

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

Scaffold or standardize a production-ready repository structure with specs, source layout, tests, CI, agent context, config examples, release notes, and operational docs. Use when starting a new repo, turning a prototype into a maintainable project, adding missing repository foundations, or creating a repo skeleton before implementation. For AGENTS.md-only context scaffolding, use agentsmd-scaffold.

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

Fix Flutter home feed / main screen stuck on loading spinner after login when using Riverpod StreamProvider that watches GoRouter location changes. Use when: (1) Screen shows BrandedLoadingIndicator or CircularProgressIndicator permanently after successful auth redirect, (2) Widget watches a route-type-gating provider that returns AsyncValue.loading() intermittently, (3) Logs show route location oscillating between stale and current paths during post-login transition (e.g., /welcome/* after /home/0), (4) Provider chain has double-gate: widget gates on pageContext AND data provider also gates on pageContext. Distinct from riverpod-infinite-rebuild-loop (rapid rebuilds) — this causes permanent loading state, not infinite rebuilds.

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

Use when implementing managing AI conversation context.

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

Creates structured context summaries for continuing work across AI sessions. Use when ending a session to enable seamless continuation in a new session without losing context.

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

Builds a month of social media post ideas for SMBs. Takes brand context, platforms, and goals and produces a structured content calendar with post topics, formats, angles, and visual direction for each slot. Output saves to context/content-calendar.md for use by /caption-writer and /social-creative-designer. Supports Instagram, LinkedIn, Facebook, TikTok, and X.

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

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

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

Structured logging with proper levels, context, PII handling, centralized aggregation. Use for application logging, log management integration, distributed tracing, or encountering log bloat, PII exposure, missing context errors.

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

Condense Stage 3 combined discussion content into compact markdown context for Stage 4 multi-round follow-up drafting.

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

Idiomatic Go concurrency - sync primitives, channel semantics, the select statement, and the standard channel patterns (cancellation/done-channel, fan-out/fan-in, pipeline, or-done, context, worker-pool). Use when writing or reviewing Go that spawns goroutines, shares state, or coordinates over channels, even if the user never says "concurrency" - e.g. data races, deadlocks, goroutine leaks, sync/context/select usage, or "make this parallel". Distilled from luk4z7/go-concurrency-guide.

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

Retrieve relevant information from a knowledge base using semantic, keyword, or hybrid search to ground a query. Use when the task starts with a corpus or index that must be searched; use context-ranking when candidate chunks already exist and only need ordering.

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

Think and work like an expert Human–Computer Interaction Researcher. Use when a task calls for Human–Computer Interaction Researcher judgment. Reasons from situated context, Fitts/GOMS/KLM, and CHI contribution types; runs contextual inquiry through LMM/CLMM analysis with SUS/NASA-TLX triangulation; uses Prolific/OSF and treats demand characteristics, novelty effects, ordinal misuse, and WEIRD samples as first-class failure modes.

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

Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI', 'create knowledge base', 'set up project context', or 'configure AI context'.

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

Apply DDD tactical patterns when working with domain code, and validate proposed domain models before approval (design mode). Enforces aggregate design, value objects over primitives, entity identity rules, and bounded context boundaries. Use when creating or modifying domain models, designing aggregates, working in the domain layer, or when the user mentions 'domain', 'aggregate', 'value object', 'entity', 'bounded context', or 'DDD'.

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

Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.

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

Sequenced launcher that bootstraps QA on a project with no QA in place. Chains qa-project-context → test-strategy → test-planning in one guided run, then points you at automation. Use when: "set up QA on a new project," "QA from scratch," "no QA exists yet," "/qa-start." Not for: onboarding a QA engineer to an existing team with existing tests — use qa-project-bootstrap. Not for: "which skill do I use" with no clear match — use qa-do. Related: qa-project-context, test-strategy, test-planning, qa-project-bootstrap, qa-do.

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

Make technology decisions for every product capability by discovering existing assets, evaluating vendor-aligned options, and categorizing as Reuse/Extend/Build/Buy/Integrate/Research during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on "tech stack", "build or buy?", "what technologies?", "technical decisions", "what do we reuse?", "existing stack", "vendor constraint", "IBM-first", "what tools do we need?", "evaluate solutions", "select tech stack". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and cross-references. Feeds v0.6 Architecture Design.

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

Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5 Red Team Review. Triggers on requests to identify risks, stress-test the idea, perform red team review, or when user asks "what could go wrong?", "identify risks", "red team", "risk assessment", "challenge assumptions", "stress test the idea". Consumes all prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as interview context. Outputs RISK- entries with owner decisions and mitigations. Feeds v0.5 Technical Stack Selection.

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

Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution", "implementation", "write code". Consumes EPIC- (context), TEST- (acceptance criteria). Updates existing IDs and creates code. Outputs working code with @implements traceability tags.

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

[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].

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