applying-coding-style

Enforces personal naming, commenting, and testing standards when writing TypeScript, Vue, and SCSS code.

3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/OktayCopurlu/ai-shared --skill applying-coding-style-oktaycopurlu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: applying-coding-style
Source: https://github.com/OktayCopurlu/ai-shared/tree/main/.github/workflows/skills/applying-coding-style
Command: npx skills add https://github.com/OktayCopurlu/ai-shared --skill applying-coding-style-oktaycopurlu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written or edited by AI assistants often drifts from personal style conventions, accumulating vague names, redundant comments, dead code, and poorly structured tests. This Skill applies a consistent set of personal coding standards to every file you generate or modify. ## Core Features & Use Cases - Naming and Comment Rules: Enforces descriptive names that eliminate the need for comments, boolean prefixes like is/has/should, and bans JSDoc on internal functions, TODOs, and commented-out code. - Code Shape Discipline: Applies a YAGNI decision ladder, DRY consolidation at the third occurrence, vertical spacing rules, and change-scope discipline so edits stay minimal and compilable. - Testing Style Guide: Structures tests with describe('when ...') / it('<behavior>') hierarchy, one assertion focus per test, and rules against flaky, redundant, or multi-phase tests. - Use Case: When asking an AI to refactor a Vue component or write new TypeScript utilities, the output automatically follows your naming, spacing, and test-structure conventions without repeated prompting. ## Quick Start Apply your coding style standards while writing a new TypeScript utility function with unit tests.

Frequently Asked Questions about applying-coding-style

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

FAQPage Schema
How do I enforce consistent naming conventions in AI-generated code?▼

Define explicit naming rules such as boolean prefixes (is, has, should, can), verb-phrase function names, and UPPER_SNAKE_CASE constants, then load them as a skill so every generation follows them. Names should be descriptive enough to replace comments.

How to structure unit tests with describe and it blocks?▼

Use an outer describe for the unit, nested describe('when <scenario>') for preconditions, and it('<present-tense behavior>') for outcomes. Keep one assertion focus per test, never put conditions in it blocks, and avoid joining independent outcomes with 'and'.

When should I write comments in code?▼

Only for non-obvious 'why' decisions, workarounds for framework bugs with issue links, and complex regex explanations. Never write JSDoc on internal functions, inline comments restating code, TODOs, or commented-out code.

Does this style guide work with Vue and SCSS files?▼

Yes, the standards explicitly apply when generating or editing TypeScript, Vue, and SCSS files. The naming, comment, spacing, and change-discipline rules are language-agnostic within that scope.

When should I extract duplicated code into a shared function?▼

Treat two occurrences as a signal to assess drift risk, not an automatic extraction trigger. Consolidate by the third occurrence, or earlier when the copies are likely to diverge and cause maintenance problems.