skills.rest
epam
epamOFFICIAL
Explore all skills by this author →
Website𝕏@EPAMSYSTEMSGitHub

dial-development

Standardize coding conventions for ai-dial-chat components, hooks, and store code.

503|60|Updated Sep 7, 2023
Search Tags:#frontend#best-practices#lint#redux#coding-conventions#type-check#dial-development
One-click install
npx skills add https://github.com/epam/ai-dial-chat --skill dial-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dial-development
Source: https://github.com/epam/ai-dial-chat/tree/main/.claude/skills/dial-development
Command: npx skills add https://github.com/epam/ai-dial-chat --skill dial-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes coding conventions and development practices for ai-dial-chat to ensure consistency across components, hooks, and store code.

Core Features & Use Cases

  • Naming & file patterns: PascalCase components, kebab-case files, and consistent export patterns.
  • Code organization: Recommended import order, Redux epic patterns, and React FC usage.
  • Quality gates: Lint/format/typecheck commands, and a clear pre-PR checklist.

Quick Start

Consult the development-practices guide at .claude/guides/development-practices.md and apply the conventions when writing components, hooks, or store code.

Frequently Asked Questions about dial-development

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

FAQPage Schema
What coding conventions should I follow for ai-dial-chat frontend development?▼

Frontend coding conventions for ai-dial-chat require PascalCase for React components, kebab-case for file names, and consistent export patterns to ensure standardization across components, hooks, and store code.

How do I structure Redux epics and React hooks for ai-dial-chat?▼

Structure Redux epics and React hooks using recommended import order, React FC usage, and specific store code patterns defined in the development-practices guide to maintain consistent code organization.

What lint, format, and typecheck commands are required before submitting a PR?▼

Run the lint, format, and typecheck commands specified in the development-practices guide, then complete the pre-PR checklist to verify naming, imports, and types meet ai-dial-chat coding conventions.

Can I use this Skill to update existing UI components and reducers, or is it only for new code?▼

This Skill applies to both creating and updating UI components, hooks, reducers, and PRs, ensuring existing code adheres to current naming, import, type, and Redux conventions during modifications.

Why does my ai-dial-chat component fail the pre-PR checklist?▼

Components fail the pre-PR checklist when they violate coding conventions such as incorrect file naming, improper import order, missing type definitions, or non-standard React FC and Redux epic patterns.

Related Skills

Explore More Software Engineering Skills→
cdrgurucdrguru
1

gemini-cli-init

Initialize Gemini CLI configuration and auditor persona for the PACK workflow.

Community
Intermediate
nanokajsnanokajs

ship-pr

Run format, lint, typecheck, and test checks before creating a pull request.

Official
Intermediate
rsnormanrsnorman

quality-check

Run ESLint, Prettier, and TypeScript type checks on code.

Community
Intermediate
peopledearpeopledear
1

Frontend Components

Enforce frontend component coding standards in Claude Code workflows.

Official
Basic