diff --git a/guidelines/Guidelines.md b/guidelines/Guidelines.md index 673b8c48..7434a120 100644 --- a/guidelines/Guidelines.md +++ b/guidelines/Guidelines.md @@ -20,8 +20,14 @@ documentation organized in separate files. ### 🤖 Default AI Workflow (MUST FOLLOW) -**When asked to write a prompt, audit, or review, ALWAYS follow this sequence:** - +**See the [Workflow Orchestration Skill](../.claude/skills/workflow-orchestration/SKILL.md) for comprehensive guidance on:** +- Single-file audit workflows (4-step: prompt → audit → report → tasks) +- Multi-audit orchestrator workflows with parallel execution +- Folder structure and naming conventions +- YAML frontmatter templates for all content types +- Task list management and archiving procedures + +**Quick reference:** When told to "write a prompt" or "audit X", use the skill's decision tree to choose single-file or orchestrator workflow, then execute the full sequence (create prompt → run audit → save report → extract tasks). The skill provides reusable YAML templates and detailed step-by-step guidance. 1. **Create a prompt** in `/prompts/` — defines the audit scope, steps, and references to relevant guidelines. 1. **Run the audit** described in the prompt against the codebase and guidelines. @@ -69,21 +75,23 @@ general documentation. ### 📁 Mandatory Folder Conventions +The project uses three dedicated workflow folders. **All AI-generated and human-authored workflow artifacts MUST be stored in these folders.** See the [Workflow Orchestration Skill](../.claude/skills/workflow-orchestration/SKILL.md) for full folder structure rules and conventions. The project uses three dedicated workflow folders. **All AI-generated and human-authored workflow artifacts MUST be stored in these folders.** Never place prompts, reports, or task lists anywhere else (e.g., never in root, never in `/guidelines/`). -| Folder | Purpose | Naming Convention | -|---|---|---| -| `/prompts/` | All prompt files for AI-assisted tasks | `{topic}.md` or subfolder `{topic}/` with `orchestrator.md` | -| `/reports/` | All audit findings, analysis results, reports | Subfolder per audit: `/reports/{audit-name}/` | -| `/tasks/` | All task lists and checklists | `task-list.md` is the master general-purpose task list | -| `/docs/` | General project documentation, quick references, attributions | Descriptive filenames (e.g., `Attributions.md`, `quick-reference.md`) | -| `/scripts/` | All build, utility, and automation scripts (`.ts`, `.sh`, `.js`) | Descriptive filenames (e.g., `verify-build.ts`, `deploy.sh`) | +**Quick Reference:** -**Rules:** +| Folder | Purpose | +|---|---| +| `/prompts/` | All prompt files for AI-assisted tasks | +| `/reports/` | All audit findings, analysis results, reports | +| `/tasks/` | All task lists and checklists; `/tasks/task-list.md` is the persistent master | +| `/docs/` | General project documentation, quick references, attributions | +| `/scripts/` | All build, utility, and automation scripts | +**Critical rule:** Never delete `/tasks/task-list.md` — it is the persistent master checklist. 1. **Prompts:** Always create new prompt files in `/prompts/`. For multi-step workflows, create a subfolder with a master `orchestrator.md` and child prompt files. 1. **Reports:** Always write reports to `/reports/`, inside a suitable subfolder (e.g., `/reports/root-cleanup/`, `/reports/css-audit/`). One subfolder per audit or topic. @@ -166,6 +174,10 @@ created, completed, or archived. 1. When ALL tasks in a task list are marked complete, move the entry in `master-task-list.md` from "Active" to "Completed (pending archive)" +**Report archiving process:** +1. When a report's associated task list is 100% complete, wait 30 days from completion, then move the report folder from `/reports/{topic}/` to `/reports/archived/{topic}/` +2. Reports in `/reports/archived/` can be deleted after 7 days +3. Only delete from `/reports/archived/` — never delete active reports 1. After 30 days in "Completed", move the file to `/tasks/archived/` and update `master-task-list.md` 1. Only delete from `/tasks/archived/` — never delete active or recently completed task lists diff --git a/guidelines/README.md b/guidelines/README.md index 579b26d7..79640930 100644 --- a/guidelines/README.md +++ b/guidelines/README.md @@ -52,8 +52,7 @@ Follow this **exact reading order** to understand the design system: 1. **[design-tokens/spacing.md](./design-tokens/spacing.md)** - Spacing system #### Step 4: Understand Data System (REQUIRED) - -1. **[Data System Documentation](../data/README.md)** - Mock data system and centralized content management +15. **[Data System Documentation](./data-models.md)** - Data model definitions and centralized content management #### Step 5: Read Theme Documentation (REQUIRED) @@ -200,7 +199,7 @@ guidelines/ ## Building a Page Component - Start with [overview-components.md](./overview-components.md) -- Check [Data System Documentation](../data/README.md) for content +- Check [data-models.md](./data-models.md) for content structure - Review [Guidelines.md](./Guidelines.md) Section 1 for architecture ## Using a Specific Component diff --git a/guidelines/events-system.md b/guidelines/events-system.md index 37d5927e..afbd7a03 100644 --- a/guidelines/events-system.md +++ b/guidelines/events-system.md @@ -1,3 +1,12 @@ +--- +title: "Events System — Data Model & Architecture Guidelines" +filename: "/guidelines/events-system.md" +created: "2026-02-01" +modified: "2026-10-22" +version: "1.0.0" +status: "complete" +--- + # Events System — Data Model & Architecture Guidelines **Version:** 1.0.0 diff --git a/guidelines/wordpress-block-patterns.md b/guidelines/wordpress-block-patterns.md index 38ce03bb..e726154c 100644 --- a/guidelines/wordpress-block-patterns.md +++ b/guidelines/wordpress-block-patterns.md @@ -1,3 +1,12 @@ +--- +title: "WordPress Block Pattern Mapping" +filename: "/guidelines/wordpress-block-patterns.md" +created: "2026-02-01" +modified: "2026-10-22" +version: "1.0.0" +status: "complete" +--- + # WordPress Block Pattern Mapping **Version:** 1.0.0