setup
Use when project lacks ACC folders, first install, or user says setup/bootstrap ACC. Not for daily plan/build.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when project lacks ACC folders, first install, or user says setup/bootstrap ACC. Not for daily plan/build.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | setup |
| description | Use when project lacks ACC folders, first install, or user says setup/bootstrap ACC. Not for daily plan/build. |
Use $setup after the plugin is installed in Codex.
Reply rule:
This package is Codex Desktop. For Codex CLI, install Anyone Can Code CLI from the same marketplace (separate plugin).
Run /hooks, trust anyone-can-code, then restart Codex.
This is the plugin's memory. Without it, Codex forgets you between sessions. You must repeat this after every plugin update.
No trust = hooks do nothing = auto-memory dead. Then $setup.
none (default) or optional obsidian..codex/anyone-can-code/ (state, artifacts, learning, logs, memory).$setup --project-hooks; --agents-md write (never overwrite).doctor.py; writes receipts under state/receipts/.Open folder as vault, then select chosen memory folder.--memory-path <folder>--viewer none|obsidian--viewer-action none|download-page|install|open-vault--consent-viewer-action--import-source <path>--import-scope ask|project|user|shared--confirm-import--agents-md skip|write (default: skip; never overwrites existing file).codex/hooks/ for projects that want local lifecycle control.After setup, use action_suggest.suggest_actions. If suggestions: plain words —
"Codex Settings → Actions → paste script." Desktop-first UI; CLI can run same
scripts in terminal. NEVER write app settings yourself.
Next: $onboard or $orchestrator for first real task.
When this skill's job is finished:
Use when a plan or concrete tasks exist and user said build/go/implement. Not to invent scope or claim done without verify.
Use when goal/spec is clear and you need ordered tasks before writing code. Not while still clarifying.
Use when about to claim done/works/fixed, or user asks test/check/prove. Run evidence; not for pure planning chat.
Use when another installed plugin/skill may do the job better, or to route specialists. ACC stays workflow owner.
Use when user wants an explicit recorded decision or blocker saved to artifacts. Not silent monitoring.
Use when request is too vague to plan or build. Not when goal and constraints are already clear.