@cubis/foundry 0.3.11 → 0.3.12

package/Ai Agent Workflow/powers/tdd-workflow/POWER.md

@@ -1,13 +1,152 @@
+````markdown
 ---
+inclusion: manual
 name: tdd-workflow
 description: Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
 
-# tdd-workflow
+# TDD Workflow
 
-This is a compatibility power wrapper for the `tdd-workflow` skill.
+> Write tests first, code second.
 
-Primary source:
-- `Ai Agent Workflow/skills/tdd-workflow/SKILL.md`
+---
+
+## 1. The TDD Cycle
+
+```
+🔴 RED → Write failing test
+    ↓
+🟢 GREEN → Write minimal code to pass
+    ↓
+🔵 REFACTOR → Improve code quality
+    ↓
+   Repeat...
+```
+
+---
+
+## 2. The Three Laws of TDD
+
+1. Write production code only to make a failing test pass
+2. Write only enough test to demonstrate failure
+3. Write only enough code to make the test pass
+
+---
+
+## 3. RED Phase Principles
+
+### What to Write
+
+| Focus | Example |
+|-------|---------|
+| Behavior | "should add two numbers" |
+| Edge cases | "should handle empty input" |
+| Error states | "should throw for invalid data" |
+
+### RED Phase Rules
+
+- Test must fail first
+- Test name describes expected behavior
+- One assertion per test (ideally)
+
+---
+
+## 4. GREEN Phase Principles
+
+### Minimum Code
+
+| Principle | Meaning |
+|-----------|---------|
+| **YAGNI** | You Aren't Gonna Need It |
+| **Simplest thing** | Write the minimum to pass |
+| **No optimization** | Just make it work |
+
+### GREEN Phase Rules
+
+- Don't write unneeded code
+- Don't optimize yet
+- Pass the test, nothing more
+
+---
+
+## 5. REFACTOR Phase Principles
+
+### What to Improve
+
+| Area | Action |
+|------|--------|
+| Duplication | Extract common code |
+| Naming | Make intent clear |
+| Structure | Improve organization |
+| Complexity | Simplify logic |
+
+### REFACTOR Rules
+
+- All tests must stay green
+- Small incremental changes
+- Commit after each refactor
+
+---
+
+## 6. AAA Pattern
+
+Every test follows:
+
+| Step | Purpose |
+|------|---------|
+| **Arrange** | Set up test data |
+| **Act** | Execute code under test |
+| **Assert** | Verify expected outcome |
+
+---
+
+## 7. When to Use TDD
+
+| Scenario | TDD Value |
+|----------|-----------|
+| New feature | High |
+| Bug fix | High (write test first) |
+| Complex logic | High |
+| Exploratory | Low (spike, then TDD) |
+| UI layout | Low |
+
+---
+
+## 8. Test Prioritization
+
+| Priority | Test Type |
+|----------|-----------|
+| 1 | Happy path |
+| 2 | Error cases |
+| 3 | Edge cases |
+| 4 | Performance |
+
+---
+
+## 9. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Skip the RED phase | Watch test fail first |
+| Write tests after | Write tests before |
+| Over-engineer initial | Keep it simple |
+| Multiple asserts | One behavior per test |
+| Test implementation | Test behavior |
+
+---
+
+## 10. AI-Augmented TDD
+
+### Multi-Agent Pattern
+
+| Agent | Role |
+|-------|------|
+| Agent A | Write failing tests (RED) |
+| Agent B | Implement to pass (GREEN) |
+| Agent C | Optimize (REFACTOR) |
+
+---
 
-Use this folder for power-specific extensions when needed.
+> **Remember:** The test is the specification. If you can't write a test, you don't understand the requirement.
+````

package/Ai Agent Workflow/powers/tdd-workflow/SKILL.md

@@ -1,11 +1,149 @@
 ---
 name: tdd-workflow
 description: Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
 
-# tdd-workflow
+# TDD Workflow
 
-This power mirrors the base skill:
-- `Ai Agent Workflow/skills/tdd-workflow/SKILL.md`
+> Write tests first, code second.
 
-When both exist, prefer the base skill as source of truth unless power-specific overrides are added here.
+---
+
+## 1. The TDD Cycle
+
+```
+🔴 RED → Write failing test
+    ↓
+🟢 GREEN → Write minimal code to pass
+    ↓
+🔵 REFACTOR → Improve code quality
+    ↓
+   Repeat...
+```
+
+---
+
+## 2. The Three Laws of TDD
+
+1. Write production code only to make a failing test pass
+2. Write only enough test to demonstrate failure
+3. Write only enough code to make the test pass
+
+---
+
+## 3. RED Phase Principles
+
+### What to Write
+
+| Focus | Example |
+|-------|---------|
+| Behavior | "should add two numbers" |
+| Edge cases | "should handle empty input" |
+| Error states | "should throw for invalid data" |
+
+### RED Phase Rules
+
+- Test must fail first
+- Test name describes expected behavior
+- One assertion per test (ideally)
+
+---
+
+## 4. GREEN Phase Principles
+
+### Minimum Code
+
+| Principle | Meaning |
+|-----------|---------|
+| **YAGNI** | You Aren't Gonna Need It |
+| **Simplest thing** | Write the minimum to pass |
+| **No optimization** | Just make it work |
+
+### GREEN Phase Rules
+
+- Don't write unneeded code
+- Don't optimize yet
+- Pass the test, nothing more
+
+---
+
+## 5. REFACTOR Phase Principles
+
+### What to Improve
+
+| Area | Action |
+|------|--------|
+| Duplication | Extract common code |
+| Naming | Make intent clear |
+| Structure | Improve organization |
+| Complexity | Simplify logic |
+
+### REFACTOR Rules
+
+- All tests must stay green
+- Small incremental changes
+- Commit after each refactor
+
+---
+
+## 6. AAA Pattern
+
+Every test follows:
+
+| Step | Purpose |
+|------|---------|
+| **Arrange** | Set up test data |
+| **Act** | Execute code under test |
+| **Assert** | Verify expected outcome |
+
+---
+
+## 7. When to Use TDD
+
+| Scenario | TDD Value |
+|----------|-----------|
+| New feature | High |
+| Bug fix | High (write test first) |
+| Complex logic | High |
+| Exploratory | Low (spike, then TDD) |
+| UI layout | Low |
+
+---
+
+## 8. Test Prioritization
+
+| Priority | Test Type |
+|----------|-----------|
+| 1 | Happy path |
+| 2 | Error cases |
+| 3 | Edge cases |
+| 4 | Performance |
+
+---
+
+## 9. Anti-Patterns
+
+| ❌ Don't | ✅ Do |
+|----------|-------|
+| Skip the RED phase | Watch test fail first |
+| Write tests after | Write tests before |
+| Over-engineer initial | Keep it simple |
+| Multiple asserts | One behavior per test |
+| Test implementation | Test behavior |
+
+---
+
+## 10. AI-Augmented TDD
+
+### Multi-Agent Pattern
+
+| Agent | Role |
+|-------|------|
+| Agent A | Write failing tests (RED) |
+| Agent B | Implement to pass (GREEN) |
+| Agent C | Optimize (REFACTOR) |
+
+---
+
+> **Remember:** The test is the specification. If you can't write a test, you don't understand the requirement.

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

@@ -0,0 +1,89 @@
+````markdown
+---
+inclusion: manual
+name: terraform-engineer
+description: Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development, state management, provider configuration, multi-environment workflows, infrastructure testing.
+license: MIT
+metadata:
+  author: https://github.com/Jeffallan
+  version: "1.0.0"
+  domain: infrastructure
+  triggers: Terraform, infrastructure as code, IaC, terraform module, terraform state, AWS provider, Azure provider, GCP provider, terraform plan, terraform apply
+  role: specialist
+  scope: implementation
+  output-format: code
+  related-skills: cloud-architect, devops-engineer, kubernetes-specialist
+---
+
+# Terraform Engineer
+
+Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.
+
+## Role Definition
+
+You are a senior DevOps engineer with 10+ years of infrastructure automation experience. You specialize in Terraform 1.5+ with multi-cloud providers, focusing on reusable modules, secure state management, and enterprise compliance. You build scalable, maintainable infrastructure code.
+
+## When to Use This Skill
+
+- Building Terraform modules for reusability
+- Implementing remote state with locking
+- Configuring AWS, Azure, or GCP providers
+- Setting up multi-environment workflows
+- Implementing infrastructure testing
+- Migrating to Terraform or refactoring IaC
+
+## Core Workflow
+
+1. **Analyze infrastructure** - Review requirements, existing code, cloud platforms
+2. **Design modules** - Create composable, validated modules with clear interfaces
+3. **Implement state** - Configure remote backends with locking and encryption
+4. **Secure infrastructure** - Apply security policies, least privilege, encryption
+5. **Test and validate** - Run terraform plan, policy checks, automated tests
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Modules | `references/module-patterns.md` | Creating modules, inputs/outputs, versioning |
+| State | `references/state-management.md` | Remote backends, locking, workspaces, migrations |
+| Providers | `references/providers.md` | AWS/Azure/GCP configuration, authentication |
+| Testing | `references/testing.md` | terraform plan, terratest, policy as code |
+| Best Practices | `references/best-practices.md` | DRY patterns, naming, security, cost tracking |
+
+## Constraints
+
+### MUST DO
+- Use semantic versioning for modules
+- Enable remote state with locking
+- Validate inputs with validation blocks
+- Use consistent naming conventions
+- Tag all resources for cost tracking
+- Document module interfaces
+- Pin provider versions
+- Run terraform fmt and validate
+
+### MUST NOT DO
+- Store secrets in plain text
+- Use local state for production
+- Skip state locking
+- Hardcode environment-specific values
+- Mix provider versions without constraints
+- Create circular module dependencies
+- Skip input validation
+- Commit .terraform directories
+
+## Output Templates
+
+When implementing Terraform solutions, provide:
+1. Module structure (main.tf, variables.tf, outputs.tf)
+2. Backend configuration for state
+3. Provider configuration with versions
+4. Example usage with tfvars
+5. Brief explanation of design decisions
+
+## Knowledge Reference
+
+Terraform 1.5+, HCL syntax, AWS/Azure/GCP providers, remote backends (S3, Azure Blob, GCS), state locking (DynamoDB, Azure Blob leases), workspaces, modules, dynamic blocks, for_each/count, terraform plan/apply, terratest, tflint, Open Policy Agent, cost estimation
+````

package/Ai Agent Workflow/powers/terraform-engineer/SKILL.md

@@ -44,11 +44,11 @@ Load detailed guidance based on context:
 
 | Topic | Reference | Load When |
 |-------|-----------|-----------|
-| Modules | `steering/module-patterns.md` | Creating modules, inputs/outputs, versioning |
-| State | `steering/state-management.md` | Remote backends, locking, workspaces, migrations |
-| Providers | `steering/providers.md` | AWS/Azure/GCP configuration, authentication |
-| Testing | `steering/testing.md` | terraform plan, terratest, policy as code |
-| Best Practices | `steering/best-practices.md` | DRY patterns, naming, security, cost tracking |
+| Modules | `references/module-patterns.md` | Creating modules, inputs/outputs, versioning |
+| State | `references/state-management.md` | Remote backends, locking, workspaces, migrations |
+| Providers | `references/providers.md` | AWS/Azure/GCP configuration, authentication |
+| Testing | `references/testing.md` | terraform plan, terratest, policy as code |
+| Best Practices | `references/best-practices.md` | DRY patterns, naming, security, cost tracking |
 
 ## Constraints
 

package/Ai Agent Workflow/powers/test-master/POWER.md

@@ -1,38 +1,11 @@
+````markdown
 ---
-name: test-master
-displayName: Test Master
-description:
-  Use when writing tests, creating test strategies, or building automation
-  frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance
-  testing, security testing.
-keywords:
-  - test
-  - testing
-  - QA
-  - unit test
-  - integration test
-  - E2E
-  - coverage
-  - performance test
-  - security test
-  - regression
-  - test strategy
-  - test automation
-  - test framework
-  - quality metrics
-  - defect
-  - exploratory
-  - usability
-  - accessibility
-  - localization
-  - manual testing
-  - shift-left
-  - quality gate
-  - flaky test
-  - test maintenance
-author: OneUp
+inclusion: manual
+name: "test-master"
+description: "Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing."
 ---
 
+
 # Test Master
 
 ## Overview
@@ -70,19 +43,19 @@ Load detailed guidance on-demand:
 
 | Topic          | Reference                           | Load When                                                        |
 | -------------- | ----------------------------------- | ---------------------------------------------------------------- |
-| Unit Testing   | `steering/unit-testing.md`          | Jest, Vitest, pytest patterns                                    |
-| Integration    | `steering/integration-testing.md`   | API testing, Supertest                                           |
-| E2E            | `steering/e2e-testing.md`           | E2E strategy, user flows                                         |
-| Performance    | `steering/performance-testing.md`   | k6, load testing                                                 |
-| Security       | `steering/security-testing.md`      | Security test checklist                                          |
-| Reports        | `steering/test-reports.md`          | Report templates, findings                                       |
-| QA Methodology | `steering/qa-methodology.md`        | Manual testing, quality advocacy, shift-left, continuous testing |
-| Automation     | `steering/automation-frameworks.md` | Framework patterns, scaling, maintenance, team enablement        |
+| Unit Testing   | `references/unit-testing.md`          | Jest, Vitest, pytest patterns                                    |
+| Integration    | `references/integration-testing.md`   | API testing, Supertest                                           |
+| E2E            | `references/e2e-testing.md`           | E2E strategy, user flows                                         |
+| Performance    | `references/performance-testing.md`   | k6, load testing                                                 |
+| Security       | `references/security-testing.md`      | Security test checklist                                          |
+| Reports        | `references/test-reports.md`          | Report templates, findings                                       |
+| QA Methodology | `references/qa-methodology.md`        | Manual testing, quality advocacy, shift-left, continuous testing |
+| Automation     | `references/automation-frameworks.md` | Framework patterns, scaling, maintenance, team enablement        |
 
 <!-- Rows below adapted from obra/superpowers by Jesse Vincent (@obra), MIT License -->
 
-| TDD Iron Laws | `steering/tdd-iron-laws.md` | TDD methodology, test-first development, red-green-refactor |
-| Testing Anti-Patterns | `steering/testing-anti-patterns.md` | Test review, mock issues, test quality problems |
+| TDD Iron Laws | `references/tdd-iron-laws.md` | TDD methodology, test-first development, red-green-refactor |
+| Testing Anti-Patterns | `references/testing-anti-patterns.md` | Test review, mock issues, test quality problems |
 
 ## Constraints
 
@@ -109,3 +82,4 @@ Jest, Vitest, pytest, React Testing Library, Supertest, Playwright, Cypress, k6,
 - **Fullstack Guardian** - Receives features for testing
 - **Playwright Expert** - E2E testing specifics
 - **DevOps Engineer** - CI/CD test integration
+````

package/Ai Agent Workflow/powers/test-master/SKILL.md

@@ -41,19 +41,19 @@ Load detailed guidance on-demand:
 
 | Topic          | Reference                           | Load When                                                        |
 | -------------- | ----------------------------------- | ---------------------------------------------------------------- |
-| Unit Testing   | `steering/unit-testing.md`          | Jest, Vitest, pytest patterns                                    |
-| Integration    | `steering/integration-testing.md`   | API testing, Supertest                                           |
-| E2E            | `steering/e2e-testing.md`           | E2E strategy, user flows                                         |
-| Performance    | `steering/performance-testing.md`   | k6, load testing                                                 |
-| Security       | `steering/security-testing.md`      | Security test checklist                                          |
-| Reports        | `steering/test-reports.md`          | Report templates, findings                                       |
-| QA Methodology | `steering/qa-methodology.md`        | Manual testing, quality advocacy, shift-left, continuous testing |
-| Automation     | `steering/automation-frameworks.md` | Framework patterns, scaling, maintenance, team enablement        |
+| Unit Testing   | `references/unit-testing.md`          | Jest, Vitest, pytest patterns                                    |
+| Integration    | `references/integration-testing.md`   | API testing, Supertest                                           |
+| E2E            | `references/e2e-testing.md`           | E2E strategy, user flows                                         |
+| Performance    | `references/performance-testing.md`   | k6, load testing                                                 |
+| Security       | `references/security-testing.md`      | Security test checklist                                          |
+| Reports        | `references/test-reports.md`          | Report templates, findings                                       |
+| QA Methodology | `references/qa-methodology.md`        | Manual testing, quality advocacy, shift-left, continuous testing |
+| Automation     | `references/automation-frameworks.md` | Framework patterns, scaling, maintenance, team enablement        |
 
 <!-- Rows below adapted from obra/superpowers by Jesse Vincent (@obra), MIT License -->
 
-| TDD Iron Laws | `steering/tdd-iron-laws.md` | TDD methodology, test-first development, red-green-refactor |
-| Testing Anti-Patterns | `steering/testing-anti-patterns.md` | Test review, mock issues, test quality problems |
+| TDD Iron Laws | `references/tdd-iron-laws.md` | TDD methodology, test-first development, red-green-refactor |
+| Testing Anti-Patterns | `references/testing-anti-patterns.md` | Test review, mock issues, test quality problems |
 
 ## Constraints