standards
/standards
Cross-project coding standards. Triggers on /codeforge:review or new module setup. Naming, typing, immutability, KISS/DRY/YAGNI, error handling, observability.
- Author
- prashantxo ↗
- Repository
- codeforge ↗
- Licence
- MIT
- Last repository change
- 26.06.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Cross-project coding standards. Triggers on /codeforge:review or new module setup. Naming, typing, immutability, KISS/DRY/YAGNI, error handling, observability.
Original author description
Cross-project coding standards. Triggers on /codeforge:review or new module setup. Naming, typing, immutability, KISS/DRY/YAGNI, error handling, observability.
How it works
- Naming
- Typing
- Principles
- Error handling
- Observability (every cross-boundary call)
- Review checklist
SKILL.md preview
---
name: standards
description: Cross-project coding standards. Triggers on /codeforge:review or new module setup. Naming, typing, immutability, KISS/DRY/YAGNI, error handling, observability.
allowed-tools: Read, Grep, Glob
---
# codeforge:standards
## Naming
| Thing | Rule | Good | Bad |
|-------|------|------|-----|
| Variable | What it holds | `activeUserId` | `x`, `data` |
| Boolean | A question | `isAuthenticated` | `auth`, `flag` |
| Function | Verb + noun | `fetchUserById` | `userData`, `doStuff` |
| File | kebab-case | `user-profile.ts` | `UserProfile.ts` |
## Typing
| Rule | Detail |
|------|--------|
| No `any` | No `object`. No untyped returns. |
| Define types first | Before writing function bodies |
| Discriminated unions | For state machines, not boolean flags |
## Principles
| Principle | Rule |
|-----------|------|
| KISS | Simplest solution that passes the tests |
| DRY | 3+ identical blocks → extract a function |
| YAGNI | No abstractions for hypothetical future use |
| Immutability | `const` by default. Never mutate arguments. |
## Error handling
| Rule | Detail |
|------|--------|
| Carry context | What failed, with what input, why |
| No silent swallow | Never `catch (e) {}` |
| 400 vs 500 | User errors vs system errors, never conflate |
| Structured logs | `{ event, userId, input, error }`, no `console.log` in prod |
## Observability (every cross-boundary call)
```
log: { event: "action.start", traceId, input }
log: { event: "action.success", traceId, durationMs }
log: { event: "action.failed", traceId, err }
metric: increment action.calls, action.errors
```
Thread `traceId` through every log line.
## Review checklist
- [ ] Names describe what things hold, not how they got there
- [ ] No `any`, no implicit `unknown`
- [ ] No argument mutation
- [ ] No silent error swallowing
- [ ] No dead code or commented-out blocks
- [ ] Structured logs on all external calls
- [ ] Tests for every new function
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · prashantxo/codeforge | 100 | MIT |
| NathanColosimo/skills | 100 | MIT |
| ciro-maciel/ccm-stack | 100 | MIT |
| itamarzand88/cli-anything-web | 100 | MIT |
| danielchukuma-dev/cougr | 95 | MIT |
| stellar/stellar-dev-skill | 90 | Apache-2.0 |
| rylsherdamz-rgb/stellar-forge | 90 | MIT |
Database snapshot: 13.11.2026 · package version a3c4945eb22f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100clean-code
Coding standards (SRP, DRY, KISS, YAGNI, naming) with a pre-edit dependency check and a completion self-check. Use when writing, editing or finishing code. - 100coding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies. - 100local-awesome-code-standards-c28c96db
Universal coding standards — naming, structure, immutability, error handling, type safety, backend layering, frontend architecture — that fill the gaps after the project's own conventions. Use when starting a module, refactoring to team conventions, setting up lint rules,… - 96java-coding-standards
Spring Bootサービス向けのJavaコーディング標準:命名、不変性、Optional使用、ストリーム、例外、ジェネリクス、プロジェクトレイアウト。 - 95pact-coding-standards
Clean code principles, error handling patterns, and coding standards for PACT Code phase. Use when: implementing features, refactoring code, reviewing code quality, establishing coding conventions, or handling errors and exceptions. Triggers on: code quality, clean code,… - 80Code Standards
This skill should be used when the user asks about "code quality", "file size limits", "function length", "KISS", "DRY", "YAGNI", "SRP", "best practices", "clean code", "cyclomatic complexity", "code review checklist", "refactoring rules", or mentions specific thresholds for…