@cubis/foundry 0.3.31 → 0.3.33

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/deployment-procedures/SKILL.md

@@ -1,241 +1,21 @@
 ---
 name: deployment-procedures
-description: Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
-allowed-tools: Read, Glob, Grep, Bash
+description: "Compatibility alias skill. Deprecated: use devops-engineer."
+metadata:
+  deprecated: true
+  replaced_by: devops-engineer
+  removal_target: v0.6.0
 ---
 
 # Deployment Procedures
 
-> Deployment principles and decision-making for safe production releases.
-> **Learn to THINK, not memorize scripts.**
+## Compatibility Alias
 
----
-
-## ⚠️ How to Use This Skill
-
-This skill teaches **deployment principles**, not bash scripts to copy.
-
-- Every deployment is unique
-- Understand the WHY behind each step
-- Adapt procedures to your platform
-
----
-
-## 1. Platform Selection
-
-### Decision Tree
-
-```
-What are you deploying?
-│
-├── Static site / JAMstack
-│   └── Vercel, Netlify, Cloudflare Pages
-│
-├── Simple web app
-│   ├── Managed → Railway, Render, Fly.io
-│   └── Control → VPS + PM2/Docker
-│
-├── Microservices
-│   └── Container orchestration
-│
-└── Serverless
-    └── Edge functions, Lambda
-```
-
-### Each Platform Has Different Procedures
-
-| Platform | Deployment Method |
-|----------|------------------|
-| **Vercel/Netlify** | Git push, auto-deploy |
-| **Railway/Render** | Git push or CLI |
-| **VPS + PM2** | SSH + manual steps |
-| **Docker** | Image push + orchestration |
-| **Kubernetes** | kubectl apply |
-
----
-
-## 2. Pre-Deployment Principles
-
-### The 4 Verification Categories
-
-| Category | What to Check |
-|----------|--------------|
-| **Code Quality** | Tests passing, linting clean, reviewed |
-| **Build** | Production build works, no warnings |
-| **Environment** | Env vars set, secrets current |
-| **Safety** | Backup done, rollback plan ready |
-
-### Pre-Deployment Checklist
-
-- [ ] All tests passing
-- [ ] Code reviewed and approved
-- [ ] Production build successful
-- [ ] Environment variables verified
-- [ ] Database migrations ready (if any)
-- [ ] Rollback plan documented
-- [ ] Team notified
-- [ ] Monitoring ready
-
----
-
-## 3. Deployment Workflow Principles
-
-### The 5-Phase Process
-
-```
-1. PREPARE
-   └── Verify code, build, env vars
-
-2. BACKUP
-   └── Save current state before changing
-
-3. DEPLOY
-   └── Execute with monitoring open
-
-4. VERIFY
-   └── Health check, logs, key flows
-
-5. CONFIRM or ROLLBACK
-   └── All good? Confirm. Issues? Rollback.
-```
-
-### Phase Principles
-
-| Phase | Principle |
-|-------|-----------|
-| **Prepare** | Never deploy untested code |
-| **Backup** | Can't rollback without backup |
-| **Deploy** | Watch it happen, don't walk away |
-| **Verify** | Trust but verify |
-| **Confirm** | Have rollback trigger ready |
-
----
-
-## 4. Post-Deployment Verification
-
-### What to Verify
-
-| Check | Why |
-|-------|-----|
-| **Health endpoint** | Service is running |
-| **Error logs** | No new errors |
-| **Key user flows** | Critical features work |
-| **Performance** | Response times acceptable |
-
-### Verification Window
-
-- **First 5 minutes**: Active monitoring
-- **15 minutes**: Confirm stable
-- **1 hour**: Final verification
-- **Next day**: Review metrics
+This skill is deprecated and kept for backward compatibility.
 
----
-
-## 5. Rollback Principles
-
-### When to Rollback
-
-| Symptom | Action |
-|---------|--------|
-| Service down | Rollback immediately |
-| Critical errors | Rollback |
-| Performance >50% degraded | Consider rollback |
-| Minor issues | Fix forward if quick |
-
-### Rollback Strategy by Platform
-
-| Platform | Rollback Method |
-|----------|----------------|
-| **Vercel/Netlify** | Redeploy previous commit |
-| **Railway/Render** | Rollback in dashboard |
-| **VPS + PM2** | Restore backup, restart |
-| **Docker** | Previous image tag |
-| **K8s** | kubectl rollout undo |
-
-### Rollback Principles
-
-1. **Speed over perfection**: Rollback first, debug later
-2. **Don't compound errors**: One rollback, not multiple changes
-3. **Communicate**: Tell team what happened
-4. **Post-mortem**: Understand why after stable
-
----
-
-## 6. Zero-Downtime Deployment
-
-### Strategies
-
-| Strategy | How It Works |
-|----------|--------------|
-| **Rolling** | Replace instances one by one |
-| **Blue-Green** | Switch traffic between environments |
-| **Canary** | Gradual traffic shift |
-
-### Selection Principles
-
-| Scenario | Strategy |
-|----------|----------|
-| Standard release | Rolling |
-| High-risk change | Blue-green (easy rollback) |
-| Need validation | Canary (test with real traffic) |
-
----
-
-## 7. Emergency Procedures
+Use `devops-engineer` as the canonical skill.
 
-### Service Down Priority
-
-1. **Assess**: What's the symptom?
-2. **Quick fix**: Restart if unclear
-3. **Rollback**: If restart doesn't help
-4. **Investigate**: After stable
-
-### Investigation Order
-
-| Check | Common Issues |
-|-------|--------------|
-| **Logs** | Errors, exceptions |
-| **Resources** | Disk full, memory |
-| **Network** | DNS, firewall |
-| **Dependencies** | Database, APIs |
-
----
-
-## 8. Anti-Patterns
-
-| ❌ Don't | ✅ Do |
-|----------|-------|
-| Deploy on Friday | Deploy early in week |
-| Rush deployment | Follow the process |
-| Skip staging | Always test first |
-| Deploy without backup | Backup before deploy |
-| Walk away after deploy | Monitor for 15+ min |
-| Multiple changes at once | One change at a time |
-
----
-
-## 9. Decision Checklist
-
-Before deploying:
-
-- [ ] **Platform-appropriate procedure?**
-- [ ] **Backup strategy ready?**
-- [ ] **Rollback plan documented?**
-- [ ] **Monitoring configured?**
-- [ ] **Team notified?**
-- [ ] **Time to monitor after?**
-
----
-
-## 10. Best Practices
-
-1. **Small, frequent deploys** over big releases
-2. **Feature flags** for risky changes
-3. **Automate** repetitive steps
-4. **Document** every deployment
-5. **Review** what went wrong after issues
-6. **Test rollback** before you need it
-
----
+## Migration
 
-> **Remember:** Every deployment is a risk. Minimize risk through preparation, not speed.
+1. Replace direct references to `deployment-procedures` with `devops-engineer`.
+2. Apply the full workflow from `devops-engineer` for new work.

package/workflows/workflows/agent-environment-setup/platforms/cursor/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/workflows/workflows/agent-environment-setup/platforms/cursor/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/workflows/workflows/agent-environment-setup/platforms/cursor/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/workflows/workflows/agent-environment-setup/platforms/cursor/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/workflows/workflows/agent-environment-setup/platforms/cursor/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/workflows/workflows/agent-environment-setup/platforms/cursor/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,
+      ),
+    );
+  }
+}
+```