# Loopx Project

Use for LoopX project lifecycle work: connect or configure a project/Goal, repair...

- Repository: https://github.com/loopx-project/loopx (6526 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add loopx-project/loopx --skill loopx-project -g -a claude-code -y`
Codex: `npx skills add loopx-project/loopx --skill loopx-project -g -a codex -y`
Cursor: `npx skills add loopx-project/loopx --skill loopx-project -g -a cursor -y`
Gemini CLI: `npx skills add loopx-project/loopx --skill loopx-project -g -a gemini-cli -y`

## Description

Use for LoopX project lifecycle work: connect or configure a project/Goal, repair project-local state or stale dashboard status, sync registry entries, or diagnose CLI/PATH/status/history routing. In an already bound Goal, also use for a material direct-user deliverable or correction that must refine cumulative outcome requirements. Other ordinary task execution and routine refresh-state settlement already directed by a current interaction_contract do not require this skill. For registering durable project materials, prefer loopx-doc-registry.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# LoopX Project Workflow

Use this skill when the requested operation changes or diagnoses the project
lifecycle, Goal configuration, registry routing, or status projection, or a direct
user request materially refines the bound Goal’s supporting outcomes. A LoopX
mention, registry path, or routine `refresh-state` command in an admitted task
does not by itself select the project lifecycle workflow.

For ordinary task execution, follow the current `interaction_contract`, its
required reads and ordered settlement commands. Do not repeat onboarding,
registry synchronization, or lifecycle discovery merely to execute that packet.
This routing rule does not replace fresh admission, lease checks, required
reads, or repair instructions. A missing or contradictory contract still needs
the relevant diagnosis; an explicit request to use this skill still applies.

If the task is mainly about reading,
remembering, recording, indexing, or registering a durable project material,
load `loopx-doc-registry` and use that narrower workflow first.

LoopX has two layers:

- **Project-local state**: each repo owns `.loopx/registry.json`; new Goal state
  defaults to `.loopx/goals/<goal-id>/ACTIVE_GOAL_STATE.md`.
- **Shared local control plane**: the default `~/.loopx` stores run history and
  `registry.global.json` for multi-project status.

Use the registry-declared `state_file` and the resolved runtime/global-registry
route for existing installations. `.codex/goals` and `~/.codex/loopx` are legacy
compatibility paths, not defaults to recreate or migrate implicitly. If routes
conflict, diagnose the existing state before selecting or migrating one.

Do not manually copy one project's registry entry into another project. Local
`connect` and `refresh-state` should sync into the shared global registry
automatically.

## Read The Relevant Procedure Before Acting

The rest: https://github.com/loopx-project/loopx/blob/HEAD/skills/loopx-project/SKILL.md