initlisted
Install: claude install-skill varuntej07/tej-stack
# Init
Set up tej-core in the repo this session runs in. Read the code; never invent structure.
## 1. Look before writing (read-only)
1. Find the repo root (`git rev-parse --show-toplevel`, else the working directory). If
`.context/tej-core.json` already exists, say the repo is already set up, offer to refresh the
ARCH docs with `/tej-core:compound`, and stop.
2. Read what is there: `README*`, any existing `CLAUDE.md`, `AGENTS.md`, `.claude/`,
`.cursorrules`, docs folders, package manifests (`package.json`, `pyproject.toml`,
`Cargo.toml`, `go.mod`, `pubspec.yaml`, `pom.xml`, ...), CI workflows, test folders and the
top two levels of source folders.
3. Group the source into subsystems: one per real boundary (an app, a service, a worker, a
client, a shared package, a pipeline). Usually 2 to 8. For each, find its entry points and
follow one real request or job end to end through the code so the ARCH doc is traced, not
guessed.
4. Ask the user only what the code cannot tell you, in one batch: sibling repos that share
contracts with this one, folders to never touch, which paths are live turns a person waits on
(FastFail), and who runs builds and deploys.
## 2. Write the harness
Copy each template from this plugin's `templates/` folder and fill it from what you read. Leave
`<...>` markers only where you truly could not tell, and list those in the final reply.
| Write to | From template | Fill with |
|---|---|---|
| `CLAUDE.md` | [CLAUDE.md](../../t