skills.rest
whddltjdwhd
whddltjdwhdCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

bellog-structure

Standardize Bellog project structure with defined directory layouts and naming conventions.

2|Updated Feb 17, 2025
Search Tags:#typescript#frontend#naming-conventions#code-organization#project-standards#file-structure
One-click install
npx skills add https://github.com/whddltjdwhd/bellog --skill bellog-structure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bellog-structure
Source: https://github.com/whddltjdwhd/bellog/tree/main/.claude/skills/bellog-structure
Command: npx skills add https://github.com/whddltjdwhd/bellog --skill bellog-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bellog projects often suffer from ad-hoc file layouts and inconsistent naming, causing onboarding friction and maintenance overhead.

Core Features & Use Cases

  • Standardized project structure: defines top-level folders and deeper layouts to keep code and content organized.
  • Consistent naming: prescribes file and directory naming to improve discoverability and collaboration.
  • Onboarding & refactoring: provides a ready-to-use blueprint when creating new files or reorganizing existing code.

Quick Start

Follow the Bellog structure guide to reorganize or initialize a new project folder using the defined file layout and naming conventions.

Frequently Asked Questions about bellog-structure

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

FAQPage Schema
What is the best way to organize a TypeScript frontend project structure?▼

A consistent TypeScript frontend project structure uses defined directory layouts for src, app, and components to keep code organized. This standardization improves discoverability and reduces maintenance overhead during development.

How do I enforce naming conventions for frontend files and directories?▼

To enforce naming conventions for frontend files, prescribe specific patterns for directories like src, app, and components. Consistent file and directory naming improves discoverability and collaboration across the project.

When do I need to standardize file layout and code organization?▼

Standardize file layout and code organization when creating new files or reorganizing existing code to reduce onboarding friction. Applying a defined directory blueprint ensures consistency and scalable maintenance for new and existing projects.

Does this project structure guide work for refactoring existing code?▼

Yes, this project structure guide works for refactoring existing code by providing a ready-to-use blueprint for reorganizing files across src, app, components, and lib. It helps eliminate ad-hoc file layouts and inconsistent naming.

Why does inconsistent naming cause onboarding friction in frontend projects?▼

Inconsistent naming causes onboarding friction because ad-hoc file layouts make it difficult to locate code and public assets. Standardized organization patterns and prescribed naming reduce maintenance overhead and improve discoverability.

Related Skills

Explore More Software Engineering Skills→
feraudetferaudet

test-conventions

Standardize TypeScript monorepo test conventions with Vitest and React Testing Library.

Community
Intermediate
kabakakabaka

vite-react-project-structure

Define standardized file layouts for Vite + React projects.

Community
Basic
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
Oleh-BashtovyiOleh-Bashtovyi
2

frontend-standards

Validates React 19 and TypeScript frontend code against Learnix project standards.

Community
Advanced