@rubix0270/arboris 1.0.2 → 1.0.4

package/prisma/skills/angular-developer/references/signals-overview.md

@@ -1,94 +0,0 @@
-# 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/prisma/skills/angular-developer/references/tailwind-css.md

@@ -1,69 +0,0 @@
-# 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/prisma/skills/angular-developer/references/template-driven-forms.md

@@ -1,114 +0,0 @@
-# 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>
-```

package/prisma/skills/angular-developer/references/testing-fundamentals.md

@@ -1,65 +0,0 @@
-# Testing Fundamentals
-
-This guide covers the fundamental principles and practices for writing Angular unit and component tests. Use the runner already configured in the project.
-
-## Core Philosophy: Async-First
-
-Modern Angular applications often schedule state changes asynchronously, especially when using signals or zoneless change detection. Tests should account for this.
-
-Prefer the "Act, Wait, Assert" pattern:
-
-1. **Act:** Update state or perform an action (e.g., set a component input, click a button).
-2. **Wait:** Use `await fixture.whenStable()` to allow the framework to process the scheduled update and render the changes.
-3. **Assert:** Verify the outcome.
-
-### Basic Test Structure Example
-
-```ts
-import {ComponentFixture, TestBed} from '@angular/core/testing';
-import {MyComponent} from './my.component';
-
-describe('MyComponent', () => {
-  let component: MyComponent;
-  let fixture: ComponentFixture<MyComponent>;
-  let h1: HTMLElement;
-
-  beforeEach(async () => {
-    // 1. Configure the test module
-    await TestBed.configureTestingModule({
-      imports: [MyComponent],
-    }).compileComponents();
-
-    // 2. Create the component fixture
-    fixture = TestBed.createComponent(MyComponent);
-    component = fixture.componentInstance;
-    h1 = fixture.nativeElement.querySelector('h1');
-  });
-
-  it('should display the default title', async () => {
-    // ACT: (Implicit) Component is created with default state.
-    // WAIT for initial data binding.
-    await fixture.whenStable();
-    // ASSERT the initial state.
-    expect(h1.textContent).toContain('Default Title');
-  });
-
-  it('should display a different title after a change', async () => {
-    // ACT: Change the component's title property.
-    component.title.set('New Test Title');
-
-    // WAIT for the asynchronous update to complete.
-    await fixture.whenStable();
-
-    // ASSERT the DOM has been updated.
-    expect(h1.textContent).toContain('New Test Title');
-  });
-});
-```
-
-## TestBed and ComponentFixture
-
-- **`TestBed`**: The primary utility for creating a test-specific Angular module. Use `TestBed.configureTestingModule({...})` in your `beforeEach` to declare components, provide services, and set up imports needed for your test.
-- **`ComponentFixture`**: A handle on the created component instance and its environment.
-  - `fixture.componentInstance`: Access the component's class instance.
-  - `fixture.nativeElement`: Access the component's root DOM element.
-  - `fixture.debugElement`: An Angular-specific wrapper around the `nativeElement` that provides safer, platform-agnostic ways to query the DOM (e.g., `debugElement.query(By.css('p'))`).

package/prisma/skills/api-connector-builder/SKILL.md

@@ -1,121 +0,0 @@
----
-name: api-connector-builder
-description: Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.
-metadata:
-  origin: ECC direct-port adaptation
-version: "1.0.0"
----
-
-# API Connector Builder
-
-Use this when the job is to add a repo-native integration surface, not just a generic HTTP client.
-
-The point is to match the host repository's pattern:
-
-- connector layout
-- config schema
-- auth model
-- error handling
-- test style
-- registration/discovery wiring
-
-## When to Use
-
-- "Build a Jira connector for this project"
-- "Add a Slack provider following the existing pattern"
-- "Create a new integration for this API"
-- "Build a plugin that matches the repo's connector style"
-
-## Guardrails
-
-- do not invent a new integration architecture when the repo already has one
-- do not start from vendor docs alone; start from existing in-repo connectors first
-- do not stop at transport code if the repo expects registry wiring, tests, and docs
-- do not cargo-cult old connectors if the repo has a newer current pattern
-
-## Workflow
-
-### 1. Learn the house style
-
-Inspect at least 2 existing connectors/providers and map:
-
-- file layout
-- abstraction boundaries
-- config model
-- retry / pagination conventions
-- registry hooks
-- test fixtures and naming
-
-### 2. Narrow the target integration
-
-Define only the surface the repo actually needs:
-
-- auth flow
-- key entities
-- core read/write operations
-- pagination and rate limits
-- webhook or polling model
-
-### 3. Build in repo-native layers
-
-Typical slices:
-
-- config/schema
-- client/transport
-- mapping layer
-- connector/provider entrypoint
-- registration
-- tests
-
-### 4. Validate against the source pattern
-
-The new connector should look obvious in the codebase, not imported from a different ecosystem.
-
-## Reference Shapes
-
-### Provider-style
-
-```text
-providers/
-  existing_provider/
-    __init__.py
-    provider.py
-    config.py
-```
-
-### Connector-style
-
-```text
-integrations/
-  existing/
-    client.py
-    models.py
-    connector.py
-```
-
-### TypeScript plugin-style
-
-```text
-src/integrations/
-  existing/
-    index.ts
-    client.ts
-    types.ts
-    test.ts
-```
-
-## Quality Checklist
-
-- [ ] matches an existing in-repo integration pattern
-- [ ] config validation exists
-- [ ] auth and error handling are explicit
-- [ ] pagination/retry behavior follows repo norms
-- [ ] registry/discovery wiring is complete
-- [ ] tests mirror the host repo's style
-- [ ] docs/examples are updated if expected by the repo
-
-## Related Skills
-
-- `backend-patterns`
-- `mcp-server-patterns`
-- `github-ops`