メニュー
Linear issue tracking — create issues when features are discussed, assign on start, move through In Progress → Done. Always active during coding sessions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | linear |
| version | 1.0.0 |
| description | Linear issue tracking — create issues when features are discussed, assign on start, move through In Progress → Done. Always active during coding sessions. |
| allowed-tools | ["Bash","Read","MCP"] |
Always active. Any work discussed in a session should be tracked.
| Field | Value |
|---|---|
| Team | Ara (key ARA) |
| Project | Ara launch v1 |
| Me | Adi Singh (me) |
| Status | When |
|---|---|
| Todo | Planned, ready to pick up |
| In Progress | Actively working |
| In Review | PR attached, awaiting review |
| Done | Merged/shipped |
list_issues(query: "...", team: "Ara")save_issue(title, description, team: "Ara", project: "Ara launch v1", state: "Todo")ARA-42)save_issue(id: "ARA-42", assignee: "me", state: "In Progress")
save_issue(id: "ARA-42", state: "In Review", links: [{url: "<pr_url>", title: "PR #N"}])
save_issue(id: "ARA-42", state: "Done")
| Action | Tool | Key params |
|---|---|---|
| Search | list_issues | query, team: "Ara" |
| Create / update | save_issue | title, team, state, assignee, links |
| List statuses | list_issue_statuses | team: "Ara" |
| My profile | get_user | query: "me" |
End-to-end validate a `text.ara.so/backend` (website-agent) fix against a real Railway preview environment BEFORE merging to main. Pushes the current branch, deploys the SHA to the long-lived `preview` Railway env, confirms the new `git_sha` is live via `/healthz`, then sends a focused signed webhook replay (single-turn or short multi-turn) to a reserved 555-01XX test phone, and polls Braintrust for the root span's `outcome` / rounds / tools / reply. Use whenever you change anything in `backend/src/` (tool handlers, system prompt, builder loop, etc.) and want production-fidelity proof — not just unit tests — before opening the PR. Invoked as `/replay-railway-preview` or `/replay railway preview`.
Ara's secrets convention — all runtime credentials live in Infisical (project "Ara-passwords"), one folder per active GitHub repo (`/ara-engineer`, `/text-ara-so`). The old megarepo lives at `/legacy-ara-megarepo` tagged `legacy` — reference only. Never ask the user to paste keys; never commit .env; never build a custom vault.
Align the website-agent (system prompt + routing) with successful on-Ara website building; analyze Braintrust traces for derailment (wrong phase, local-dev tutoring, missing deploy, paywall/connect confusion), patch `text.ara.so/backend` (primarily `system-prompt.ts`), then verify in a tight loop—`bt` / Braintrust evals / `bun run e2e` (replay + live)—and report a before vs after fit table. Invoked as `/align`, `/align <trace url>`, `/align users …` (pair with `/trace` to gather traces). Companion to `/trace`.
Ara agent-trace debugging — inspect Braintrust traces for the website-agent (TS/Bun, Cerebras, Vercel AI SDK v6). Invoked as `/trace recent`, `/trace turn <turn_id>`, `/trace convo <chat_id>`, `/trace user <phone>`, `/trace top users` (aggregate: who messaged most in a time window — one latest-turn link per sender, table below), `/trace tool <name>`, `/trace span <id>`, `/trace <url>`, `/trace test` (run canonical e2e via `text.ara.so/backend/scripts/e2e.ts` (`bun run e2e --target=local --scenarios=<name>`)), `/trace score`, `/trace online`, or `/trace grow`. **Use `/align`** to align system prompt and gates to traces and report before/after tables (`skills/align/SKILL.md`). **When the user asks for users’ traces / links:** give **one permalink per user** — the **latest** `webhook.inbound` root only. **When they ask for top / busiest users over a time range:** use the **top users table** format (Msgs, User, single review link) — no per-thread “all turns” column unless they ask.
Deeply research a technology already in the stack. Pulls latest official docs, changelogs, release notes, production recipes, and pitfalls via heavy web search — then maps findings onto the exact usage pattern in this repo to surface underused features and confirm best practices. Use whenever someone asks "are we using X right?", "what's the best way to use X for Y?", or "what did X ship recently that we should adopt?"
Braintrust `bt` CLI for Ara — every agent-facing service emits spans to the `Ara` project (org `Aradotso`). Use for inspecting logs/traces/prompts/evals, authenticating, SQL over spans, and wrapping new code with tracing. For the Ara-specific span shape and debug recipes (`/trace recent`, `/trace turn`, `/trace user`, etc.) see the companion `/trace` skill.