Style

**Site relevance:** Anti-Christ.org

**Memory type:** UAI memory file

**Source path:** Anti-Christ.org/.uai/style.uai

**Size:** 1.1 KB

Summary

Match existing WordPress, theme, and plugin patterns.

Source Headings

Style
Code
Documentation
Public Claims

Source Preview

This source file is short enough to preview directly on its source-memory page.

---
uai: "1.0"
type: style
title: "Anti-Christ.org Style"
created: "2026-05-10"
updated: "2026-05-10"
status: active
source: "https://uaix.org/en-us/specification/project-handoff/"
---

# Style

## Code

- Match existing WordPress, theme, and plugin patterns.
- Keep changes scoped to the route, template, plugin, or documentation boundary implied by the task.
- Add abstractions only when they remove real duplication or match a local pattern.
- Use concise comments only where the code is not self-explanatory.

## Documentation

- Keep current shipped behavior in code, `.uai/`, package-local notes, release evidence, or explicit owner decisions.
- Keep older dated strategy memos and former docs as archived Wiki.FFTAC.org source notes unless promoted into hot memory or implementation.
- Package-level notes should point durable context back to `.uai/` and Wiki.FFTAC.org.

## Public Claims

- Tie public support, security, AI, legal, and capability claims to current evidence.
- Label placeholders and uncertain material clearly.
- Do not describe a planned feature as shipped.