@cubis/foundry 0.3.62 → 0.3.64

package/workflows/skills/typescript-pro/SKILL.md

@@ -20,6 +20,12 @@ metadata:
 - Reducing type regressions in monorepos.
 - Preparing for upcoming TS 6/7 behavior shifts.
 
+## When not to use
+
+- Plain JavaScript-only work where runtime constraints matter more than type architecture.
+- Database-only tuning with no TypeScript code change.
+- Simple shell or config edits that do not benefit from TS guidance.
+
 ## Core workflow
 
 1. Confirm runtime and module target (Node, browser, edge).
@@ -44,6 +50,18 @@ metadata:
 - Use schema validation (zod/valibot/etc.) for external input.
 - Treat type errors as design feedback, not noise.
 
+## Debugging and observability
+
+- Reproduce type regressions with focused compiler output before widening changes.
+- Keep runtime validation and structured logging at untrusted boundaries.
+- Prefer targeted failing examples over broad `as`-based workarounds.
+
+## Performance and reliability
+
+- Keep module boundaries explicit so public types stay stable.
+- Use incremental builds/project references deliberately in large repos.
+- Measure hot runtime paths separately from type-system complexity.
+
 ## Avoid
 
 - Library-facing `any`.
@@ -53,8 +71,10 @@ metadata:
 
 ## Reference files
 
-- `references/configuration.md`
-- `references/advanced-types.md`
-- `references/type-guards.md`
-- `references/utility-types.md`
-- `references/patterns.md`
+| File | Load when |
+| --- | --- |
+| `references/configuration.md` | `tsconfig`, strictness, module targets, or project references need detail. |
+| `references/advanced-types.md` | Generics, conditional types, mapped types, or template literals are central. |
+| `references/type-guards.md` | Narrowing and runtime-safe type refinement need detail. |
+| `references/utility-types.md` | Utility-type composition or shared helper types are in scope. |
+| `references/patterns.md` | Type-safe architecture patterns or public API design needs detail. |

package/workflows/skills/ui-ux-pro-max/SKILL.md

@@ -158,8 +158,8 @@ python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persi
 ```
 
 This creates:
-- `design-system/MASTER.md` — Global Source of Truth with all design rules
-- `design-system/pages/` — Folder for page-specific overrides
+- a `design-system` master markdown document as the global source of truth
+- a `design-system/pages/` folder for page-specific overrides
 
 **With page-specific override:**
 ```bash
@@ -167,17 +167,17 @@ python3 skills/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persi
 ```
 
 This also creates:
-- `design-system/pages/dashboard.md` — Page-specific deviations from Master
+- a page-specific markdown override for the selected page
 
 **How hierarchical retrieval works:**
-1. When building a specific page (e.g., "Checkout"), first check `design-system/pages/checkout.md`
+1. When building a specific page (for example, Checkout), first check for a page-specific override file in `design-system/pages/`
 2. If the page file exists, its rules **override** the Master file
-3. If not, use `design-system/MASTER.md` exclusively
+3. If not, use the master design-system document exclusively
 
 **Context-aware retrieval prompt:**
 ```
-I am building the [Page Name] page. Please read design-system/MASTER.md.
-Also check if design-system/pages/[page-name].md exists.
+I am building the [Page Name] page. Please read the master design-system markdown document.
+Also check if a page-specific markdown override exists under `design-system/pages/`.
 If the page file exists, prioritize its rules.
 If not, use the Master rules exclusively.
 Now, generate the code...

package/workflows/skills/ux-ui-consistency/SKILL.md

@@ -113,12 +113,15 @@ try {
 - [ ] Screen reader labels present
 - [ ] Focus order is logical
 
-## Steering Files
+## References
 
-- `one_component_rules.md` - Complete design system component usage guide
-- `ux_checklist.md` - UX review checklist for all screens
+Load detailed guidance only when needed.
+
+| File | Load when |
+| --- | --- |
+| `steering/one_component_rules.md` | Enforcing design-system component usage and avoiding raw widget drift |
+| `steering/ux_checklist.md` | Running a full UX consistency review across a screen or feature |
 
 ## Templates
 
 - `screen_states_widget` - Complete screen state handling template
-

package/workflows/skills/variant-analysis/SKILL.md

@@ -69,7 +69,7 @@ For each match, document:
 - **Exploitability**: Reachable? Controllable inputs?
 - **Priority**: Based on impact and exploitability
 
-For deeper strategic guidance, see [METHODOLOGY.md](METHODOLOGY.md).
+For deeper strategic guidance, see [METHODOLOGY.md](references/METHODOLOGY.md).
 
 ## Tool Selection
 
@@ -139,4 +139,4 @@ Ready-to-use templates in `resources/`:
 **Semgrep** (`resources/semgrep/`):
 - `python.yaml`, `javascript.yaml`, `java.yaml`, `go.yaml`, `cpp.yaml`
 
-**Report**: `resources/variant-report-template.md`
+**Report**: `resources/variant-report-template.md`