# tela - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for tela. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ## What It Can Do - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0001` supported 0.86 ## How to Start - `git clone https://github.com/zcag/tela.git` Evidence: `README.md` Claim: `clm_0003` supported 0.86 - `claude mcp add --transport http tela https://telawiki.com/api/mcp` Evidence: `README.md` Claim: `clm_0004` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Needs admin / security approval - **Why**: Continuing may involve secrets, accounts, external services, or sensitive context; get admin or security approval first. ### 30-Second Read - **What to do now**: Needs admin / security approval - **Minimum safe next step**: Run Prompt Preview first; if credentials or an enterprise environment are involved, get approval before trialing - **Do not trust yet**: Role quality and task fit cannot be trusted directly. - **Continuing will touch**: Role selection bias, Command execution, Host AI configuration ### What You Can Trust Now - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0002` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0001` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0003` supported 0.86 ### What You Cannot Trust Yet - **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results. - **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI. - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `CLAUDE.md` - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. ### What Continuing Will Touch - **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions. - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `CLAUDE.md` - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md` - **Environment variables / API keys**: Project entry docs explicitly showing API key, token, secret, or account credential configuration. Why: If a real install needs credentials, use test credentials first and go through a permission/compliance review. Evidence: `CLAUDE.md`, `README.md`, `docs/architecture.md`, `docs/atlas.md` et al. - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Use an interactive trial to verify the task profile and role match first; do not import the whole role library up front. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **Do not use real production credentials**: Once an environment variable / API key enters the host or toolchain, it can create account and compliance risk. (applies when: When environment signals like API, TOKEN, KEY, or SECRET appear.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **Be ready to revoke test API keys or tokens**: If test credentials leak or are misused, you can cut losses quickly. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0005` inferred 0.45 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0006` supported 0.86 - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0001` supported 0.86 ### Context Scale - Total files: 2472 - Important-file coverage: 40/2472 - Evidence index entries: 80 - Role / Skill entries: 47 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for tela, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat tela as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for tela, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 47 role / Skill / project-doc entries. - **Submission assets** (project_doc): Widget screenshots + app icon for the Claude / ChatGPT directory submissions. Rendered from the real widget bundles backend/internal/api/widgets/ .html with demo-account data, cropped to just the app response per both forms' guidance . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/submission-assets/README.md` - **CLAUDE.md — tela** (project_doc): Working context for tela. Read before contributing. Full architecture is in docs/ docs/ and the deepest subsystem detail in docs/architecture.md docs/architecture.md ; this file is the conventions + hard rules + the things that bite. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CLAUDE.md` - **tela** (project_doc): The wiki that writes itself — from the code you already ship. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md` - **deck — Slidev render sidecar** (project_doc): A tela deck is a page whose body is Slidev markdown whole page — a page is either a deck or a doc, set by deck: true . Two output paths off the same parse + theme-injection core: Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `deck/README.md` - **tela — frontend** (project_doc): React 19 + TypeScript + Vite SPA for tela ../README.md . Tailwind v4 + Radix + Milkdown editor + TanStack Query/Router + Orama + cmdk + Lucide + Storybook. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `frontend/README.md` - **tela landing** (project_doc): The standalone marketing landing page for tela — a separate Astro static site, in the same repo as the app but built and deployed independently. backend/ and frontend/ are untouched by this. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `landing/README.md` - **tela-mcp** (project_doc): A thin stdio↔HTTP proxy to a Tela https://telawiki.com instance's built-in MCP server. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `mcp/README.md` - **internal/rag — semantic retrieval** (project_doc): Self-contained hybrid retrieval over pages : heading-aware markdown chunking, pluggable embeddings, and RRF-fused lexical + vector chunk search on Postgres + pgvector. Agent-first — no answer-LLM; every hit carries a citation page id + heading path . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/internal/rag/README.md` - **JWK Set JSON Web Key Set** (project_doc): ! Go Reference https://pkg.go.dev/badge/github.com/MicahParks/jwkset.svg https://pkg.go.dev/github.com/MicahParks/jwkset Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/MicahParks/jwkset/README.md` - **keyfunc** (project_doc): ! Go Reference https://pkg.go.dev/badge/github.com/MicahParks/keyfunc/v3.svg https://pkg.go.dev/github.com/MicahParks/keyfunc/v3 Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/MicahParks/keyfunc/v3/README.md` - **xxhash** (project_doc): ! Go Reference https://pkg.go.dev/badge/github.com/cespare/xxhash/v2.svg https://pkg.go.dev/github.com/cespare/xxhash/v2 ! Test https://github.com/cespare/xxhash/actions/workflows/test.yml/badge.svg https://github.com/cespare/xxhash/actions/workflows/test.yml Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/cespare/xxhash/v2/README.md` - **websocket** (project_doc): ! Go Reference https://pkg.go.dev/badge/github.com/coder/websocket.svg https://pkg.go.dev/github.com/coder/websocket ! Go Coverage https://coder.github.io/websocket/coverage.svg https://coder.github.io/websocket/coverage.html Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/coder/websocket/README.md` - **Go JOSE** (project_doc): ! godoc https://pkg.go.dev/badge/github.com/go-jose/go-jose/v4.svg https://pkg.go.dev/github.com/go-jose/go-jose/v4 ! godoc https://pkg.go.dev/badge/github.com/go-jose/go-jose/v4/jwt.svg https://pkg.go.dev/github.com/go-jose/go-jose/v4/jwt ! license https://img.shields.io/badge/license-apache 2.0-blue.svg?style=flat https://raw.githubusercontent.com/go-jose/go-jose/master/LICENSE Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/go-jose/go-jose/v4/README.md` - **Safe JSON** (project_doc): This repository contains a fork of the encoding/json package from Go 1.6. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/go-jose/go-jose/v4/json/README.md` - **jwt-go** (project_doc): ! build https://github.com/golang-jwt/jwt/actions/workflows/build.yml/badge.svg https://github.com/golang-jwt/jwt/actions/workflows/build.yml ! Go Reference https://pkg.go.dev/badge/github.com/golang-jwt/jwt/v5.svg https://pkg.go.dev/github.com/golang-jwt/jwt/v5 ! Coverage Status https://coveralls.io/repos/github/golang-jwt/jwt/badge.svg?branch=main https://coveralls.io/github/golang-jwt/jwt?branch=main Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/golang-jwt/jwt/v5/README.md` - **pgpassfile** (project_doc): ! https://godoc.org/github.com/jackc/pgpassfile?status.svg https://godoc.org/github.com/jackc/pgpassfile ! Build Status https://travis-ci.org/jackc/pgpassfile.svg https://travis-ci.org/jackc/pgpassfile Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/pgpassfile/README.md` - **pgservicefile** (project_doc): ! Go Reference https://pkg.go.dev/badge/github.com/jackc/pgservicefile.svg https://pkg.go.dev/github.com/jackc/pgservicefile ! Build Status https://github.com/jackc/pgservicefile/actions/workflows/ci.yml/badge.svg https://github.com/jackc/pgservicefile/actions/workflows/ci.yml Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/pgservicefile/README.md` - **CLAUDE.md** (project_doc): This file provides guidance to Claude Code claude.ai/code when working with code in this repository. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/pgx/v5/CLAUDE.md` - **pgx - PostgreSQL Driver and Toolkit** (project_doc): ! Go Reference https://pkg.go.dev/badge/github.com/jackc/pgx/v5.svg https://pkg.go.dev/github.com/jackc/pgx/v5 ! Build Status https://github.com/jackc/pgx/actions/workflows/ci.yml/badge.svg https://github.com/jackc/pgx/actions/workflows/ci.yml Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/pgx/v5/README.md` - **pgio** (project_doc): Package pgio is a low-level toolkit building messages in the PostgreSQL wire protocol. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/pgx/v5/internal/pgio/README.md` - **pgconn** (project_doc): Package pgconn is a low-level PostgreSQL database driver. It operates at nearly the same level as the C library libpq. It is primarily intended to serve as the foundation for higher level libraries such as https://github.com/jackc/pgx. Applications should handle normal queries with a higher level library and only use pgconn directly when required for low-level access to PostgreSQL functionality. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/pgx/v5/pgconn/README.md` - **pgproto3** (project_doc): Package pgproto3 is an encoder and decoder of the PostgreSQL wire protocol version 3. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/pgx/v5/pgproto3/README.md` - **Puddle** (project_doc): ! Go Reference https://pkg.go.dev/badge/github.com/jackc/puddle/v2.svg https://pkg.go.dev/github.com/jackc/puddle/v2 ! Build Status https://github.com/jackc/puddle/actions/workflows/ci.yml/badge.svg Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/jackc/puddle/v2/README.md` - **PDF Reader** (project_doc): ! Built with WeBuild https://raw.githubusercontent.com/webuild-community/badge/master/svg/WeBuild.svg https://webuild.community Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/ledongthuc/pdf/README.md` - **Readme** (project_doc): See ! Go Reference https://pkg.go.dev/badge/github.com/prometheus/client golang/prometheus.svg https://pkg.go.dev/github.com/prometheus/client golang/prometheus . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/prometheus/client_golang/prometheus/README.md` - **procfs** (project_doc): This package provides functions to retrieve system, kernel, and process metrics from the pseudo-filesystems /proc and /sys. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/prometheus/procfs/README.md` - **encoding/json ! GoDoc https://godoc.org/github.com/segmentio/encoding/json?status.svg https://godoc.org/github.com/segm…** (project_doc): encoding/json ! GoDoc https://godoc.org/github.com/segmentio/encoding/json?status.svg https://godoc.org/github.com/segmentio/encoding/json Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `backend/vendor/github.com/segmentio/encoding/json/README.md` - **go-mail - Easy to use, yet comprehensive library for sending mails with Go** (project_doc):