anyone-can-code
anyone-can-code contiene 21 skills recopiladas de mitunmanav, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
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.
Use when verify failed, same error twice, or something is broken. Diagnose before retry; not for first green build.
Use when a change would alter accepted scope/plan and needs user confirm. Not for tiny in-scope edits.
Use when moving to a new chat/thread/tool/model or context is near limit. Not for same-thread small questions.
Use when user asks what ACC is doing, what is next, or what is blocked in plain words.
Use when user wants force-save a lesson or promote a rule after a real win/fail. Not every turn — hooks auto-save memory.
Use when start point is unclear (idea, repo, bug, feature) before plan/build. Not when route already clear.
Use when intent is unclear and you must pick one ACC step (plan/build/verify/fix/resume). Route once then stop — not whole-session mode.
Use after meaningful code work or before verify to improve naming/clarity. Not instead of verify.
Use when work was interrupted, state looks stale, or user says continue/where were we. Not for brand-new work.
Use when changing ACC prefs (talk style, learning, automations, memory path). Not for code tasks.
Use when project lacks ACC folders, first install, or user says setup/bootstrap ACC. Not for daily plan/build.
Use when user wants a checkpoint: where we are, next step, blockers. Not for deep rebuilds.
Use after marketplace plugin refresh to migrate project state. Not for daily coding.
Use when user asks token/cost/usage of Codex. Zero-token disk read; not for product features.
Use when user asks what ACC remembers, wiki health, or memory looks broken. Not Codex built-in /memories.