Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Sign in
Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

A page, a video or an image online.

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Separate shared core from client code v1.0.0

Use this resource to audit the boundary between shared core and client code

New

  • 392 downloads
  • 216 likes
  • 181 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install core-client-boundary-audit

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent detects the project type, maps the boundary between the shared core and per-client code, then looks for violations: hardcoded client identifiers, client-specific conditionals and misplaced files. It produces a map, a report and a refactoring plan. You get a healthier multi-client codebase.

Mostly picked by

Updated November 2, 2026

Card for the “Separate shared core from client code” skill

Details

Works in
Install guides
Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: audit modes, boundary map and violation search
  • SKILL.md: core/client separation principle and refactoring plan

Good fit for

  • One codebase serves several clients and fixes get mixed up
  • You want to document what is shared before adding a client

Not for

    Tags

    • multi-client
    • architecture
    • refactoring
    • separation

    About

    You say

    “Check the core and client boundary in this project and tell me where client code is hardcoded.”

    Card for the “Separate shared core from client code” skill

    Skill published by jezweb under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to audit the boundary between shared core and client code
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE1.1 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • SKILL.md12.5 KB

    Origin and licence

    Listed unmodified

    Author
    jezweb
    Source
    github.com/jezweb/claude-skills/tree/1260fa7439b36b18dbf16648ccc7fb44783f6c23/plugins/dev-tools/skills/fork-discipline
    Licence
    MIT

    Notice

    « fork-discipline » (jezweb, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.