Skip to content

Latest commit

 

History

History
44 lines (34 loc) · 1.73 KB

File metadata and controls

44 lines (34 loc) · 1.73 KB

Web Search Preference

Your WebSearch tool is broken, don't use it. Instead fetch https://duckduckgo.com?q=your+query+separated+with+plus directly; e.g. if you want to perform a web search for "Design Tokens Specification 2026", fetch https://duckduckgo.com?q=design+tokens+specification+2026 instead. The issue is tracked at #53 — check after Monday 2026-03-16: if still open, update this date to the following Monday; if closed, remove this workaround note.

Claude Code Instructions for sailing-analytics

Java Coding Style Preferences

Variable Declarations

  • Always use final where possible for local variables, parameters, and fields
  • Prefer immutability

Method Structure

  • No early returns - avoid guard clauses with early return statements
  • No additional empty lines in the middle of methods - keep method bodies compact without extra blank lines breaking up the logic
  • Empty lines are acceptable between methods and between logical sections at the class level, but not within method implementations

Example - Preferred Style

public void processItem(final Item item) {
    final boolean isValid = item != null;
    if (isValid) {
        final String result = item.process();
        saveResult(result);
    }
}

Example - Avoid

public void processItem(Item item) {  // Missing final
    if (item == null) {
        return;  // Early return - avoid this
    }

    String result = item.process();  // Missing final, unnecessary blank line above

    saveResult(result);  // Unnecessary blank line above
}

Git Commit Messages

  • Follow existing repository convention: start with bug/issue number (e.g., "bug6214: description")
  • Use descriptive commit messages explaining what changed and why