「internal」の検索結果

Internal Harness instruction source for auto-paper-intake. Route through visible Harness aliases instead of invoking directly.

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

Internal Harness instruction source for auto-paper-harden. Route through visible Harness aliases instead of invoking directly.

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

Internal Harness instruction source for review-packet. Route through visible Harness aliases instead of invoking directly.

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

Manage Apple Reminders on macOS via remindctl — list, add, edit, complete, delete to-dos that sync to iPhone/iPad. Trigger on "reminder", "Reminders app", "提醒我" with phone sync, or adding personal todos with due dates. macOS only. Skip when the user wants agent-internal alerts (use memory_store or external scheduling) or calendar events.

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

Internal guidance for presenting Pi helper output back to the user

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

Internal guidance for composing prompts that Pi runs (DeepSeek by default) handle reliably for coding, review, diagnosis, and research tasks

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

Authoritative reference for Pi (@earendil-works/pi-coding-agent): install, configure, run, and extend it. Use for the CLI and configuration, providers and models, extensions, skills, MCP, codemode, the SDK/RPC, security and trust, design philosophy, and the pi repository's internals and contribution rules.

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

Internal helper contract for calling the pi-companion runtime from Claude Code

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

Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: "work backwards", "write a PRFAQ", "press release first", "is this idea worth building", "pressure-test this concept", "filter this before brainstorm", "is this a real product". Also catches solution-first pitches ("I want to build X that does Y") and technology-first pitches ("use AI to...") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.

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

Skill for developing REST API endpoints in internal/server/. Covers routing, request validation, WebSocket streaming, and API conventions.

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

Skill for developing AI agent engine components in internal/agent/. Covers the ReAct loop, swarm delegation, planning, verification, memory reflection, and cron automation.

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

Skill for developing messaging channel adapters via WASM Plugins and managing routing, session state, pairing codes, and accounts in internal/channels/.

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

Add a Gradle dependency or module, or triage a build failure. Use when editing gradle.properties or a build.gradle.kts. Not for plugin internals (convention-plugin-development) or version bumps (dependency-update).

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

Author or modify a build-logic convention plugin. Use when changing plugin internals, the diagnostics catalog, or Rust-native wiring. Not for adding a dependency/module (gradle-build-system) or version bumps (dependency-update).

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

Topic cluster and keyword-to-page mapping — group keywords by search intent (validated by SERP overlap, not word similarity), map each cluster to an existing or proposed page, flag cannibalization, and lay out pillar, supporting posts, and internal links. Use when asked to "build a content cluster", "map our SEO cluster for [topic]", "which page should target these keywords", "create a topic cluster", or "what should our pillar page be about".

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

Content brief generator — takes a topic or keyword and produces a complete content brief with target keyword, search intent, recommended structure, internal link targets, word count, CTA, and competitive gap analysis. Use when asked to "write a content brief", "brief this blog post", "plan this article", or "what should we cover for [keyword]".

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

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

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

Internal legal controls review — approval workflows, contract lifecycle, access to sensitive docs. Use when asked to "audit our controls", "review approval workflows", or "who can access sensitive contracts".

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

Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before commits or releases, when writing deployment docs for an OSS project, or when the user asks to "set up the privacy guard", "install privacy-guard", "check for leaks", "protect this public repo". Bootstraps a pre-commit hook backed by a gitignored local denylist plus gitleaks.

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

Martial arts as body discipline — the shared pedagogical structure across striking, grappling, and weapon arts (stance, distance, timing, ukemi, live partner work, graded ranking, and the ethical container the best schools enforce). Covers karate, judo, jiu-jitsu (Brazilian and traditional Japanese), aikido, kendo/kenjutsu, boxing, muay Thai, and wrestling at enough depth that an agent can place a user into a reasonable first-month practice and recognize the safety failures that matter most. Leans on Moshé Feldenkrais's judo background and Yang Jwing-Ming's martial scholarship for the internal-to-external bridge. Use for any query about beginning a martial art, training injury patterns, graded progression, or the ethics of combat training.

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

Comparative framing across contemplative and mind-body traditions — Sōtō Zen and Rinzai Zen, Theravada vipassana, Tibetan Vajrayana, classical yoga and its eight limbs, Daoist internal cultivation, secular MBSR and MBCT, engaged mindfulness as Thich Nhat Hanh teaches it, Christian contemplative prayer, Sufi dhikr, the Hesychast tradition of the Eastern Orthodox church — for the routing agent who has to understand where a user is already standing before recommending a practice. Covers the pedagogical voice of each tradition, the places they overlap, the places they genuinely disagree, and the non-sectarian framing the college department uses. Use when a user arrives with a prior tradition, when a query spans more than one tradition, or when the agent needs a vocabulary for what is shared and what is lineage-specific.

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

Statics, dynamics, stress-strain analysis, materials selection, failure modes, and finite element analysis concepts for engineered structures. Covers free-body diagrams, equilibrium, internal forces (shear and moment), beam deflection, column buckling, material properties, factor of safety, fatigue, fracture mechanics, and FEA workflow. Use when analyzing loads on structures, selecting materials, predicting failure, or interpreting structural behavior.

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

Corporate finance fundamentals for evaluating business decisions under cost, time, and risk constraints. Covers time value of money, net present value, internal rate of return, payback period, break-even analysis, cost-benefit analysis, debt vs equity, working capital, and the basic financial statements. Use when evaluating an investment, sizing a funding round, structuring a capital stack, or reading a balance sheet.

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

Identity, authentication, authorization, and token management for cloud platforms. Covers Keystone-style scoped tokens, OAuth 2.0 flows, OpenID Connect, JWT structure and pitfalls, federation with SAML/OIDC, service-to-service auth with mTLS and SPIFFE, principle of least privilege, IAM role design, and the service catalog pattern (public/internal/admin endpoints). Use when designing authn/authz for a multi-tenant cloud service, integrating with an identity provider, or reviewing IAM policies for over-privilege.

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