PHPackages                             rasmusgodske/godske-dev-rules - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. rasmusgodske/godske-dev-rules

ActiveLibrary[Utility & Helpers](/categories/utility)

rasmusgodske/godske-dev-rules
=============================

Development convention rules for Claude Code - PHP, Laravel, Vue, TypeScript, Python, and more

00PHP

Since Feb 1Pushed 3mo agoCompare

[ Source](https://github.com/RasmusGodske/godske-dev-rules)[ Packagist](https://packagist.org/packages/rasmusgodske/godske-dev-rules)[ RSS](/packages/rasmusgodske-godske-dev-rules/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Godske Dev Rules
================

[](#godske-dev-rules)

Development convention rules for Claude Code. Provides reusable coding conventions for PHP, Laravel, Vue, TypeScript, Python, and more.

Installation
------------

[](#installation)

```
composer require rasmusgodske/godske-dev-rules --dev
```

Usage
-----

[](#usage)

After installation, run the artisan command to sync rules to your project:

```
php artisan dev-rules:update
```

This copies the rules to `.claude/rules/techstack/` in your project.

### Options

[](#options)

```
# Update rules (overwrites existing)
php artisan dev-rules:update --force

# Custom installation path
php artisan dev-rules:update --path=.claude/rules/custom
```

Rule Categories
---------------

[](#rule-categories)

CategoryPathDescriptionBackend`backend/`PHP and Laravel conventionsFrontend`frontend/`Vue 3 and TypeScript conventionsData Classes`dataclasses/`Spatie Laravel Data patternsE2E`e2e/`Playwright testing conventionsPrinciples`principles/`Cross-cutting development principlesPython`python/`Python development conventionsHow Rules Work
--------------

[](#how-rules-work)

Rules are markdown files that Claude Code automatically loads based on file paths. Each rule has YAML frontmatter specifying when it should load:

```
---
paths: app/**/*.php
---

# PHP Conventions

Your conventions here...
```

When you edit a `.php` file, rules matching `app/**/*.php` are loaded automatically.

Directory Structure
-------------------

[](#directory-structure)

After running `dev-rules:update`, your project will have:

```
.claude/rules/
├── techstack/           # Rules from this package (synced)
│   ├── backend/
│   ├── frontend/
│   ├── dataclasses/
│   ├── e2e/
│   ├── principles/
│   └── python/
└── project/             # Your custom rules (not synced)
    ├── backend/
    └── frontend/

```

Custom Rules
------------

[](#custom-rules)

Add project-specific rules to `.claude/rules/project/`. These are NOT overwritten when running `dev-rules:update`.

Updating Rules
--------------

[](#updating-rules)

When a new version of this package is released:

```
composer update rasmusgodske/godske-dev-rules
php artisan dev-rules:update --force
```

Contributing
------------

[](#contributing)

See [CONTRIBUTING.md](rules/CONTRIBUTING.md) for guidelines on adding or modifying rules.

Migration from laravel-vue-rules
--------------------------------

[](#migration-from-laravel-vue-rules)

If you were using `rasmusgodske/laravel-vue-rules`:

1. Remove the old package:

    ```
    composer remove rasmusgodske/laravel-vue-rules
    ```
2. Install the new package:

    ```
    composer require rasmusgodske/godske-dev-rules --dev
    ```
3. Update your rules:

    ```
    php artisan dev-rules:update --force
    ```

The new package includes all the same rules plus Python conventions.

License
-------

[](#license)

MIT

###  Health Score

18

—

LowBetter than 8% of packages

Maintenance54

Moderate activity, may be stable

Popularity0

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity12

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/f1b31583549e6a4a645af04d046c1f54cd528857fc51946c17e65ce062362ceb?d=identicon)[RasmusGodske](/maintainers/RasmusGodske)

---

Top Contributors

[![RasmusGodske](https://avatars.githubusercontent.com/u/8774823?v=4)](https://github.com/RasmusGodske "RasmusGodske (1 commits)")

### Embed Badge

![Health badge](/badges/rasmusgodske-godske-dev-rules/health.svg)

```
[![Health](https://phpackages.com/badges/rasmusgodske-godske-dev-rules/health.svg)](https://phpackages.com/packages/rasmusgodske-godske-dev-rules)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)