cast-code 1.0.5 → 1.0.7

package/dist/modules/skills/definitions/specialized/database-operations.md

@@ -1,78 +0,0 @@
----
-name: database-operations
-description: Database design and query optimization
-tools:
-  - read_file
-  - write_file
-  - edit_file
-  - shell
----
-
-# Database Operations — Domain Knowledge
-
-This skill teaches you database design, query optimization, and safe migration practices. Study this to make good data modeling decisions.
-
-## Schema Design Principles
-
-### Normalization Rules
-- **1NF**: Atomic values, no repeating groups
-- **2NF**: No partial dependencies on composite keys
-- **3NF**: No transitive dependencies
-
-### When to Denormalize
-| Situation | Denormalize? | Technique |
-|-----------|-------------|-----------|
-| Read-heavy, write-rare | Yes | Materialized view / computed column |
-| Reporting/analytics | Yes | Star schema / denormalized table |
-| Real-time dashboard | Yes | Pre-aggregated cache |
-| OLTP with consistency needs | No | Keep normalized |
-
-## Query Optimization
-
-### Indexing Decision Framework
-| Query pattern | Index type |
-|---------------|------------|
-| `WHERE col = value` | B-tree index on col |
-| `WHERE col1 = X AND col2 = Y` | Composite index (col1, col2) |
-| `WHERE col LIKE 'prefix%'` | B-tree (prefix only) |
-| `ORDER BY col` | Index on col |
-| `WHERE col IN (...)` | B-tree index on col |
-| Full-text search | GIN / Full-text index |
-
-### Performance Diagnosis
-1. `EXPLAIN ANALYZE` the slow query
-2. Look for: Seq Scan (missing index), Nested Loop (N+1), Sort (missing index)
-3. Add index → re-explain → verify improvement
-
-### Common Performance Issues
-| Problem | Symptom | Fix |
-|---------|---------|-----|
-| N+1 queries | Many identical queries | Eager loading / JOIN |
-| Missing index | Seq Scan on large table | Add appropriate index |
-| Over-fetching | SELECT * on wide table | Select specific columns |
-| Lock contention | Timeout errors | Shorter transactions |
-
-## Migration Safety
-
-### Safe Operations (can run anytime)
-- Add nullable column
-- Add index CONCURRENTLY
-- Create new table
-- Add constraint with NOT VALID
-
-### Dangerous Operations (need careful planning)
-| Operation | Risk | Safe approach |
-|-----------|------|---------------|
-| Drop column | Data loss | Deploy code first, drop later |
-| Rename column | Breaks queries | Add new, migrate, drop old |
-| Change type | Data corruption | Add new column, backfill, swap |
-| Add NOT NULL | Fails on existing nulls | Backfill first, then constrain |
-
-## ORM vs Raw SQL
-
-| Use ORM when... | Use Raw SQL when... |
-|-----------------|---------------------|
-| Standard CRUD | Complex aggregations |
-| Migrations | Performance-critical queries |
-| Type safety needed | Database-specific features |
-| Rapid prototyping | Bulk operations |

package/dist/modules/skills/definitions/specialized/frontend-bootstrap.md

@@ -1,71 +0,0 @@
----
-name: frontend-bootstrap
-description: Bootstrap full frontend projects from Figma and product requirements
-tools:
-  - read_file
-  - write_file
-  - edit_file
-  - glob
-  - grep
-  - ls
-  - shell
----
-
-# Frontend Bootstrap from Figma
-
-Use this skill when the goal is to turn a prototype into a complete frontend foundation quickly.
-
-## Outcome Targets
-
-- Deliver a runnable frontend scaffold with routing, layout, and core pages.
-- Generate reusable UI primitives before page-specific components.
-- Apply consistent styling through design tokens and theme variables.
-- Keep architecture ready for backend integration.
-
-## Figma-to-Code Workflow
-
-1. Map screens and flows:
-- Identify all top-level screens in the prototype.
-- Capture navigation structure and page hierarchy.
-- Note critical interaction states (loading, empty, error, success).
-
-2. Extract design system:
-- Color palette, typography scale, spacing scale, border radius, shadow set.
-- Component variants for button, input, select, table, modal, card, badge, tabs.
-- Breakpoints and responsive behavior.
-
-3. Plan project structure:
-- `src/app` or `src/pages` for routes/screens.
-- `src/components/ui` for primitives.
-- `src/components/features` for domain components.
-- `src/styles` for tokens/theme/global styles.
-- `src/lib` for utilities and configuration.
-
-4. Generate in layers:
-- First: tokens/theme + base layout + routes.
-- Second: UI primitives and variants.
-- Third: screen composition using primitives.
-- Fourth: stubs for API services and typed contracts.
-
-5. Validate consistency:
-- Verify token usage over hardcoded values.
-- Verify responsive layout across mobile/tablet/desktop.
-- Verify accessibility basics: semantic roles, labels, focus, contrast.
-
-## Heuristics for Common Elements
-
-- Table-heavy screens:
-  - Create reusable `DataTable` with column config, pagination, loading and empty states.
-- Form-heavy screens:
-  - Create form field wrappers with validation message and helper text support.
-- Modal-heavy flows:
-  - Standardize modal shell, close behavior, keyboard handling, and action footer.
-- Dashboard screens:
-  - Prioritize layout grid and card primitives before chart wiring.
-
-## Integration Readiness
-
-- Keep API and data fetching behind dedicated service/hooks layers.
-- Use mock data adapters initially to unblock UI.
-- Preserve clear boundaries so backend integration only replaces adapters and endpoints.
-

package/dist/modules/skills/definitions/specialized/react-patterns.md

@@ -1,77 +0,0 @@
----
-name: react-patterns
-description: React component patterns and best practices
-tools:
-  - read_file
-  - write_file
-  - edit_file
----
-
-# React Patterns — Domain Knowledge
-
-This skill teaches you React best practices, component architecture, and performance patterns. Study this to write idiomatic React code.
-
-## Component Architecture Decision Tree
-
-| Need | Pattern | Why |
-|------|---------|-----|
-| Simple display | Functional component | No state needed |
-| Local state | useState/useReducer | Component-level reactivity |
-| Shared state | Context + useContext | Cross-component without prop drilling |
-| Server data | React Query / SWR | Cache, refetch, loading states |
-| Side effects | useEffect with cleanup | Subscriptions, timers, API calls |
-| Reusable logic | Custom hooks | Extract and share behavior |
-
-## Component Patterns
-
-### Functional Components (always prefer)
-```tsx
-interface Props {
-  title: string;
-  onClick?: () => void;
-}
-
-export function MyComponent({ title, onClick }: Props) {
-  return <button onClick={onClick}>{title}</button>;
-}
-```
-
-### Custom Hooks (extract reusable logic)
-```tsx
-function useCounter(initial = 0) {
-  const [count, setCount] = useState(initial);
-  const increment = useCallback(() => setCount(c => c + 1), []);
-  return { count, increment };
-}
-```
-
-### Composition over Inheritance
-- Use `children` prop for flexible layouts
-- Use render props for shared behavior
-- Use compound components for related UI (Tabs/Tab, Select/Option)
-
-## Performance Rules
-
-| Problem | Solution | When |
-|---------|----------|------|
-| Expensive calc re-runs | `useMemo(() => calc, [deps])` | calc takes >1ms |
-| Callback causes re-render | `useCallback(fn, [deps])` | Passed to memoized child |
-| Component re-renders unnecessarily | `React.memo(Component)` | Props rarely change |
-| Large bundle | `React.lazy(() => import(...))` | Route-level splitting |
-| Long list | Virtualization (react-window) | 100+ items |
-
-## Anti-Patterns to Avoid
-
-1. **State for derived data** — Compute from existing state instead of storing separately
-2. **useEffect for transforms** — Transform during render, not in effects
-3. **Index as key** — Use stable IDs from data, not array index
-4. **Nested ternaries in JSX** — Extract to variables or early returns
-5. **Prop drilling 3+ levels** — Use Context or composition
-
-## Accessibility Checklist
-
-- Semantic HTML (`button` not `div onClick`)
-- ARIA labels for icon-only buttons
-- Keyboard navigation (Tab, Enter, Escape)
-- Focus management after modals/dialogs
-- Color contrast (4.5:1 minimum)

package/dist/modules/skills/definitions/specialized/testing-strategies.md

@@ -1,79 +0,0 @@
----
-name: testing-strategies
-description: Testing patterns and strategies
-tools:
-  - read_file
-  - write_file
-  - edit_file
-  - shell
----
-
-# Testing Strategies — Domain Knowledge
-
-This skill teaches you how to write effective tests. Study this to learn what to test, how to structure tests, and when to use different testing approaches.
-
-## Testing Pyramid
-
-| Level | Speed | Count | Coverage |
-|-------|-------|-------|----------|
-| Unit | Fast (ms) | Many | Functions, classes, utils |
-| Integration | Medium (s) | Moderate | API routes, DB queries, services |
-| E2E | Slow (s-min) | Few | Critical user flows only |
-
-## The AAA Pattern (ALWAYS follow this)
-
-```typescript
-test('should [behavior] when [condition]', () => {
-  // Arrange — set up the test
-  const calculator = new Calculator();
-
-  // Act — perform the action
-  const result = calculator.add(2, 3);
-
-  // Assert — verify the result
-  expect(result).toBe(5);
-});
-```
-
-## What to Test (Decision Framework)
-
-| Code type | Test approach | Priority |
-|-----------|---------------|----------|
-| Pure functions | Unit test with edge cases | HIGH |
-| API endpoints | Integration test with real DB | HIGH |
-| UI components | Render + interaction tests | MEDIUM |
-| Config/setup | Smoke test (does it load?) | LOW |
-| External APIs | Mock + contract test | MEDIUM |
-| Error paths | Unit test thrown errors | HIGH |
-
-## Test Naming Convention
-
-- `should [expected behavior] when [condition]`
-- `[method] returns [result] for [input]`
-- `throws [error] when [invalid input]`
-
-## Mocking Rules
-
-| Mock when... | Don't mock when... |
-|-------------|-------------------|
-| External API calls | Core business logic |
-| Database in unit tests | Database in integration tests |
-| Time (Date.now, timers) | Simple utility functions |
-| Random values | Data transformations |
-| File system in CI | File system in integration |
-
-## Running Tests
-
-- `npm test` or `npx jest` — run all tests
-- `npm test -- --watch` — watch mode
-- `npm test -- --coverage` — coverage report
-- `npm test -- path/to/file` — run specific file
-- `npx jest --testPathPattern="pattern"` — filter by pattern
-
-## Common Mistakes
-
-1. **Testing implementation, not behavior** — Test WHAT it does, not HOW
-2. **Shared mutable state between tests** — Reset in beforeEach
-3. **Not testing error cases** — Happy path + error paths
-4. **Brittle snapshot tests** — Only snapshot stable, small components
-5. **Skipping async cleanup** — Always await and clean up promises/timers