@kennethsolomon/shipkit 1.0.0

package/skills/sk:features/SKILL.md

@@ -0,0 +1,238 @@
+---
+name: sk:features
+description: "Sync docs/sk:features/ specs with the current codebase. Auto-detects changed areas and updates only affected specs. Creates the spec system from scratch if it doesn't exist."
+---
+
+<!-- Generated by /sk:setup-claude -->
+
+# /sk:features
+
+Keep feature specifications in `docs/sk:features/` in sync with the actual codebase.
+Works with **any project** — framework-agnostic, auto-discovers source structure.
+
+## What This Does
+
+Maintains `docs/sk:features/` as a platform-agnostic feature specification system —
+the single source of truth shared between web, mobile, and any other platform
+that uses the same backend. Each spec covers: DB schema, business logic, API
+contract, permissions, edge cases, error states, web/mobile UI behavior, and
+platform divergences.
+
+---
+
+## Steps
+
+### Step 1: Detect Project State
+
+Check what exists:
+
+```bash
+ls docs/sk:features/ 2>/dev/null && echo "EXISTS" || echo "MISSING"
+ls docs/FEATURES.md 2>/dev/null && echo "INDEX_EXISTS" || echo "INDEX_MISSING"
+```
+
+**If `docs/sk:features/` does not exist:**
+Ask the user: "No feature specification system found. Create one from scratch?"
+- Yes → jump to **[Create From Scratch](#create-from-scratch)** below
+- No → stop
+
+**If `docs/sk:features/` exists:**
+Continue to Step 2.
+
+---
+
+### Step 2: Determine Update Scope
+
+Present three options:
+
+> **What would you like to update?**
+> **A. Auto-detect** *(recommended)* — scan recent git changes, update only affected specs
+> **B. Select features** — pick which specs to update from the list
+> **C. Refresh all** — update every spec from current source code
+
+Wait for the user's choice.
+
+---
+
+### Step 3A: Auto-detect Changed Features
+
+```bash
+git log --since="7 days ago" --name-only --pretty=format: | grep -v '^$' | sort -u
+```
+
+Map changed file paths to feature specs using these rules:
+
+1. **Read `docs/FEATURES.md`** to get the list of all spec files and their names.
+2. For each changed file, determine which spec it belongs to:
+   - Match by **feature name similarity**: if the spec is `expenses.md`, look for changed files containing `expense` in their path.
+   - Match by **directory**: if the spec is `budgets.md`, match files under any `budgets/` or `budget/` directory.
+   - Match by **schema files**: if any migration file, `schema.sql`, `schema.prisma`, `database.ts`, or similar schema file changed → mark ALL specs as potentially affected (schema changes ripple everywhere).
+3. Deduplicate the affected spec list.
+4. Report which specs will be updated and ask for confirmation.
+
+---
+
+### Step 3B: User Selects Features
+
+List all `.md` files in `docs/sk:features/` (excluding `_template.md`).
+Let the user pick which ones to update.
+
+---
+
+### Step 3C: Refresh All
+
+Set update list = all `.md` files in `docs/sk:features/` (excluding `_template.md`).
+
+---
+
+### Step 4: Update Each Affected Spec
+
+For each spec file to update, follow this sequence:
+
+#### 4a. Read the existing spec
+Understand its current content and section structure.
+
+#### 4b. Discover relevant source files
+
+Use a three-step lookup — no hardcoded paths:
+
+1. **Name-based search**: the feature name from the spec filename (e.g., `expenses.md` → feature name `expenses`). Search the repo:
+   ```bash
+   # Find files whose name contains the feature keyword
+   find . -type f \( -name "*expense*" -o -name "*expenses*" \) \
+     ! -path "*/node_modules/*" ! -path "*/.git/*" ! -path "*/docs/*" \
+     2>/dev/null | head -30
+   ```
+   Adjust the keyword to match the feature name.
+
+2. **Related Docs in spec**: read the `## Related Docs` section of the existing spec — it lists previously referenced files. Read those files too.
+
+3. **DB schema hint**: read the `## Database Schema` section — it names tables. Search migrations and schema files for those table names.
+
+#### 4c. Read the source files
+Read all discovered source files to understand the current implementation.
+
+#### 4d. Identify what changed
+Compare the current source code against what the spec describes:
+- New or removed DB columns / tables / constraints
+- Changed business logic rules or state transitions
+- New/changed API payloads or query patterns
+- Updated permission keys or tier requirements
+- New edge cases, error codes, or recovery paths
+
+#### 4e. Update only changed sections
+Rewrite only the sections that are out of date. **Preserve all unchanged sections verbatim.**
+Update the `> Status` block if the implementation status on either platform changed.
+
+---
+
+### Step 5: Handle New Features
+
+If source code has a clear new feature (new hook, new route group, new major component) with no corresponding spec:
+
+1. Create `docs/sk:features/<feature-name>.md` using `docs/sk:features/_template.md` as base.
+   If `_template.md` doesn't exist, use this 11-section structure:
+   ```
+   Status → Overview → Database Schema → Business Logic → API Contract
+   → Permissions & Access Control → Edge Cases → Error States
+   → UI/UX Behavior (### Web + ### Mobile) → Platform Notes → Related Docs
+   ```
+2. Fill all 11 sections from current source code.
+3. Add the new spec to `docs/FEATURES.md` under the appropriate section.
+
+---
+
+### Step 6: Update Master Index
+
+Review `docs/FEATURES.md`:
+- Add links for any new specs
+- Update status columns (Web / Mobile) if implementation status changed
+- Update any tier/feature tables if permissions changed
+
+---
+
+### Step 7: Report and Commit
+
+Show a summary:
+- ✅ **Updated**: `spec-name.md` — what changed (1 sentence each)
+- ➕ **Added**: any new spec files
+- ⏭️ **Skipped**: specs with no detected changes
+
+Ask: **"Commit the updated specs?"**
+- Yes → stage only files under `docs/` and commit:
+  `docs(features): update feature specs to reflect current implementation`
+- No → leave changes unstaged for the user to review
+
+---
+
+## Create From Scratch
+
+When `docs/sk:features/` doesn't exist, discover and document all features:
+
+### Discovery Phase
+
+1. **Detect source structure** — find where feature logic lives:
+   ```bash
+   # Look for hooks, services, controllers, models, routes
+   ls src/ lib/ app/ 2>/dev/null
+   find . -maxdepth 4 -type f \
+     \( -name "use-*.ts" -o -name "use-*.js" \
+        -o -name "*.service.ts" -o -name "*.controller.ts" \
+        -o -name "*.model.ts" -o -name "*.router.ts" \) \
+     ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null | head -50
+   ```
+
+2. **Detect schema files** — migrations, ORM schemas:
+   ```bash
+   find . -maxdepth 5 \
+     \( -name "schema.sql" -o -name "*.schema.prisma" \
+        -o -name "database.ts" -o -name "*.migration.*" \) \
+     ! -path "*/node_modules/*" ! -path "*/.git/*" 2>/dev/null
+   ls supabase/migrations/ 2>/dev/null | tail -10
+   ls prisma/ 2>/dev/null
+   ```
+
+3. **Identify feature domains** from the discovered files — group related files into named features.
+
+4. **Report discovered features** and ask the user to confirm/adjust the list before creating anything.
+
+### Creation Phase
+
+For each confirmed feature:
+1. Read all relevant source files.
+2. Create `docs/sk:features/<feature-name>.md` with all 11 sections — based entirely on source code.
+
+Also create:
+- `docs/FEATURES.md` — master index with:
+  - How-to-use section (web path + mobile path via `../project-name/docs/`)
+  - Feature table grouped by domain
+  - Tier/subscription overview (if the project has tiers)
+- `docs/sk:features/_template.md` — 11-section template for future specs
+
+Commit: `docs: add feature specification system`
+
+---
+
+## Quality Rules (Always Apply)
+
+- **Source-verified only** — every claim must be findable in source code; never invent behavior
+- **No placeholders** — no `// TODO`, no `false // will be computed`, no assumed values
+- **Surgical updates** — only rewrite what changed; preserve unchanged sections verbatim
+- **Numeric JSX coercion** — when documenting frontend behavior, note `!!value` (not `value &&`) for numerics to avoid rendering `0` as text in React/React Native
+- **Local date, not UTC** — for any time-bounded query (current month, today, etc.), document that implementations must use local `new Date()`, not `toISOString()` which returns UTC and causes off-by-one for users in non-UTC timezones
+- **All 11 sections required** — mark "N/A" only if genuinely not applicable
+
+## Source Discovery Heuristics (Reference)
+
+When locating source files for a feature named `<name>`:
+
+| What to look for | Search pattern |
+|---|---|
+| Hooks / composables | `use-<name>.*`, `use<Name>.*` |
+| Components | directories or files matching `<name>/`, `*<name>*` |
+| API routes / controllers | `<name>.route.*`, `<name>.controller.*`, `api/<name>/` |
+| Services / repositories | `<name>.service.*`, `<name>.repo.*` |
+| DB schema | `migrations/` containing table name, `schema.prisma`, `database.ts` |
+| Tests | `<name>.test.*`, `<name>.spec.*` |
+
+These are starting points — read broadly and verify before updating any section.

package/skills/sk:frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/skills/sk:frontend-design/SKILL.md

@@ -0,0 +1,191 @@
+---
+name: sk:frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Produces design direction, mockups, and visual specifications — NOT code.
+license: Complete terms in LICENSE.txt
+---
+
+## CRITICAL: Design Phase Only — NO CODE
+
+**This skill is a design phase, not an implementation phase.**
+
+- **DO NOT** write, edit, or generate any code (no React, no HTML/CSS/JS, no file edits)
+- **DO NOT** use file editing tools (Edit, Write, Bash)
+- **Pencil MCP tools ARE allowed** — they create visual design artifacts, not code
+- **DO produce** design direction, ASCII mockups, layout specs, component structure descriptions, color/typography decisions, and interaction notes
+- Implementation happens in `/sk:execute-plan` — not here
+
+This skill guides the design of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Output is a design artifact: a clear, decision-complete visual specification that `/sk:write-plan` and `/sk:execute-plan` can use to implement.
+
+The user provides frontend requirements: a component, page, application, or interface to design. They may include context about the purpose, audience, or technical constraints.
+
+## Before You Start
+
+1. If `tasks/findings.md` exists and has content, read it in full. Use the agreed
+   approach and requirements as the design brief — this replaces the need to ask the
+   user to re-explain what was already decided in brainstorming.
+
+2. If `tasks/lessons.md` exists, read it in full. Apply every active lesson as a
+   constraint during design — particularly any patterns flagged under **Bug** that
+   relate to frontend structure, component architecture, or styling conventions.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then produce a **design artifact** — not code — that includes:
+- ASCII or text-based layout mockups for key screens/states
+- Color palette (hex values, CSS variable names)
+- Typography choices (font families, sizes, weights, tracking)
+- Component structure description (what elements exist, their hierarchy)
+- Interaction notes (hover states, transitions, animations to implement)
+- Any specific Tailwind classes or CSS patterns to use during implementation
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+
+Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
+
+**IMPORTANT**: Match design detail to the aesthetic vision. Maximalist designs need elaborate layout descriptions, rich animation notes, and dense component specs. Minimalist designs need precise spacing rules, restrained color notes, and careful typographic ratios. Elegance comes from committing to the vision fully.
+
+Remember: Claude is capable of extraordinary creative thinking. Don't hold back on the design direction — show what can be envisioned when thinking outside the box and committing fully to a distinctive aesthetic.
+
+## Output Format
+
+End every `/sk:frontend-design` session with a structured summary:
+
+```
+## Design Summary
+
+### Aesthetic Direction
+[One paragraph describing the tone, feel, and visual identity]
+
+### Color Palette
+- Background: #xxxxxx (--var-name)
+- Foreground: #xxxxxx (--var-name)
+- Accent: #xxxxxx (--var-name)
+
+### Typography
+- Display: [Font name] — [weight/size/tracking notes]
+- Body: [Font name] — [weight/size notes]
+
+### Layout Mockup
+[ASCII or text mockup of the key screen(s)]
+
+### Component Notes
+[Description of each component: structure, states, interactions]
+
+### Animation & Motion
+[What moves, when, how — described in words]
+
+### Implementation Notes
+[Specific Tailwind classes, CSS patterns, or gotchas for /sk:execute-plan]
+```
+
+After presenting the design summary, ask the user:
+
+**"Would you like me to create a Pencil visual mockup? (y/n)"**
+
+---
+
+## Pencil Visual Mockup Phase
+
+Only run this phase if the user answers **y** or **yes**.
+
+### Step 1 — Find or create the .pen file
+
+Check `docs/design/` for an existing `.pen` file that matches this design (by name or topic).
+
+- **Existing file found**: call `open_document(filePath)` to open it, then skip to Step 3.
+- **No file found**: call `open_document('new')` to create a fresh canvas.
+  - The file will be saved to `docs/design/{design-name}.pen` — use a slug derived from the design subject (e.g., `docs/design/dashboard-analytics.pen`).
+
+### Step 2 — Load design context
+
+Run these two calls before drawing anything:
+
+1. `get_guidelines(topic)` — pick the closest topic:
+   - `web-app` → dashboards, SaaS, admin panels
+   - `landing-page` → marketing sites, portfolios, product pages
+   - `mobile-app` → mobile-first interfaces
+   - `design-system` → component libraries, style guides
+   - `table` → data-heavy UIs
+   - `slides` → presentations
+
+2. `get_style_guide_tags` → then `get_style_guide(tags, name)` — pick tags that match the aesthetic direction decided in the design summary (e.g., dark, minimal, editorial, playful, corporate, luxury). This gives Pencil a visual language to work from.
+
+### Step 3 — Set the color palette as variables
+
+Call `set_variables` to register the color palette from the Design Summary as Pencil variables so they can be referenced throughout the design:
+
+```
+{
+  "color-bg": "#xxxxxx",
+  "color-fg": "#xxxxxx",
+  "color-accent": "#xxxxxx"
+  // + any other palette values
+}
+```
+
+### Step 4 — Build the mockup
+
+Use `batch_design` to construct the visual. Work screen by screen:
+
+1. Create a **frame** for each key screen identified in the Layout Mockup.
+2. Inside each frame, add sections matching the component hierarchy from Component Notes.
+3. Reuse components from the design system where they fit (buttons, inputs, cards, tables, etc.) — these are already available as reusable components in the canvas.
+4. Apply the color variables and typography direction to every element.
+5. Keep batches focused: aim for one screen per batch_design call to stay within limits.
+
+### Step 5 — Validate and iterate
+
+After each screen is built, call `get_screenshot` to visually inspect the result.
+
+- If layout or spacing is off: call `snapshot_layout` to inspect computed positions, then fix with another `batch_design` call.
+- Iterate until the screen faithfully represents the Design Summary.
+
+### Step 6 — Handle existing file updates
+
+When opening an existing `.pen` file to update a design:
+
+1. Call `get_editor_state(include_schema: false)` to see current top-level nodes.
+2. Call `snapshot_layout` on affected frames to understand what's there.
+3. Use `batch_design` with `update` or `replace` operations — do not delete and recreate unless necessary.
+4. Validate with `get_screenshot` after each batch.
+
+### Step 7 — Finish
+
+Tell the user the path to the saved `.pen` file and confirm which screens were created or updated.
+
+Then tell the user: **"Run `/sk:write-plan` to turn this design into an implementation plan."**
+
+---
+
+## Model Routing
+
+Read `.shipkit/sk:config.json` from the project root if it exists.
+
+- If `model_overrides["sk:frontend-design"]` is set, use that model — it takes precedence.
+- Otherwise use the `profile` field. Default: `balanced`.
+
+| Profile | Model |
+|---------|-------|
+| `full-sail` | opus (inherit) |
+| `quality` | opus (inherit) |
+| `balanced` | sonnet |
+| `budget` | sonnet |
+
+> `opus` = inherit (uses the current session model). When spawning sub-agents via the Agent tool, pass `model: "<resolved-model>"`.

package/skills/sk:laravel-init/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: sk:laravel-init
+description: "Configure an existing Laravel project with opinionated production-ready conventions. Detects stack, installs tools, generates CLAUDE.md and tasks/ files."
+---
+
+# /laravel-init
+
+Configure this Laravel project with production-ready conventions. Safe to run on fresh installs or existing projects.
+
+## What This Does
+
+Invokes the `setup-claude` skill to:
+
+1. **Detect stack** from `composer.json` + `package.json`
+2. **Install missing dev tools**: PHPStan/Larastan, Rector, Pint, Pest
+3. **Publish config files** (if missing): `phpstan.neon`, `rector.php`, `pint.json`
+4. **Configure strict models** in `AppServiceProvider`
+5. **Generate `CLAUDE.md`** — stack-aware, with full workflow, conventions, and sub-agent patterns
+6. **Bootstrap `tasks/`** — findings, lessons, todo, progress, security-findings
+7. **Generate `.claude/commands/`** — lint, test
+8. **Pre-seed `tasks/findings.md`** with detected stack info
+
+## Idempotent
+
+Safe to run multiple times. Existing files with custom content are never overwritten.
+Generated `CLAUDE.md` (with `<!-- Generated by /laravel-init -->` marker) is auto-updated to the latest template on re-run.
+
+### Updating Existing CLAUDE.md
+
+Behavior depends on who owns the file:
+
+- **Generated** (has `<!-- Generated by /laravel-init -->` marker): safe to edit directly with section-level updates using `<!-- BEGIN/END -->` markers
+- **User-owned** (no marker): never edit — create `CLAUDE-sub-agents.md` alongside it and let the user copy what they want
+
+## After Running
+
+Start with `/sk:brainstorm` to plan your feature.