What problem does it solve? Adding a command or screen to the FoolProof Telegram bot requires touching many conventions at once — folder layering, the feature contract, import aliases, lint zones, and test placement — and missing any one of them silently breaks the rule that a feature folder must be deletable without breaking the build. ## Core Features & Use Cases - Feature folder scaffolding: Defines the layered structure (domain, render, bot, samples) with downward-only imports and a composition-root entry point. - Feature contract guidance: Specifies how commands, listeners, resume, and stop hooks are declared so the installer registers them safely and no handler swallows another feature's input. - Lint zone verification: Requires proving each new ESLint zone actually fails on a deliberate violation, covering flat-config replacement, minimatch comment pitfalls, and dynamic-import blind spots. - Use Case: When adding a new bot command like a player statistics screen, follow this Skill to create the folder, declare it in package.json and main.ts, fence it with lint zones, and wire tests and copy correctly. ## Quick Start Ask the AI to add a new feature folder for a new bot command following the add-a-feature conventions before writing any implementation code.
