「context」の検索結果

Build students' capacity to place historical documents in their temporal and social context. Use when students read sources without considering what was happening at the time, or know the context but don't deploy it.

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

Use when starting work on a PERSONAL brand — a founder, coach, or creator, not a company: creates `.agents/personal-brand-context-global.md` covering story, expertise, audience, positioning, platforms, visual identity, and the asset inventory of style refs, face refs, logo, palette, and background, with region variants for US, EU, SEA, and LATAM. Skills 23 to 28 read it first. Trigger on 'personal brand setup', 'set up my founder brand', 'coach personal brand context', 'creator profile setup', 'the AI does not know my story', 'build my personal brand from zero'. Not for — a company or product brand, see `00-marketing-plan-global` and `product-marketing-context-global`; the 12-month strategy built on this, see `23-personal-brand-strategy-global`.

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

Phoenix context design — creating/splitting contexts, Scope (1.8+); Use when editing contexts, routers, or designing…

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

Phoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers. Use when editing contexts, routers, or designing boundaries.

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

Context management specialist for multi-agent workflows and long-running tasks. Use when coordinating multiple agents, preserving context across sessions, or managing complex project state. Focuses on context compression and distribution.

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

When the user wants to create or update their startup context document. Also use when the user mentions "set up context", "tell you about my startup", or any other skill needs context that doesn't exist yet.

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

Create optimized project-context.md for AI agent consistency. Use when the user says "project context" or "generate context"

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

Run a complete design workflow -- from establishing context through four progressive design levels (Capabilities, Components, Interactions, Contracts) to an approved blueprint. Composes knowledge-priming, context-anchoring, learning-harvest, collaborative-judgment, design-first, architecture, and domain-driven-design into one process. Handles both new features (create context doc) and resuming existing work (load context doc). Level 5 (Implementation) is delegated to code-forge. Use when starting a design, planning architecture, or when the user says 'design a feature', 'blueprint', 'start designing', 'plan the architecture', or 'let's design before coding'.

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

Transform v0.6 specifications into context-window-sized work packages (EPICs) during PRD v0.7 Build Execution. Triggers on requests to create epics, scope work, break down implementation, or when user asks "create epics", "scope work", "break down work", "context window sizing", "what to build first?", "implementation planning", "epic breakdown". Consumes API-, DBT-, FEA-, ARC-. Outputs EPIC- entries with objectives, ID references, dependencies, and context windows. Feeds v0.7 Test Planning.

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

Create and fill .agents/qa-project-context.md with the project's tech stack, test frameworks, CI/CD pipeline, environments, quality goals, risk areas, team structure, and conventions. This is the one file every other QA skill reads first, so they skip redundant discovery and give context-aware advice. Use when: "set up QA context," "configure testing," "initialize project," first use of any QA skill. Not for: bootstrapping a brand-new project's QA end-to-end — use qa-start (which calls this skill as its first step). Related: qa-start, risk-based-testing, test-strategy, qa-metrics, playwright-automation.

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

Build students' capacity to place historical documents in their temporal and social context. Use when students read sources without considering what was happening at the time, or know the context but don't deploy it.

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

Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"

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

Build, normalize, and maintain the user's Career Context file so downstream platform outputs stay factual and consistent. Use when the user wants an agent to consolidate CV data, LinkedIn exports, GitHub history, project summaries, bio facts, achievements, or positioning into one professional source of truth before editing platform-specific assets.

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

Maintainer-only skill for refreshing VitaeContext wiki knowledge from official sources. Use only from a local repository clone when a maintainer asks to refresh one module, audit all module wiki entries, or audit module source lists.

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

Delegate long-context analysis, research, and large-document summarization to Google Gemini CLI (1M-token context) via non-interactive `gemini -p`, preserving Claude context. Use when the user says 'use gemini'/'hand off to gemini' or a task needs 100K+ tokens of context.

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

Use when looking up library documentation, API references, framework patterns, or code examples for ANY library (React, Next.js, Vue, Django, Laravel, etc.) and the Context7 MCP server is unavailable or not configured. Fetches the same current docs directly via the Context7 REST API as a fallback. Triggers on: how to use library, API docs, framework pattern, import usage, library example.

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

Generate a state document (context transfer) that allows any fresh AI instance to resume work without conversation history. Use this skill whenever the user asks to checkpoint, create a state transfer, save state, generate a handoff document, create compaction insurance, or says anything like 'snapshot this', 'create a context transfer', 'checkpoint', 'save state for handoff', 'write a recovery doc', or 'transfer context'. Also trigger when the user mentions compaction concerns, session handoff, multi-session continuity, or wants to preserve the current conversation's state. Works for any conversation type: projects, research, debugging, investigations, design sessions, or long-running chats. This skill produces a structured markdown document optimized for AI cold-start recovery, not human notes.

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

Master optimization protocol for Gemini Agent (Antigravity) to unlock native 2M+ to 10M+ long-context reasoning, Gemini 4 Pro & Gemini 4 Flash dynamic thinking budget control, native context caching, Multimodal Live API, and high-speed problem solving / Protokol optimasi utama untuk Gemini Agent (Antigravity) untuk mengaktifkan pemikiran long-context 2M+ hingga 10M+, kontrol thinking budget dinamis Gemini 4 Pro & Gemini 4 Flash, context caching native, Multimodal Live API, dan pemecahan masalah kecepatan tinggi.

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

Decomposes a contextualized plan into atomic, independently executable tasks with complete embedded context, registered through the plan API. Use after SAM Stage 3 Context Integration produces the contextualized plan artifact — when the plan is ready for task generation with CLEAR ordering, CoVe checks, and dependency graphs for parallel execution.

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

Package codebases into LLM-optimized markdown, and run the Deep Think Authority pipeline (context-builder → Deep Think review → structured AUTHORITY → Flash/Antigravity implementation agent). Use when generating project context, preparing Deep Think reviews, or binding a weaker coding agent to a senior reasoning pass.

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

Generates a structured Project Brief — a comprehensive markdown document that extracts goals, architecture, knowledge file inventory, Custom Instructions summary, Memory contents, current state, ecosystem position, and key decisions from a Claude Project. Briefs serve as uploadable context documents: add one to any other Project for immediate deep awareness of the source Project's purpose, architecture, and progress. Use when user says "create a brief," "brief this project," "extract project context," "generate a project summary for another project," "I need to share this project's context," "prepare this project for cross-project reference," or "document this project." Also use when the user is preparing to work across Projects and needs portable context. Do NOT use for session handoffs, project audits, or Memory optimization (use rootnode-session-handoff, rootnode-project-audit, or rootnode-memory-optimization respectively, if available).

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

AI internal coordination using stigmergic signals — managing information freshness in context and memory, decay rates for assumption staleness, and emergent coherent behavior from simple local protocols. Use during complex tasks where multiple sub-tasks must coordinate, when context has grown long and information freshness is uncertain, after context compression when information may have been lost, or when sub-task outputs need to feed into each other cleanly without degradation.

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

Sets up a complete per-client workspace in Cowork with isolated context, preferences, deliverable templates, running notes, decision log, and automatic status reporting. For consultants, agencies, and professional services. Useful when onboarding a new client, during engagement kickoffs, for organizing existing client relationships, and when multiple clients need isolated context. Use when the user says "set up a client", "new client project", "client system", "client context", "client workspace", or "onboard a client".

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

Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.

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