starter-kit-adapt

Restructures Claude configuration for a Vue SSR Starter Kit after forking.

3|Updated Jan 14, 2023
One-click install
npx skills add https://github.com/e-xode/vue-ssr --skill starter-kit-adapt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starter-kit-adapt
Source: https://github.com/e-xode/vue-ssr/tree/main/.claude/skills/starter-kit-adapt
Command: npx skills add https://github.com/e-xode/vue-ssr --skill starter-kit-adapt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of a broken or outdated Claude configuration after you fork or clone the Vue SSR Starter Kit, especially when dependency versions, enabled skill modules, locales, or architecture assumptions change.

Core Features & Use Cases

  • Post-fork adaptation checklist: Provides a structured process to rename project references, update hardcoded version notes, and align the configuration with your new repo identity.
  • Skill and rules pruning/selection: Guides what to keep, customize, and remove when your fork changes scope (e.g., dropping MongoDB, authentication, Vuetify/SCSS, or i18n).
  • Agent fleet and cross-link consistency: Instructs how to update .claude/agents/ and to run the audit workflow to prevent broken references and stale index entries.

Quick Start

Tell the AI: “I forked vue-ssr for my new project—walk me through the exact post-fork changes I should make to CLAUDE.md, the skill set, the agent fleet, and the rules, and tell me what to verify with audit.py.”

Frequently Asked Questions about starter-kit-adapt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I adapt a Claude config after forking a Vue SSR starter kit?

Post-fork adaptation of a Claude config involves restructuring the skill set, agent fleet, and path-scoped rules to match the new project, ensuring all identity references and architecture assumptions are updated.

What do I need to update in CLAUDE.md when removing starter-kit capabilities like MongoDB or Vuetify?

When removing capabilities like MongoDB, authentication, or Vuetify, you must prune related cross-references, adjust version-sensitive descriptions, and remove the corresponding skill modules and path-scoped rules from the config.

How do I prevent broken references in the agent fleet after changing dependency versions?

To prevent broken references when changing dependency versions, update the `.claude/agents/` directory and validate configuration consistency by running the included audit workflow to catch stale index entries.

Can I change locales in my Vue SSR fork without breaking the Claude configuration?

Yes, you can modify locales in your fork, but the Claude configuration requires post-fork adaptation to update version-sensitive descriptions and align the skill set with the new locale architecture.

What is the best way to rename project references in a forked Claude config?

The best way to rename project references is to follow a structured post-fork adaptation checklist that updates hardcoded version notes and aligns the configuration with the new repository identity.

Why does my Claude config have stale index entries after forking the Vue SSR Starter Kit?

Stale index entries occur because the forked config retains original cross-references and skill modules; running the audit workflow validates consistency and identifies references that need pruning.