4,041 件 ・ 関連度順
概要と使いどころ
Modular design, interface stability, dependency management, AI-code health. Triggers: architecture, design, structure, modules, dependencies, coupling, system design.
日本語の概要は準備中です。原文の説明を表示しています。
Record a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name any document type inside the subject — journey, prd, idea, or cpat included — to get exactly that type. Planning a feature or an unnamed intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.
日本語の概要は準備中です。原文の説明を表示しています。
Critical pre-implementation review. Find what AI breaks. Verdict: PROCEED, REVISE, or RETHINK. Triggers: review plan, tear apart, critique, analyze.
日本語の概要は準備中です。原文の説明を表示しています。
Используй только внутри активного Codex Project Autopilot-проекта, когда data-layer уже относится к плану автопилота.
日本語の概要は準備中です。原文の説明を表示しています。
Используй только внутри активного Codex Project Autopilot-проекта, когда уже выбрана проектная фаза и нужен design direction по плану автопилота.
日本語の概要は準備中です。原文の説明を表示しています。
Show KERNEL help. The unified skill system, state operations, agents, current plugin status. Triggers: help, how, what, skills, commands.
日本語の概要は準備中です。原文の説明を表示しています。
Rules as hypotheses: falsifiable tests, confidence updates, graduate or kill. Triggers: experiment, hypothesis, prove, test rule, validate methodology, evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you create a CLI written in Julia packages or MCP servers
日本語の概要は準備中です。原文の説明を表示しています。
Initialize KERNEL links and AgentDB in a confirmed Vaults directory.
日本語の概要は準備中です。原文の説明を表示しています。
Code review for PRs or staged changes. >80% confidence threshold. Verdict: APPROVE, REQUEST CHANGES, or COMMENT. Triggers: review, pr, code review.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnosis before prescription: reproduce, hypothesize, isolate, fix root cause, add a regression test; refactor mode maps deps, coupling and blast radius. Triggers: bug, error, fix, broken, not working, crashed, stack trace, exception, refactor, restructure, coupling, dependency map.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review.
日本語の概要は準備中です。原文の説明を表示しています。
Используй только внутри активного Codex Project Autopilot-проекта после discovery или approval, а не для обычных архитектурных вопросов вне автопилота.
日本語の概要は準備中です。原文の説明を表示しています。
Context engineering: compaction, progressive disclosure, structured notes via AgentDB. Triggers: tokens, compaction, memory, handoff, summarize, context window.
日本語の概要は準備中です。原文の説明を表示しています。
Используй только когда пользователь явно просит запустить Codex Project Autopilot, продолжить проект из .codex-agent или в текущем workspace уже есть активный .codex-agent.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-agent orchestration: lane contracts, worker-model doctrine, fault tolerance. Triggers: orchestrate, coordinate, agents, parallel, spawn, contract, tier 2, tier 3.
日本語の概要は準備中です。原文の説明を表示しています。
Observability dashboard. Session stats, agent tracking, hook performance, learning health. Triggers: metrics, stats, dashboard, observability.
日本語の概要は準備中です。原文の説明を表示しています。
How AgentGuards enforces its guardrails in Codex — fully automatic, via hooks, with nothing for you to call. Load this if asked how AgentGuards works, whether you need to screen something yourself, or why no agentguards check_input / authorize_action tools are available.
日本語の概要は準備中です。原文の説明を表示しています。
First-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Modes, named as the first word: init import converts the repo's authored context — CLAUDE.md, AGENTS.md, .cursor/rules and other agent instructions, ADR and RFC folders, contributor docs, internal pages of a published docs site, recoverable git history — into native typed documents with no import marks, staged by a plan when the volume is large; init refresh adds facts that appeared since, or drills into one domain with init refresh <domain>. Use on a fresh clone, empty `.archcore/`, 'set up archcore', 'migrate our CLAUDE.md to archcore', 'import our docs and ADRs', or to wire host configs. Not for individual docs or planning.
日本語の概要は準備中です。原文の説明を表示しています。
Audit or explicitly synchronize Claude and Codex repository governance without overwriting conflicts. Triggers: governance sync, CLAUDE.md, AGENTS.md, instruction mirror.
日本語の概要は準備中です。原文の説明を表示しています。
Report AgentGuards guardrail status. Use when the user asks whether AgentGuards is active, healthy, or correctly configured in Codex.
日本語の概要は準備中です。原文の説明を表示しています。
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных frontend-задач вне автопилота.
日本語の概要は準備中です。原文の説明を表示しています。
The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review.
日本語の概要は準備中です。原文の説明を表示しています。
AI code quality checks. The Big 5: input validation, edge cases, error handling, duplication, complexity. Triggers: quality, big 5, ai code, review, validate.
日本語の概要は準備中です。原文の説明を表示しています。