@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.1

package/template/.claude/skills/type-design/SKILL.md

@@ -1,84 +1,84 @@
----
-name: type-design
-description: Analyzes type and interface design for encapsulation, invariant expression, usefulness, and enforcement. Use when introducing new types, reviewing PRs with type changes, or refactoring domain models.
----
-
-# Type Design
-
-Use this skill to evaluate whether types make invalid states hard or impossible to represent without over-engineering the codebase.
-
-## Core Rule
-
-Make illegal states unrepresentable when it prevents real bugs, but do not make simple things complex.
-
-## When To Use
-
-- New type, interface, schema, model, DTO, or value object is introduced.
-- A PR changes type relationships, constructors, factories, or public API contracts.
-- A refactor moves validation, mutation, or domain rules across module boundaries.
-- A reviewer needs a pragmatic quality rating for type design.
-
-## Analysis Scope
-
-Review:
-
-- Type/interface definitions.
-- Constructors, factories, parsers, and validators.
-- Setter methods and mutation points.
-- Public API surface and exported types.
-- Relationships between fields that must remain consistent.
-
-## Evaluation Dimensions
-
-| Dimension | Ask |
-|---|---|
-| Encapsulation | Can callers violate invariants from outside the type boundary? |
-| Invariant Expression | Are the important constraints obvious from the type shape? |
-| Invariant Usefulness | Do the constraints prevent real bugs or only add ceremony? |
-| Invariant Enforcement | Are invalid instances impossible or at least rejected at boundaries? |
-
-Rate each dimension from 1 to 10. Scores below 5 require concrete findings.
-
-## Anti-Patterns
-
-| Anti-pattern | Risk |
-|---|---|
-| Exposed mutable internals | Callers can break invariants after construction. |
-| Doc-only invariants | The rule exists only in comments and is easy to bypass. |
-| No constructor or parser validation | Invalid instances can enter the system. |
-| Anemic domain model | Rules are scattered across callers. |
-| God type | Too many responsibilities make the type hard to use correctly. |
-| Over-modeled simple data | Complexity exceeds the bug-prevention value. |
-
-## Output Format
-
-```markdown
-## Type Design Review: [Scope]
-
-### Types Reviewed
-| Type | File | Purpose |
-|---|---|---|
-| `TypeName` | `path/file.ts:10` | Represents ... |
-
-### Ratings
-| Type | Encapsulation | Expression | Usefulness | Enforcement | Overall |
-|---|---:|---:|---:|---:|---:|
-| `TypeName` | 8 | 7 | 8 | 6 | 7.25 |
-
-### Findings
-#### [Severity] [Title]
-**Location**: `path/file.ts:23`
-**Problem**: [What invariant can fail]
-**Impact**: [Concrete bug or maintenance risk]
-**Recommendation**: [Smallest useful improvement]
-
-### Verdict
-[Well-designed / Adequate / Needs improvement / Significant issues]
-```
-
-## Verification
-
-- Findings cite concrete files and lines.
-- Recommendations fit the project's existing type style.
-- Suggestions include trade-offs when they add ceremony.
-- No recommendation depends on speculative future requirements.
+---
+name: type-design
+description: Analyzes type and interface design for encapsulation, invariant expression, usefulness, and enforcement. Use when introducing new types, reviewing PRs with type changes, or refactoring domain models.
+---
+
+# Type Design
+
+Use this skill to evaluate whether types make invalid states hard or impossible to represent without over-engineering the codebase.
+
+## Core Rule
+
+Make illegal states unrepresentable when it prevents real bugs, but do not make simple things complex.
+
+## When To Use
+
+- New type, interface, schema, model, DTO, or value object is introduced.
+- A PR changes type relationships, constructors, factories, or public API contracts.
+- A refactor moves validation, mutation, or domain rules across module boundaries.
+- A reviewer needs a pragmatic quality rating for type design.
+
+## Analysis Scope
+
+Review:
+
+- Type/interface definitions.
+- Constructors, factories, parsers, and validators.
+- Setter methods and mutation points.
+- Public API surface and exported types.
+- Relationships between fields that must remain consistent.
+
+## Evaluation Dimensions
+
+| Dimension | Ask |
+|---|---|
+| Encapsulation | Can callers violate invariants from outside the type boundary? |
+| Invariant Expression | Are the important constraints obvious from the type shape? |
+| Invariant Usefulness | Do the constraints prevent real bugs or only add ceremony? |
+| Invariant Enforcement | Are invalid instances impossible or at least rejected at boundaries? |
+
+Rate each dimension from 1 to 10. Scores below 5 require concrete findings.
+
+## Anti-Patterns
+
+| Anti-pattern | Risk |
+|---|---|
+| Exposed mutable internals | Callers can break invariants after construction. |
+| Doc-only invariants | The rule exists only in comments and is easy to bypass. |
+| No constructor or parser validation | Invalid instances can enter the system. |
+| Anemic domain model | Rules are scattered across callers. |
+| God type | Too many responsibilities make the type hard to use correctly. |
+| Over-modeled simple data | Complexity exceeds the bug-prevention value. |
+
+## Output Format
+
+```markdown
+## Type Design Review: [Scope]
+
+### Types Reviewed
+| Type | File | Purpose |
+|---|---|---|
+| `TypeName` | `path/file.ts:10` | Represents ... |
+
+### Ratings
+| Type | Encapsulation | Expression | Usefulness | Enforcement | Overall |
+|---|---:|---:|---:|---:|---:|
+| `TypeName` | 8 | 7 | 8 | 6 | 7.25 |
+
+### Findings
+#### [Severity] [Title]
+**Location**: `path/file.ts:23`
+**Problem**: [What invariant can fail]
+**Impact**: [Concrete bug or maintenance risk]
+**Recommendation**: [Smallest useful improvement]
+
+### Verdict
+[Well-designed / Adequate / Needs improvement / Significant issues]
+```
+
+## Verification
+
+- Findings cite concrete files and lines.
+- Recommendations fit the project's existing type style.
+- Suggestions include trade-offs when they add ceremony.
+- No recommendation depends on speculative future requirements.

package/template/.claude/skills/ui-ux-pro-max/SKILL.md

@@ -1,75 +1,75 @@
----
-name: ui-ux-pro-max
-description: AI-powered design intelligence with 50+ styles, 95+ color palettes, and automated design system generation. Use when designing, building, or reviewing UI/UX.
----
-
-# UI/UX Pro Max (Design Intelligence)
-
-Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 9 technology stacks. Searchable database with priority-based recommendations.
-
-## Prerequisites
-
-Python is required for the design system search tool.
-
-## How to Use This Skill
-
-When you need to perform UI/UX work (design, build, create, implement, review, fix, improve), follow this process:
-
-### 1. Analyze User Requirements
-Extract key information:
-- **Product type**: SaaS, e-commerce, dashboard, etc.
-- **Style keywords**: minimal, playful, professional, dark mode, etc.
-- **Industry**: healthcare, fintech, gaming, etc.
-- **Stack**: React, Vue, Next.js, or default to `html-tailwind`.
-
-### 2. Generate Design System (REQUIRED)
-**Always start by generating a design system** to get comprehensive recommendations:
-
-```bash
-python3 .claude/.shared/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
-```
-
-### 3. Persist Design System
-To save the design system for hierarchical retrieval:
-
-```bash
-python3 .claude/.shared/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" [--page "name"]
-```
-
-### 4. Detailed Domain Searches
-Supplement with specific details as needed:
-- `style`: `--domain style "keywords"`
-- `chart`: `--domain chart "keywords"`
-- `ux`: `--domain ux "keywords"`
-- `typography`: `--domain typography "keywords"`
-
----
-
-## Design Guidelines & Standards
-
-### Professional UI Rules
-- **No emoji icons**: Use SVG icons (Heroicons, Lucide).
-- **Stable hover states**: Use color/opacity transitions, avoid layout shifts.
-- **Consistent icon sizing**: Use fixed viewBox (24x24) with w-6 h-6.
-- **Cursor pointer**: Add `cursor-pointer` to all interactive elements.
-
-### Contrast & Visibility
-- **Light Mode Glass**: Use `bg-white/80` or higher.
-- **Text Contrast**: Use high-contrast slates (e.g., slate-900 for body).
-- **Border visibility**: Ensure borders are visible in both light/dark modes.
-
-### Layout
-- **Floating navbar**: Add `top-4 left-4 right-4` spacing.
-- **Responsive**: Test at 375px, 768px, 1024px, 1440px.
-
-## Pre-Delivery Checklist
-
-- [ ] No emojis used as icons (use SVG instead).
-- [ ] Hover states don't cause layout shift.
-- [ ] All clickable elements have `cursor-pointer`.
-- [ ] Transitions are smooth (150-300ms).
-- [ ] Responsive at all major breakpoints.
-- [ ] No horizontal scroll on mobile.
-
----
-*Powered by UI-UX Pro Max Engine*
+---
+name: ui-ux-pro-max
+description: AI-powered design intelligence with 50+ styles, 95+ color palettes, and automated design system generation. Use when designing, building, or reviewing UI/UX.
+---
+
+# UI/UX Pro Max (Design Intelligence)
+
+Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 9 technology stacks. Searchable database with priority-based recommendations.
+
+## Prerequisites
+
+Python is required for the design system search tool.
+
+## How to Use This Skill
+
+When you need to perform UI/UX work (design, build, create, implement, review, fix, improve), follow this process:
+
+### 1. Analyze User Requirements
+Extract key information:
+- **Product type**: SaaS, e-commerce, dashboard, etc.
+- **Style keywords**: minimal, playful, professional, dark mode, etc.
+- **Industry**: healthcare, fintech, gaming, etc.
+- **Stack**: React, Vue, Next.js, or default to `html-tailwind`.
+
+### 2. Generate Design System (REQUIRED)
+**Always start by generating a design system** to get comprehensive recommendations:
+
+```bash
+python3 .claude/.shared/ui-ux-pro-max/scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
+```
+
+### 3. Persist Design System
+To save the design system for hierarchical retrieval:
+
+```bash
+python3 .claude/.shared/ui-ux-pro-max/scripts/search.py "<query>" --design-system --persist -p "Project Name" [--page "name"]
+```
+
+### 4. Detailed Domain Searches
+Supplement with specific details as needed:
+- `style`: `--domain style "keywords"`
+- `chart`: `--domain chart "keywords"`
+- `ux`: `--domain ux "keywords"`
+- `typography`: `--domain typography "keywords"`
+
+---
+
+## Design Guidelines & Standards
+
+### Professional UI Rules
+- **No emoji icons**: Use SVG icons (Heroicons, Lucide).
+- **Stable hover states**: Use color/opacity transitions, avoid layout shifts.
+- **Consistent icon sizing**: Use fixed viewBox (24x24) with w-6 h-6.
+- **Cursor pointer**: Add `cursor-pointer` to all interactive elements.
+
+### Contrast & Visibility
+- **Light Mode Glass**: Use `bg-white/80` or higher.
+- **Text Contrast**: Use high-contrast slates (e.g., slate-900 for body).
+- **Border visibility**: Ensure borders are visible in both light/dark modes.
+
+### Layout
+- **Floating navbar**: Add `top-4 left-4 right-4` spacing.
+- **Responsive**: Test at 375px, 768px, 1024px, 1440px.
+
+## Pre-Delivery Checklist
+
+- [ ] No emojis used as icons (use SVG instead).
+- [ ] Hover states don't cause layout shift.
+- [ ] All clickable elements have `cursor-pointer`.
+- [ ] Transitions are smooth (150-300ms).
+- [ ] Responsive at all major breakpoints.
+- [ ] No horizontal scroll on mobile.
+
+---
+*Powered by UI-UX Pro Max Engine*