Imported from YOGESHS347/ARCHITECT (
.agents/AGENTS.md). Install upstream withnpx skills add YOGESHS347/ARCHITECT --skill .agents. Copyright stays with the author.
Workspace Rules
Real Developer Refactoring Standard
When resolving linter errors, type-check failures, or bugs, do not use superficial "band-aid" fixes (e.g., casting to any/unknown, using ts-ignore, or mildly altering mutable state). Instead, act as a senior software engineer:
- Strict Typing: Always trace and import the exact domain models (interfaces/types) rather than using generic objects or
Recordtypes. - Structural Integrity: If a function relies on complex mutable state (
letvariables reassigned in massiveif/elseblocks), refactor the logic. Use helper functions, pure functions, or Immediately Invoked Function Expressions (IIFEs) to returnconstobjects. - Declarative over Imperative: Prioritize declarative patterns. If you touch a piece of code to fix a bug, leave the surrounding function cleaner and more robust than you found it.
