@cubis/foundry 0.3.10

package/Ai Agent Workflow/skills/design-system-builder/POWER.md

@@ -0,0 +1,150 @@
+---
+name: "design-system-builder"
+displayName: "Design System Builder"
+description: "Create and review design system components: API design, token usage, theming, variants, and documentation"
+keywords:
+  [
+    "design system",
+    "components",
+    "component design",
+    "tokens",
+    "theming",
+    "variants",
+    "widget api",
+  ]
+---
+
+# Design System Builder
+
+## Overview
+
+This power helps you create new design system components or update existing ones, ensuring consistent API design, proper token usage, theming support, and comprehensive documentation.
+
+## When to Use
+
+- Creating new One\* components
+- Updating existing One\* components
+- Reviewing component API design
+- Adding new variants to components
+- Ensuring token compliance in components
+
+## Component Design Principles
+
+### 1. Token-Based Styling
+
+```dart
+// ❌ Don't hardcode values
+Container(
+  padding: EdgeInsets.all(16),
+  decoration: BoxDecoration(
+    color: Color(0xFF123456),
+    borderRadius: BorderRadius.circular(8),
+  ),
+)
+
+// ✅ Use design tokens
+Container(
+  padding: EdgeInsets.all(AppSpacing.lg), // Use your spacing tokens
+  decoration: BoxDecoration(
+    color: Theme.of(context).colorScheme.surface, // Use theme colors
+    borderRadius: BorderRadius.circular(AppRadius.md), // Use radius tokens
+  ),
+)
+```
+
+### 2. Semantic API
+
+```dart
+// ✅ Semantic, clear API
+class AppButton extends StatelessWidget {
+  final String label;
+  final VoidCallback? onPressed;
+  final bool isLoading;
+  final bool isDisabled;
+  final Widget? leading;
+  final Widget? trailing;
+
+  // Named constructors for variants
+  AppButton.primary({...});
+  AppButton.secondary({...});
+  AppButton.ghost({...});
+}
+```
+
+### 3. Composition Over Configuration
+
+```dart
+// ✅ Compose smaller components
+class AppCard extends StatelessWidget {
+  final Widget child;
+  final EdgeInsets? padding;
+  final Color? backgroundColor;
+
+  AppCard.elevated({...}) : this(
+    padding: EdgeInsets.all(AppSpacing.lg),
+    backgroundColor: Theme.of(context).colorScheme.surface,
+    elevation: 2,
+  );
+}
+```
+
+## Component Checklist
+
+### API Design
+
+- [ ] Semantic property names (label, errorText, leading, trailing)
+- [ ] Sensible defaults (minimal required params)
+- [ ] Named constructors for variants
+- [ ] Consistent with other design system components
+
+### Token Usage
+
+- [ ] No hardcoded colors (use theme colors or color tokens)
+- [ ] No hardcoded spacing (use spacing tokens)
+- [ ] No hardcoded typography (use text styles)
+- [ ] No hardcoded radius (use radius tokens)
+
+### Theming
+
+- [ ] Respects light/dark theme
+- [ ] Uses theme-aware colors (context.colors)
+- [ ] Adapts to platform (iOS/Android)
+
+### Variants
+
+- [ ] Variants defined as enums or named constructors
+- [ ] Each variant has clear use case
+- [ ] Variants share common base implementation
+
+### Documentation
+
+- [ ] Doc comment explaining purpose
+- [ ] At least 2 usage examples
+- [ ] Migration notes from raw Flutter widgets
+
+### Testing
+
+- [ ] Widget test for each variant
+- [ ] Test disabled/loading states
+- [ ] Test accessibility (semantic labels)
+- [ ] Consider golden tests for visual regression
+
+## Output Format
+
+When creating/reviewing a component:
+
+1. **Component Spec** (purpose, variants, API)
+2. **Token Usage** (which tokens are used)
+3. **Implementation Notes** (composition, theming)
+4. **Examples** (2+ usage snippets)
+5. **Tests** (widget tests + golden ideas)
+6. **Migration Notes** (how to replace old widgets)
+
+## Steering Files
+
+- `component_api_guidelines.md` - API design best practices
+
+## Templates
+
+- `one_component_skeleton` - Component template
+- `component_widget_test` - Widget test template

package/Ai Agent Workflow/skills/design-system-builder/SKILL.md

@@ -0,0 +1,150 @@
+---
+name: "design-system-builder"
+displayName: "Design System Builder"
+description: "Create and review design system components: API design, token usage, theming, variants, and documentation"
+keywords:
+  [
+    "design system",
+    "components",
+    "component design",
+    "tokens",
+    "theming",
+    "variants",
+    "widget api",
+  ]
+---
+
+# Design System Builder
+
+## Overview
+
+This power helps you create new design system components or update existing ones, ensuring consistent API design, proper token usage, theming support, and comprehensive documentation.
+
+## When to Use
+
+- Creating new One\* components
+- Updating existing One\* components
+- Reviewing component API design
+- Adding new variants to components
+- Ensuring token compliance in components
+
+## Component Design Principles
+
+### 1. Token-Based Styling
+
+```dart
+// ❌ Don't hardcode values
+Container(
+  padding: EdgeInsets.all(16),
+  decoration: BoxDecoration(
+    color: Color(0xFF123456),
+    borderRadius: BorderRadius.circular(8),
+  ),
+)
+
+// ✅ Use design tokens
+Container(
+  padding: EdgeInsets.all(AppSpacing.lg), // Use your spacing tokens
+  decoration: BoxDecoration(
+    color: Theme.of(context).colorScheme.surface, // Use theme colors
+    borderRadius: BorderRadius.circular(AppRadius.md), // Use radius tokens
+  ),
+)
+```
+
+### 2. Semantic API
+
+```dart
+// ✅ Semantic, clear API
+class AppButton extends StatelessWidget {
+  final String label;
+  final VoidCallback? onPressed;
+  final bool isLoading;
+  final bool isDisabled;
+  final Widget? leading;
+  final Widget? trailing;
+
+  // Named constructors for variants
+  AppButton.primary({...});
+  AppButton.secondary({...});
+  AppButton.ghost({...});
+}
+```
+
+### 3. Composition Over Configuration
+
+```dart
+// ✅ Compose smaller components
+class AppCard extends StatelessWidget {
+  final Widget child;
+  final EdgeInsets? padding;
+  final Color? backgroundColor;
+
+  AppCard.elevated({...}) : this(
+    padding: EdgeInsets.all(AppSpacing.lg),
+    backgroundColor: Theme.of(context).colorScheme.surface,
+    elevation: 2,
+  );
+}
+```
+
+## Component Checklist
+
+### API Design
+
+- [ ] Semantic property names (label, errorText, leading, trailing)
+- [ ] Sensible defaults (minimal required params)
+- [ ] Named constructors for variants
+- [ ] Consistent with other design system components
+
+### Token Usage
+
+- [ ] No hardcoded colors (use theme colors or color tokens)
+- [ ] No hardcoded spacing (use spacing tokens)
+- [ ] No hardcoded typography (use text styles)
+- [ ] No hardcoded radius (use radius tokens)
+
+### Theming
+
+- [ ] Respects light/dark theme
+- [ ] Uses theme-aware colors (context.colors)
+- [ ] Adapts to platform (iOS/Android)
+
+### Variants
+
+- [ ] Variants defined as enums or named constructors
+- [ ] Each variant has clear use case
+- [ ] Variants share common base implementation
+
+### Documentation
+
+- [ ] Doc comment explaining purpose
+- [ ] At least 2 usage examples
+- [ ] Migration notes from raw Flutter widgets
+
+### Testing
+
+- [ ] Widget test for each variant
+- [ ] Test disabled/loading states
+- [ ] Test accessibility (semantic labels)
+- [ ] Consider golden tests for visual regression
+
+## Output Format
+
+When creating/reviewing a component:
+
+1. **Component Spec** (purpose, variants, API)
+2. **Token Usage** (which tokens are used)
+3. **Implementation Notes** (composition, theming)
+4. **Examples** (2+ usage snippets)
+5. **Tests** (widget tests + golden ideas)
+6. **Migration Notes** (how to replace old widgets)
+
+## Steering Files
+
+- `component_api_guidelines.md` - API design best practices
+
+## Templates
+
+- `one_component_skeleton` - Component template
+- `component_widget_test` - Widget test template

package/Ai Agent Workflow/skills/design-system-builder/references/component_api_guidelines.md

@@ -0,0 +1,20 @@
+# One* component API guidelines
+
+## Keep APIs predictable
+- Named parameters
+- Defaults match the most common use case
+- Avoid optional booleans that conflict (use enums)
+
+## Prefer slots over flags
+Bad:
+- `hasLeadingIcon`, `hasTrailingIcon`
+Good:
+- `leading`, `trailing`
+
+## Theming
+- Use OneTheme / tokens only
+- Provide override hooks carefully (don’t allow raw colors everywhere)
+
+## Accessibility
+- Provide semantic labels for icon-only variants
+- Ensure focus and keyboard nav works on desktop

package/Ai Agent Workflow/skills/design-system-builder/steering/component_api_guidelines.md

@@ -0,0 +1,20 @@
+# One* component API guidelines
+
+## Keep APIs predictable
+- Named parameters
+- Defaults match the most common use case
+- Avoid optional booleans that conflict (use enums)
+
+## Prefer slots over flags
+Bad:
+- `hasLeadingIcon`, `hasTrailingIcon`
+Good:
+- `leading`, `trailing`
+
+## Theming
+- Use OneTheme / tokens only
+- Provide override hooks carefully (don’t allow raw colors everywhere)
+
+## Accessibility
+- Provide semantic labels for icon-only variants
+- Ensure focus and keyboard nav works on desktop

package/Ai Agent Workflow/skills/design-system-builder/templates/component_widget_test.md

@@ -0,0 +1,21 @@
+```
+// templates/component_widget_test.tmpl
+//
+// Copy into test/widget/design_system/<component>_test.dart
+
+import 'package:flutter_test/flutter_test.dart';
+import 'package:flutter/material.dart';
+
+void main() {
+  testWidgets('renders primary variant', (tester) async {
+    await tester.pumpWidget(
+      const MaterialApp(
+        home: Scaffold(
+          body: OneActionButton(label: 'Save', onPressed: null),
+        ),
+      ),
+    );
+    expect(find.text('Save'), findsOneWidget);
+  });
+}
+```

package/Ai Agent Workflow/skills/design-system-builder/templates/one_component_skeleton.md

@@ -0,0 +1,38 @@
+```
+// templates/one_component_skeleton.tmpl
+//
+// Skeleton for a One* component using tokens.
+
+class OneActionButton extends StatelessWidget {
+  const OneActionButton({
+    super.key,
+    required this.label,
+    required this.onPressed,
+    this.variant = OneButtonVariant.primary,
+    this.isLoading = false,
+    this.semanticLabel,
+  });
+
+  final String label;
+  final VoidCallback? onPressed;
+  final OneButtonVariant variant;
+  final bool isLoading;
+  final String? semanticLabel;
+
+  @override
+  Widget build(BuildContext context) {
+    final effectiveLabel = semanticLabel ?? label;
+
+    return Semantics(
+      button: true,
+      label: effectiveLabel,
+      child: OneButton(
+        label: label,
+        onPressed: isLoading ? null : onPressed,
+        variant: variant,
+        isLoading: isLoading,
+      ),
+    );
+  }
+}
+```

package/Ai Agent Workflow/skills/devops-engineer/POWER.md

@@ -0,0 +1,99 @@
+---
+name: devops-engineer
+displayName: Devops Engineer
+description:
+  Use when setting up CI/CD pipelines, containerizing applications, or
+  managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud
+  platforms, GitOps.
+keywords:
+  - DevOps
+  - CI/CD
+  - deployment
+  - Docker
+  - Kubernetes
+  - Terraform
+  - GitHub Actions
+  - infrastructure
+  - platform engineering
+  - incident response
+  - on-call
+  - self-service
+author: OneUp
+---
+
+# DevOps Engineer
+
+## Overview
+
+Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation.
+
+## Role Definition
+
+You are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:
+
+- **Build Hat**: Automating build, test, and packaging
+- **Deploy Hat**: Orchestrating deployments across environments
+- **Ops Hat**: Ensuring reliability, monitoring, and incident response
+
+## When to Use This Skill
+
+- Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
+- Containerizing applications (Docker, Docker Compose)
+- Kubernetes deployments and configurations
+- Infrastructure as code (Terraform, Pulumi)
+- Cloud platform configuration (AWS, GCP, Azure)
+- Deployment strategies (blue-green, canary, rolling)
+- Building internal developer platforms and self-service tools
+- Incident response, on-call, and production troubleshooting
+- Release automation and artifact management
+
+## Core Workflow
+
+1. **Assess** - Understand application, environments, requirements
+2. **Design** - Pipeline structure, deployment strategy
+3. **Implement** - IaC, Dockerfiles, CI/CD configs
+4. **Deploy** - Roll out with verification
+5. **Monitor** - Set up observability, alerts
+
+## Available Steering Files
+
+Load detailed guidance on-demand:
+
+| Topic          | Reference                           | Load When                                                      |
+| -------------- | ----------------------------------- | -------------------------------------------------------------- |
+| GitHub Actions | `references/github-actions.md`        | Setting up CI/CD pipelines, GitHub workflows                   |
+| Docker         | `references/docker-patterns.md`       | Containerizing applications, writing Dockerfiles               |
+| Kubernetes     | `references/kubernetes.md`            | K8s deployments, services, ingress, pods                       |
+| Terraform      | `references/terraform-iac.md`         | Infrastructure as code, AWS/GCP provisioning                   |
+| Deployment     | `references/deployment-strategies.md` | Blue-green, canary, rolling updates, rollback                  |
+| Platform       | `references/platform-engineering.md`  | Self-service infra, developer portals, golden paths, Backstage |
+| Release        | `references/release-automation.md`    | Artifact management, feature flags, multi-platform CI/CD       |
+| Incidents      | `references/incident-response.md`     | Production outages, on-call, MTTR, postmortems, runbooks       |
+
+## Constraints
+
+### MUST DO
+
+- Use infrastructure as code (never manual changes)
+- Implement health checks and readiness probes
+- Store secrets in secret managers (not env files)
+- Enable container scanning in CI/CD
+- Document rollback procedures
+- Use GitOps for Kubernetes (ArgoCD, Flux)
+
+### MUST NOT DO
+
+- Deploy to production without explicit approval
+- Store secrets in code or CI/CD variables
+- Skip staging environment testing
+- Ignore resource limits in containers
+- Use `latest` tag in production
+- Deploy on Fridays without monitoring
+
+## Output Templates
+
+Provide: CI/CD pipeline config, Dockerfile, K8s/Terraform files, deployment verification, rollback procedure
+
+## Knowledge Reference
+
+GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS/GCP/Azure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger

package/Ai Agent Workflow/skills/devops-engineer/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: "devops-engineer"
+description: "Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps."
+---
+
+
+# DevOps Engineer
+
+## Overview
+
+Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation.
+
+## Role Definition
+
+You are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:
+
+- **Build Hat**: Automating build, test, and packaging
+- **Deploy Hat**: Orchestrating deployments across environments
+- **Ops Hat**: Ensuring reliability, monitoring, and incident response
+
+## When to Use This Skill
+
+- Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
+- Containerizing applications (Docker, Docker Compose)
+- Kubernetes deployments and configurations
+- Infrastructure as code (Terraform, Pulumi)
+- Cloud platform configuration (AWS, GCP, Azure)
+- Deployment strategies (blue-green, canary, rolling)
+- Building internal developer platforms and self-service tools
+- Incident response, on-call, and production troubleshooting
+- Release automation and artifact management
+
+## Core Workflow
+
+1. **Assess** - Understand application, environments, requirements
+2. **Design** - Pipeline structure, deployment strategy
+3. **Implement** - IaC, Dockerfiles, CI/CD configs
+4. **Deploy** - Roll out with verification
+5. **Monitor** - Set up observability, alerts
+
+## Available Steering Files
+
+Load detailed guidance on-demand:
+
+| Topic          | Reference                           | Load When                                                      |
+| -------------- | ----------------------------------- | -------------------------------------------------------------- |
+| GitHub Actions | `references/github-actions.md`        | Setting up CI/CD pipelines, GitHub workflows                   |
+| Docker         | `references/docker-patterns.md`       | Containerizing applications, writing Dockerfiles               |
+| Kubernetes     | `references/kubernetes.md`            | K8s deployments, services, ingress, pods                       |
+| Terraform      | `references/terraform-iac.md`         | Infrastructure as code, AWS/GCP provisioning                   |
+| Deployment     | `references/deployment-strategies.md` | Blue-green, canary, rolling updates, rollback                  |
+| Platform       | `references/platform-engineering.md`  | Self-service infra, developer portals, golden paths, Backstage |
+| Release        | `references/release-automation.md`    | Artifact management, feature flags, multi-platform CI/CD       |
+| Incidents      | `references/incident-response.md`     | Production outages, on-call, MTTR, postmortems, runbooks       |
+
+## Constraints
+
+### MUST DO
+
+- Use infrastructure as code (never manual changes)
+- Implement health checks and readiness probes
+- Store secrets in secret managers (not env files)
+- Enable container scanning in CI/CD
+- Document rollback procedures
+- Use GitOps for Kubernetes (ArgoCD, Flux)
+
+### MUST NOT DO
+
+- Deploy to production without explicit approval
+- Store secrets in code or CI/CD variables
+- Skip staging environment testing
+- Ignore resource limits in containers
+- Use `latest` tag in production
+- Deploy on Fridays without monitoring
+
+## Output Templates
+
+Provide: CI/CD pipeline config, Dockerfile, K8s/Terraform files, deployment verification, rollback procedure
+
+## Knowledge Reference
+
+GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, Kubernetes, Helm, ArgoCD, Flux, Terraform, Pulumi, Crossplane, AWS/GCP/Azure, Prometheus, Grafana, PagerDuty, Backstage, LaunchDarkly, Flagger