Update instruction files

Author: ashleyshaw

.github/SAVED_REPLIES.md .github/SAVED_REPLIES.md .md.github/SAVED_REPLIES.md renamed to .github/SAVED_REPLIES.md .md

@@ -28,8 +28,6 @@ Applies to all code, content, and UI you generate. Covers WCAG 2.2 AA alignment,
 
 ### Bias Awareness - Inclusive Language
 
-## Bias Awareness - Inclusive Language
-
 In addition to producing accessible code, GitHub Copilot and similar tools must also demonstrate respectful and bias-aware behavior in accessibility contexts. All generated output must follow these principles:
 
 - **Respectful, Inclusive Language**
@@ -131,6 +129,8 @@ When using roving tabindex to manage focus in a composite component, the element
   - If a background color is not set or is fully transparent, then the contrast ratio is calculated against the background color of the parent element.
 - Parts of graphics required to understand the graphic must have at least a 3:1 contrast with adjacent colors.
 - Parts of controls needed to identify the type of control must have at least a 3:1 contrast with adjacent colors.
+- Parts of controls needed to communicate state (pressed, focus, checked, etc.) must have at least a 3:1 contrast with adjacent colors.
+- Do not rely on colour alone to convey information; pair colour with text, iconography, or shapes.
 
 ## Examples
 
@@ -143,14 +143,6 @@ When using roving tabindex to manage focus in a composite component, the element
 - Manually test keyboard navigation (Tab, Shift+Tab, Enter, Escape, Arrow keys) and focus visibility.
 - Verify colour contrast meets WCAG 2.2 AA for text and controls.
 
-## References
-
-- `.github/instructions/instructions.instructions.md`
-- `.github/instructions/mermaid.instructions.md` (for diagram a11y)
-- `.github/instructions/documentation-formats.instructions.md`
-- Parts of controls needed to identify the state of the control (pressed, focus, checked, etc.) must have at least a 3:1 contrast with adjacent colors.
-- Color must not be used as the only way to convey information. E.g., a red border to convey an error state, color coding information, etc. Use text and/or shapes in addition to color to convey information.
-
 ### Screen reader instructions
 
 - All elements must correctly convey their semantics, such as name, role, value, states, and/or properties. Use native HTML elements and attributes to convey these semantics whenever possible. Otherwise, use appropriate ARIA attributes.
@@ -497,3 +489,10 @@ Tables should be used for static information that is best represented in a tabul
 #### Use grids for dynamic information
 
 Grids should be used for dynamic information that is best represented in a grid format. This includes data that is organized into rows and columns, such as date pickers, interactive calendars, spreadsheets, etc.
+
+## References
+
+- [instructions.instructions.md](.github/instructions/instructions.instructions.md)
+- [documentation-formats.instructions.md](.github/instructions/documentation-formats.instructions.md)
+- [mermaid.instructions.md](.github/instructions/mermaid.instructions.md)
+- [WCAG 2.2 AA](https://www.w3.org/TR/WCAG22/)

.github/instructions/_index.instructions.md

@@ -133,10 +133,10 @@ metadata:
 
 ## References
 
-- `AGENTS.md`
-- `.github/agents/template.agent.md`
-- `.github/instructions/instructions.instructions.md`
-- `.github/instructions/automation.instructions.md`
-- `.github/instructions/documentation-formats.instructions.md`
-- `.github/instructions/quality-assurance.instructions.md`
-- `SECURITY.md`
+- [AGENTS.md](AGENTS.md)
+- [template.agent.md](.github/agents/template.agent.md)
+- [instructions.instructions.md](.github/instructions/instructions.instructions.md)
+- [automation.instructions.md](.github/instructions/automation.instructions.md)
+- [documentation-formats.instructions.md](.github/instructions/documentation-formats.instructions.md)
+- [quality-assurance.instructions.md](.github/instructions/quality-assurance.instructions.md)
+- [SECURITY.md](SECURITY.md)

.github/instructions/a11y.instructions.md

@@ -63,16 +63,6 @@ Ensure consistent, reliable, and maintainable automation across GitHub repositor
 - Validate workflows with `actionlint` and ensure actions are pinned to SHAs.
 - Check labeler/labels/issue-types YAML against schemas where provided.
 
-## References
-
-- `.github/instructions/instructions.instructions.md`
-- `.github/instructions/workflows.instructions.md`
-- `.github/instructions/labeling.instructions.md`
-- `.github/instructions/file-organisation.instructions.md`
-- `.github/agents/agent.md`
-
----
-
 ## Automation Architecture
 
 ### System Overview
@@ -179,7 +169,7 @@ What this agent does and why it exists.
 - Validation requirements
 - Failure handling
 
-## References
+## Template References
 
 - Related workflows
 - Documentation
@@ -774,21 +764,15 @@ echo $?
 
 ## References
 
-### Documentation
-
-- [GitHub Actions](https://docs.github.com/en/actions)
+- [instructions.instructions.md](.github/instructions/instructions.instructions.md)
+- [workflows.instructions.md](.github/instructions/workflows.instructions.md)
+- [labeling.instructions.md](.github/instructions/labeling.instructions.md)
+- [pull-requests.instructions.md](.github/instructions/pull-requests.instructions.md)
+- [issues.instructions.md](.github/instructions/issues.instructions.md)
+- [quality-assurance.instructions.md](.github/instructions/quality-assurance.instructions.md)
+- [file-organisation.instructions.md](.github/instructions/file-organisation.instructions.md)
+- [agent.md](.github/agents/agent.md)
+- [GitHub Actions Documentation](https://docs.github.com/en/actions)
 - [GitHub API](https://docs.github.com/en/rest)
 - [Semantic Versioning](https://semver.org/)
 - [Keep a Changelog](https://keepachangelog.com/)
-
-### Related Instructions
-
-- [Workflows](./workflows.instructions.md)
-- [Labeling](./labeling.instructions.md)
-- [Pull Requests](./pull-requests.instructions.md)
-- [Issues](./issues.instructions.md)
-- [Quality Assurance](./quality-assurance.instructions.md)
-
----
-
-*This document consolidates automation standards for GitHub community health repositories. All automation must follow these standards for consistency and reliability.*

.github/instructions/agent-spec.instructions.md

@@ -42,13 +42,6 @@ Applies to all code, documentation, automation, and AI-generated content across
 - Validate links in docs and ensure accessibility standards are met.
 - Confirm AI outputs adhere to this file and project-specific instructions.
 
-## References
-
-- `.github/instructions/linting.instructions.md`
-- `.github/instructions/documentation-formats.instructions.md`
-- `.github/instructions/a11y.instructions.md`
-- `.github/instructions/instructions.instructions.md`
-
 This document is the single source of truth for all coding standards in LightSpeedWP projects. It applies to **all code, docs, automation, and AI-generated content**.
 
 ---
@@ -60,7 +53,7 @@ This document is the single source of truth for all coding standards in LightSpe
 - [Formatting & Automation](#formatting--automation)
 - [Documentation Standards](#documentation-standards)
 - [AI & Copilot Instructions](#ai--copilot-instructions)
-- [References & Related Guidance](#references--related-guidance)
+- [References](#references)
 
 ---
 
@@ -77,19 +70,19 @@ This document is the single source of truth for all coding standards in LightSpe
 ## Language-Specific Standards
 
 - **JavaScript/TypeScript:**
-  - Lint with ESLint (flat/classic), Prettier.
-  - Reference: [`linting-javascript.instructions.md`](./linting-javascript.instructions.md)
+  - Lint with ESLint (flat/classic) and Prettier.
+  - Reference: [`languages.instructions.md`](./languages.instructions.md)
 
 - **JSON:**
-  - Enforce strict schemas and formatting with Prettier, (optionally) AJV.
-  - Reference: [`linting-json.instructions.md`](./linting-json.instructions.md)
+  - Enforce strict schemas and formatting with Prettier and, where required, AJV.
+  - Reference: [`languages.instructions.md`](./languages.instructions.md)
 
 - **Markdown:**
-  - Use markdownlint + Prettier.
-  - Reference: [`linting-markdown.instructions.md`](./linting-markdown.instructions.md)
+  - Use markdownlint and Prettier.
+  - Reference: [`documentation-formats.instructions.md`](./documentation-formats.instructions.md)
 - **YAML:**
-  - Use yamllint, Spectral, actionlint for workflows.
-  - Reference: [`linting-yaml.instructions.md`](./linting-yaml.instructions.md)
+  - Use yamllint, Spectral, and actionlint for workflows.
+  - Reference: [`languages.instructions.md`](./languages.instructions.md) and [`workflows.instructions.md`](./workflows.instructions.md)
 
 ---
 
@@ -115,14 +108,15 @@ All documentation links to files within the same repository should use `/blob/HE
 
 ---
 
-## References & Related Guidance
-
-- [LightSpeed Custom Instructions](../custom-instructions.md)
-- [LightSpeed Copilot Prompts Index](../prompts/prompts.md)
-- [LightSpeed Agents Index](../agents/agent.md)
-- [LightSpeed GitHub Workflow Governance](../docs/WORKFLOWS.md)
-
----
+## References
 
-*This file is the canonical reference for all code, documentation, and automation standards in LightSpeedWP projects.
-All contributors, agents, and AI assistants must comply with these standards.*
+- [linting.instructions.md](.github/instructions/linting.instructions.md)
+- [documentation-formats.instructions.md](.github/instructions/documentation-formats.instructions.md)
+- [languages.instructions.md](.github/instructions/languages.instructions.md)
+- [a11y.instructions.md](.github/instructions/a11y.instructions.md)
+- [workflows.instructions.md](.github/instructions/workflows.instructions.md)
+- [instructions.instructions.md](.github/instructions/instructions.instructions.md)
+- [LightSpeed Custom Instructions](.github/custom-instructions.md)
+- [LightSpeed Copilot Prompts Index](.github/prompts/prompts.md)
+- [LightSpeed Agents Index](.github/agents/agent.md)
+- [LightSpeed GitHub Workflow Governance](docs/WORKFLOWS.md)

.github/instructions/automation.instructions.md

@@ -358,7 +358,7 @@ How to use or interact with contents.
 ├── file2.js - Description
 └── folder/ - Description
 
-## References
+## Template References
 
 - [Link to related docs]
 - [Link to instructions]
@@ -434,7 +434,7 @@ What this folder contains and why.
 
 How to use files in this folder.
 
-## References
+## Template References
 
 - [Related documentation]
 ````
@@ -683,30 +683,24 @@ build/
 coverage/
 ```
 
+
+*This document consolidates community health standards for GitHub repositories. All files and documentation must follow these standards for consistency and professionalism.*
+
 ---
 
 ## References
 
-### GitHub Documentation
-
+- [instructions.instructions.md](.github/instructions/instructions.instructions.md)
+- [file-organisation.instructions.md](.github/instructions/file-organisation.instructions.md)
+- [documentation-formats.instructions.md](.github/instructions/documentation-formats.instructions.md)
+- [readme.instructions.md](.github/instructions/readme.instructions.md)
+- [automation.instructions.md](.github/instructions/automation.instructions.md)
+- [workflows.instructions.md](.github/instructions/workflows.instructions.md)
+- [issues.instructions.md](.github/instructions/issues.instructions.md)
+- [pull-requests.instructions.md](.github/instructions/pull-requests.instructions.md)
 - [Community Health Files](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions)
 - [About READMEs](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes)
 - [Saved Replies](https://docs.github.com/en/get-started/writing-on-github/working-with-saved-replies/using-saved-replies)
-
-### Best Practices
-
 - [README Best Practices](https://www.makeareadme.com/)
 - [Open Source Guides](https://opensource.guide/)
 - [Conventional Commits](https://www.conventionalcommits.org/)
-
-### Related Instructions
-
-- [Documentation Formats](./documentation-formats.instructions.md)
-- [Automation](./automation.instructions.md)
-- [Workflows](./workflows.instructions.md)
-- [Issues](./issues.instructions.md)
-- [Pull Requests](./pull-requests.instructions.md)
-
----
-
-*This document consolidates community health standards for GitHub repositories. All files and documentation must follow these standards for consistency and professionalism.*

.github/instructions/coding-standards.instructions.md

@@ -62,8 +62,6 @@ Applies to all Copilot/agent work in this repository. Covers behaviour guardrail
 
 ## References
 
-- `.github/instructions/instructions.instructions.md`
-- `.github/instructions/file-organisation.instructions.md`
-- `.github/instructions/coding-standards.instructions.md`
-
----
+- [instructions.instructions.md](.github/instructions/instructions.instructions.md)
+- [file-organisation.instructions.md](.github/instructions/file-organisation.instructions.md)
+- [coding-standards.instructions.md](.github/instructions/coding-standards.instructions.md)

.github/instructions/community-standards.instructions.md

@@ -130,13 +130,6 @@ Every documentation file should start with YAML frontmatter including:
 - Validate links and frontmatter references after edits.
 - Use accessibility checks for headings, contrast (if styled), and alt text.
 
-## References
-
-- `.github/instructions/instructions.instructions.md`
-- `.github/instructions/readme.instructions.md`
-- `.github/instructions/a11y.instructions.md`
-- `.github/instructions/documentation-formats.instructions.md`
-
 ### Documentation Checklist
 
 - [ ] YAML frontmatter is present and complete
@@ -153,3 +146,10 @@ Every documentation file should start with YAML frontmatter including:
 - [ ] Contribution and review process described
 - [ ] Compliance/security info present if needed
 - [ ] Footer is present and complete
+
+## References
+
+- [instructions.instructions.md](./instructions.instructions.md)
+- [readme.instructions.md](./readme.instructions.md)
+- [a11y.instructions.md](./a11y.instructions.md)
+- [documentation-formats.instructions.md](./documentation-formats.instructions.md)

.github/instructions/copilot-operations.instructions.md

@@ -44,20 +44,6 @@ Applies to Markdown files across the repository. Covers formatting rules, frontm
 - Validate frontmatter against repo schemas where applicable.
 - Use Mermaid preview/render checks and contrast verification for diagrams.
 
-## References
-
-- `.github/instructions/readme.instructions.md`
-- `.github/instructions/a11y.instructions.md`
-- `.github/instructions/instructions.instructions.md`
-
-This document consolidates standards for Markdown formatting, YAML frontmatter metadata, and Mermaid diagram implementation across all GitHub repository documentation and community health files.
-
-## Purpose
-
-Ensure consistent, accessible, and well-structured documentation that supports automation, discoverability, and maintainability across GitHub repositories.
-
----
-
 ## Table of Contents
 
 - [Markdown Standards](#markdown-standards)
@@ -594,33 +580,19 @@ jobs:
 
 ## References
 
-### Markdown
-
+- [instructions.instructions.md](.github/instructions/instructions.instructions.md)
+- [readme.instructions.md](.github/instructions/readme.instructions.md)
+- [a11y.instructions.md](.github/instructions/a11y.instructions.md)
+- [languages.instructions.md](.github/instructions/languages.instructions.md)
+- [linting.instructions.md](.github/instructions/linting.instructions.md)
 - [markdownlint Documentation](https://github.com/DavidAnson/markdownlint)
 - [Prettier Markdown Support](https://prettier.io/docs/en/options.html#prose-wrap)
 - [GitHub Flavored Markdown](https://github.github.com/gfm/)
 - [CommonMark Specification](https://commonmark.org/)
-
-### YAML Frontmatter
-
 - [YAML Specification](https://yaml.org/spec/)
 - [JSON Schema](https://json-schema.org/)
 - [GitHub Issue Templates](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests)
-
-### Mermaid
-
 - [Mermaid Documentation](https://mermaid.js.org/)
 - [GitHub Mermaid Support](https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/)
 - [Mermaid Live Editor](https://mermaid.live)
 - [W3C Complex Images](https://www.w3.org/WAI/tutorials/images/complex/)
-
-### Related Instructions
-
-- [Coding Standards](./coding-standards.instructions.md)
-- [Languages Standards](./languages.instructions.md)
-- [Accessibility Standards](./a11y.instructions.md)
-- [Linting Standards](./linting.instructions.md)
-
----
-
-*This document consolidates documentation format standards for GitHub community health repositories. All documentation must follow these standards for consistency, accessibility, and automation compatibility.*