architect

Enforce TypeScript safety and modular architecture for the Knock-Knock project.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/Stonek79/knock-knock --skill architect-stonek79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Stonek79/knock-knock/tree/main/.agent/skills/architect
Command: npx skills add https://github.com/Stonek79/knock-knock --skill architect-stonek79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Эксперт по чистому коду, TypeScript и архитектуре проекта Knock-Knock. Этот навык помогает вести рефакторинг, создавать новые модули и обеспечивать модульную, тестируемую архитектуру, сохраняя ясность и качество кода.

Core Features & Use Cases

  • Обеспечивает отсутствие any, применение строгих типов и использование Generics для повторного использования кода.
  • Применение подхода Feature-Sliced Design: разделение бизнес-логики и слоёв инфраструктуры, разделение состояний клиента и сервера.
  • Руководство по реализации безопасных API и верификации через Zod v4, а также принципы чистого кода и linting для проекта Knock-Knock.

Quick Start

Используйте архитектурный навык при аудите кода или рефакторинге модуля, чтобы обеспечить соответствие стандартам проекта.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I enforce strict TypeScript architecture and prevent any usage during refactoring?

To enforce strict TypeScript architecture during refactoring, this skill prohibits any usage, mandates type-safe patterns with Generics, and applies Zod-based validation to maintain scalable, modular design across frontend and backend.

What is the best way to structure a scalable TypeScript project using Feature-Sliced Design?

Feature-Sliced Design structures scalable TypeScript projects by separating business logic from infrastructure layers and dividing client and server states, ensuring modular boundaries and separation of concerns for maintainable code.

How do I implement type-safe API validation with Zod in a TypeScript project?

Type-safe API validation with Zod is implemented by enforcing strict schema definitions that replace any types, ensuring runtime data verification and consistent type safety across module boundaries.

Can I use this architecture skill for both frontend and backend module creation?

Yes, this architecture skill applies to both frontend and backend module creation, enforcing consistent linting guardrails, separation of concerns, and modular architecture to ensure scalable and maintainable design.

Why does my TypeScript refactoring break modular boundaries and separation of concerns?

TypeScript refactoring breaks modular boundaries when business logic mixes with infrastructure layers, which this skill prevents by enforcing Feature-Sliced Design, strict type safety, and consistent architectural guardrails.