# Standardize PHP and TypeScript Code

Mixed codebases often drift in formatting, names, and type discipline. This skill gives Claude, Codex, and Claude Code consistent review guidance.

## Install

```bash
npx skillstore add devanb/global-coding-style
```

## Metadata

- Status: approved
- Slug: devanb-global-coding-style
- Skillstore revision: r1
- Version status: missing
- Tree hash: 94cecb2dd74f0d37225eeff7830e66d896fb4d966d0b929edd32f04beb85e185
- Author: DevanB
- GitHub username: DevanB
- License: MIT
- Repository: https://github.com/DevanB/lucidlog/tree/master/.claude/skills/global-coding-style
- Ref: 0519034dad657fb1f7706e0550e962beeda73fdf
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/devanb-global-coding-style
- Manifest: https://skillstore.pages.dev/api/skills/devanb-global-coding-style/manifest

## Capabilities

- Guides PHP, TypeScript, and JavaScript edits toward consistent style rules.
- Prompts use of Laravel Pint for PHP formatting work.
- Prompts use of Ultracite for JavaScript and TypeScript linting.
- Encourages explicit PHP return types and parameter type hints.
- Supports cleanup of unused imports, dead code, and commented blocks.
- Frames review preparation around readability, maintainability, and DRY principles.

## Use Cases

- Review a Laravel change: Check PHP edits for type declarations, formatting expectations, unused imports, and review readiness.
- Clean up frontend code: Apply TypeScript and JavaScript style guidance before linting, formatting, or opening a pull request.
- Prepare mixed-stack changes: Keep naming, formatting, and maintainability expectations aligned across backend and frontend files.

## Prompt Templates

### Check style basics

```
Review these PHP, TypeScript, or JavaScript changes for naming, formatting, and obvious cleanup issues.
```

### Prepare for linting

```
Update this change so it is ready for Laravel Pint, Ultracite, and relevant static analysis checks.
```

### Improve type safety

```
Review this code for missing PHP return types, parameter type hints, TypeScript type gaps, and avoidable dynamic behavior.
```

### Audit maintainability

```
Assess this mixed PHP and TypeScript change for DRY violations, dead code, review risk, and maintainability improvements.
```

## Limitations

- It does not include the referenced detailed coding standard inside the skill package.
- It cannot run formatters or static analyzers without project tooling access.
- It does not define language rules for systems outside PHP, TypeScript, and JavaScript.
- It provides guidance, not automatic enforcement in a repository.

## Best Practices

- Use the skill before opening a pull request or asking for review.
- Run project formatters and static analyzers after applying style changes.
- Pair style guidance with repository-specific rules when they are available.

## Anti Patterns

- Do not use the skill as a replacement for automated linting or tests.
- Do not apply broad refactors when a focused formatting change is enough.
- Do not follow external file references unless the content is included and reviewed.

## Security Audit

- Audited at: 2026-07-09T11:10:40.902\+00:00
- Summary: The skill contains one Markdown link that traverses outside the skill directory at SKILL.md line 30. No prompt injection or malicious intent was found, but the external relative reference is a real marketplace boundary risk.

## Stats

- Views: 199
- Downloads: 11
- Favorites: 0
- Popularity score: 0