skills/codelit-guide/references/codelit-knowledge.md

# Codelit: public product reference

Retrieved for this plugin: September 23, 2026. Scope: public documentation, not an authenticated account, repository, or production audit. The sources below support documented capabilities; they do not prove an implementation or a completed run.

## Product identity [S1]

Codelit's quick-start documentation presents a conversation-led entry. A requested outcome leads to a Product Plan, Architecture, Agent Team, or Plan & Ship artifact in the same Thread. Users can preview the result and open its editing workspace. Keep the current product distinct from Codelit's earlier coding-learning product and from unofficial website mockups.

## Product Plans [S2]

Product Plan starters describe features, user stories, milestones, success measures, and suggested technology. A plan can lead into architecture or an agent-team design. Technology listed for an example product is not evidence of Codelit's own stack.

## Architecture [S3]

The feature catalog describes architecture generation and review using specifications, repository content, and dependency or infrastructure files, plus scaffolding and failure-exploration features. Treat these as published capability descriptions. A generated diagram or automated review is not a load-test result, compliance certification, or proof that any deployment is safe.

## Agent Teams [S4]

The build guide starts with the desired outcome, useful source, destination, and timing. It favors a small roster with specific responsibilities. Flow supports inspection and direct edits; advanced configuration exposes models, retries, instructions, and scopes. A verifier is useful when errors would be costly. None of this establishes a fixed internal roster for Codelit's own engineering system.

## Samples versus live work [S1]

The quick-start guide distinguishes a bounded safe proof from Live run. The safe proof checks example material without model or external-app calls. Live work requires account, connection, scope, approval, and spending checks. Connector writes and browser actions remain simulated during the personalized proof. Those are descriptions of Codelit, not capabilities granted by this plugin.

## Plan & Ship [S5, S6]

The public page accepts ideas, repositories, and proven teams as starting points for reviewed delivery. It describes product, architecture, repo-pack, and provider handoff outputs, including GitHub, Linear, and Jira. The detailed guide emphasizes preserving accepted source artifacts, showing changes before acceptance, and keeping source warnings visible. It also describes a new-repository GitHub path; the public overview describes a branch/pull-request path. Verify the task-specific adapter before claiming which action will occur. Draft planning can proceed with missing evidence, but that evidence must not be fabricated or silently marked verified.

## Public API boundary [S7]

The API page documents architecture generation, GitHub analysis, and a signed deployed-team trigger. It also describes signed result delivery. Its model-key guidance is inconsistent: one section requires a key while another says none is required. Resolve the current authentication contract from authoritative implementation or updated docs before integration. Never embed a deployment token or signing secret in a plugin, prompt, or public URL. No API endpoint was exercised while building this package.

## Navigation and public policy pages [S8, S9, S10, S11]

Product Plan starters, Architecture templates, and Agent Team templates are separate public destinations. This plugin links to those pages or to currently verified individual templates. Opening a link does not transfer a generated artifact or establish an authenticated connection. See [the navigation rules](template-links.md).

Codelit's public privacy policy and terms are available at the URLs below. Their published descriptions are not a substitute for inspected production configuration or an independent compliance audit. Do not infer that this skills-only plugin inherits the website's connected-account capabilities. The publisher should review whether these policies need clarification for a public plugin release.

## What this plugin actually contains

Five instruction skills, proposed templates, this dated product reference, an illustrative workflow, a proposed integration boundary, manual behavioral tests, a dated navigation registry, the publisher-supplied logo, public-submission preparation materials, and a local package validator. It has no MCP server, app dependency, scheduled task, background process, provider credentials, or autonomous runtime. It can guide available host tools only within their existing authorization.

## Unverified implementation details

Codelit's production framework, database, orchestration engine, queues, infrastructure topology, hosting, deployed model routes, tenant-isolation implementation, operational targets, and certification status are not established here. Answer such questions using authorized code/configuration/run evidence or label the answer a proposed design.

## Sources

- [S1] Quick start: https://codelit.io/docs/quick-start
- [S2] Product Plan starters: https://codelit.io/specs
- [S3] Feature catalog: https://codelit.io/features
- [S4] Build an Agent Team: https://codelit.io/docs/build-agent-team
- [S5] Plan & Ship guide: https://codelit.io/docs/plan-and-ship
- [S6] Plan & Ship overview: https://codelit.io/plan-and-ship
- [S7] API reference: https://codelit.io/docs/api
- [S8] Architecture templates: https://codelit.io/templates
- [S9] Agent Team templates: https://codelit.io/agent-templates
- [S10] Privacy Policy: https://codelit.io/privacy
- [S11] Terms of Service: https://codelit.io/terms

Refresh changing product facts before relying on them. Prefer current task-specific guides over broad marketing copy. Cite the section and source supporting the claim; do not cite a template as proof of production behavior.