@cubis/foundry 0.3.10 → 0.3.12

package/Ai Agent Workflow/powers/deployment-procedures/SKILL.md

@@ -1,11 +1,241 @@
 ---
 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
 ---
 
-# deployment-procedures
+# Deployment Procedures
 
-This power mirrors the base skill:
-- `Ai Agent Workflow/skills/deployment-procedures/SKILL.md`
+> Deployment principles and decision-making for safe production releases.
+> **Learn to THINK, not memorize scripts.**
 
-When both exist, prefer the base skill as source of truth unless power-specific overrides are added here.
+---
+
+## ⚠️ 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
+
+---
+
+## 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
+
+### 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
+
+---
+
+> **Remember:** Every deployment is a risk. Minimize risk through preparation, not speed.

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

@@ -1,4 +1,6 @@
+````markdown
 ---
+inclusion: manual
 name: "design-system-builder"
 displayName: "Design System Builder"
 description: "Create and review design system components: API design, token usage, theming, variants, and documentation"
@@ -148,3 +150,4 @@ When creating/reviewing a component:
 
 - `one_component_skeleton` - Component template
 - `component_widget_test` - Widget test template
+````

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

@@ -1,26 +1,11 @@
+````markdown
 ---
-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
+inclusion: manual
+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
@@ -61,14 +46,14 @@ Load detailed guidance on-demand:
 
 | Topic          | Reference                           | Load When                                                      |
 | -------------- | ----------------------------------- | -------------------------------------------------------------- |
-| GitHub Actions | `steering/github-actions.md`        | Setting up CI/CD pipelines, GitHub workflows                   |
-| Docker         | `steering/docker-patterns.md`       | Containerizing applications, writing Dockerfiles               |
-| Kubernetes     | `steering/kubernetes.md`            | K8s deployments, services, ingress, pods                       |
-| Terraform      | `steering/terraform-iac.md`         | Infrastructure as code, AWS/GCP provisioning                   |
-| Deployment     | `steering/deployment-strategies.md` | Blue-green, canary, rolling updates, rollback                  |
-| Platform       | `steering/platform-engineering.md`  | Self-service infra, developer portals, golden paths, Backstage |
-| Release        | `steering/release-automation.md`    | Artifact management, feature flags, multi-platform CI/CD       |
-| Incidents      | `steering/incident-response.md`     | Production outages, on-call, MTTR, postmortems, runbooks       |
+| 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
 
@@ -97,3 +82,4 @@ Provide: CI/CD pipeline config, Dockerfile, K8s/Terraform files, deployment veri
 ## 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/powers/devops-engineer/SKILL.md

@@ -44,14 +44,14 @@ Load detailed guidance on-demand:
 
 | Topic          | Reference                           | Load When                                                      |
 | -------------- | ----------------------------------- | -------------------------------------------------------------- |
-| GitHub Actions | `steering/github-actions.md`        | Setting up CI/CD pipelines, GitHub workflows                   |
-| Docker         | `steering/docker-patterns.md`       | Containerizing applications, writing Dockerfiles               |
-| Kubernetes     | `steering/kubernetes.md`            | K8s deployments, services, ingress, pods                       |
-| Terraform      | `steering/terraform-iac.md`         | Infrastructure as code, AWS/GCP provisioning                   |
-| Deployment     | `steering/deployment-strategies.md` | Blue-green, canary, rolling updates, rollback                  |
-| Platform       | `steering/platform-engineering.md`  | Self-service infra, developer portals, golden paths, Backstage |
-| Release        | `steering/release-automation.md`    | Artifact management, feature flags, multi-platform CI/CD       |
-| Incidents      | `steering/incident-response.md`     | Production outages, on-call, MTTR, postmortems, runbooks       |
+| 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
 

package/Ai Agent Workflow/powers/documentation-templates/POWER.md

@@ -1,13 +1,197 @@
+````markdown
 ---
+inclusion: manual
 name: documentation-templates
 description: Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
+allowed-tools: Read, Glob, Grep
 ---
 
-# documentation-templates
+# Documentation Templates
 
-This is a compatibility power wrapper for the `documentation-templates` skill.
+> Templates and structure guidelines for common documentation types.
 
-Primary source:
-- `Ai Agent Workflow/skills/documentation-templates/SKILL.md`
+---
+
+## 1. README Structure
+
+### Essential Sections (Priority Order)
+
+| Section | Purpose |
+|---------|---------|
+| **Title + One-liner** | What is this? |
+| **Quick Start** | Running in <5 min |
+| **Features** | What can I do? |
+| **Configuration** | How to customize |
+| **API Reference** | Link to detailed docs |
+| **Contributing** | How to help |
+| **License** | Legal |
+
+### README Template
+
+```markdown
+# Project Name
+
+Brief one-line description.
+
+## Quick Start
+
+[Minimum steps to run]
+
+## Features
+
+- Feature 1
+- Feature 2
+
+## Configuration
+
+| Variable | Description | Default |
+|----------|-------------|---------|
+| PORT | Server port | 3000 |
+
+## Documentation
+
+- [API Reference](./docs/api.md)
+- [Architecture](./docs/architecture.md)
+
+## License
+
+MIT
+```
+
+---
+
+## 2. API Documentation Structure
+
+### Per-Endpoint Template
+
+```markdown
+## GET /users/:id
+
+Get a user by ID.
+
+**Parameters:**
+| Name | Type | Required | Description |
+|------|------|----------|-------------|
+| id | string | Yes | User ID |
+
+**Response:**
+- 200: User object
+- 404: User not found
+
+**Example:**
+[Request and response example]
+```
+
+---
+
+## 3. Code Comment Guidelines
+
+### JSDoc/TSDoc Template
+
+```typescript
+/**
+ * Brief description of what the function does.
+ * 
+ * @param paramName - Description of parameter
+ * @returns Description of return value
+ * @throws ErrorType - When this error occurs
+ * 
+ * @example
+ * const result = functionName(input);
+ */
+```
+
+### When to Comment
+
+| ✅ Comment | ❌ Don't Comment |
+|-----------|-----------------|
+| Why (business logic) | What (obvious) |
+| Complex algorithms | Every line |
+| Non-obvious behavior | Self-explanatory code |
+| API contracts | Implementation details |
+
+---
+
+## 4. Changelog Template (Keep a Changelog)
+
+```markdown
+# Changelog
+
+## [Unreleased]
+### Added
+- New feature
+
+## [1.0.0] - 2025-01-01
+### Added
+- Initial release
+### Changed
+- Updated dependency
+### Fixed
+- Bug fix
+```
+
+---
+
+## 5. Architecture Decision Record (ADR)
+
+```markdown
+# ADR-001: [Title]
+
+## Status
+Accepted / Deprecated / Superseded
+
+## Context
+Why are we making this decision?
+
+## Decision
+What did we decide?
+
+## Consequences
+What are the trade-offs?
+```
+
+---
+
+## 6. AI-Friendly Documentation (2025)
+
+### llms.txt Template
+
+For AI crawlers and agents:
+
+```markdown
+# Project Name
+> One-line objective.
+
+## Core Files
+- [src/index.ts]: Main entry
+- [src/api/]: API routes
+- [docs/]: Documentation
+
+## Key Concepts
+- Concept 1: Brief explanation
+- Concept 2: Brief explanation
+```
+
+### MCP-Ready Documentation
+
+For RAG indexing:
+- Clear H1-H3 hierarchy
+- JSON/YAML examples for data structures
+- Mermaid diagrams for flows
+- Self-contained sections
+
+---
+
+## 7. Structure Principles
+
+| Principle | Why |
+|-----------|-----|
+| **Scannable** | Headers, lists, tables |
+| **Examples first** | Show, don't just tell |
+| **Progressive detail** | Simple → Complex |
+| **Up to date** | Outdated = misleading |
+
+---
 
-Use this folder for power-specific extensions when needed.
+> **Remember:** Templates are starting points. Adapt to your project's needs.
+````