orlando-japan/claude-code-setting
Skill Claude CodeCodex
Solve exactly what was asked with the minimum code. Invoke when tempted to add abstractions, helpers, flags, or handling for hypothetical future cases.
orlando-japan/claude-code-setting
Skill Claude CodeCodex
Write a spec that a different engineer could implement without asking questions. Invoke when starting a new feature, especially one that will be handed off or implemented later.
orlando-japan/claude-code-setting
Skill Claude CodeCodex
Edit only the minimum lines needed. Leave unrelated code alone even if you'd write it differently. Invoke for any bug fix or small feature where scope discipline matters.
orlando-japan/claude-code-setting
Skill Claude CodeCodex
Structured approach to designing a non-trivial system. Invoke when scoping a new service, feature, or subsystem before implementation.
orlando-japan/claude-code-setting
Skill Claude CodeCodex
Work through an approved task list without drifting off-scope. Invoke during /spec:apply or any structured implementation where tasks are pre-defined.
orlando-japan/claude-code-setting
Skill Claude CodeCodex
Red → green → refactor discipline. Invoke when requirements are clear, the interface is small, or when fixing a bug that needs a reproduction.
orlando-japan/claude-code-setting
Skill Claude CodeCodex
Before writing code, surface load-bearing assumptions and verify or ask about each one. Invoke when starting any non-trivial task to avoid building on wrong guesses.
orlando-japan/claude-code-setting
Skill Claude CodeCodex
Add distributed tracing to a service so you can follow a request across service boundaries. Invoke when debugging cross-service latency or setting up observability from scratch.