You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a contributor to Nexus, I want the repository to say where components are authored and how to run them, so that I do not look for them at the path they used to occupy.
Acceptance Criteria
Given the repository's contributor-facing documentation, when it is read, then it names the authored tree's location and states that .claude/ is not it.
Given that documentation, when it is read, then it describes the maintainer's loop as pointing the install location at the checkout, with the commands to do so.
GivenREADME.md, CLAUDE.md and docs/, when each is searched for instructions that place or deploy Nexus components into this repository's .claude/, then there are none.
Given a contributor follows the documented setup from a fresh clone, when they finish, then they can edit a component and see the edit take effect.
Notes
This story exists because the move is invisible in the diff to anyone who does not already know about it, and because the repository's own instructions are the first thing that goes stale when the arrangement they describe changes.
As a contributor to Nexus, I want the repository to say where components are authored and how to run them, so that I do not look for them at the path they used to occupy.
Acceptance Criteria
.claude/is not it.README.md,CLAUDE.mdanddocs/, when each is searched for instructions that place or deploy Nexus components into this repository's.claude/, then there are none.Notes
This story exists because the move is invisible in the diff to anyone who does not already know about it, and because the repository's own instructions are the first thing that goes stale when the arrangement they describe changes.