LlmWikis Style

--- title: "LlmWikis Style" description: "LlmWikis Style is a uai-system source file exposed by AIWikis.org with provenance, current content, and generated explanation." slug: "llmwikis/uai-system/files/uai-style-uai-b8be54df" status: "working-draft" trust_level: "generated-evidence" source_status: "current-source-file" content_type: "source-file" generated_by: "tools/sync-source-files.ps1" last_reprocessed: "2026-04-30" source_site: "llmwikis.org" source_url: "https://llmwikis.org/" canonical_url: "https://aiwikis.org/llmwikis/uai-system/files/uai-style-uai-b8be54df/" canonical: "https://aiwikis.org/llmwikis/uai-system/files/uai-style-uai-b8be54df/" source_reference: ".uai/style.uai" file_type: "uai" content_category: "uai-system" content_hash: "sha256:b8be54df676fdca0ac25734fb58c9273b8925cd8d83ed17cdd20d882b5f77424" last_fetched: "2026-04-30T22:07:25.2671233Z" last_changed: "2026-04-29T02:07:37.0821645Z" import_status: "unchanged" duplicate_group_id: "sfg-106" generated_explanation: true explanation_last_generated: "2026-04-30T22:07:25.2671233Z" source_domains:

tags:

related_files:

---

"llmwikis.org"
"ai-memory"
"provenance"
"llm-wiki"
"uai"
"retrieval"
"prompt-size-minimization"
""

LlmWikis Style

LlmWikis Style is a uai-system source file exposed by AIWikis.org with provenance, current content, and generated explanation.

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/uai-system/files/uai-style-uai-b8be54df/
Source reference	`.uai/style.uai`
File type	`uai`
Content category	`uai-system`
Last fetched	`2026-04-30T22:07:25.2671233Z`
Last changed	`2026-04-29T02:07:37.0821645Z`
Content hash	`sha256:b8be54df676fdca0ac25734fb58c9273b8925cd8d83ed17cdd20d882b5f77424`
Import status	`unchanged`
Raw source layer	`data/sources/llmwikis/uai-style-uai-b8be54df676f.uai`
Normalized source layer	`data/normalized/llmwikis/uai-style-uai-b8be54df676f.txt`

Current File Content

Structure Preview

LlmWikis Style
Writing Style
Editorial Style
UI Style
Code Style
Naming

Raw Version

---
uaix: "1.0"
type: style
title: "LlmWikis Style"
created: "2026-04-26"
updated: "2026-04-27"
author: "LlmWikis maintainers"
version: 8
---

# LlmWikis Style

## Writing Style

- Use plain, source-aware technical language.
- Write the LLM Wiki handbook as practical builder documentation: concrete folders, procedures, prompts, checks, and examples.
- Clearly separate current support from planned work.
- Mark UAIX-related pages as non-normative explainers.
- Link to canonical UAIX routes instead of restating normative UAI-1 details as if LlmWikis owns them.
- Do not attribute the LLM Wiki concept by creator name in public website copy. Direct links to the foundational idea file are allowed when labeled neutrally.
- Prefer concrete templates, checklists, and page types over broad marketing claims.
- Write for humans and AI readers.

## Editorial Style

- Every factual model, benchmark, protocol, organization, or source page needs citations before it becomes public reference content.
- AI-assisted drafts must be human-reviewed.
- Use "planned", "candidate", "pilot", or "not yet live" for future features.
- Avoid claiming freshness unless a source timestamp and ingestion path exists.

## UI Style

- Quiet, technical, readable, and focused on navigation.
- Treat "Screen Real Estate" as a project design term: informational pages should spend the first viewport on useful content, route choices, matrices, examples, status, and source context rather than decorative whitespace, oversized cards, or brochure-style spacing.
- Use a public-interest reference-site structure for dense informational pages: navigation, search, route indexes, status tables, source boundaries, and practical sequences should appear before any optional narrative or promotional framing.
- Use liquid layouts by default. Wide sections may span the available viewport with modest gutters, while readable prose keeps a measured line length.
- Do not use Bootstrap, Bootstrap-like marketing templates, decorative hero art, glass panels, gradient-orb backgrounds, or product-launch CTA blocks for the handbook surface.
- Use the civic/reference palette now established in the theme: paper, ink, sage, civic green, ochre, rust, reference blue, and muted plum. Do not return to the dark SaaS cyan/purple gradient palette without explicit approval.
- Treat the site like a static documentation handbook even while implemented in WordPress: stable routes, dense pages, visible status, code blocks, prompt blocks, and crawler-friendly text.
- Use cards only for repeated items or bounded tools.
- Keep page sections full-width or unframed; avoid nested cards.
- Make the brand visible in the first viewport.
- Keep the palette mixed and restrained, not a one-hue theme.
- Keep buttons, labels, and navigation text short enough to fit on mobile.
- Preserve the responsive audit findings as implementation rules, not public report content: constrained reading measures, auto-fit grids, scroll-safe tables/code blocks, touch-sized controls, no horizontal page overflow, and viewport checks after public-surface changes.
- Keep the civic/reference stylesheet layer after legacy dark portal rules until the old CSS is consolidated. The launch surface should not render black page backgrounds, low-contrast dark hero text, fixed narrow card columns, fixed mobile menu overlays, or one-word-per-line card copy.
- Treat Light/Dark as a real site theme, not a one-off contrast patch: the visible toggle label names the active theme, the dark theme should invert the light civic/reference surfaces with deliberate readable tokens, and both themes should keep the same liquid layout density.

## Code Style

- Follow WordPress escaping and sanitization conventions.
- Keep custom behavior in theme/plugin files, not WordPress core.
- Prefer simple WordPress APIs over custom database access.
- Add comments only where they clarify non-obvious behavior.

## Naming

- Use `LlmWikis` for the project name in docs and public copy.
- Use `LlmWikis.org` for the public site name.
- Use `llmwikis-` prefixes for theme/plugin functions and handles.

Why This File Exists

This is a UAI AI Memory handoff file from llmwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This .uai file is a compact style packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: LlmWikis Style; Writing Style; Editorial Style; UI Style; Code Style; Naming. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Provenance And History

Current observation: 2026-04-30T22:07:25.2671233Z
Source origin: current-source-workspace
Retrieval method: local-source-workspace
Duplicate group: sfg-106 (primary)
Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LlmWikis Style",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/uai-system/files/uai-style-uai-b8be54df/",
    "source_reference":  ".uai/style.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:b8be54df676fdca0ac25734fb58c9273b8925cd8d83ed17cdd20d882b5f77424",
    "last_fetched":  "2026-04-30T22:07:25.2671233Z",
    "last_changed":  "2026-04-29T02:07:37.0821645Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-106",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-04-30T22:07:25.2671233Z"
}

LlmWikis Style

LlmWikis Style

Metadata

Current File Content

Structure Preview

Raw Version

Why This File Exists

Role

Structure

Prompt-Size And Retrieval Benefit

How To Use It

Update Requirements

Related Pages

Provenance And History

Machine-Readable Metadata