メニュー
MANDATORY: Invoke this skill when adding new prompts, agents, rules, commands, or entire configuration folders to the agent.files repository. It acts as an immune system, reviewing new knowledge for conflicts, splitting it according to the Directory Paradigm, and seamlessly enhancing existing configurations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Auto-apply when working with Angular. Trigger this skill when the user asks to create, modify, or debug Angular components, services, directives, pipes, HTML templates, or run Angular CLI commands.
Auto-apply when working with Go (Golang). Trigger this skill when the user asks to create, modify, or debug Go code, HTTP handlers, middleware, CLI tools, or Go tests.
Auto-apply when working with Zig. Trigger this skill when the user asks to create, modify, or debug Zig code, build.zig scripts, or Zig tests.
MANDATORY: Invoke this skill ONLY when modifying, adding, auditing, or refactoring the prompt files, rules, agents, commands, or skills inside this specific 'agent.files' configuration repository. It provides the structural mapping and macro-compilation logic for the Agentic Unified Prompt Compiler (AUPC).
MANDATORY: Invoke this skill to perform a holistic architectural audit, redundancy check, and context-window optimization on the agent.files repository. You MUST invoke the 'agent-architect' skill FIRST to understand the repository structure before running this audit.
MANDATORY: Invoke this skill when adding support for a BRAND NEW AI IDE (e.g., VS Code Copilot, Windsurf) to the agent.files repository. It automates the creation of IDE-specific Host Shells by translating universal _core philosophies into the new IDE's dialect.
| name | agent-ingestor |
| description | MANDATORY: Invoke this skill when adding new prompts, agents, rules, commands, or entire configuration folders to the agent.files repository. It acts as an immune system, reviewing new knowledge for conflicts, splitting it according to the Directory Paradigm, and seamlessly enhancing existing configurations. |
| disable-model-invocation | true |
SCOPE CONSTRAINT (CRITICAL):
You have been invoked to ingest new AI prompt configurations into the agent.files repository. You MUST already understand the underlying architecture of this project. If you do not understand the Directory Paradigm, the Lexical Ban, and the <!-- @import --> macro system, STOP and load the agent-architect skill immediately.
The user will provide you with new knowledge. This could be:
Your goal is to safely assimilate this knowledge into our existing _core/ (Universal Philosophies) and all existing IDE Host Shells (e.g., opencode/, cursor/, copilot/, or any other bootstrapped IDE directories in the root). You must maximize enhancement while strictly preventing logical conflicts and IDE dialect leakage.
You must execute the ingestion process through the following strict phases:
_core/ dimensions (1_governance through 5_commands) and existing Host Shells.git commit -m", but our _core/1_governance/execution_safety.md says "NEVER run git commit").If no conflicts exist (or if the human resolves them), you must deconstruct the new knowledge.
glob, grep, Task, YAML, @Codebase, slash commands).
_core/ 4D structure (1_governance, 2_workflows, 3_engineering, 4_refactoring, 5_commands).Once the pure knowledge is categorized into _core/ (either by enhancing an existing file or creating a new one), you must deploy it to the Host Shells.
CRITICAL: You must respect the diverse routing paradigms of each IDE.
.cursor/rules/*.mdc)? If so, define the exact globs..cursor/agents/*.md) with the correct YAML (model: fast or inherit).opencode/agents/*.md)?DO NOT write or modify any files to the file system yet. You must follow a strict "Propose -> Approve -> Execute" workflow.
_core/ and the target IDE directories._core/ files and the IDE-Specific Routing Rules for the Host Shells.