@mytechtoday/augment-extensions 1.7.0 → 2.3.0

package/augment-extensions/coding-standards/html/CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+All notable changes to this module will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-02-25
+
+### Added
+
+- Initial release of HTML Standards module
+- Comprehensive HTML coding standards for modern web development with semantic HTML, accessibility guidelines, and HTML5 features
+
+### Changed
+
+- N/A
+
+### Deprecated
+
+- N/A
+
+### Removed
+
+- N/A
+
+### Fixed
+
+- N/A
+
+### Security
+
+- N/A
+
+## Guidelines
+
+When updating this changelog:
+
+1. **Added** for new features
+2. **Changed** for changes in existing functionality
+3. **Deprecated** for soon-to-be removed features
+4. **Removed** for now removed features
+5. **Fixed** for any bug fixes
+6. **Security** in case of vulnerabilities
+
+Each version should:
+- Use semantic versioning (MAJOR.MINOR.PATCH)
+- Include the release date in YYYY-MM-DD format
+- List changes in the appropriate category
+- Link to relevant issues or PRs when applicable
+

package/augment-extensions/coding-standards/html/metadata.json

@@ -0,0 +1,25 @@
+{
+  "version": "1.0.0",
+  "name": "html-standards",
+  "displayName": "HTML Standards",
+  "description": "Comprehensive HTML coding standards for modern web development with semantic HTML, accessibility guidelines, and HTML5 features",
+  "type": "coding-standards",
+  "language": "html",
+  "tags": [
+    "html",
+    "web",
+    "frontend",
+    "accessibility",
+    "semantic-html"
+  ],
+  "compatibility": {
+    "augmentMinVersion": "1.0.0",
+    "nodeMinVersion": "18.0.0"
+  },
+  "characterCount": 32477,
+  "lastUpdated": "2026-02-25",
+  "files": {
+    "rules": "html-standards.md",
+    "examples": null
+  }
+}

package/augment-extensions/coding-standards/html-css-js/CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+All notable changes to this module will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-02-25
+
+### Added
+
+- Initial release of HTML/CSS/JavaScript Standards module
+- Comprehensive HTML/CSS/JavaScript coding standards for modern web development with semantic HTML, modern CSS features, and ES6+ JavaScript
+
+### Changed
+
+- N/A
+
+### Deprecated
+
+- N/A
+
+### Removed
+
+- N/A
+
+### Fixed
+
+- N/A
+
+### Security
+
+- N/A
+
+## Guidelines
+
+When updating this changelog:
+
+1. **Added** for new features
+2. **Changed** for changes in existing functionality
+3. **Deprecated** for soon-to-be removed features
+4. **Removed** for now removed features
+5. **Fixed** for any bug fixes
+6. **Security** in case of vulnerabilities
+
+Each version should:
+- Use semantic versioning (MAJOR.MINOR.PATCH)
+- Include the release date in YYYY-MM-DD format
+- List changes in the appropriate category
+- Link to relevant issues or PRs when applicable
+

package/augment-extensions/coding-standards/html-css-js/metadata.json

@@ -0,0 +1,40 @@
+{
+  "version": "1.0.0",
+  "name": "html-css-js-standards",
+  "displayName": "HTML/CSS/JavaScript Standards",
+  "description": "Comprehensive HTML/CSS/JavaScript coding standards for modern web development with semantic HTML, modern CSS features, and ES6+ JavaScript",
+  "type": "coding-standards",
+  "language": "html-css-js",
+  "tags": [
+    "html",
+    "css",
+    "javascript",
+    "web",
+    "frontend",
+    "accessibility",
+    "performance"
+  ],
+  "compatibility": {
+    "augmentMinVersion": "1.0.0",
+    "nodeMinVersion": "18.0.0"
+  },
+  "characterCount": 165097,
+  "lastUpdated": "2026-02-25",
+  "files": {
+    "rules": [
+      "async-patterns.md",
+      "css-modern-features.md",
+      "css-standards.md",
+      "dom-manipulation.md",
+      "html-standards.md",
+      "javascript-standards.md",
+      "performance.md",
+      "tooling.md"
+    ],
+    "examples": [
+      "async-examples.js",
+      "dom-examples.js",
+      "javascript-examples.js"
+    ]
+  }
+}

package/augment-extensions/coding-standards/js/CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+All notable changes to this module will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-02-25
+
+### Added
+
+- Initial release of JavaScript Standards module
+- Comprehensive JavaScript coding standards for modern web development with ES6+, DOM manipulation, async patterns, and framework integration
+
+### Changed
+
+- N/A
+
+### Deprecated
+
+- N/A
+
+### Removed
+
+- N/A
+
+### Fixed
+
+- N/A
+
+### Security
+
+- N/A
+
+## Guidelines
+
+When updating this changelog:
+
+1. **Added** for new features
+2. **Changed** for changes in existing functionality
+3. **Deprecated** for soon-to-be removed features
+4. **Removed** for now removed features
+5. **Fixed** for any bug fixes
+6. **Security** in case of vulnerabilities
+
+Each version should:
+- Use semantic versioning (MAJOR.MINOR.PATCH)
+- Include the release date in YYYY-MM-DD format
+- List changes in the appropriate category
+- Link to relevant issues or PRs when applicable
+

package/augment-extensions/coding-standards/js/metadata.json

@@ -0,0 +1,37 @@
+{
+  "version": "1.0.0",
+  "name": "js-standards",
+  "displayName": "JavaScript Standards",
+  "description": "Comprehensive JavaScript coding standards for modern web development with ES6+, DOM manipulation, async patterns, and framework integration",
+  "type": "coding-standards",
+  "language": "javascript",
+  "tags": [
+    "javascript",
+    "js",
+    "web",
+    "frontend",
+    "es6",
+    "async",
+    "dom"
+  ],
+  "compatibility": {
+    "augmentMinVersion": "1.0.0",
+    "nodeMinVersion": "18.0.0"
+  },
+  "characterCount": 101818,
+  "lastUpdated": "2026-02-25",
+  "files": {
+    "rules": [
+      "async-patterns.md",
+      "dom-manipulation.md",
+      "javascript-standards.md",
+      "performance.md",
+      "tooling.md"
+    ],
+    "examples": [
+      "async-examples.js",
+      "dom-examples.js",
+      "javascript-examples.js"
+    ]
+  }
+}

package/augment-extensions/coding-standards/perl/README.md

@@ -0,0 +1,173 @@
+# Perl Coding Standard
+
+This document defines the coding standards for all Perl code in projects using augment-extensions. The goal is to ensure consistency, readability, maintainability, security, and performance across Perl 5.20+ codebases (preferably 5.36+ for modern features).
+
+These guidelines build on core Perl community recommendations:
+- `perlstyle` (core Perl style guide)
+- Perl Best Practices (Damian Conway, O'Reilly 2005 — still highly relevant)
+- Modern Perl (4th edition practices)
+- Perltidy defaults with overrides for team consistency
+
+All Perl code **must** pass strict and warnings, and should use modern features where they improve clarity and safety.
+
+## 1. File Naming and Organization
+
+- Use lowercase_with_underscores.pl for scripts.
+- Use CamelCase.pm for modules / classes (but prefer lowercase_with_underscores.pm for utility modules when not object-oriented).
+- Main application entry point: `app.pl` or `scriptname.pl`.
+- Tests: `t/001_basic.t`, `t/foo-bar.t` (use descriptive names).
+- Configuration files: `.pl`, `.conf`, or `.ini` (avoid `.pm` unless it's a config module).
+- Organize large projects with `lib/`, `bin/`, `t/`, `script/`, `share/`.
+
+**Must** place `use strict;` and `use warnings;` (or `use v5.36;` which implies them) at the top of every file.
+
+```perl
+use v5.36;    # Enables strict, warnings, signatures, etc.
+```
+
+## 2. Indentation and Whitespace
+
+Use 4 spaces for indentation (no tabs).
+Use perltidy with project .perltidyrc for automatic formatting:
+-i=4 -et=4 -l=100 -ce -bar -bbb -bbc -bbs
+
+Align fat commas (=>) where reasonable.
+
+Keep lines ≤ 100 characters (soft limit 120).
+One true brace style (K&R / OTBS): opening brace on same line as control structure.
+
+Blank lines:
+1 between logical blocks inside subroutines.
+2 between subroutines.
+
+Avoid trailing whitespace.
+
+
+Example:
+```perl
+sub process_data ($data) {
+    my $result = {};
+
+    if ($data->{enabled}) {
+        $result->{status} = 'active';
+    }
+    else {
+        $result->{status} = 'inactive';
+    }
+
+    return $result;
+}
+```
+
+## 3. Naming Conventions
+
+Variables: $snake_case (lowercase with underscores).
+Constants: UPPER_CASE.
+Subroutines: snake_case().
+Packages/Modules: CamelCase for OO / distributions, lowercase::with::namespaces otherwise.
+Filehandles: $fh or $IN_FH, $OUT_FH.
+Package variables: avoid globals; prefer our or state when needed.
+Avoid single-letter variables except for obvious loop counters ($i, $j) or throwaways ($_).
+
+Prefer lexical variables (my, our, state) over local or package globals.
+Avoid $a, $b outside sort blocks.
+
+## 4. Comments and Documentation
+
+Use POD for module/user documentation.
+Inline comments for non-obvious logic only.
+Use # for comments, aligned when possible.
+Document all subs with purpose, params, returns using simple POD or plain comments.
+For complex regexes, use /xms and comment each line.
+
+Example:
+```perl
+
+# Parse ISO date with named captures
+if ($input =~ m{
+    ^ (?<year>   \d{4} ) -
+      (?<month>  \d{2} ) -
+      (?<day>    \d{2} ) $
+}xms) {
+    # ...
+}
+```
+
+## 5. Language Features and Best Practices
+
+Alwaysuse v5.36; (or at minimum use 5.20;) for signatures, postderef, etc.
+Use subroutine signatures (sub foo ($bar, $baz) { ... }).
+Prefer say over print when no newline is unwanted.
+Use // (defined-or) and //= over || for defaults unless undef is meaningful.
+List assignment and slices for clarity:
+
+```perl
+my ($host, $port) = @config{qw(host port)};
+```
+
+Use Carp instead of die in libraries (croak, confess).
+Prefer exceptions over return undef for error handling.
+Use Try::Tiny or core try/catch (v5.36+) for exception handling.
+
+```perl
+use Try::Tiny;
+
+try {
+    dangerous_operation();
+}
+catch {
+    croak "Failed: $_";
+};
+```
+
+## 6. Control Structures
+
+Prefer postfix conditionals for simple guards:
+
+```perl
+return if !$condition;
+```
+
+Use for instead of foreach (they are synonyms, but for is idiomatic).
+Avoid C-style for (;;) unless performance-critical.
+Use given/when sparingly (deprecated in future Perl); prefer if/elsif/else.
+
+## 7. Regular Expressions
+
+Always use /xms flags for complex regexes.
+Use named captures ((?<name>...)) over numbered.
+Prefer qr// for building regexes.
+Quote regex metacharacters when interpolating user input (quotemeta).
+
+## 8. Error Handling and Security
+
+Check return values of system calls (open, sysread, chdir, etc.).
+Use IPC::System::Simple or capture output safely.
+Taint mode (-T) for CGI / untrusted input scripts.
+Use Hash::Util to lock hashes where appropriate.
+Avoid system(@args) with interpolation; prefer list form.
+
+## 9. Testing
+
+Use Test2::V0 or Test::More + Test2::Suite.
+Write tests first when feasible (TDD encouraged).
+Aim for >80% coverage on business logic.
+Use done_testing() instead of plan count.
+
+## 10. Performance and Modernization
+
+Profile before optimizing (Devel::NYTProf).
+Prefer arrayrefs over arrays for large data.
+Use Moo / Moose / Mojo::Base for OO (project choice).
+Avoid source filters.
+Use feature qw( postderef signatures ) if not using v5.36.
+
+## Tooling
+
+Run perltidy -b before commit.
+Use perlcritic with severity 3+ (custom .perlcriticrc recommended).
+Enforce via pre-commit hooks or CI.
+
+Follow these guidelines unless a deliberate, documented exception exists. Consistency across the codebase takes precedence over individual preferences.
+
+This new Perl standard mirrors the structure, prescriptive tone, code examples, and depth seen in the repo's other language standards (e.g., Python's emphasis on modern features/type hints, PHP's PSR adherence with extensions). Place it in `augment-extensions/coding-standards/perl/README.md` (or similar) to match the pattern. If you need adjustments or more sections, let me know!

package/augment-extensions/coding-standards/php/CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+All notable changes to this module will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-02-25
+
+### Added
+
+- Initial release of PHP Coding Standards module
+- Comprehensive PHP coding standards following PSR standards and modern PHP best practices across various project types including web applications, APIs, CLI tools, CMS integrations, e-commerce systems, and legacy migrations.
+
+### Changed
+
+- N/A
+
+### Deprecated
+
+- N/A
+
+### Removed
+
+- N/A
+
+### Fixed
+
+- N/A
+
+### Security
+
+- N/A
+
+## Guidelines
+
+When updating this changelog:
+
+1. **Added** for new features
+2. **Changed** for changes in existing functionality
+3. **Deprecated** for soon-to-be removed features
+4. **Removed** for now removed features
+5. **Fixed** for any bug fixes
+6. **Security** in case of vulnerabilities
+
+Each version should:
+- Use semantic versioning (MAJOR.MINOR.PATCH)
+- Include the release date in YYYY-MM-DD format
+- List changes in the appropriate category
+- Link to relevant issues or PRs when applicable
+

package/augment-extensions/coding-standards/php/metadata.json

@@ -0,0 +1,35 @@
+{
+  "version": "1.0.0",
+  "name": "php-standards",
+  "displayName": "PHP Coding Standards",
+  "description": "Comprehensive PHP coding standards following PSR standards and modern PHP best practices across various project types including web applications, APIs, CLI tools, CMS integrations, e-commerce systems, and legacy migrations.",
+  "type": "coding-standards",
+  "tags": null,
+  "compatibility": {
+    "augmentMinVersion": "1.0.0",
+    "nodeMinVersion": "18.0.0"
+  },
+  "characterCount": 186539,
+  "lastUpdated": "2026-02-25",
+  "files": {
+    "rules": [
+      "api-development.md",
+      "category-configuration.md",
+      "cli-tools.md",
+      "cms-integration.md",
+      "code-quality.md",
+      "documentation.md",
+      "ecommerce.md",
+      "error-handling.md",
+      "legacy-migration.md",
+      "naming-conventions.md",
+      "performance.md",
+      "psr-standards.md",
+      "security.md",
+      "testing.md",
+      "type-declarations.md",
+      "web-applications.md"
+    ],
+    "examples": null
+  }
+}

package/augment-extensions/coding-standards/powershell/CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+All notable changes to this module will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-02-25
+
+### Added
+
+- Initial release of PowerShell Coding Standards module
+- Comprehensive PowerShell coding standards for professional, maintainable, and secure PowerShell code across automation, modules, DSC, cloud orchestration, administrative tools, cross-platform scripts, and legacy migrations.
+
+### Changed
+
+- N/A
+
+### Deprecated
+
+- N/A
+
+### Removed
+
+- N/A
+
+### Fixed
+
+- N/A
+
+### Security
+
+- N/A
+
+## Guidelines
+
+When updating this changelog:
+
+1. **Added** for new features
+2. **Changed** for changes in existing functionality
+3. **Deprecated** for soon-to-be removed features
+4. **Removed** for now removed features
+5. **Fixed** for any bug fixes
+6. **Security** in case of vulnerabilities
+
+Each version should:
+- Use semantic versioning (MAJOR.MINOR.PATCH)
+- Include the release date in YYYY-MM-DD format
+- List changes in the appropriate category
+- Link to relevant issues or PRs when applicable
+

package/augment-extensions/coding-standards/powershell/metadata.json

@@ -0,0 +1,33 @@
+{
+  "version": "1.0.0",
+  "name": "powershell-standards",
+  "displayName": "PowerShell Coding Standards",
+  "description": "Comprehensive PowerShell coding standards for professional, maintainable, and secure PowerShell code across automation, modules, DSC, cloud orchestration, administrative tools, cross-platform scripts, and legacy migrations.",
+  "type": "coding-standards",
+  "tags": null,
+  "compatibility": {
+    "augmentMinVersion": "1.0.0",
+    "nodeMinVersion": "18.0.0"
+  },
+  "characterCount": 162000,
+  "lastUpdated": "2026-02-25",
+  "files": {
+    "rules": [
+      "administrative-tools.md",
+      "automation-scripts.md",
+      "cloud-orchestration.md",
+      "configuration-schema.md",
+      "cross-platform-scripts.md",
+      "dsc-configurations.md",
+      "error-handling.md",
+      "legacy-migrations.md",
+      "modules-functions.md",
+      "naming-conventions.md",
+      "performance-optimization.md",
+      "security-practices.md",
+      "testing-guidelines.md",
+      "universal-standards.md"
+    ],
+    "examples": null
+  }
+}

package/augment-extensions/coding-standards/python/CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+All notable changes to this module will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.1.0] - 2026-02-25
+
+### Added
+
+- Initial release of Python Coding Standards module
+- Comprehensive Python coding standards including naming conventions, type hints (PEP 484, 585, 604), and error handling
+
+### Changed
+
+- N/A
+
+### Deprecated
+
+- N/A
+
+### Removed
+
+- N/A
+
+### Fixed
+
+- N/A
+
+### Security
+
+- N/A
+
+## Guidelines
+
+When updating this changelog:
+
+1. **Added** for new features
+2. **Changed** for changes in existing functionality
+3. **Deprecated** for soon-to-be removed features
+4. **Removed** for now removed features
+5. **Fixed** for any bug fixes
+6. **Security** in case of vulnerabilities
+
+Each version should:
+- Use semantic versioning (MAJOR.MINOR.PATCH)
+- Include the release date in YYYY-MM-DD format
+- List changes in the appropriate category
+- Link to relevant issues or PRs when applicable
+

package/augment-extensions/coding-standards/python/metadata.json

@@ -0,0 +1,38 @@
+{
+  "version": "1.1.0",
+  "name": "python-standards",
+  "displayName": "Python Coding Standards",
+  "description": "Comprehensive Python coding standards including naming conventions, type hints (PEP 484, 585, 604), and error handling",
+  "type": "coding-standards",
+  "tags": [
+    "python",
+    "pep8",
+    "pep484",
+    "pep585",
+    "pep604",
+    "type-hints",
+    "error-handling",
+    "best-practices",
+    "mypy"
+  ],
+  "compatibility": {
+    "augmentMinVersion": "1.0.0",
+    "nodeMinVersion": "18.0.0"
+  },
+  "characterCount": 116868,
+  "lastUpdated": "2026-02-25",
+  "files": {
+    "rules": [
+      "async-patterns.md",
+      "best-practices.md",
+      "code-organization.md",
+      "documentation.md",
+      "error-handling.md",
+      "naming-conventions.md",
+      "testing.md",
+      "tooling.md",
+      "type-hints.md"
+    ],
+    "examples": null
+  }
+}