# Standardize Project Coding Practices

Teams lose time when code style, validation, and workflow decisions vary across files. This skill gives Claude, Codex, and Claude Code consistent standards to apply during development.

## Install

```bash
npx skillstore add joseph obrien/89jobrien-global-standards
```

## Metadata

- Status: approved
- Slug: 89jobrien-global-standards
- Version: 1.0.1
- Author version: 1.0.1
- Skillstore revision: r1
- Version status: valid
- Tree hash: f8cae66189da287c3ace3beb9bd7b582d312aa4c35b3e437ad39a2fefb5e701b
- Author: Joseph OBrien
- GitHub username: 89jobrien
- License: MIT
- Repository: https://github.com/89jobrien/steve/tree/main/steve/skills/global-standards
- Ref: c4037264bbd363c572662d6154a3ab28f5ca4f53
- 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: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/89jobrien-global-standards
- Manifest: https://skillstore.pages.dev/api/skills/89jobrien-global-standards/manifest

## Capabilities

- Applies naming, formatting, and structure guidance across common programming languages.
- Guides comment and docstring decisions with focus on useful context.
- Recommends error handling patterns for user messages, logging, retries, and cleanup.
- Promotes client-side and server-side validation with sanitization guidance.
- Helps keep dependencies, frameworks, file structure, and workflows consistent.

## Use Cases

- Review a Pull Request: Check whether code changes follow naming, comments, validation, and error handling conventions.
- Plan a New Feature: Choose patterns for files, dependencies, validation, and error handling before implementation starts.
- Create Team Standards: Use the reference files as a baseline for shared coding and workflow conventions.

## Prompt Templates

### Check Basic Style

```
Review this change against the global standards. Focus on names, formatting, comments, and avoidable duplication.
```

### Improve Error Handling

```
Use the global standards to improve error handling. Check user messages, logging, cleanup, retries, and propagation boundaries.
```

### Validate Feature Design

```
Evaluate this feature plan against global standards. Cover validation, security boundaries, file structure, dependencies, and framework consistency.
```

### Audit Project Conventions

```
Audit this repository for global standards alignment. Identify convention gaps, repeated patterns, dependency concerns, and documentation updates.
```

## Limitations

- It provides standards guidance, not automated linting or formatting by itself.
- It does not replace project-specific rules stored outside the skill files.
- It cannot verify behavior without access to the target codebase and tests.
- It gives general guidance that may need adaptation for regulated environments.

## Best Practices

- Load the relevant reference file before making detailed standards decisions.
- Compare new code with nearby project patterns before adding new abstractions.
- Run project tests and quality checks after applying standards changes.

## Anti Patterns

- Do not use the skill as a substitute for project-specific requirements.
- Do not add new dependencies before checking existing tools and conventions.
- Do not apply generic standards when local code has a clear established pattern.

## Security Audit

- Audited at: 2026-07-05T12:27:52.839\+00:00
- Summary: All fourteen static findings are false positives caused by Markdown formatting or benign standards documentation. No prompt-injection, command-execution, secret-access, or data-exfiltration intent was found in the reviewed files.

## Stats

- Views: 183
- Downloads: 13
- Favorites: 0
- Popularity score: 0