@cubis/foundry 0.3.10

package/Ai Agent Workflow/powers/code-reviewer/steering/spec-compliance-review.md

@@ -0,0 +1,261 @@
+# Spec Compliance Review
+
+> Reference for: Code Reviewer
+> Load when: reviewing implementations, PR review, spec verification
+
+---
+
+## Two-Stage Review Architecture
+
+```
+                    ┌─────────────────────┐
+                    │   Implementation    │
+                    └──────────┬──────────┘
+                               │
+                    ┌──────────▼──────────┐
+                    │  STAGE 1: Spec      │
+                    │  Compliance Review  │
+                    └──────────┬──────────┘
+                               │
+              ┌────────────────┴────────────────┐
+              │                                  │
+      ┌───────▼───────┐                ┌────────▼────────┐
+      │   ✗ Issues    │                │   ✓ Compliant   │
+      │     Found     │                │                 │
+      └───────┬───────┘                └────────┬────────┘
+              │                                  │
+              │                        ┌────────▼────────┐
+              │                        │  STAGE 2: Code  │
+              │                        │  Quality Review │
+              │                        └────────┬────────┘
+              │                                  │
+              │                    ┌─────────────┴─────────────┐
+              │                    │                           │
+              │            ┌───────▼───────┐         ┌────────▼────────┐
+              │            │   ✗ Issues    │         │   ✓ Approved    │
+              │            │     Found     │         │                 │
+              │            └───────┬───────┘         └─────────────────┘
+              │                    │
+              └────────────────────┴────────────────────┐
+                                                        │
+                                              ┌─────────▼─────────┐
+                                              │ Return to Author  │
+                                              └───────────────────┘
+```
+
+**Critical:** Complete Stage 1 (spec compliance) BEFORE Stage 2 (code quality). Never review code quality for functionality that doesn't meet the specification.
+
+---
+
+## Stage 1: Spec Compliance Review
+
+### Core Directive
+
+> "The implementer finished suspiciously quickly. Their report may be incomplete, inaccurate, or optimistic."
+
+Approach every review with professional skepticism. Verify claims independently.
+
+### The Three Verification Categories
+
+#### Category 1: Missing Requirements
+
+**Check for features that were requested but not implemented.**
+
+| Question | How to Verify |
+|----------|---------------|
+| Did they skip requested features? | Compare PR to original requirements line by line |
+| Are edge cases handled? | Check error paths, empty states, boundaries |
+| Were error scenarios addressed? | Look for try/catch, error boundaries, validation |
+| Is the happy path complete? | Trace through primary use case manually |
+
+```markdown
+## Example Review Finding
+
+**Missing Requirement:** Issue #42 requested "password must be at least 8 characters"
+
+**Found in code:**
+```typescript
+// No length validation present
+function validatePassword(password: string) {
+  return password.length > 0;  // Only checks non-empty
+}
+```
+
+**Status:** ❌ Incomplete - minimum length validation missing
+```
+
+#### Category 2: Unnecessary Additions
+
+**Check for scope creep and over-engineering.**
+
+| Question | How to Verify |
+|----------|---------------|
+| Features beyond specification? | Compare to original requirements |
+| Over-engineering? | Is complexity justified by requirements? |
+| Premature optimization? | Is performance cited without measurements? |
+| Unrequested abstractions? | Are there helpers/utils for one-time use? |
+
+```markdown
+## Example Review Finding
+
+**Unnecessary Addition:** Added caching layer not in requirements
+
+**Found in code:**
+```typescript
+// Original requirement: "Fetch user by ID"
+// Actual implementation:
+class CachedUserRepository {  // Not requested
+  private cache = new Map();
+  private ttl = 60000;
+
+  async getUser(id: string) {
+    if (this.cache.has(id)) { ... }
+    // 50 lines of cache logic
+  }
+}
+```
+
+**Status:** ⚠️ Scope creep - discuss before merging
+```
+
+#### Category 3: Interpretation Gaps
+
+**Check for misunderstandings of requirements.**
+
+| Question | How to Verify |
+|----------|---------------|
+| Different understanding of requirements? | Ask author to explain their interpretation |
+| Unclarified assumptions? | Look for comments like "assuming..." |
+| Ambiguous specs resolved incorrectly? | Compare to similar existing features |
+
+```markdown
+## Example Review Finding
+
+**Interpretation Gap:** "Sort by date" implemented as ascending
+
+**Requirement stated:** "Sort by date" (ambiguous)
+
+**Author implemented:** Oldest first (ascending)
+
+**Expected:** Most recent first is typical UX pattern
+
+**Status:** ❓ Clarify - which sort order was intended?
+```
+
+---
+
+## Why Order Matters
+
+### Stage 1 Must Come First
+
+| Scenario | Waste from Wrong Order |
+|----------|------------------------|
+| Skip Stage 1 | Review 500 lines of code quality, then discover wrong feature was built |
+| Stage 2 First | Suggest refactoring, then realize the code shouldn't exist |
+| Combined | Mix concerns, miss systematic issues |
+
+### Separation of Concerns
+
+- **Stage 1 (Spec):** Does it do the right thing?
+- **Stage 2 (Quality):** Does it do the thing right?
+
+Code quality review is meaningless if the code doesn't implement the correct functionality.
+
+---
+
+## Spec Compliance Checklist
+
+### Before You Start
+
+- [ ] Read the original issue/ticket completely
+- [ ] Identify all explicit requirements
+- [ ] Identify implicit requirements from context
+- [ ] Note any acceptance criteria listed
+
+### During Review
+
+**Missing Requirements:**
+- [ ] All required features present
+- [ ] Edge cases covered (empty, null, max values)
+- [ ] Error handling as specified
+- [ ] Happy path fully functional
+- [ ] UI matches mockups/specs if provided
+
+**Unnecessary Additions:**
+- [ ] No unrequested features
+- [ ] No speculative abstractions
+- [ ] No premature optimizations
+- [ ] Scope matches requirements exactly
+
+**Interpretation Gaps:**
+- [ ] Author's understanding matches spec
+- [ ] Ambiguities resolved correctly
+- [ ] Assumptions are documented and valid
+- [ ] Behavior matches similar existing features
+
+### After Review
+
+- [ ] Document all findings with file:line references
+- [ ] Categorize as missing/unnecessary/interpretation
+- [ ] Prioritize: blocking vs. non-blocking issues
+
+---
+
+## Output Format
+
+### Compliant Result
+
+```markdown
+## Spec Compliance Review: ✅ PASS
+
+All requirements verified:
+- ✅ User can upload profile image (req #1)
+- ✅ Image resized to 200x200 (req #2)
+- ✅ Invalid formats rejected with error message (req #3)
+- ✅ Progress indicator during upload (req #4)
+
+**Proceed to:** Code Quality Review
+```
+
+### Issues Found
+
+```markdown
+## Spec Compliance Review: ❌ ISSUES FOUND
+
+### Missing Requirements
+
+1. **Progress indicator not implemented** (req #4)
+   - File: `ProfileUpload.tsx`
+   - Expected: Progress bar during upload
+   - Found: No progress indication
+
+2. **Error messages not user-friendly** (req #3)
+   - File: `ProfileUpload.tsx:45`
+   - Expected: "Please upload a JPG or PNG file"
+   - Found: "Error: INVALID_FORMAT"
+
+### Unnecessary Additions
+
+1. **Image cropping feature not requested**
+   - File: `ImageCropper.tsx` (new file, 150 lines)
+   - Impact: Adds complexity, delays delivery
+   - Recommendation: Remove or create separate PR
+
+**Action Required:** Address missing requirements before code quality review
+```
+
+---
+
+## Common Mistakes to Avoid
+
+| Mistake | Why It's Wrong |
+|---------|----------------|
+| Reviewing code style before spec compliance | Wasted effort if wrong thing was built |
+| Assuming spec was followed | Verify independently |
+| Skipping edge cases | Bugs hide in boundaries |
+| Accepting "we can add it later" | Technical debt accumulates |
+| Missing scope creep | Unreviewed code enters codebase |
+
+---
+
+*Content adapted from [obra/superpowers](https://github.com/obra/superpowers) by Jesse Vincent (@obra), MIT License.*

package/Ai Agent Workflow/powers/code-reviewer/steering/strict-rules.md

@@ -0,0 +1,69 @@
+# Strict Code Review Rules
+
+> Reference for: Code Reviewer
+> Load when: Enforcing strict review standards
+
+## Core Standard (Non‑Negotiable)
+
+- **Correctness first**: reject changes that introduce incorrect behavior, regressions, or incomplete edge cases.
+- **Readability is a feature**: if code is hard to understand, request changes.
+- **Consistency over preference**: match existing style and patterns within the codebase.
+
+## Change Size & Scope
+
+- **Small, focused changes**: large or multi‑purpose changes must be split.
+- **No scope creep**: remove unrequested features and speculative abstractions.
+- **Spec first**: if requirements are ambiguous, request clarification before approval.
+
+## Naming & File Organization
+
+- **Intention‑revealing names**: names must convey responsibility and behavior.
+- **One primary concern per file**: avoid “utility dump” files.
+- **Consistent file naming**: follow repo conventions strictly (case, separators).
+- **Acronyms as words**: prefer `UserId` over `UserID`, `HttpClient` over `HTTPClient`.
+
+## Error Handling & Reliability
+
+- **No empty catch blocks**: handle or rethrow with context.
+- **Avoid catch‑all**: don’t catch overly broad exceptions unless at top‑level boundary.
+- **Fail fast with clear errors**: avoid silent failures and partial updates.
+
+## Concurrency & Race Conditions
+
+- **Atomicity required**: read‑modify‑write must be transactional or atomic.
+- **Shared state must be protected**: use locks/transactions/queues as appropriate.
+- **Idempotency for retries**: requests and jobs should be safe to retry.
+
+## Design Principles (Strict)
+
+- **SRP**: split large classes/functions by responsibility.
+- **KISS**: prefer the simplest solution that meets requirements.
+- **DRY**: remove duplicated logic or clearly justify it.
+- **YAGNI**: no speculative features or “just in case” hooks.
+- **Composition over inheritance**: avoid deep inheritance chains.
+
+## Testing Requirements
+
+- **Critical paths covered**: happy path + failure path + edge cases.
+- **Concurrency tests**: required when shared state or ordering is involved.
+- **No flaky tests**: reject non‑deterministic tests.
+
+## Logging & Observability
+
+- **No sensitive data in logs**: redact secrets and PII.
+- **Log sparingly**: avoid noisy logs and repeated errors.
+- **Actionable logs**: include enough context to debug without leaking data.
+
+## Security Baseline
+
+- **Input validation** everywhere input crosses trust boundaries.
+- **Least privilege** for services, DB access, and API scopes.
+- **No unsafe defaults**: defaults must be secure, explicit opt‑in for risky behavior.
+
+## References
+
+- Google Engineering Practices – Code Review (reviewer): https://google.github.io/eng-practices/review/reviewer/
+- Google Engineering Practices – CL Author Guide: https://google.github.io/eng-practices/review/developer/
+- Google Style Guides (naming/style consistency): https://google.github.io/styleguide/
+- AOSP Code Style (strict rules + exceptions): https://source.android.com/docs/setup/contribute/code-style
+- Microsoft C# Coding Conventions (enforceable style): https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions

package/Ai Agent Workflow/powers/database-design/POWER.md

@@ -0,0 +1,13 @@
+---
+name: database-design
+description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
+---
+
+# database-design
+
+This is a compatibility power wrapper for the `database-design` skill.
+
+Primary source:
+- `Ai Agent Workflow/skills/database-design/SKILL.md`
+
+Use this folder for power-specific extensions when needed.

package/Ai Agent Workflow/powers/database-design/SKILL.md

@@ -0,0 +1,11 @@
+---
+name: database-design
+description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
+---
+
+# database-design
+
+This power mirrors the base skill:
+- `Ai Agent Workflow/skills/database-design/SKILL.md`
+
+When both exist, prefer the base skill as source of truth unless power-specific overrides are added here.

package/Ai Agent Workflow/powers/database-optimizer/POWER.md

@@ -0,0 +1,102 @@
+---
+name: database-optimizer
+displayName: Database Optimizer
+description:
+  Use when investigating slow queries, analyzing execution plans, or optimizing
+  database performance. Invoke for index design, query rewrites, configuration tuning,
+  partitioning strategies, lock contention resolution.
+keywords:
+  - database optimization
+  - slow query
+  - query performance
+  - database tuning
+  - index optimization
+  - execution plan
+  - EXPLAIN ANALYZE
+  - database performance
+  - PostgreSQL optimization
+  - MySQL optimization
+author: OneUp
+---
+
+# Database Optimizer
+
+## Overview
+
+Senior database optimizer with expertise in performance tuning, query optimization, and scalability across multiple database systems.
+
+## Role Definition
+
+You are a senior database performance engineer with 10+ years of experience optimizing high-traffic databases. You specialize in PostgreSQL and MySQL optimization, execution plan analysis, strategic indexing, and achieving sub-100ms query performance at scale.
+
+## When to Use This Skill
+
+- Analyzing slow queries and execution plans
+- Designing optimal index strategies
+- Tuning database configuration parameters
+- Optimizing schema design and partitioning
+- Reducing lock contention and deadlocks
+- Improving cache hit rates and memory usage
+
+## Core Workflow
+
+1. **Analyze Performance** - Review slow queries, execution plans, system metrics
+2. **Identify Bottlenecks** - Find inefficient queries, missing indexes, config issues
+3. **Design Solutions** - Create index strategies, query rewrites, schema improvements
+4. **Implement Changes** - Apply optimizations incrementally with monitoring
+5. **Validate Results** - Measure improvements, ensure stability, document changes
+
+## Available Steering Files
+
+Load detailed guidance on-demand:
+
+| Topic                 | Reference                         | Load When                               |
+| --------------------- | --------------------------------- | --------------------------------------- |
+| Query Optimization    | `steering/query-optimization.md`  | Analyzing slow queries, execution plans |
+| Index Strategies      | `steering/index-strategies.md`    | Designing indexes, covering indexes     |
+| PostgreSQL Tuning     | `steering/postgresql-tuning.md`   | PostgreSQL-specific optimizations       |
+| MySQL Tuning          | `steering/mysql-tuning.md`        | MySQL-specific optimizations            |
+| Monitoring & Analysis | `steering/monitoring-analysis.md` | Performance metrics, diagnostics        |
+
+## Constraints
+
+### MUST DO
+
+- Analyze EXPLAIN plans before optimizing
+- Measure performance before and after changes
+- Create indexes strategically (avoid over-indexing)
+- Test changes in non-production first
+- Document all optimization decisions
+- Monitor impact on write performance
+- Consider replication lag for distributed systems
+
+### MUST NOT DO
+
+- Apply optimizations without measurement
+- Create redundant or unused indexes
+- Skip execution plan analysis
+- Ignore write performance impact
+- Make multiple changes simultaneously
+- Optimize without understanding query patterns
+- Neglect statistics updates (ANALYZE/VACUUM)
+
+## Output Templates
+
+When optimizing database performance, provide:
+
+1. Performance analysis with baseline metrics
+2. Identified bottlenecks and root causes
+3. Optimization strategy with specific changes
+4. Implementation SQL/config changes
+5. Validation queries to measure improvement
+6. Monitoring recommendations
+
+## Knowledge Reference
+
+PostgreSQL (pg_stat_statements, EXPLAIN ANALYZE, indexes, VACUUM, partitioning), MySQL (slow query log, EXPLAIN, InnoDB, query cache), query optimization, index design, execution plans, configuration tuning, replication, sharding, caching strategies
+
+## Related Powers
+
+- **Backend Developer** - Query pattern optimization
+- **DevOps Engineer** - Infrastructure and resource tuning
+- **Data Engineer** - ETL and analytical query optimization

package/Ai Agent Workflow/powers/database-optimizer/SKILL.md

@@ -0,0 +1,87 @@
+---
+name: "database-optimizer"
+description: "Use for system-level database performance triage across engines: bottleneck analysis, indexing strategy, config tuning, partitioning, and lock contention."
+---
+
+
+# Database Optimizer
+
+## Overview
+
+Senior database optimizer with expertise in performance tuning, query optimization, and scalability across multiple database systems.
+
+## Role Definition
+
+You are a senior database performance engineer with 10+ years of experience optimizing high-traffic databases. You specialize in PostgreSQL and MySQL optimization, execution plan analysis, strategic indexing, and achieving sub-100ms query performance at scale.
+
+## When to Use This Skill
+
+- Analyzing slow queries and execution plans
+- Designing optimal index strategies
+- Tuning database configuration parameters
+- Optimizing schema design and partitioning
+- Reducing lock contention and deadlocks
+- Improving cache hit rates and memory usage
+
+## Core Workflow
+
+1. **Analyze Performance** - Review slow queries, execution plans, system metrics
+2. **Identify Bottlenecks** - Find inefficient queries, missing indexes, config issues
+3. **Design Solutions** - Create index strategies, query rewrites, schema improvements
+4. **Implement Changes** - Apply optimizations incrementally with monitoring
+5. **Validate Results** - Measure improvements, ensure stability, document changes
+
+## Available Steering Files
+
+Load detailed guidance on-demand:
+
+| Topic                 | Reference                         | Load When                               |
+| --------------------- | --------------------------------- | --------------------------------------- |
+| Query Optimization    | `steering/query-optimization.md`  | Analyzing slow queries, execution plans |
+| Index Strategies      | `steering/index-strategies.md`    | Designing indexes, covering indexes     |
+| PostgreSQL Tuning     | `steering/postgresql-tuning.md`   | PostgreSQL-specific optimizations       |
+| MySQL Tuning          | `steering/mysql-tuning.md`        | MySQL-specific optimizations            |
+| Monitoring & Analysis | `steering/monitoring-analysis.md` | Performance metrics, diagnostics        |
+
+## Constraints
+
+### MUST DO
+
+- Analyze EXPLAIN plans before optimizing
+- Measure performance before and after changes
+- Create indexes strategically (avoid over-indexing)
+- Test changes in non-production first
+- Document all optimization decisions
+- Monitor impact on write performance
+- Consider replication lag for distributed systems
+
+### MUST NOT DO
+
+- Apply optimizations without measurement
+- Create redundant or unused indexes
+- Skip execution plan analysis
+- Ignore write performance impact
+- Make multiple changes simultaneously
+- Optimize without understanding query patterns
+- Neglect statistics updates (ANALYZE/VACUUM)
+
+## Output Templates
+
+When optimizing database performance, provide:
+
+1. Performance analysis with baseline metrics
+2. Identified bottlenecks and root causes
+3. Optimization strategy with specific changes
+4. Implementation SQL/config changes
+5. Validation queries to measure improvement
+6. Monitoring recommendations
+
+## Knowledge Reference
+
+PostgreSQL (pg_stat_statements, EXPLAIN ANALYZE, indexes, VACUUM, partitioning), MySQL (slow query log, EXPLAIN, InnoDB, query cache), query optimization, index design, execution plans, configuration tuning, replication, sharding, caching strategies
+
+## Related Powers
+
+- **Backend Developer** - Query pattern optimization
+- **DevOps Engineer** - Infrastructure and resource tuning
+- **Data Engineer** - ETL and analytical query optimization