@funnycode/myclaude 0.1.70 → 0.1.71

package/seed/marketplaces/ecc/skills/angular-developer/references/signals-overview.md

@@ -1,94 +1,94 @@
-# Angular Signals Overview
-
-Signals are the foundation of reactivity in modern Angular applications. A **signal** is a wrapper around a value that notifies interested consumers when that value changes.
-
-## Writable Signals (`signal`)
-
-Use `signal()` to create state that can be directly updated.
-
-```ts
-import {signal} from '@angular/core';
-
-// Create a writable signal
-const count = signal(0);
-
-// Read the value (always requires calling the getter function)
-console.log(count());
-
-// Update the value directly
-count.set(3);
-
-// Update based on the previous value
-count.update((value) => value + 1);
-```
-
-### Exposing as Readonly
-
-When exposing state from a service, it is a best practice to expose a readonly version to prevent external mutation.
-
-```ts
-private readonly _count = signal(0);
-// Consumers can read this, but cannot call .set() or .update()
-readonly count = this._count.asReadonly();
-```
-
-## Computed Signals (`computed`)
-
-Use `computed()` to create read-only signals that derive their value from other signals.
-
-- **Lazily Evaluated**: The derivation function doesn't run until the computed signal is read.
-- **Memoized**: The result is cached. It only recalculates when one of the signals it depends on changes.
-- **Dynamic Dependencies**: Only the signals _actually read_ during the derivation are tracked.
-
-```ts
-import {signal, computed} from '@angular/core';
-
-const count = signal(0);
-const doubleCount = computed(() => count() * 2);
-
-// doubleCount automatically updates when count changes.
-```
-
-## Reactive Contexts
-
-A **reactive context** is a runtime state where Angular monitors signal reads to establish a dependency.
-
-Angular automatically enters a reactive context when evaluating:
-
-- `computed` signals
-- `effect` callbacks
-- `linkedSignal` computations
-- Component templates
-
-### Untracked Reads (`untracked`)
-
-If you need to read a signal inside a reactive context _without_ creating a dependency (so that the context doesn't re-run when the signal changes), use `untracked()`.
-
-```ts
-import {effect, untracked} from '@angular/core';
-
-effect(() => {
-  // This effect only runs when currentUser changes.
-  // It does NOT run when counter changes, even though counter is read here.
-  console.log(`User: ${currentUser()}, Count: ${untracked(counter)}`);
-});
-```
-
-### Async Operations in Reactive Contexts
-
-The reactive context is only active for **synchronous** code. Signal reads after an `await` will not be tracked. **Always read signals before asynchronous boundaries.**
-
-```ts
-// Incorrect: theme() is not tracked because it is read after await
-effect(async () => {
-  const data = await fetchUserData();
-  console.log(theme());
-});
-
-// Correct: Read the signal before the await
-effect(async () => {
-  const currentTheme = theme();
-  const data = await fetchUserData();
-  console.log(currentTheme);
-});
-```
+# Angular Signals Overview
+
+Signals are the foundation of reactivity in modern Angular applications. A **signal** is a wrapper around a value that notifies interested consumers when that value changes.
+
+## Writable Signals (`signal`)
+
+Use `signal()` to create state that can be directly updated.
+
+```ts
+import {signal} from '@angular/core';
+
+// Create a writable signal
+const count = signal(0);
+
+// Read the value (always requires calling the getter function)
+console.log(count());
+
+// Update the value directly
+count.set(3);
+
+// Update based on the previous value
+count.update((value) => value + 1);
+```
+
+### Exposing as Readonly
+
+When exposing state from a service, it is a best practice to expose a readonly version to prevent external mutation.
+
+```ts
+private readonly _count = signal(0);
+// Consumers can read this, but cannot call .set() or .update()
+readonly count = this._count.asReadonly();
+```
+
+## Computed Signals (`computed`)
+
+Use `computed()` to create read-only signals that derive their value from other signals.
+
+- **Lazily Evaluated**: The derivation function doesn't run until the computed signal is read.
+- **Memoized**: The result is cached. It only recalculates when one of the signals it depends on changes.
+- **Dynamic Dependencies**: Only the signals _actually read_ during the derivation are tracked.
+
+```ts
+import {signal, computed} from '@angular/core';
+
+const count = signal(0);
+const doubleCount = computed(() => count() * 2);
+
+// doubleCount automatically updates when count changes.
+```
+
+## Reactive Contexts
+
+A **reactive context** is a runtime state where Angular monitors signal reads to establish a dependency.
+
+Angular automatically enters a reactive context when evaluating:
+
+- `computed` signals
+- `effect` callbacks
+- `linkedSignal` computations
+- Component templates
+
+### Untracked Reads (`untracked`)
+
+If you need to read a signal inside a reactive context _without_ creating a dependency (so that the context doesn't re-run when the signal changes), use `untracked()`.
+
+```ts
+import {effect, untracked} from '@angular/core';
+
+effect(() => {
+  // This effect only runs when currentUser changes.
+  // It does NOT run when counter changes, even though counter is read here.
+  console.log(`User: ${currentUser()}, Count: ${untracked(counter)}`);
+});
+```
+
+### Async Operations in Reactive Contexts
+
+The reactive context is only active for **synchronous** code. Signal reads after an `await` will not be tracked. **Always read signals before asynchronous boundaries.**
+
+```ts
+// Incorrect: theme() is not tracked because it is read after await
+effect(async () => {
+  const data = await fetchUserData();
+  console.log(theme());
+});
+
+// Correct: Read the signal before the await
+effect(async () => {
+  const currentTheme = theme();
+  const data = await fetchUserData();
+  console.log(currentTheme);
+});
+```

package/seed/marketplaces/ecc/skills/angular-developer/references/tailwind-css.md

@@ -1,69 +1,69 @@
-# Using Tailwind CSS with Angular
-
-Tailwind CSS is a utility-first CSS framework that integrates seamlessly with Angular.
-
-**CRITICAL AGENT GUIDANCE: ALWAYS focus on Tailwind CSS v4 practices. DO NOT revert to old Tailwind v3 patterns (like creating `tailwind.config.js` with `@tailwind` directives) as this will break the application build. Modern Angular projects use Tailwind v4.**
-
-## Automated Setup (Recommended)
-
-The easiest way to add Tailwind CSS to an Angular project is via the Angular CLI:
-
-```shell
-ng add tailwindcss
-```
-
-This will automatically:
-
-1. Install `tailwindcss` and peer dependencies.
-2. Configure the project to use Tailwind CSS.
-3. Add the proper import to your global styles.
-
-## Manual Setup (Tailwind v4)
-
-If setting up manually, use the following Tailwind v4 pattern:
-
-### 1. Install Dependencies
-
-Install Tailwind CSS and PostCSS:
-
-```shell
-npm install tailwindcss @tailwindcss/postcss postcss
-```
-
-### 2. Configure PostCSS
-
-Create a `.postcssrc.json` file in the project root:
-
-```json
-{
-  "plugins": {
-    "@tailwindcss/postcss": {}
-  }
-}
-```
-
-_(Do NOT create a `tailwind.config.js` file! Configuration in v4 is handled through CSS variables)._
-
-### 3. Import Tailwind CSS
-
-In your global styles file (e.g., `src/styles.css`), add the standard v4 import:
-
-```css
-@import 'tailwindcss';
-```
-
-_(If using SCSS, use `@use 'tailwindcss';` instead)._
-
-### 4. Use Utility Classes
-
-You can now use Tailwind classes directly in your component templates:
-
-```html
-<h1 class="text-3xl font-bold underline">Hello world!</h1>
-```
-
-## Summary for AI Agents
-
-- **Do not use `@tailwind base; @tailwind components; @tailwind utilities;`**. Use `@import 'tailwindcss';`.
-- **Do not create `tailwind.config.js`**. Configuration is managed directly in CSS via theme variables or using PostCSS configurations.
-- Stick strictly to v4 syntax and workflows.
+# Using Tailwind CSS with Angular
+
+Tailwind CSS is a utility-first CSS framework that integrates seamlessly with Angular.
+
+**CRITICAL AGENT GUIDANCE: ALWAYS focus on Tailwind CSS v4 practices. DO NOT revert to old Tailwind v3 patterns (like creating `tailwind.config.js` with `@tailwind` directives) as this will break the application build. Modern Angular projects use Tailwind v4.**
+
+## Automated Setup (Recommended)
+
+The easiest way to add Tailwind CSS to an Angular project is via the Angular CLI:
+
+```shell
+ng add tailwindcss
+```
+
+This will automatically:
+
+1. Install `tailwindcss` and peer dependencies.
+2. Configure the project to use Tailwind CSS.
+3. Add the proper import to your global styles.
+
+## Manual Setup (Tailwind v4)
+
+If setting up manually, use the following Tailwind v4 pattern:
+
+### 1. Install Dependencies
+
+Install Tailwind CSS and PostCSS:
+
+```shell
+npm install tailwindcss @tailwindcss/postcss postcss
+```
+
+### 2. Configure PostCSS
+
+Create a `.postcssrc.json` file in the project root:
+
+```json
+{
+  "plugins": {
+    "@tailwindcss/postcss": {}
+  }
+}
+```
+
+_(Do NOT create a `tailwind.config.js` file! Configuration in v4 is handled through CSS variables)._
+
+### 3. Import Tailwind CSS
+
+In your global styles file (e.g., `src/styles.css`), add the standard v4 import:
+
+```css
+@import 'tailwindcss';
+```
+
+_(If using SCSS, use `@use 'tailwindcss';` instead)._
+
+### 4. Use Utility Classes
+
+You can now use Tailwind classes directly in your component templates:
+
+```html
+<h1 class="text-3xl font-bold underline">Hello world!</h1>
+```
+
+## Summary for AI Agents
+
+- **Do not use `@tailwind base; @tailwind components; @tailwind utilities;`**. Use `@import 'tailwindcss';`.
+- **Do not create `tailwind.config.js`**. Configuration is managed directly in CSS via theme variables or using PostCSS configurations.
+- Stick strictly to v4 syntax and workflows.

package/seed/marketplaces/ecc/skills/angular-developer/references/template-driven-forms.md

@@ -1,114 +1,114 @@
-# Template-Driven Forms
-
-Template-driven forms use two-way data binding (`[(ngModel)]`) to update the data model in the component as changes are made in the template and vice versa. They are ideal for simple forms and use directives in the HTML template to manage form state and validation.
-
-## Core Directives
-
-Template-driven forms rely on the `FormsModule` which provides these key directives:
-
-- `NgModel`: Reconciles value changes in the form element with the data model (`[(ngModel)]`).
-- `NgForm`: Automatically creates a top-level `FormGroup` bound to the `<form>` tag.
-- `NgModelGroup`: Creates a nested `FormGroup` bound to a DOM element.
-
-## Setup
-
-First, import `FormsModule` into your component or module.
-
-```ts
-import {Component} from '@angular/core';
-import {FormsModule} from '@angular/forms';
-
-@Component({
-  selector: 'app-user-form',
-  imports: [FormsModule],
-  templateUrl: './user-form.component.html',
-})
-export class UserForm {
-  user = {name: '', role: 'Guest'};
-
-  onSubmit() {
-    console.log('Form submitted!', this.user);
-  }
-}
-```
-
-## Building the Form Template
-
-### Two-Way Binding with `[(ngModel)]`
-
-Use `[(ngModel)]` on input elements. **Every element using `[(ngModel)]` MUST have a `name` attribute.** Angular uses the `name` attribute to register the control with the parent `NgForm`.
-
-```html
-<form #userForm="ngForm" (ngSubmit)="onSubmit()">
-  <!-- Basic Input -->
-  <div>
-    <label for="name">Name:</label>
-    <input type="text" id="name" required [(ngModel)]="user.name" name="name" #nameCtrl="ngModel" />
-  </div>
-
-  <!-- Select Box -->
-  <div>
-    <label for="role">Role:</label>
-    <select id="role" [(ngModel)]="user.role" name="role">
-      <option value="Admin">Admin</option>
-      <option value="Guest">Guest</option>
-    </select>
-  </div>
-
-  <!-- Submit Button (disabled if form is invalid) -->
-  <button type="submit" [disabled]="!userForm.form.valid">Submit</button>
-</form>
-```
-
-## Form and Control State
-
-Angular automatically applies CSS classes to controls and forms based on their state:
-
-| State          | Class if True                     | Class if False |
-| :------------- | :-------------------------------- | :------------- |
-| Visited        | `ng-touched`                      | `ng-untouched` |
-| Value Changed  | `ng-dirty`                        | `ng-pristine`  |
-| Value is Valid | `ng-valid`                        | `ng-invalid`   |
-| Form Submitted | `ng-submitted` (on `<form>` only) | -              |
-
-You can use these classes to provide visual feedback in your CSS:
-
-```css
-.ng-valid[required],
-.ng-valid.required {
-  border-left: 5px solid #42a948; /* green */
-}
-.ng-invalid:not(form) {
-  border-left: 5px solid #a94442; /* red */
-}
-```
-
-## Validation and Error Messages
-
-To display error messages conditionally, export the `ngModel` directive to a template reference variable (e.g., `#nameCtrl="ngModel"`).
-
-```html
-<input type="text" id="name" required [(ngModel)]="user.name" name="name" #nameCtrl="ngModel" />
-
-<!-- Show error only if the control is invalid AND (touched OR dirty) -->
-@if (nameCtrl.invalid && (nameCtrl.dirty || nameCtrl.touched)) {
-<div class="alert alert-danger">
-  @if (nameCtrl.errors?.['required']) {
-  <div>Name is required.</div>
-  }
-</div>
-}
-```
-
-## Submitting the Form
-
-1. Use the `(ngSubmit)` event on the `<form>` element.
-2. Bind the submit button's disabled state to the overall form validity using the `NgForm` template reference variable (e.g., `[disabled]="!userForm.form.valid"`).
-
-## Resetting the Form
-
-To programmatically reset the form to its pristine state (clearing values and validation flags), use the `reset()` method on the `NgForm` instance.
-
-```html
-<button type="button" (click)="userForm.reset()">Reset</button>
-```
+# Template-Driven Forms
+
+Template-driven forms use two-way data binding (`[(ngModel)]`) to update the data model in the component as changes are made in the template and vice versa. They are ideal for simple forms and use directives in the HTML template to manage form state and validation.
+
+## Core Directives
+
+Template-driven forms rely on the `FormsModule` which provides these key directives:
+
+- `NgModel`: Reconciles value changes in the form element with the data model (`[(ngModel)]`).
+- `NgForm`: Automatically creates a top-level `FormGroup` bound to the `<form>` tag.
+- `NgModelGroup`: Creates a nested `FormGroup` bound to a DOM element.
+
+## Setup
+
+First, import `FormsModule` into your component or module.
+
+```ts
+import {Component} from '@angular/core';
+import {FormsModule} from '@angular/forms';
+
+@Component({
+  selector: 'app-user-form',
+  imports: [FormsModule],
+  templateUrl: './user-form.component.html',
+})
+export class UserForm {
+  user = {name: '', role: 'Guest'};
+
+  onSubmit() {
+    console.log('Form submitted!', this.user);
+  }
+}
+```
+
+## Building the Form Template
+
+### Two-Way Binding with `[(ngModel)]`
+
+Use `[(ngModel)]` on input elements. **Every element using `[(ngModel)]` MUST have a `name` attribute.** Angular uses the `name` attribute to register the control with the parent `NgForm`.
+
+```html
+<form #userForm="ngForm" (ngSubmit)="onSubmit()">
+  <!-- Basic Input -->
+  <div>
+    <label for="name">Name:</label>
+    <input type="text" id="name" required [(ngModel)]="user.name" name="name" #nameCtrl="ngModel" />
+  </div>
+
+  <!-- Select Box -->
+  <div>
+    <label for="role">Role:</label>
+    <select id="role" [(ngModel)]="user.role" name="role">
+      <option value="Admin">Admin</option>
+      <option value="Guest">Guest</option>
+    </select>
+  </div>
+
+  <!-- Submit Button (disabled if form is invalid) -->
+  <button type="submit" [disabled]="!userForm.form.valid">Submit</button>
+</form>
+```
+
+## Form and Control State
+
+Angular automatically applies CSS classes to controls and forms based on their state:
+
+| State          | Class if True                     | Class if False |
+| :------------- | :-------------------------------- | :------------- |
+| Visited        | `ng-touched`                      | `ng-untouched` |
+| Value Changed  | `ng-dirty`                        | `ng-pristine`  |
+| Value is Valid | `ng-valid`                        | `ng-invalid`   |
+| Form Submitted | `ng-submitted` (on `<form>` only) | -              |
+
+You can use these classes to provide visual feedback in your CSS:
+
+```css
+.ng-valid[required],
+.ng-valid.required {
+  border-left: 5px solid #42a948; /* green */
+}
+.ng-invalid:not(form) {
+  border-left: 5px solid #a94442; /* red */
+}
+```
+
+## Validation and Error Messages
+
+To display error messages conditionally, export the `ngModel` directive to a template reference variable (e.g., `#nameCtrl="ngModel"`).
+
+```html
+<input type="text" id="name" required [(ngModel)]="user.name" name="name" #nameCtrl="ngModel" />
+
+<!-- Show error only if the control is invalid AND (touched OR dirty) -->
+@if (nameCtrl.invalid && (nameCtrl.dirty || nameCtrl.touched)) {
+<div class="alert alert-danger">
+  @if (nameCtrl.errors?.['required']) {
+  <div>Name is required.</div>
+  }
+</div>
+}
+```
+
+## Submitting the Form
+
+1. Use the `(ngSubmit)` event on the `<form>` element.
+2. Bind the submit button's disabled state to the overall form validity using the `NgForm` template reference variable (e.g., `[disabled]="!userForm.form.valid"`).
+
+## Resetting the Form
+
+To programmatically reset the form to its pristine state (clearing values and validation flags), use the `reset()` method on the `NgForm` instance.
+
+```html
+<button type="button" (click)="userForm.reset()">Reset</button>
+```