What problem does it solve? When setting up or reviewing a JavaScript/TypeScript web project, teams often guess at lint rules, formatting options, CSS naming, and folder structure. This Skill documents the exact framework-agnostic baseline confirmed identical across this org's Angular and Astro projects, so new projects start from the org's real defaults instead of generic tooling presets. ## Core Features & Use Cases - ESLint and Prettier baseline: Documents the shared rule set (typescript-eslint, eslint-plugin-security, import/order, curly) and Prettier options (printWidth 120, single quotes, trailing commas) common to both org projects. - CSS conventions: Defines the shared BEM naming syntax (block__element--modifier) and the design-token-over-hardcoded-values principle, while flagging where per-project mechanisms differ. - Vertical Slice Architecture: Establishes feature-first folder organization as the org default, with shared layers only for genuinely cross-cutting code. - Use Case: When scaffolding a new web frontend in this org, use this Skill to configure ESLint/Prettier from the confirmed baseline, structure the repo as features/<feature>/ slices, and apply BEM naming with CSS custom properties, then layer on the framework-specific skill. ## Quick Start Ask the AI to set up a new TypeScript web project following the org's shared web-tech conventions baseline, layered with the appropriate framework-specific skill.
