Skip to content
wiki.fftac.org

Agents

**Site relevance:** FFTAC.org

**Memory type:** reviewed source memory

**Source path:** FFTAC/AGENTS.md

**Size:** 4.4 KB

Summary

This is the working guide for anyone modifying the FFTAC.org WordPress Studio site.

Source Headings

  • AGENTS
  • Handoff Summary
  • Workspace Coordination
  • Loaded Context
  • Agent File Handoff
  • Required First Response
  • Read First
  • Current-State Boundaries
  • Editing Rules
  • Verification

Source Preview

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

---
uaix: "1.0"
project: "FFTAC.org"
created: "2026-05-10"
updated: "2026-05-11"
status: active
---

# AGENTS

This is the working guide for anyone modifying the FFTAC.org WordPress Studio site.

## Handoff Summary

FFTAC.org is a WordPress Studio site for The Foundation For The Anti-Christ "Who We Are" public information surface. Short-term memory lives in this repository's UAIX Project Handoff files; reviewed long-term memory routes to `WP-FFTAC/Wiki.FFTAC.org/`.

## Workspace Coordination

This repo is part of the `WP-FFTAC/` multisite workspace. Before broad work, read `WP-FFTAC/workspace.uai` when the human names any known site/domain, when a request spans multiple sites, or when the current shell directory and requested target differ. Explicit site or domain names decide which handoff bundle to load.

Use the UAIX AI Memory Package Wizard at `https://uaix.org/en-us/tools/ai-memory-package-wizard/` for visible AI Memory setup guidance. Use the LLMWikis setup wizard at `https://llmwikis.org/tools/llm-wiki-setup-wizard/` when planning LLM Wiki structure, pointing reviewed long-memory/cold-memory routing to `WP-FFTAC/Wiki.FFTAC.org/` after source-site review.

## Loaded Context

@uai[.uai/context.uai]
@uai[.uai/stack.uai]
@uai[.uai/constraints.uai]
@uai[.uai/architecture.uai]
@uai[.uai/decisions.uai]
@uai[.uai/progress.uai]
@uai[.uai/test-plan.uai]
@uai[.uai/operations.uai]
@uai[.uai/style.uai]
@uai[.uai/file-handoff.uai]
@uai[.uai/intake-index.uai]
@uai[.uai/memory.uai]

## Agent File Handoff

At the start of broad work, inspect `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, classify files sitting directly under `agent-file-handoff/`, ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file, and review `.uai/intake-index.uai` before unrelated edits.

Dropped files are local review inputs only. Use `.uai/file-handoff.uai` for active bucket, disposition, archive, Wiki.FFTAC.org long-memory, and trust-boundary rules. Reviewed files should leave active intake after the complete outcome is recorded unless the human explicitly keeps a named file active.

Production packaging now runs the workspace handoff audit. Treat active files in `Content/` or `Improvement/` as a build blocker until reviewed, logged, and archived or deliberately deferred with a current owner reason.

## Required First Response

Before broad edits, the next AI should summarize the project and immediate task in 3-5 bullets, name which `.uai` files loaded and whether any were missing or contradictory, confirm constraints that require explicit human approval, name the files/routes/docs it expects to touch, and name the targeted checks it expects to run.

## Read First

1. [readme.human](readme.human)
2. [wp-content/themes/fftac-who-we-are/README.md](wp-content/themes/fftac-who-we-are/README.md)
3. [LLM_WIKI_MEMORY_PLAN.md](LLM_WIKI_MEMORY_PLAN.md) when work needs reviewed long-memory routing through Wiki.FFTAC.org.
4. [AGENT_FILE_HANDOFF_PLAN.md](AGENT_FILE_HANDOFF_PLAN.md) when work touches dropped-file intake.
5. [../scripts/audit-agent-file-handoff.ps1](../scripts/audit-agent-file-handoff.ps1) when checking whether active intake is clear before packaging.

For WordPress Studio instructions, see [STUDIO.md](STUDIO.md).

## Current-State Boundaries

- Most custom work belongs in `wp-content/themes/fftac-who-we-are/`.
- WordPress core, Akismet, bundled WordPress files, Studio runtime files, and upstream plugin code are not owned application code unless a task explicitly says otherwise.
- Wiki.FFTAC.org long memory is background evidence until a reviewed fact is promoted into this site's hot handoff files, code, release note, or explicit owner decision.
- The worktree may already contain unrelated changes. Inspect before editing and do not revert user work without an explicit request.

## Editing Rules

- Prefer editing the custom theme for layout, templates, assets, styling, and site-specific copy.
- Do not edit `wp-admin`, `wp-includes`, bundled WordPress themes, vendor libraries, third-party license files, or WordPress Studio runtime artifacts unless there is a specific maintenance reason.
- Keep this handoff bundle concise; move bulky history and reviewed archive evidence to Wiki.FFTAC.org.

## Verification

After editing PHP files, run `php -l` against the files you changed when PHP is available. For handoff-only changes, verify that referenced files exist.
Website health report