npm - @cubis/foundry - Versions diffs - 0.3.63 → 0.3.64 - Mend

@cubis/foundry 0.3.63 → 0.3.64

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (995) hide show

package/workflows/skills/git-commit/POWER.md DELETED Viewed

@@ -1,47 +0,0 @@
----
-name: "git-commit"
-displayName: "Git Commit"
-description: "Create conventional commits with intelligent staging and message generation"
-keywords: ["git", "commit", "conventional", "stage", "push", "version control"]
----
-# Git Commit
-## Conventional Commit Format
-```
-<type>[scope]: <description>
-```
-## Types
-| Type       | Purpose                        |
-| ---------- | ------------------------------ |
-| `feat`     | New feature                    |
-| `fix`      | Bug fix                        |
-| `docs`     | Documentation only             |
-| `style`    | Formatting (no logic change)   |
-| `refactor` | Code refactor                  |
-| `perf`     | Performance improvement        |
-| `test`     | Add/update tests               |
-| `chore`    | Maintenance                    |
-## Workflow
-1. Check status: `git status --porcelain`
-2. View diff: `git diff --staged` or `git diff`
-3. Stage files: `git add <files>`
-4. Commit: `git commit -m "<type>[scope]: <description>"`
-## Rules
-- One logical change per commit
-- Present tense, imperative mood
-- Description under 72 characters
-- Reference issues: `Closes #123`
-## Safety
-- NEVER force push to main/master
-- NEVER skip hooks without explicit request
-- NEVER commit secrets

package/workflows/skills/gorouter-restoration/POWER.md DELETED Viewed

@@ -1,123 +0,0 @@
----
-name: "gorouter-restoration"
-displayName: "GoRouter & State Restoration"
-description: "GoRouter guard patterns, deep links, redirect safety, tab preservation, and restoration best practices"
-keywords:
-  [
-    "gorouter",
-    "routing",
-    "navigation",
-    "guards",
-    "deep links",
-    "state restoration",
-    "statefulshellroute",
-  ]
----
-# GoRouter & State Restoration
-## Overview
-Use this skill for safe routing architecture with GoRouter.
-Focus: guard correctness, redirect loop prevention, deep-link safety, shell navigation preservation, and restoration.
-## When to Use
-- Adding/modifying routes
-- Implementing authentication/authorization guards
-- Handling deep links
-- Preserving tab stacks with `StatefulShellRoute`
-- Fixing redirect loops or bad back-stack behavior
-## Core Rules
-1. Keep `onEnter`/`redirect` pure and fast (no async side effects).
-2. Avoid redirect loops by checking current matched location.
-3. Use `redirectLimit` intentionally for complex guard trees.
-4. Preserve user intent with `from=` query on auth redirects.
-5. Prefer IDs/path params over large objects in `extra`.
-## Guard Execution Model
-- `onEnter` runs first.
-- If allowed, top-level `redirect` runs.
-- Route-level `GoRoute.redirect` runs last.
-Design guards so each stage is deterministic and idempotent.
-## Quick Reference
-### Safe redirect logic
-```dart
-String? redirectLogic({
-  required bool isAuthenticated,
-  required bool activationDone,
-  required String matchedLocation,
-}) {
-  final isLogin = matchedLocation == '/login';
-  final isActivation = matchedLocation == '/activation';
-  if (!activationDone && !isActivation) return '/activation';
-  if (activationDone && !isAuthenticated && !isLogin) {
-    return '/login?from=${Uri.encodeComponent(matchedLocation)}';
-  }
-  if (isAuthenticated && (isLogin || isActivation)) return '/home';
-  return null;
-}
-```
-### Tab/state preservation
-```dart
-StatefulShellRoute.indexedStack(
-  branches: [
-    StatefulShellBranch(navigatorKey: _homeKey, routes: [...]),
-    StatefulShellBranch(navigatorKey: _salesKey, routes: [...]),
-    StatefulShellBranch(navigatorKey: _settingsKey, routes: [...]),
-  ],
-  builder: (context, state, shell) => AppShell(shell: shell),
-)
-```
-### Restoration
-```dart
-final router = GoRouter(
-  restorationScopeId: 'router',
-  routes: [...],
-);
-MaterialApp.router(
-  restorationScopeId: 'app',
-  routerConfig: router,
-)
-```
-## Routing Checklist
-- Routes use constants and typed parameter extraction.
-- Guards do not mutate app state.
-- Redirect logic handles both anonymous and authenticated states.
-- Deep links are validated for invalid/missing IDs.
-- Logout clears sensitive stack/history as intended.
-- Tab branch stacks remain independent.
-## Output Format
-1. Route plan (paths, params, names)
-2. Guard plan (stage, conditions, outcomes)
-3. Restoration plan (what is preserved)
-4. Edge cases (deep links, logout, back-nav)
-5. Tests (guard behavior, tab preservation, invalid params)
-## Steering Files
-- `guard_patterns.md` - Guard decision rules and anti-loop checks
-- `tab_preservation.md` - StatefulShellRoute and restoration patterns
-## Templates
-- `guard_redirect` - Guard redirect function skeleton
-- `stateful_shell_skeleton` - Tab shell starter

package/workflows/skills/microservices-architect/POWER.md DELETED Viewed

@@ -1,109 +0,0 @@
----
-name: microservices-architect
-displayName: Microservices Architect
-description:
-  Use when designing distributed systems, decomposing monoliths, or implementing
-  microservices patterns. Invoke for service boundaries, DDD, saga patterns, event
-  sourcing, service mesh, distributed tracing.
-keywords:
-  - microservices
-  - service mesh
-  - distributed systems
-  - service boundaries
-  - domain-driven design
-  - event sourcing
-  - CQRS
-  - saga pattern
-  - Kubernetes microservices
-  - Istio
-  - distributed tracing
-author: OneUp
----
-# Microservices Architect
-## Overview
-Senior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.
-## Role Definition
-You are a senior microservices architect with 15+ years of experience designing distributed systems. You specialize in service decomposition, domain-driven design, resilience patterns, service mesh technologies, and cloud-native architectures. You design systems that scale, self-heal, and enable autonomous teams.
-## When to Use This Skill
-- Decomposing monoliths into microservices
-- Defining service boundaries and bounded contexts
-- Designing inter-service communication patterns
-- Implementing resilience patterns (circuit breakers, retries, bulkheads)
-- Setting up service mesh (Istio, Linkerd)
-- Designing event-driven architectures
-- Implementing distributed transactions (Saga, CQRS)
-- Establishing observability (tracing, metrics, logging)
-## Core Workflow
-1. **Domain Analysis** - Apply DDD to identify bounded contexts and service boundaries
-2. **Communication Design** - Choose sync/async patterns, protocols (REST, gRPC, events)
-3. **Data Strategy** - Database per service, event sourcing, eventual consistency
-4. **Resilience** - Circuit breakers, retries, timeouts, bulkheads, fallbacks
-5. **Observability** - Distributed tracing, correlation IDs, centralized logging
-6. **Deployment** - Container orchestration, service mesh, progressive delivery
-## Available Steering Files
-Load detailed guidance on-demand:
-| Topic               | Reference                   | Load When                                          |
-| ------------------- | --------------------------- | -------------------------------------------------- |
-| Service Boundaries  | `references/decomposition.md` | Monolith decomposition, bounded contexts, DDD      |
-| Communication       | `references/communication.md` | REST vs gRPC, async messaging, event-driven        |
-| Resilience Patterns | `references/patterns.md`      | Circuit breakers, saga, bulkhead, retry strategies |
-| Data Management     | `references/data.md`          | Database per service, event sourcing, CQRS         |
-| Observability       | `references/observability.md` | Distributed tracing, correlation IDs, metrics      |
-## Constraints
-### MUST DO
-- Apply domain-driven design for service boundaries
-- Use database per service pattern
-- Implement circuit breakers for external calls
-- Add correlation IDs to all requests
-- Use async communication for cross-aggregate operations
-- Design for failure and graceful degradation
-- Implement health checks and readiness probes
-- Use API versioning strategies
-### MUST NOT DO
-- Create distributed monoliths
-- Share databases between services
-- Use synchronous calls for long-running operations
-- Skip distributed tracing implementation
-- Ignore network latency and partial failures
-- Create chatty service interfaces
-- Store shared state without proper patterns
-- Deploy without observability
-## Output Templates
-When designing microservices architecture, provide:
-1. Service boundary diagram with bounded contexts
-2. Communication patterns (sync/async, protocols)
-3. Data ownership and consistency model
-4. Resilience patterns for each integration point
-5. Deployment and infrastructure requirements
-## Knowledge Reference
-Domain-driven design, bounded contexts, event storming, REST/gRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem
-## Related Powers
-- **DevOps Engineer** - Container orchestration and CI/CD pipelines
-- **Kubernetes Specialist** - Advanced K8s patterns and operators
-- **GraphQL Architect** - Federation for distributed schemas
-- **Architecture Designer** - High-level system design
-- **Monitoring Expert** - Observability implementation

package/workflows/skills/nestjs-expert/POWER.md DELETED Viewed

@@ -1,130 +0,0 @@
----
-name: nestjs-expert
-displayName: Nestjs Expert
-description:
-  Use when building NestJS applications requiring modular architecture,
-  dependency injection, or TypeScript backend development. Invoke for modules, controllers,
-  services, DTOs, guards, interceptors, Mongoose.
-keywords:
-  - NestJS
-  - Nest
-  - Node.js backend
-  - TypeScript backend
-  - dependency injection
-  - controller
-  - service
-  - module
-  - guard
-  - interceptor
-  - session authentication
-author: OneUp
----
-# NestJS Expert
-## Overview
-Senior NestJS specialist with deep expertise in enterprise-grade, scalable TypeScript backend applications. Focused on session-based authentication with Fastify and MongoDB/Mongoose integration.
-## Role Definition
-You are a senior Node.js engineer with 10+ years of backend experience. You specialize in NestJS architecture, dependency injection, and enterprise patterns. You build modular, testable applications with proper separation of concerns.
-## When to Use This Power
-- Building NestJS REST APIs with Fastify
-- Implementing modules, controllers, and services
-- Creating DTOs with validation
-- Setting up session-based authentication (NOT JWT)
-- Implementing guards, interceptors, and pipes
-- Database integration with Mongoose
-## Core Workflow
-1. **Analyze requirements** - Identify modules, endpoints, entities
-2. **Design structure** - Plan module organization and dependencies
-3. **Implement** - Create modules, services, controllers with DI
-4. **Secure** - Add guards, validation, authentication
-5. **Test** - Write unit tests and E2E tests
-## Available Steering Files
-Load detailed guidance on-demand:
-| Topic             | Reference                            | Load When                                   |
-| ----------------- | ------------------------------------ | ------------------------------------------- |
-| Controllers       | `references/controllers-routing.md`    | Creating controllers, routing, Swagger docs |
-| Services          | `references/services-di.md`            | Services, dependency injection, providers   |
-| DTOs              | `references/dtos-validation.md`        | Validation, class-validator, DTOs           |
-| Authentication    | `references/authentication.md`         | Session auth, guards, roles, multi-tenant   |
-| Testing           | `references/testing-patterns.md`       | Unit tests, E2E tests, mocking              |
-| Express Migration | `references/migration-from-express.md` | Migrating from Express.js to NestJS         |
-## Authentication Approach
-**OneUp uses session-based authentication, NOT JWT.**
-```typescript
-// Session-based auth with Fastify
-@Post('login')
-async login(@Body() dto: LoginDto, @Req() request: FastifyRequest) {
-  const user = await this.authService.validateUser(dto.username, dto.password);
-  // Store user info in session
-  request.session.set('userId', user.userId);
-  request.session.set('organizationId', user.organizationId);
-  request.session.set('role', user.role);
-  return { message: 'Login successful' };
-}
-@Post('logout')
-async logout(@Req() request: FastifyRequest) {
-  request.session.delete();
-  return { message: 'Logout successful' };
-}
-```
-See `references/authentication.md` for complete session auth implementation.
-## Constraints
-### MUST DO
-- Use dependency injection for all services
-- Validate all inputs with class-validator
-- Use DTOs for request/response bodies
-- Implement proper error handling with HTTP exceptions
-- Document APIs with Swagger decorators
-- Write unit tests for services
-- Use environment variables for configuration
-### MUST NOT DO
-- Expose passwords or secrets in responses
-- Trust user input without validation
-- Use `any` type unless absolutely necessary
-- Create circular dependencies between modules
-- Hardcode configuration values
-- Skip error handling
-## Output Templates
-When implementing NestJS features, provide:
-1. Module definition
-2. Controller with Swagger decorators
-3. Service with error handling
-4. DTOs with validation
-5. Tests for service methods
-## Knowledge Reference
-NestJS, TypeScript, Mongoose, Fastify, @fastify/secure-session, class-validator, class-transformer, Swagger/OpenAPI, Jest, Supertest, Guards, Interceptors, Pipes, Filters
-## Related Powers
-- **Fastify Patterns** - Fastify adapter and session configuration
-- **Mongoose NestJS** - MongoDB integration patterns
-- **Test Master** - Comprehensive testing strategies
-- **Security Reviewer** - Security auditing

package/workflows/skills/nextjs-developer/POWER.md DELETED Viewed

@@ -1,166 +0,0 @@
----
-name: "nextjs-developer"
-displayName: "Next.js Developer"
-description: "Expert Next.js 14+ developer with App Router, Server Components, Server Actions, performance optimization, SEO, and production deployment patterns"
-keywords:
-  [
-    "nextjs",
-    "next.js",
-    "react",
-    "app router",
-    "server components",
-    "server actions",
-    "vercel",
-    "ssr",
-    "seo",
-    "typescript",
-  ]
----
-# Next.js Developer
-## Overview
-Senior Next.js developer expertise for Next.js 14+ with App Router and full-stack features. Covers server components, server actions, edge runtime, performance optimization, and production deployment with focus on fast, SEO-friendly applications.
-## When to Use
-- Building new Next.js 14+ projects with App Router
-- Implementing Server Components and Server Actions
-- Optimizing Core Web Vitals and performance
-- Setting up data fetching with caching and revalidation
-- Configuring SEO (metadata, sitemaps, structured data)
-- Deploying to Vercel, Docker, or self-hosted environments
-- Writing tests with Playwright and React Testing Library
-## Quick Reference
-### App Router File Conventions
-```
-app/
-├── layout.tsx          # Root layout (required)
-├── page.tsx            # Home page
-├── loading.tsx         # Loading UI (Suspense boundary)
-├── error.tsx           # Error boundary
-├── not-found.tsx       # 404 page
-├── (auth)/             # Route group (no URL segment)
-│   ├── login/page.tsx
-│   └── register/page.tsx
-├── dashboard/
-│   ├── layout.tsx      # Nested layout
-│   ├── page.tsx
-│   └── @modal/         # Parallel route (slot)
-│       └── (..)settings/page.tsx  # Intercepting route
-└── api/
-    └── route.ts        # API route handler
-```
-### Server vs Client Components
-```tsx
-// Server Component (default) — no directive needed
-async function ProductList() {
-  const products = await db.product.findMany();
-  return (
-    <ul>
-      {products.map((p) => (
-        <li key={p.id}>{p.name}</li>
-      ))}
-    </ul>
-  );
-}
-// Client Component — needs 'use client' directive
-("use client");
-import { useState } from "react";
-export function Counter() {
-  const [count, setCount] = useState(0);
-  return <button onClick={() => setCount((c) => c + 1)}>{count}</button>;
-}
-```
-### Server Actions
-```tsx
-// Inline server action
-async function createPost(formData: FormData) {
-  "use server";
-  const title = formData.get("title") as string;
-  await db.post.create({ data: { title } });
-  revalidatePath("/posts");
-}
-// In a form
-<form action={createPost}>
-  <input name="title" />
-  <button type="submit">Create</button>
-</form>;
-```
-### Data Fetching with Cache
-```tsx
-// Cached by default (static)
-const data = await fetch("https://api.example.com/data");
-// Revalidate every 60 seconds (ISR)
-const data = await fetch("https://api.example.com/data", {
-  next: { revalidate: 60 },
-});
-// No cache (dynamic)
-const data = await fetch("https://api.example.com/data", {
-  cache: "no-store",
-});
-```
-### Metadata API
-```tsx
-// Static metadata
-export const metadata: Metadata = {
-  title: "My App",
-  description: "Description",
-  openGraph: { title: "My App", images: ["/og.png"] },
-};
-// Dynamic metadata
-export async function generateMetadata({ params }): Promise<Metadata> {
-  const product = await getProduct(params.id);
-  return { title: product.name };
-}
-```
-## Quality Checklist
-- [ ] TypeScript strict mode enabled
-- [ ] Core Web Vitals > 90
-- [ ] SEO score > 95
-- [ ] Error boundaries on all routes
-- [ ] Loading states for async content
-- [ ] Edge runtime compatible where needed
-- [ ] Monitoring and error tracking configured
-## Steering Files
-| File                   | Load When                                                            |
-| ---------------------- | -------------------------------------------------------------------- |
-| `app-router.md`        | Route structure, layouts, route groups, parallel/intercepting routes |
-| `server-components.md` | Server/Client component patterns, streaming, Suspense                |
-| `server-actions.md`    | Form handling, mutations, validation, optimistic updates             |
-| `data-fetching.md`     | Fetch patterns, caching, revalidation, SWR/React Query               |
-| `performance.md`       | Image/font/script optimization, Core Web Vitals, bundle analysis     |
-| `seo.md`               | Metadata API, sitemaps, structured data, Open Graph                  |
-| `deployment.md`        | Vercel, Docker, self-hosting, monitoring, multi-region               |
-| `testing.md`           | Playwright E2E, component tests, visual regression, accessibility    |
-## Performance Targets
-| Metric | Target  |
-| ------ | ------- |
-| TTFB   | < 200ms |
-| FCP    | < 1s    |
-| LCP    | < 2.5s  |
-| CLS    | < 0.1   |
-| FID    | < 100ms |

package/workflows/skills/oneup-design/POWER.md DELETED Viewed

@@ -1,72 +0,0 @@
----
-name: "oneup-design"
-displayName: "OneUp Design System"
-description: "OneUp HR design system with One* components, colors, spacing, and typography tokens"
-keywords: ["design", "ui", "component", "color", "spacing", "padding", "typography", "OneText", "OneButton", "OneCard", "widget", "theme"]
----
-# OneUp Design System
-## Onboarding
-Import the design system:
-```dart
-import '../../../../core/design_system/one_design_system.dart';
-```
-## When to Load Steering Files
-- Working with colors → `colors.md`
-- Working with spacing/padding → `spacing.md`
-- Using One* components → `components.md`
-## MCP Tools (Use Before Writing UI)
-1. `listComponents` → Find One* component
-2. `getComponentSpec` → Get props/examples
-3. `getDesignTokens` → Get tokens
-4. `validateWidget` → Validate compliance
-## Quick Reference
-### Colors
-```dart
-// Theme-aware
-context.colors.primary
-context.colors.surface
-context.colors.onSurface
-// Static
-OneColor.success   // #2DC656
-OneColor.error     // #FF3C35
-OneColor.white
-```
-### Spacing
-```dart
-OneSpacing.sm   // 8
-OneSpacing.md   // 12
-OneSpacing.lg   // 16
-OneSpacing.xl   // 20
-```
-### Padding
-```dart
-OnePadding.screenHorizontal  // h: 20
-OnePadding.cardAll           // all: 16
-OnePadding.custom(left: OneSpacing.sm)
-```
-### Forbidden Patterns
-```dart
-// ❌ Never use
-SizedBox(height: 16)         // Use OneSpacing.lg
-Color(0xFF...)               // Use context.colors.X
-Colors.white                 // Use OneColor.white
-Text(...)                    // Use OneText.X()
-ElevatedButton(...)          // Use OneButton.primary()
-```