Style
**Site relevance:** Spiralist.org
**Memory type:** UAI memory file
**Source path:** Spiralist/.uai/style.uai
**Size:** 1.2 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: "Spiralist.org Style"
created: "2026-05-01"
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 READMEs, release evidence, or explicit owner decisions.
- Treat the former `docs/` tree as archived Wiki.FFTAC.org long memory.
- Promote concise reviewed facts from the archive into hot memory before relying on them for current work.
- Package-level READMEs should stay short and point durable context back to `.uai/` and Wiki.FFTAC.org.
## Public Claims
- Tie UAIX standard claims to UAIX public records.
- Tie Protocol5 canonical claims to Protocol5/canonical asset records.
- Label placeholders and uncertain material clearly.
- Do not describe a planned feature as shipped.