development-best-practices

Enforce anti-hallucination, anti-hardcoding, and robust engineering practices across projects.

Updated Jan 19, 2026

Search Tags:#testing #development #security #logging #best-practices #error-handling #anti-hallucination

Ready to run

npx skills add https://github.com/onshoreoutsourcing/lighthouse-beacon --skill development-best-practices

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: development-best-practices
Source: https://github.com/onshoreoutsourcing/lighthouse-beacon/tree/main/.claude/skills/development-best-practices
Command: npx skills add https://github.com/onshoreoutsourcing/lighthouse-beacon --skill development-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a structured framework to prevent AI hallucinations, hardcoding, and unsafe coding practices by guiding teams to apply standardized development best practices across design, implementation, and review.

Core Features & Use Cases

Anti-Hallucination: verify code signatures, APIs, and file structures before use.
Anti-Hardcoding and Externalized Configuration: promote config-based behavior and environment-driven values.
Error Handling and Logging: enforce try/catch, proper logging levels, and correlation IDs.
Testing and Security: encourage unit and integration tests and security validation as part of the development workflow.
Use Case: during feature design review, run the validation workflow and ensure code meets the standards before commit.

Quick Start

Run the development-best-practices skill to validate your code against the defined patterns and references, then execute the provided validation scripts before committing changes.

Frequently Asked Questions about development-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent AI code hallucinations when generating project features?▼

Preventing AI code hallucinations requires verifying code signatures, APIs, and file structures before use. This skill enforces anti-hallucination checks during design and review to ensure generated code matches actual external dependencies and project structures.

What's the best way to enforce externalized configuration and avoid hardcoding values?▼

Enforcing externalized configuration involves promoting config-based behavior and environment-driven values instead of static inputs. This skill guides teams to eliminate hardcoding by applying standardized development practices across implementation and review phases.

How do I standardize error handling and logging across development projects?▼

Standardizing error handling and logging requires enforcing try/catch blocks, proper logging levels, and correlation IDs throughout your codebase. This skill provides a structured framework to apply these robust engineering practices during feature work.

Can I validate code against security and testing standards before committing changes?▼

Yes, you can validate code against security and testing standards before committing by running validation scripts and consulting integrated references. This skill encourages unit tests, integration tests, and security validation as part of the workflow.

Do I need to run validation scripts during feature design review?▼

You need to run validation scripts during feature design review to ensure code meets defined patterns and quality standards before commit. This skill requires executing the validation workflow and adhering to integrated references to maintain compliance.