Write minimum necessary code following YAGNI principle to prevent bloat and over-engineering. Use when implementing features to keep the codebase lean and avoid premature optimization or speculative features.
Writes minimal, necessary code following YAGNI principle to prevent bloat. Triggers when implementing features to avoid premature optimization and over-engineering.
/plugin marketplace add binee108/nine-step-workflow-plugin/plugin install nine-step-workflow@lilylab-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Implement what's needed NOW, not what MIGHT be needed.
Avoid:
You Aren't Gonna Need It
# ❌ Over-engineered
class ValidatorFactory:
def create(self, type):
if type == 'basic': return BasicValidator()
elif type == 'advanced': return AdvancedValidator()
# 10 more types... (only use BasicValidator!)
# ✅ Minimal
class EntityValidator:
def validate(self, entity):
return entity.required_field is not None
// ❌ Over-engineered
class ValidatorFactory {
create(type) {
if (type === 'basic') return new BasicValidator();
else if (type === 'advanced') return new AdvancedValidator();
// 10 more types... (only use BasicValidator!)
}
}
// ✅ Minimal
class EntityValidator {
validate(entity) {
return entity.requiredField !== null && entity.requiredField !== undefined;
}
}
// ❌ Over-engineered
type ValidatorFactory struct{}
func (f *ValidatorFactory) Create(validatorType string) Validator {
switch validatorType {
case "basic":
return &BasicValidator{}
case "advanced":
return &AdvancedValidator{}
// 10 more types... (only use BasicValidator!)
}
return nil
}
// ✅ Minimal
type EntityValidator struct{}
func (v *EntityValidator) Validate(entity *Entity) bool {
return entity.RequiredField != ""
}
Do: Solve current requirements simply Don't: Add "maybe later" features
For detailed patterns, see reference.md For more examples, see examples.md
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.