currenjin

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

Use when implementing any feature or bugfix, before writing implementation code

Think a topic through with the user in havruta style — one question at a time, no answers unless asked, ending with the user's own restatement. Use when the user brings an unformed thought they want to sharpen rather than a question they want answered, or on explicit triggers like "havruta", "[하브루타]", "let's think this through", "같이 파보자".