belos-street

Define naming, file organization, style, and testing conventions for JavaScript and TypeScript projects.

8|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/belos-street/skill-kit --skill belos-street
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: belos-street
Source: https://github.com/belos-street/skill-kit/tree/main/skills/belos-street
Command: npx skills add https://github.com/belos-street/skill-kit --skill belos-street

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a single source of truth for naming, file organization, code style, testing practices, and LLM-safe coding guidelines to reduce inconsistency, onboarding friction, and review churn across a codebase.

Core Features & Use Cases

  • Naming Conventions: Clear kebab-case, PascalCase and camelCase rules for files, components, types, and variables to avoid ambiguity.
  • Code Organization & Style: Recommended project directory layouts, import ordering, and Prettier/ESLint style choices to keep projects uniform.
  • Testing & LLM Guidance: Testing philosophy (TDD, AAA), test coverage priorities, and LLM coding guidelines for safe, minimal, and surgical edits.
  • Use Case: Standardize conventions for a JavaScript/TypeScript front-end project to streamline code reviews, onboard new developers faster, and ensure consistent automated formatting.

Quick Start

Apply the Belos Street conventions to align project naming, organization, style, and tests across your repository.

Frequently Asked Questions about belos-street

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

FAQPage Schema
What are the best coding conventions for standardizing JavaScript and TypeScript projects?

Standard coding conventions for JavaScript and TypeScript projects define naming rules, directory structure, and Prettier or ESLint settings to reduce code review friction. Implementing consistent file organization and style rules ensures uniform frontend and full-stack codebases across your team.

How do I set up file naming conventions and directory structure for a frontend codebase?

To set up naming conventions and directory structure, apply clear kebab-case, PascalCase, and camelCase rules for files, components, and types. Organizing your project layout with standardized import ordering keeps frontend codebases uniform and avoids ambiguity during development.

Does this coding convention Skill include guidelines for LLM-assisted development?

Yes, this coding convention Skill includes LLM-safe coding guidelines designed to ensure safe, minimal, and surgical edits. It provides specific LLM behavioral guidelines alongside standard code style and testing practices to safely integrate AI into your workflow.

What testing strategy and priorities should I use for full-stack JavaScript applications?

A recommended testing strategy for full-stack JavaScript applications follows TDD and AAA patterns with clear test coverage priorities. Establishing these testing philosophies alongside coding conventions ensures maintainable, thoroughly tested code across your project repository.

Can I apply these code style and organization rules to existing TypeScript projects?

Yes, you can apply these code style and organization rules to existing TypeScript projects to streamline code reviews and onboard new developers faster. Implementing recommended Prettier and ESLint settings ensures consistent automated formatting across legacy and new code.