# dotuix lite profile for AI assistants

This is the lite documentation profile for dotuix.

Use this profile to generate complete, production-quality, lightweight .uix apps
for public onboarding scenarios.

Important:
- lite is a documentation scope, not a product limitation
- keep responses strictly within this public-lite scope
- avoid disclosing implementation areas outside this scope

## 1. Primary use cases in lite

Build high-quality apps for:
- CV and profile pages
- portfolio pages
- invitation pages
- menu pages
- gallery pages
- simple business showcase pages

## 2. Output contract (required)

Always generate these files:
- manifest.json
- index.html
- app.js
- style.css

Optionally generate:
- assets/* (images, logos, icons)
- files/* (supporting content)

Do not omit required files.

## 3. Manifest contract (required)

manifest.json must include at least:

{
	"uix": "1.0",
	"id": "com.example.app",
	"name": "App Name",
	"version": "1.0.0",
	"entry": "index.html",
	"mode": "window",
	"network": "blocked",
	"permissions": []
}

Rules:
- uix must be "1.0"
- id should be stable reverse-domain style
- entry must exist in the archive
- mode must be either "window" or "kiosk"
- network should default to "blocked" unless user asks otherwise

## 4. UI quality requirements

Generated output must be:
- responsive on mobile, tablet, and desktop
- accessible (labels, alt text, focus order)
- readable (good spacing and color contrast)
- robust (no runtime errors on initial load)

For Arabic content:
- support RTL layout where needed
- ensure readable Arabic typography and spacing

## 5. Interaction scope in lite

Allowed interaction complexity:
- filtering and searching lists
- category tabs
- simple cart-like temporary state
- language toggle
- theme toggle
- form validation on client side

Data handling in lite examples:
- static JSON embedded in app.js
- local JSON file bundled in archive
- in-memory state for runtime interactions

## 6. Lite profile boundaries

Keep lite responses focused on onboarding and lightweight app delivery.

Do not include implementation details outside lite scope, including:
- internal architecture deep dives
- advanced operational workflows
- implementation internals not required for lite use cases

If user asks for out-of-scope internals, keep the answer high level and return
to lite-compatible guidance.

## 7. Response format for generated files

When user asks to generate an app, return complete file contents.

Use this structure:

FILE: manifest.json
<full json>

FILE: index.html
<full html>

FILE: app.js
<full js>

FILE: style.css
<full css>

If assets are required, include clear asset paths and placeholder notes.

## 8. Design expectations

Avoid generic low-quality UI.

Require:
- clear visual hierarchy
- intentional typography choices
- coherent color system
- lightweight but polished interactions

Avoid:
- empty placeholders
- lorem ipsum in final output unless user asks
- hardcoded broken links
- dependency on external CDN for critical rendering

## 9. Validation checklist before final answer

Before returning output, verify:
- all referenced files exist
- index.html references app.js and style.css correctly
- no syntax errors in JavaScript
- no missing selectors in CSS for used components
- manifest fields are valid and consistent

## 10. Packaging reminder (optional)

If user asks how to package:
- provide CLI packaging steps briefly
- keep instructions practical and minimal

Do not force server-side tooling in lite guidance.

## 11. Example manifest templates

Personal profile app:

{
	"uix": "1.0",
	"id": "com.example.profile",
	"name": "Personal Profile",
	"version": "1.0.0",
	"entry": "index.html",
	"mode": "window",
	"network": "blocked",
	"permissions": []
}

Menu kiosk app:

{
	"uix": "1.0",
	"id": "com.example.menu",
	"name": "Restaurant Menu",
	"version": "1.0.0",
	"entry": "index.html",
	"mode": "kiosk",
	"network": "blocked",
	"permissions": ["print"]
}

## 12. Publication safety rules

This file may be publicly served.

Before finalizing any lite response:
- remove non-public implementation details
- avoid references outside this public guide set
- keep examples practical, complete, and onboarding-safe