- All agent implementations and specs are located in
.github/agents/directory - Each agent must have both a code file (
.js,.py, etc.) and a spec (.md) following the template. - All contributors must follow the org coding standards defined in
.github/instructions/.
| Agent | Tests | Notes |
|---|---|---|
| TBD | ⏳ | Awaiting test implementation |
Note: As agents are developed and tested, this table will be updated with their status. ✅ indicates passing tests, ❌ indicates failing tests, and ⏳ indicates tests pending implementation.
| Principle / Rule | Guidance / Details |
|---|---|
| Language | Use UK English; optimise for clarity, scalability, maintainability, and profitable outcomes. |
| Modularity | Prefer minimal, modular solutions; justify heavier tools with ROI and maintenance cost. |
| Coding Standards | Follow Coding Standards Instructions and Linting Instructions for all code (CSS, HTML, JS, PHP, etc.). |
| Code Changes | All code changes must include lint fixes, relevant tests, and a short rationale summarising the change. |
| Security | Never output secrets. Treat production and customer data as sensitive. Follow OWASP top 10. |
| Accessibility & Performance | Non-negotiable; highlight potential issues during reviews. |
| WordPress Block Usage | Prefer theme.json and block components over bespoke code to avoid vendor lock-in. |
| Safe Defaults & Questions | When unsure, propose safe defaults and ask one focused question to clarify requirements. |
| Area | File Reference | Notes / Usage |
|---|---|---|
| Coding Standards | .github/instructions/coding-standards.instructions.md | Unified standards for all code |
| Linting Standards | .github/instructions/linting.instructions.md | Main index for all linting rules |
| HTML Templates | .github/instructions/html-template.instructions.md | Markup standards |
| Pattern Development | .github/instructions/pattern-development.instructions.md | Block patterns for WordPress |
| PHP Block Instructions | .github/instructions/php-block.instructions.md | PHP block usage |
| Theme JSON | .github/instructions/theme-json.instructions.md | Theme configuration standards |
Other Key Indexes:
- Linting Index: .github/instructions/linting.instructions.md
- Coding Standards Index: .github/instructions/coding-standards.instructions.md
- Use the default PR template: .github/PULL_REQUEST_TEMPLATE.md
- Additional PR templates are available in: .github/PULL_REQUEST_TEMPLATES/
- Use the template most relevant to your change (e.g. feature, fix, documentation, etc.)
Start here for all key standards:
- Coding Standards Index: Unified standards, best practices, and documentation for all LightSpeed projects.
- Linting Instructions Index: Primary index and guidance for all linting rules, tools, and file-type-specific standards.
| Resource Name | Reference | Purpose / Notes |
|---|---|---|
| Custom Instructions | .github/custom-instructions.md | Central Copilot/org instructions, prompts, and standards |
| Agent Directory | .github/agents/ |
Directory of agent specs, stubs, and implementations |
| WP Block Build Agent Spec | .github/agents/wp-block-build.agent.md | Detailed build process for multi-block plugin agent |
| Development Assistant | .github/agents/development-assistant.agent.md | AI development assistant with context-specific modes |
| Prompts Index | .github/prompts/prompts.md | Master prompt index and authoring conventions |
(Recommended Reference Pattern)
Reference main index files directly in your workflow or documentation:
-
@lightspeedwp/.github/files/.github/instructions/coding-standards.instructions.md -
@lightspeedwp/.github/files/.github/instructions/linting.instructions.md -
For file-type or topic-specific instructions, see all files in
.github/instructions/.
For up-to-date standards, always reference the index instruction files above. See also: .github/custom-instructions.md for central org-wide Copilot and agent guidance.